REDCINE to FCP and back

[Howard Buksbaum]

Hey there,

I'm trying to work with Epic footage in FCP7 and since it can't use the R3D files I'm creating proxies inside Redcine. Normally when I go through this process I just export the entire R3D using proxy 1/2 setting. I bring the proxies into FCP, edit and export my sequence as FCP XML. I then import the FCP XML into Redcine which links back to the original R3Ds. Then I can apply an initial grade, export as PRORES 4444 and render out high res quicktimes. Export the timeline for FCP. Open it in FCP and finish the project in Color.

Everything works fine.

This time I tried setting an in and an out in Redcine, prior to creating the proxy files so I can save space. Although I end up with trimmed proxies that I can work with in FCP, when it comes time to bump up and apply an initial grade back in Redcine, it appears that the FCP XML in and out points are relative to the beginning of the trimmed clips. So if my in-point in FCP is 15 seconds into the clip, back in Redcine the 15 second offset is applied from the begging of the original R3D and not from the in-point of the R3D. So it should really be the R3D in-point + 15 seconds.

Is there a setting I'm missing or something I may not be doing?

What's interesting is that I have the RMD fils set to generate automatically so that when I check the RMD for my R3Ds, the correct in and out points are set. You'd think that there would be a setting in Redcine so that it considers the in-point of the RMD then applies the in-point from the imported FCP XML on top of that. Either that or some way to export absolute in and out points in FCP XML.

Thanks,
Howie

 

[Grant Yoshida]

In REDCINE-X PRO, there's a facility for handling this but only if you generate an FCP XML when exporting your timeline from REDCINE-X, and import that XML into FCP.
Some extra data is inserted into the XML so that when you roundtrip back to REDCINE-X it knows how to offset the in and out points.

We're looking at making this easier and more seamless to do.

 

[Grant Yoshida]

Howard, the next release of REDCINE-X PRO, Build 11, will handle this case properly without having to initially generate an XML from REDCINE-X as I described.
The timecode field in the XML is used to offset the in and out points.

 

[Howard Buksbaum]

In REDCINE-X PRO, there's a facility for handling this but only if you generate an FCP XML when exporting your timeline from REDCINE-X, and import that XML into FCP.
Some extra data is inserted into the XML so that when you roundtrip back to REDCINE-X it knows how to offset the in and out points.

We're looking at making this easier and more seamless to do.

Sounds good - When you say "export your timeline," what if I'm just trimming my clips in a bin? I don't create a timeline? Do I have to throw all my trimmed clips on a timeline, export my timeline as individual clips then import the timeline into FCP?

Howie

 

[Grant Yoshida]

Sounds good - When you say "export your timeline," what if I'm just trimming my clips in a bin? I don't create a timeline? Do I have to throw all my trimmed clips on a timeline, export my timeline as individual clips then import the timeline into FCP?

Howie

It's not strictly limited to timelines -- if you're exporting a bin, you can use the "Project" export option and an FCP XML will be generated if it's enabled in the export preset.

Note that Build 11, when it comes out, will make things much easier since you don't need to worry about details like this, it should just work.