the mising link for me in red workflow

[nanuk]

hi there,

perhaps it is a stupid question:

when i follow a the workflow scenarios i always stumble over one question. whren i export an edl from final cut which has the ref qt in how do i get back to the original .r3d file to conform that in scratch or speed grade? is the missing link crimson?

thx nanuk

[Anonymous]

@nanuk 26034 wrote:

hi there,

perhaps it is a stupid question:

when i follow a the workflow scenarios i always stumble over one question. whren i export an edl from final cut which has the ref qt in how do i get back to the original .r3d file to chnform that in scratch or speed grade? is the missing link crimson?

thx nanuk

Yes either Crimson or similar

Cut your Proxies in Final Cut.
Export an XML.
Convert the XML with crimsonworkflow.
Import all the R3D Files you used in your Final Cut Sequenz in Redcine ( Load ALL ).
Then load your converted XML File in Redcine.

there are a few workflows – but yes you do need something to allow a link back to the .R3Ds

mike

[summerJ]

thanks alot mike!!!

nanuk

[Anonymous]

@mseymour7 26035 wrote:

Yes either Crimson or similar

Cut your Proxies in Final Cut.
Export an XML.
Convert the XML with crimsonworkflow.
Import all the R3D Files you used in your Final Cut Sequenz in Redcine ( Load ALL ).
Then load your converted XML File in Redcine.

there are a few workflows – but yes you do need something to allow a link back to the .R3Ds

mike

We have a problem here where the crimsonworkflow changes the file name, adding an event prefix Z00001_origfilename, Z000002_origfilename, etc. It has something to do with the python format file name specifier, though we can’t find any additional info at the moment because the crimson site help link is broken. The result is that the xml doesn’t recognise the dpx so we can’t relink the media automatically, and have to recreate the edit by hand.

Marcus, Molinare Barcelona

[bnw]

Ouch! You should be able to use find/replace in a decent text editor to remove those extra bits from the XML. Or if you know a UNIX guru you can do that with a shell script.

Lewis, Molinare London 🙂

[Anonymous]

Yes, a shell script. That’s what we reckon on doing today.
Thanks for the reply, Lewis.

Marcus, Molinare BCN.

UPDATE: We’re trying out a new thing. Our editors in FCP/Crimson/RedCine, have “Cowboy Intermediates” selected in Crimson. This causes the name change but they need this to get a correct view of their edit in RedCine. Changing this to “No Intermediates”, stops the name change and we can output the DPX’s from Crimson Redline. Testing it now.

Marcus

[Anonymous]

I have an added question here. Trying to get a Flame, or rather wiretap central to pick up an XML out of FCP to see Red files, instead of the quicktime transcoded pro res used in the Edit.

I am still having trouble with making the XML point to the native R3d files so that i can convert them and import them into flame. I want to bypass using redcine.

Has someone here tried this successfully?

Thanks
Theo

[Kaustubh Satam]

Yes, it works. There are actually several adsk scripts that ship with WTC that will “clean” up a XMl or EDL into a more WTC friendly format. Relinks back to the sources just fine on our end.

Good luck,

MrJ

[Anonymous]

MrJ,
Do you mean, you dont have to import all your sources first to relink? I want to ONLY bring in what is needed via wiretap and an XML, not bring in all my sources and then relink the XML.

If so, then great! thats what i need, what shall i tell my administrators to look for, when you say scripts for WTC?

Thanks again

[Kaustubh Satam]

No, Feed WTC the XML (after you’ve run it through the script) and it will find out all the sources for you and only debayer the needed footate. The scripts are most likely in the wiretapcentral html directotry.

Good luck!

[Kaustubh Satam]

Just checked my install. The scripts are not there, so I must have left them there from the Beta cycle. You can call support and ask them for a copy, they should be able to help you out further.

MrJ

[Anonymous]

Ok, having not found those python scripts, i havent called discreet yet but It seems the biggest problem i was having in getting Wiretap in seeing my XML properly is in the naming convention in the XML. Always have your REEL name the same as the clip name, if not then WT will not read it properly.

I went through FCP, generated an XML, conformed it using Clipfinder ( which is free).. this changes the quicktime associations into RED sources, and into wiretap. perfect

Wiretap uses the REEL name it seems to find the red files accordingly.

hope this helps others too!

[Author]

Posts