[Jeremy Garchow]

I wonder what would happen if you pulled the movs out of the card directory?

I typically generate proxies with RedCineX and can link/relink back and forth from mov to R3D very easily.

The movs are in a different directory, though, separate from R3D.

[Jeremy Garchow]

The R3D files will span no matter.

If the card was formatted fat32 the movs will span after 4Gigs. If formatted UDF, the mov will not span.

Do you get the freeze frames in RCX as well?

[Jeremy Garchow]

[Bret Williams] “What a mess.”

No doubt. There are a long list of gotchas with Red.

Again, were the proxy files made with RCX, or where they shot at the same time and recorded in camera?

Sometimes, the format of the media card in the Red can screw this process up (Fat32 vs UDF).

Usually RCX can relink to all the media, though, without the freeze frame.

Another process to try is to make a duplicate timeline in FCPX, strip out all the audio and unnecessary footage (like anything that is not Red originated) and try it on an audioless XML and see if that works.

That should get rid of your sync’d clips too.

[Jeremy Garchow]

[Bret Williams] “Nah the original proxies from the shoot were just 1080p ProResLT with embedded PCM audio.
“

I understand, but in the translation, that information somehow got changed to “wavs” instead of just linking to the audio of the Proxy movies.

I would try Resolve and see if that works. Resolve can link to the R3D too (although it’s a bit trickier) and export to FCPXML.

[Jeremy Garchow]

I see. So the audio that is now “wavs” was probably the original audio in the Proxy movies.

All the R3D project I do usually have separate, discrete audio, so I can’t say that I’ve seen this before.

Try opening the shallow XML in Resolve (if you have it) and see what the audio does.

Where were the proxies made? On the camera during recording or later?

Do you still have access to the audio in a earlier timeline? You could always detach that audio and copy/paste it in to the relinked timeline.

Jeremy

[Jeremy Garchow]

You mean the audio didn’t relink?

Was the audio on the R3D the same as the Proxies?

[Jeremy Garchow]

RCX kinda sucks with FCPXML. Actually, no, it doesn’t kinda suck, it does suck.

Export a shallow XML, and then use SendToX to translate.

Jeremy

[Jeremy Garchow]

[Jeff Kirkland] “I think what he’s after is to have the output frame size change according to the crop like it would in if you cropped an image in Photoshop – so of you started with 1920×1080 and cropped to 220×513, that’s what the output movie size would be.”

That’s what Screenflow does.

Still in FCPX this process takes a few seconds, as you know, and wouldn’t seem to impede workflow.

[Jeremy Garchow]

I’m having trouble understanding why this isn’t viable?

If you use Screenflow as your screen capture software, you can drop directly on the canvas and export.

[Jeremy Garchow]

Here’s a shot in Preview. I used the crop tool to drag and select the window. You can see the pixel size (1630×1071), then you simply set the pixel size in the Project settings in FCPX and you are done.

See here: