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 :)
No app can handle speed ramps with R3D, because R3D can only be played at normal speed.
Remove all speed ramps and then use Resolve 9 to consolidate all you red files to the folder of your choice.
Hi jake, i dont want to trim r3d. I just want to consolidate, gathering all r3d files listed in the edlor xml and copy to new location. We dont want to store 35TB of RAW into our server.
We are writing our own application for this, but not yet finish. If u know any better way of doing it, will be great.
A simple shell script (ie. one line, or drawn out a small paragraph) could parse an xml file and copy the used R3Ds and RMDs on a unix or osx system. I would start with grep, awk and sed.
Cory
We build GUI version for this task and it works wonderful, just like how i want it to be. By doing so, we only gather r3d we need from the source file without trimming and it is able to detect source file from multiple location. Progress bar still WIP, but it's workable for now. It also listed the total size in MB that we need to copy. We want to improve this for trimming r3d but more functionality, so when detecting speedramp, it is able to export the exact in and out from the xml before doing the speedramp in 100% speed. So during post conform, di system wont have any problem in conforming the speed listed in r3d. Also couple of more function. It's work in progress
But Scratch actually has to import all the source clips first which takes a very long time if you're loading all footage from a feature film shoot from FW800 and USB drives...
I've discovered EDL Spy which does the trick for me - although it doesn't do multiple disks in a single pass so you need to set it to search through each disk separately. Still way faster than doing it through Scratch though.