-
CatDV and RED Footage
-
is there a way currently to make this work with Epic R3D files without quicktime. I am working on projects with so many TBs of data that there is no way that I can generate proxy files from all the footage, Premiere Pro works fine with the original footage without transcoding but I am lookng for a better archive solution.
-
Funny you should revive this thread.
We are currently doing an implementation where we are cataloging and archiving RED EPIC footage.
As of CatDV 10.0.1, you can use an .mov or .mp4 proxy of a R3D file so if you can create a proxy, you can have CatDV show the proxy and then you can manipulate the R3D’s. We are using an outside script to drive REDLINE and batch jobs to create proxy for CatDV to use
One note, you can’t use REDLINE with Worker Node on its own due to the fact that REDLINE doesn’t have job management so if you start a job from the CLI, it just keeps stacking up jobs and doesn’t queue them to keep you processor from being swamped. However, if you just want to use REDCINE X and create proxy and put them in place manually, it works fine.
So while you can’t “read” R3D’s natively in CatDV, we certainly have a solid workflow for RED files now, in my opinion.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
At this point, what is the easiest way to bring in the Raw Red footage (which I am able to do now) Then link it to the proxies I made in Redcine that are .movs? Maybe I overlooked something, they have the same exact name and are in the proxy folder, along with all my other proxies that link up great. On a different note, the Xuggle plug-in works fantastic for our C300 and C100 footage, especially for making proxies. So kudos for that!
Hannah Vinson
DP & Whatever else needs to be done 🙂
Water Street Media Works -
Ah, here I go eating my words…
There currently are some serious issues with the RED EPIC workflow. I spoke too soon about support for this. While we have been able to design a batch system for automation of the proxy, CatDV only views the R3D files while REDCINE and REDLINE make “proxy” of the entire clip, represented by the .RDC folder.
Squarebox is taking a look at this now, but if you notice, your proxy is likely named:
clip_name.mov
While your files are:
clip_name_001.R3D
clip_name_002.R3D
clip_name_003.R3D
etc…If you have a single R3D you can automate the rename so that your proxy matches the .R3D file and CatDV 10.0.1 will link them but spanned clips would end up with a full duration proxy for each segment of the R3D and I think this is not a great idea.
Also, by “fooling” the system, we move away from actually managing the files so archiving systems would fail to operate correctly.
Can you let us know the frame size and what camera you are using?
I can get 2K files in but 4K and 5K seem to not import correctly and Squarebox support is investigating this. Can you confirm?
Sorry to speak too soon on this but I feel like there is a solution forthcoming.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
-
We are shooting with the Scarlet at 4k HD. Thinking about it now, I see that linking the proxies with the R3D files is tricky because they are broken up into smaller files. So, at this point would you suggest our work around be exporting out ProRes (with the same RED files names) and linking those to the proxies? Then, possibly in the future, we might be able to link the actual files.
Hannah Vinson
DP & Whatever else needs to be done 🙂
Water Street Media Works -
Currently, if you can use a mezzanine file, that’s the best way to tackle it.
As more software natively edits RED footage we’re hoping to see updates from Squarebox to address this. They are currently evaluating it.
bryson
bryson “at” northshoreautomation.com
northshoreautomation.com
Reply to this Discussion! Login or Sign Up