[Jeremy Garchow]

CEA 608 allows embedded the caption in to the file (closed captions).

The other formats are separate files (ITT & SRT) and do not support embedding in to the file.

You can also burn-in (open captions) all formats as well by hitting the “captions” button in the Role tab of the share window.

Should look something like this:

Jeremy

[Jeremy Garchow]

Use X2Pro and select the option to reference wav files in place, and send the resulting reference AAF and all of the original audio files to the ProTools engineer.

Any other media will be embedded, though, so if your orig audio files aren’t wavs, this won’t work, and you will need to send an embedded AAF to ProTools.

[Jeremy Garchow]

You can do srt in fcpx, just change the caption role to srt.

[Jeremy Garchow]

Try trashing your prefs.

Then change your backup location to see if that works any better.

Also, make sure all your third party plugins are up to date, if you have any.

[Jeremy Garchow]

[Joe Marler] “(matching file suffix, pixel aspect ratio, audio config and timecode”

Suffix is less important. I can link between MXF and mov or r3d and mov easily as long as the audio is the same. Even frame size doesn’t matter. If the audio channels don’t match, then fcpx simply won’t relink.

I certainly do not know the ins and outs of sql or fcpx’s internal structure. I just do what works. Fcpx’s proxy relink is way more strict than even the original media link as you mention. It’s location dependent, original relink is not. It’s definitely odd.

[Joe Marler] “If your camera-generated proxies won’t relink to the original R3D files, I don’t know why. Maybe Jeremy could advise.
“

Depending on the drive format chosen on the red (UDF or FAT32) the QuickTime movies don’t follow the same spanned format as the r3ds (or MXF) FAT32 4GB chunks of media). The camera generates proxies don’t seem to have the same metadata as the RCX generated proxies. Somehow, fcpx knows how to relink to the rcx generated proxies and the spanned r3ds but can’t do this with camera generated proxies. Again, I don’t know why this is, or how it works in fcpx, but it seems to work.

This is why, with Ref especially, I use RCX to generate ‘proxies’ before editing and are usually high quality 444 redlogfilm proxies. On quicker jobs, I’ll even send those to grade rather than go through an r3d relink and file transfer.

[Jeremy Garchow]

I usually make Proxies though RCX (making sure to keep the same audio setting as R3D), and then I import that footage in to FCPX and just use the Original media method.

Then I select the clips I want to relink on the timeline, and relink to R3D, then export.

I can then relink to the ProRes movies for editing. It’s pretty seamless.

I do not use the Proxy switch in FCPX.

[Jeremy Garchow]

You could try simply relinking to the R3D files after you import the Red created Proxy files using FCPX.

Or you could try this

Or you could send an FCPXML to Resolve or RedCineX and relink there, but those will be more difficult to do.

[Jeremy Garchow]

Unfortunately, the only way to get this done is to export a Master File from FCPX, and then set to audio pass through in Compressor (like you have found out).

If you can live with the settings from FCPX (mp4 or compressed h264 mov), then you can export directly from FCPX with the Roles you desire.

Jeremy

[Jeremy Garchow]

So you are trying to export a multichannel mp4 from fcpx to compressor and keep the roles as you have set them up. Is that right?

Why not export an mp4 straight from fcpx? Do you need specific encoding parameters for the mp4 Besides the multichannel audio?

[Jeremy Garchow]

What kind of file are you trying to compress?