Welcome to our community

Be a part of something great, join today!

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

FCP to RCX to Flame

Petros Nousias

Well-known member
Joined
Jan 4, 2007
Messages
241
Reaction score
0
Points
0
Whats the way to do it?

RCX has to transcode the timeline to DPX and then everything has to be reconnected in Flame. I guess the first part is easy since RCX can import XML or EDL, but how about the second?
 
Flame can reconnect using EDL/XML just as Smoke can. When you render DPX from Redcine-X, they will retain appropriate timecode metadata needed for the conform.

Flame 2010 and above can also import R3D natively via Gateway, apply metadata settings from camera or user custom, and transcode to Stone media. This bypasses the need for Redcine-X.

Alternatively, something I like much more, is to use Wiretap Central (part of the IFFFS/Lustre product package, already installed with Flame) to handle EDL/XML R3D transcodes to DPX. It's perfect for selectively altering metadata, while retaining camera metadata for unchanged parameters.
 
Alternatively, something I like much more, is to use Wiretap Central (part of the IFFFS/Lustre product package, already installed with Flame) to handle EDL/XML R3D transcodes to DPX.

It works identical on Smoke on a Mac too.
And, yes, no new color science yet. At least on a Mac, even with latest Smoke 2011 EXT1.
 
The op tells me that they cant reconnect for some reason. The procedure is as follows:
We shoot using TOD. Proxies are drag/dropped to FCP and edited. XML is exported to RCX and the timeline is rendered to DPX. The frame sequences and the xml are then loaded in flame using all possible combinations without success. Any ideas?
 
So, we tried to do 2 separate transcodes, one through wiretap central, the other through RCX, both from the same XML. Afterwards we loaded everything in Flame's browser, we noticed that in the DPX's metadata, we got TOD in RCX's case, and Edgecode in Wiretap's. Flame still cant relink the media from RCX whereas with wiretap there's no problem whatsoever. and I cant find any setting in RCX to change the TC from TOD to Edge in the export tab. Help?
 
As I said, I can relink with wiretap's but not RCX's. I'll switch the camera to Edgecode from now on, but I already have some footage that needs to be processed that was shot with TOD
 
So, we tried to do 2 separate transcodes, one through wiretap central, the other through RCX, both from the same XML. Afterwards we loaded everything in Flame's browser, we noticed that in the DPX's metadata, we got TOD in RCX's case, and Edgecode in Wiretap's. Flame still cant relink the media from RCX whereas with wiretap there's no problem whatsoever. and I cant find any setting in RCX to change the TC from TOD to Edge in the export tab. Help?

That's strange. Was Edgecode flagged as default on the camera? DPX frame number and metadata contain TOD on my transcodes, but I know TOD was flagged on camera side.
 
Back
Top