Having Trouble with RCX XML to FCP...

[Justin Kirchhoff]

I'm grading a feature and I haven't come across this problem, was hoping to get some help.

The movie had transcoded R1 and EPIC files to Pro_Res for the offline. I've successfully exported an XML of the cut back to RCX to do preliminary color grades.

After I graded, I selected my export back as QT ProRes HQ files, with the option to create an FCP XML and send the XML back to FCP. After the footage renders, FCP doesn't show the XML, nor does the export generate a FCP XML at all, so I'm forced to make a FCP XML in the menu.

Because of this (I think), the files don't reconnect when I import the XML I created from the file menu option. I try to reconnect the media, but it's telling me it can't.

Anyone have any ideas?

I'm thinking because RCX isn't generating a FCP XML after the QT export, it is ruining my online?

Thanks in advance.

[Jerrod Cordell]

Glad I'm not the only one. Any info on this would be awesome.

[Björn Benckert]

had the same struggle when going to flame with r3d selects then the xml coming from rcxp is... not right. it has some crazy resolution and such. luckily the flame can reformat the xml into a proper settings but its kind of a 5 step blind operation. I did not manage to figure it out myself... was ripping my hair out for three nights and then our programer figured out the path in 15minutes...

I might be completely off but it seams like the xml exported from rcxp is not in the right frame size and does not have the correct tails/head lengths so there for it's not willing to bring in the cuts properly.

I was kind of glad to see the flame getting around the problem. Nice to see that extra money actually does do difference :)

[David Ibbitson]

Bjorn,

I'd like to get some more information on what might be going on here. If you want to have your programming ping redcinex at red dot com with what he changed that would be great.

Cheers,
David

[Martin Jaeger]

Not sure about all the resolution and frame size issues out of RCXP, but we too had the problem of RCXP not generating the XML file when exporting. We discovered that it only generates an XML when the render is set to "timeline (separate clips)"

[Grant Yoshida]

RCXP will currently only generate an XML when the render target is "Timeline (separate clips)" or "Project".
Is there another target you were hoping to use?

[Björn Benckert]

Bjorn,

I'd like to get some more information on what might be going on here. If you want to have your programming ping redcinex at red dot com with what he changed that would be great.

Cheers,
David

what we do is this.
In flame we import the XML through the "flame gateway"
then we "consolidate" it to less tails and heads than what we exported in red cine. (we export r3d selected takes)
Then we reformat the xml to the same format as the R3D files (or DPX files if used) this is important since an XML sadly holds count for size and a lot of other stuff that I find irrelevant at the conforming stage. In flame I copy size and all else from a source clip and paste it onto my XLM.
So for example we shot anamorphic and got DPX in 1920x786, then the XML needs to be that size.

When the XML has the right format and is located in the same flame reel as the xml i tell the flame to "relink from real" before I do that I need to make sure (if using r3D that they are set to "full debarring etc" then I get all the source linked into the xml. when relinking it's important to have "look at, timecode, tape, file name etc set to on" or it will just take the first take from the reel.

As I understand FCP does not have any of the above. I would be suprized if anyone could jump in and out of RCXP and back to final cut with a timeline filled with EFX, time warps, pan in scans etc. and have no errors. I can frankly not see it happen at all, or?

Flame does it quite properly but there is always some errors like double frames when going from time warp to reg speed or issues with reverse shots etc but that's pure bad FCP stuff when post X FCP comes they might solve some of that. but the edl/xml handling from FCP is not a straight thing it's a hack half working procedure.. as I see it.

/b