Problem! Export error in Final Cut Pro 11 and Compressor 4.9 . H265 black screen

Question

vistvo Author

Level 1

8 points

Problem! Export error in Final Cut Pro 11 and Compressor 4.9 . H265 black screen

Hello,

I'm really need help! After update to mac os 15.1.1 and Final cut pro 11, i cant to export my project.

Having h265 files in multicam project. The export is simply canceled in FCP 11 and Compressor show error reading files.

I often see a black screen while playing video in FCP 11.

I've tried doing the project again in fcpx 10.8.1 but I see the same problems.

And i dont have a lot of free storage to make Optimazed media, because it really too heavy. It's need more then 1Tb free storage.

macbook air m1, mac os 15.1.1 , fcp 11 .

This is really, really bad. My work is not getting done because of this error. I really regret to upgrade my operating system because of the new fcp11. This is not a professional program, there are more bugs than before.

Now im already thinking about to learn to work on other software and switch to Davinci Resolve Studio, at least they fix bugs very quickly.

I am very disappointed, this is a big problem!

Can anyone help me?

MacBook Air 13″

Posted on Dec 4, 2024 7:49 AM

Reply

Answer 1

Top-ranking reply

vistvo Author

Level 1

8 points

Dec 5, 2024 2:35 AM in response to terryb

When playing the video in FCP11, I see a black screen for a split second at 00:00:51:07.

When I watch the same video as a QuickTime file, I don't see a black screen.

What I have tried, but it doesn't solve the problem:

1) Delete the black screen fragment from the project. But then there are many other errors in rendering because of the black screen.

2) Create a new media library in the previous version of FCPX 10.8.1.

3) Render in earlier versions of Compressor

This partially solved the problem:

1) Send the render to Davinci Resolve using the XML file export. But some effects are not supported.

2) Create optimized media in Final Cut Pro. This completely solved the black screen problem and rendering now runs successfully without errors. But it took an additional 1.4TB of disk space and several hours to create.

This proves once again that Final Cut desperately needs a new release that fixes these h265 issues. And other issues, most notably the black screen in the multicam clip with the Ken Burns effect. This bug has been bothering me when editing videos for about a year now and no one is fixing it. About this bug I will create a separate message with a screenshot, to tolerate and wait for a fix is no longer strong.

With every new update of Final Cut (not Pro anymore) I hope that old bugs will be fixed, but the developers don't care.

Because of all the bugs in Final Cut, the only solution I can see for myself today is to gradually switch to editing in Davinci Resolve.

It may be less comfortable, more cumbersome, but the main thing is that they listen to user feedback and fix bugs very, very quickly.

I've been editing professionally in Final Cut Pro X for over 10 years, but my patience is running out.

Thx

Reply

Answer 2

joema

Level 4

1,197 points

Dec 7, 2024 6:54 AM in response to vistvo

Is it correct this is not a new problem but you've been having it for a year? Does it only happen in a multicam or also if exporting a single H.265 camera clip? Can you please tell us the details of the H.265 material? What make and model of camera, what frame rate, etc. These problems are often specific to variants of certain codecs. If you could use the third-party MediaInfo or Invisor utilities to obtain and post the metadata for the cameras producing H.265 (HEVC), that would help.

Does the failure only happen (or mainly happen) during export? What exact export format are you using? Is it H.264, H.265 (HEVC), 8-bit, 10-bit, 4:2:0 or 4:2:2?

It appears you have a six-camera multicam of about 6 minutes duration, is that right? Are all the cameras and codecs the same? This is running on an M1 MacBook Air? I just want to confirm the basic details.

Your screen cap shows error -17694. That is defined in VTErrors.h as kVTVideoDecoderReferenceMissingErr. It can mean the video decoder is missing a necessary reference frame required for decoding a frame during the export process.

It is common in these cases to see varying behavior between different media players and NLEs, since they may handle minor corruptions differently, attempt to skip problematic frames, or use other error concealment techniques.

Reply

Answer 3

terryb

Level 4

3,394 points

Dec 4, 2024 4:55 PM in response to vistvo

What's happening at 00:00:51:07? If it's an effect you could try deleting it and reapplying. If that doesn't work, delete the cache (select the library, choose File->Delete generated library files, and choose everything). If that doesn't work, paste a report from https://etrecheck.com into your reply using the "Additional text" button below so we can see if there's something going on with your system.

Reply

Answer 4

terryb

Level 4

3,394 points

Dec 5, 2024 3:43 PM in response to vistvo

I have to strongly disagree with your statement that the FCP developers don't care. I met them at the FCP Creative Summit last month and they are actively trying to balance new feature development and bug fixes. As Joema said on another thread, if they can't reproduce the problem, they can't fix it. Your best bet is to provide them as much data as possible about the problem using the Feedback menu item in FCP. They stated multiple times they do read everything that comes in.

If you'd like the hivemine here to see if there's something amiss with your system, post an https://etrecheck.com report as I requested.

There are many here that also use DVR and they might chime in with its pros and cons.

Reply

Problem! Export error in Final Cut Pro 11 and Compressor 4.9 . H265 black screen

Similar questions