Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Flat ProRes Transcode ?

transcode to Prores - why?

transcode to Prores - why?

That strikes me as not a good idea at all - 1080p ProResHQ is ballpark of the same size as 4K Redcode, but you lose resolution, dynamic range, RAW flexibility, etc.

why not just archive the source R3Ds?

You want viewable proxies, by all means convert it!
 
I'm with Mike on this one. Just get a bigger hard drive and archive the R3Ds...then you'll have them and won't have to worry...which will be very groovy.
Peace,

-Harry
 
Zak, Mike made a really good point. 1080P ProRes and RAW R3D files are about the same size. The RAW R3D files really do give you the best compression to quality ratio you're going to get. I can't think of anything that will offer you a smaller file size for archive without a HUGE compromise on quality.
 
Shows just how amazing the wavelet CODEC really is. The point being made here is that the R3Ds are the smallest file size of anything worth saving in.

In other words, just copy your R3Ds to another drive and keep them offsite.

Alternatively, use Red Rocket to do a realtime dump to HD-CAM and keep them on tape!

Be cheaper and more powerful to keep them on drives. Tapestock alone will cost more than that.
 
zak forrest said:
would doing a good one light color grade in RED Rocket™ and then doing NON HQ pro res be a good solution for this? i was never really well educated on the differences between HQ and regular pro res...
Click to expand...

I wanna say NON HQ Prores is about a third smaller that HQ, and of course WAY lower quality than your.r3ds . If you can, your really best of just saving the r3ds.
 
Fully agree with the consensus. Due to the modest storage requirements of the RedCode masters its difficult to make the argument that transcoding to another format is worth doing.

Plus, at this point, the newest iterations of FCP and Apple Color will allow you to work with the native files anyway - so the only real argument for transcoding to ProRes is if you need to do real time playback from a Mac without Red Rocket. To me, this is a completely separate issue from archive and/or data security.

Cheers - #19
 
Is it feasible to add some sort of error correction/redundancy to the .r3d files?

In other words say you could process them and add maybe 10 percent to the file size but have much more robust error correction in the future if there were any bit errors on the drive.

I imagine there is some ECC in there but limited due to the need for real time processing and maybe something could be done after the fact to create a more archival copy.
 
If these R3Ds are mission critical, which I'll just go ahead and assume they are, then your best bet is to get the backup over and done with. Ideally, get them onto LTO tape now. If that's not possible due to time restraints, at least backup the circle takes. Then add the rest later. But get them onto something that is stored offsite. As you mentioned, if you have a fire or a natural disaster, having a RAID 6 won't mean much.
 
You must log in or register to reply here.
Back
Top