Welcome to our community

Be a part of something great, join today!

  • 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 :)

Red Cine X Quicktime Files

Michael Notar

Well-known member
Joined
Mar 29, 2012
Messages
765
Reaction score
0
Points
0
Location
Spokane, WA
Are the Quicktime wrapper files that Cine x generates in an instant suitable for an exported file? (instead of rendering it out). How are they different? Can a look be applied to the QT wrapper files? I have a low budget movie and lots of files to export. With moderate expectations, do you think the wrapper files would be pretty good to good (finishing in 1080p). I shot 4k.
 
Scarlet. I am not asking about using the wrapper files as proxies and doing that workflow. I am curious to know if the proxy files themselves could be used as final transcoded files out of red cine x if perfect quality was not needed. were good was acceptable.
 
Scarlet. I am not asking about using the wrapper files as proxies and doing that workflow. I am curious to know if the proxy files themselves could be used as final transcoded files out of red cine x if perfect quality was not needed. were good was acceptable.


QT wrappers cannot be used as final exports as they simply link to the .r3d files. You couldn't send someone a qt wrapper unless you sent the .r3d with it, and at that point it would not serve any purpose. The QT wrapper is really meant to let the .r3d open in software that supports QuickTime but not .r3d.

You can wrap all of your red footage and start editing, and export the "qt wrappers" that are in your timeline and the final transcode will be high quality bc you are not rendering a "QuickTime wrapper"... You are rendering the .r3d... The wrapper just let the software see it.

What software will you be cutting your movie in?
 
The Quicktime proxies are a vastly outdated workflow. There was a time that it offered an advantage when working with Red footage. But that time was brief due to the proliferation of the Rocket, decrease in price per GB of storage, and now the advancement of using GPU instead of just CPU for decoding, debayering, and decompressing.

In other words: forget that the QT wrappers exist. They are entirely useless, and will only cause you pain if you try to use them for anything. The proof is in the pudding; they're created almost instantaneously, but no one is using them for anything? The only possible reason for that is that they aren't worth the meager kilobytes they take up.

NOTE: This is in regards fo QT wrappers for .r3d files ONLY. QT wrappers can be quite useful and quite powerful for utilizing and updating TIFF or DPX sequences. But these are doing an entirely different thing behind the scenes than the .r3ds, and also would still be useless to send anyone just the wrapper without the image sequence itself.
 
Back
Top