Pulling only the R3Ds needed for a cut

[David Kruta]

Hi all,

is there an easy way to pull just the R3Ds used in an edit for transfer to another system to grade? For example, I shot a film that generated hundreds of clips - about 12tb of data. But I want to get a drive together of just the R3Ds used in the EDL/XML so that I can go grade it on a different station without lugging 12tb of drives around. Any ideas?

[Steve Sherrick]

David, try Clipfinder. It allows you to import clips from an XML or EDL from FCP or Avid, and then copy those clips to a drive. I have not tested this with Epic clips however, so can't say it will work for sure.

[Paul Russell]

have you tried importing the EDL into RedCine X and then exporting the timelines as R3Dtrim?

[Steve Sherrick]

Paul's method is actually good as well. I confirmed the Clipfinder method still works with Epic R3D.

Clipfinder method

- Edit with ProRes or DNXHD. Export XML
- Import XML into Clipfinder. You'll have a list of ProRes or DNxHD clips.
- Highlight clips and choose Replace MOV with R3D
- Highlight all clips and hit CMD-C
- Paste into new directory you have created. All of the R3Ds from the edit will be copied to this new directory.

Redcine-X method

- Import XML (it will ask you to choose where the original R3Ds are)
- a new sequence/timeline will appear in your redcine-x project
- Export using R3D trim (make sure to choose your directory and other settings such as RMD
- Files are copied into your new directory. They are placed in the same folder structure. The clipfinder method will place all the R3Ds into one folder.

Let us know how it works out as you have a lot of clips and it will be interesting to see how well it works.

[Björn Benckert]

XML and r3d trim in RCXP is a nice way to extract what's wanted with a bit of heads / tails.
We usually do that for every job and make a nice scene folder with 5-10 frames handles and then reformat the XML to look for that material in the flame etc.

Then you can leave the other source drives alone and work only with the "selects". It keeps the server nice and clean and ease the workflow for CG and 3D ect.

[David Kruta]

You guys are the best. Working on it this week hopefully so I'll report back!

[Gunleik Groven]

Hm... I have been a bit sceptical to trimmed r3d's, but haven't tested them in a while either. Are they solid nowadays?

If so: Great stuff!

[Nick Shaw]

Hm... I have been a bit sceptical to trimmed r3d's, but haven't tested them in a while either. Are they solid nowadays?

If so: Great stuff!

You need to test that trimming R3Ds will not cause issues with whatever system you are conforming in.

Because an edit which contains two sub-clips from the same R3D will produce trimmed media with two instances of the same file name (although they will be in differently named folders and have different timecode) this can cause problems with conform on some systems.

If in doubt I would recommend copying the whole of the required R3D files without trimming.

[Gunleik Groven]

Thanks Nick, that's what I've done without issues...

[John Marchant]

There is also sometimes an issue taking trimmed R3Ds back into RCX-Pro, where an out point gets re-applied to the now shortened clip, resulting in RCX only using a portion of the chosen clip. It can be easily retrieved by deleting the outpoint, but can throw you if you're working on a bin of trimmed clips rather than a timeline from xml.