Redcine-X Build 351 XML Glitch

[Julio Quintana]

Hey guys. I already emailed Jonathan B. about this, but just thought I would post here in case anyone else runs into it. We edited a music video using the M camera proxies and exported an XML. We then imported it into a Redcine-X timeline (which is freaking awesome, especially with the Red Rocket). We did our color correction, then exported the whole timeline as a long 1080p ProRes HQ file. When we brought it back into FCP to sync it up with the sound, the new color corrected clip was actually longer than the original edit that we exported out of FCP. We thought at first it was a frame rate issue, but both the original FCP project and the Redcine project are 23.98.*When we looked closely we found that every shot in the entire project had been extended by exactly one frame. As in Redcine added one frame to every shot in the project, throwing everything out of sync.

It was only a five minute video, so it was just easier to manually remove the extra frames, but I'd like to know if I'm doing something wrong for future reference.

Julio

 

[Tunji Ladoja]

Hi Julio,

Just out of curiousity, did you import and export the xml directly into redcine-x or did you use clipfinder or the LUA script

Thanks

Tunji

 

[David Ibbitson]

Thanks for the heads up. There was an off by one bug. It has been fixed for the next release.

 

[Julio Quintana]

Hi Julio,

Just out of curiousity, did you import and export the xml directly into redcine-x or did you use clipfinder or the LUA script

Thanks

Tunji

I exported the XML straight from FCP and imported it right into Redcine-X. It really is an awesome workflow if you have a Red Rocket. I'm glad to hear the glitch has already been addressed.

 

[Kevin Wild]

Yes, found and posted that in the other post introducing the build. Glad I wasn't going crazy.

 

[Peter Savage]

I'm having a problem with creating new QT wrappers. The files are generated but they are just a green screen for the duration of the clip. exporting a QT file (Pro Res) file seems to be OK.

 

[Peter Savage]

ok the problem seems to have gone away now - after I installed the latest OSX update which involves a restart anyway.

 

[Peter Savage]

i spoke too soon ! very weird but the next clip I tried to re-wrap gave me the green frames again

 

[Peter Savage]

wrappers are generated perfectly in 348 - is it a REDcolor2/REDgamma2 issue?

 

[Gunleik Groven]

wrappers are generated perfectly in 348 - is it a REDcolor2/REDgamma2 issue?

I think that was confirmed in the RCX thread. Makes sense as it isn't implemented in the QT codec yet...

 

[Peter Savage]

thanks, I didn't look there but it's good to know. Strange that with a computer restart the wrappers did output ok the first time. Anyway, I'm sure it will be resolved soon

 

[Luca Immesi]

Hey guys. I already emailed Jonathan B. about this, but just thought I would post here in case anyone else runs into it. We edited a music video using the M camera proxies and exported an XML. We then imported it into a Redcine-X timeline (which is freaking awesome, especially with the Red Rocket). We did our color correction, then exported the whole timeline as a long 1080p ProRes HQ file. When we brought it back into FCP to sync it up with the sound, the new color corrected clip was actually longer than the original edit that we exported out of FCP. We thought at first it was a frame rate issue, but both the original FCP project and the Redcine project are 23.98.*When we looked closely we found that every shot in the entire project had been extended by exactly one frame. As in Redcine added one frame to every shot in the project, throwing everything out of sync.

It was only a five minute video, so it was just easier to manually remove the extra frames, but I'd like to know if I'm doing something wrong for future reference.

Julio

I have a workaround for that. http://www.esperimentocinema.com/journal/2010/11/22/rcx-edl-workflow.html