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

Pulling only the R3Ds needed for a cut

David Kruta

David Kruta

Well-known member
Joined
Jun 6, 2009
Messages
262
Reaction score
0
Points
16
Location
New York and Boston
Website
www.davidkruta.com
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?
 
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'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.
 
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.
 
You guys are the best. Working on it this week hopefully so I'll report back!
 
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!
 
Gunleik Groven said:
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!
Click to expand...

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.
 
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.
 
I wonder if you could help John?

I have an XML exported from FCP 7 and imported into RCX-Pro 14. The timeline in RCX looks fine. When I export the Bin or timeline to a new directory to collect all R3D trims it does seem to generate all the R3Ds into new folders. Which is what I want to do. But before I send the R3Ds off for grading, I thought I would test re-importing the XML and connecting to the new R3Ds. A timeline does assemble but with many of the clips missing, just appearing as black segments on the timeline? Any ideas?
 
Ricky,

Are you setting handles? There is a bug in the current release with this scenario. I've fixed it for the next release.

Cheers,
David
 
Hi David

Yes, I think handles are selected. I will try without when I'm back at my suite tomorrow. As a test I tried importing to Resolve Lite (although that's not my target App) and all the import errors seemed to be on R3Ds that were used more that once on the timeline and had subsequently been put in folders ending in S001, S002 etc So I was going to try manually putting the original R3D file directory without trimming to replace any R3Ds that have sub folders. The error in Resolve was a TC one.

Thanks
 
Hi David

I tried without handles - same result. I have manually sourced the R3D's that are being split into sub directories and copied them across to the folder with the rest of the R3D trims. I'll let you know if that works.

Ricky
 
So I tried the manual route. Then imported the XML - same problem on the timeline with blacked out clips. After re-starting RCX-Pro14 I selected all clips on the timeline and selected 'Reconnect' which I did to the new R3D trims and the whole R3Ds that were previously in sub directories. The timeline looked great - thumbnails included. But when I play back the timeline the shot in the viewer does not match the timeline?? and seems to ignore any in or out point. Even when the scrubbing line crosses an edit the shot doesn't change? but the timeline looks perfect. The RAID where the original R3Ds are storage is disconnected so the R3Ds in the timeline must be coming from the new trims?
 
You must log in or register to reply here.
Back
Top