Red missing title frames after sending project from FCPX

Question

Level 1

21 points

Red missing title frames after sending project from FCPX

Hi!

I am on a MacBook Pro M2 max with the lates MacOS and application updates. I have not installed new plugins since last time this workflow worked (I have used these titles before without problems).

Yesterday I sent a fully functioning (without any red frames) project with several third party titles from FCPX to Compressor via the "send to Compressor" option under the File menu. In Compressor, i see that the playback monitor shows red "missing title" (big letter T) wherever I have placed these third party titles. Exporting also gives me these red frames.

In the timeline in FCPx there are no red frames and all plugins/titles show normally. It does not matter if I "render all" in the timeline before sending to Compressor. I have exported Compressor presets to FCPX and using these presets when exporting the project in FCPX works fine. Also rendering a master file which is imported to Compressor works fine.

I have enabled access for Compressor to all harddisk files.

Please help! :)

MacBook Pro 16″, macOS 15.1

Posted on Nov 22, 2024 7:42 AM

Reply

Answer 1

Nov 22, 2024 8:42 AM in response to Anterialis

I don't know what to say except that I never found any advantages with Send to Compressor.

I find that it is slower than either of the alternatives - Export with Compressor Settings, or just the regular Export File from FCP.

It seems that you are not alone with this problem. There may be bugs in FCP 11 and/or Compressor 4.9 that cause Send to Compressor to not work reliably.

Reply

Answer 2

Anterialis Author

Level 1

21 points

Nov 23, 2024 12:40 AM in response to Luis Sequeira1

Thank you for your response. I've heard this several times (so I believe it to be true), so I guess it is time to change up my workflow. I guess I could make the presets in Compressor and place them in "my places" in FCPx, thereby using those presets I've made inside FCPx, never having to send anything to Compressor.

I do however like the flexibility Compressor gives me. For instance if I know I have to make a short video file less than 100 MB/s, I find it easier to change the bitrate in Compressor and immediately see the file size change... Things like that.

Other opinions or solutions to my initial problem? Thank you!

Reply

Answer 3

Anterialis Author

Level 1

21 points

Nov 23, 2024 2:48 AM in response to Luis Sequeira1

Yes, good workaround. Does this make the final result worse? Or is this basically what is already happening with "send to compressor", that FCPx renders a master file (prores 422) and sends it to Compressor? I just never liked exporting it "twice" from the original content from the camera. I imagine the quality dropping for every export process.. I might be wrong..?

Reply

Answer 4

Nov 23, 2024 2:50 AM in response to Anterialis

It is unlikely that you'll notice any difference in the final output.

I don't know exactly how it works, but I think that with "Send to Compressor", Compressor has access to the actual FCP project, and not just a rendered version. That is why there are limitations with it that are stricter than when Compressor gets a video file.

Reply

Answer 5

Nov 23, 2024 1:35 AM in response to Anterialis

You could as a workaround export a master file from FCP and then bring that to Compressor to create custom versions.

Reply

Answer 6

Anterialis Author

Level 1

21 points

Nov 24, 2024 2:26 AM in response to Luis Sequeira1

Yes, I guess this workaround is the best option. Export a master file (prores 422) which I can open and compress in Compressor.

Let me know if there are even better ways to do this!

Reply