Black video clips - FInal cut pro 11 problem

After many hours with Apple consultant we solved the problem, or my problem, with black clips. It's a short term solution but it worked. Click on a black clip> right click and click reveal in browser> then go to the clip in the browser and right click again> click on Transcode media and choose optimised and then it takes a little while and the clip will appear. Means doing this for each and every black clip but it works. It only affected the clips that I'd shot at 120fps. Brand new projects created in V11 don't have this problem. The problem starts when you have completed or are halfway through a project while using V10.8.1 and then updated to V 11.

Same problem here that occured after updating to FC 11.0

In my case only slow motion files are missing (120fps slowed down to 30fps).

When trying to relink the files - this error pops up. As if the files have been edited, but they havent. FC 11.0 doesn't recognize the files that the previous version worked with perfectly.

I am on MBP M1 pro. Sequoia 15.1.1. Footage from Lumix GH7.

The relink error is a "red herring." Actual problem: If a library containing certain high-frame-rate clips is upgraded to FCP 11.0, those may show as black. It is only certain camera-specific codecs. Not affected: Sony XAVC-S H.264 100.0 fps and 119.98 fps, iPhone HEVC 1080p/120(30) fps slo-mo. Affected and tested: Panasonic Lumix GH6 UHD 4k, 100.0 fps, 10-bit 4:2:0 HEVC.

Probably affected: some type of Nikon Z9 format; codec, resolution, other details unknown. This cannot be investigated without having the clip in hand. It is vital an original, unaltered camera clip be uploaded to a file sharing site where we can examine it.

It would help if users having any 100.0 fps or higher frame rate material could put that in a 10.8.1 test library, upgrade it to FCP 11.0, then post the results.

The only current workaround is revert to FCP 10.8.1. There are two methods: (1) By using FCP backup libraries, and (2) Export a library XML in 1.12 format, then load that into FCP 10.8.1.

Normally there are FCP library auto-backups in /Movies/Final Cut Backups. Do not attempt to open those with FCP 11.0 or they will be upgraded. Instead make an immediate file-level backup of all the FCP backup libraries to another drive or folder. Then make a duplicate copy of those because opening them with FCP 11.0 will upgrade them which cannot be reverted.

For an upgraded library on FCP 11.0 which shows the black clip problem, export a library XML using the prior 1.12 XML version. Then when running FCP 10.8.1 create a blank library and load that XML. It should restore the entire library with all clips and projects, without any black 100.0 or 119.98 fps clips. You will have to stay on 10.8.1 until this is resolved.

It is easy to interchangeably run FCP 10.8.1 and FCP 11.0 -- provided you saved the 10.8.1 'Final Cut Pro.app' package in /Applications by duplicating it or copying it somewhere. It is always a good policy before a major upgrade to make a backup of all files and especially the .app packages of major applications. Sometimes there is a Time Machine backup of the prior FCP version available.

Sure, here is download link to a clip; https://we.tl/t-fVeRLNOTYP

The problem is with my clips at 120 fps from Panasonic S5xii that exist in projects being updated to FCP version 11. But when importing the clips freshly into a version 11 project they are fine.

Lance Mcvickar wrote:

My issue is .mp4 files even when set to “copy to Library“ on import don’t copy like they should, they stay on the external drive, only aliases are created in the library/ original media, the media is not copied. Meanwhile my QuickTime screen captures do copy to the library See pic last two files are aliases for the .mp4s. Major bug I would say.

https://discussions.apple.com/content/attachment/8c24fb15-c109-4b5a-93e5-b4500ef262dc

This seems to be a completely different problem. You should start your own thread and give specific details of how you are importing. By the way, please use command-shift-4 and drag to take a screenshot. No need to use the phone, or for us to tilt our heads 😎

@hesus4444, I've downloaded your clip; metadata listed below. I've had added it to the other two Lumix clips we have, and will include that with the bug when filed. This should ensure the fix includes your camera and format.

The three clips we have so far:

• GH6 3840x2160 HEVC 10-bit 4:2:0 100.0 fps, 288 megabit/sec
• GH7 4096x2160 HEVC 10-bit 4:2:0 119.88 fps, 288 megabit/sec
• S5XII 1920x1080 H.264 10-bit 4:2:2 119.88 fps, 416 megabit/sec

I've tested several 100.0 and 119.88 fps HEVC and H.264 10-bit 4:2:0 and 10-bit 4:2:2 clips from Sony cameras, and those work OK. Two years ago, there was a black frame problem unique to Sony mirrorless and the DJI Mavic 3 (5k 10-bit 4:2:0 H.264, all frame rates).

The 2023 Sony issue was fixed rapidly, but FCP & MacOS engineering did not have the DJI clips to examine when the bug was first filed, and it took a long time to get those fixed. That illustrates why it's so important to file bugs including sample clips that demonstrate the problem.

Lumix S1H 100FPS clips are affected - do not update if you use this camera and are mid project.

I shot a project earlier this year hundreds of affected clips - gone back to edit after the update and now I can't relink any of them even though they are the original files.

Has anyone found a way to relink the media? This is painful.

I have a similar problem with H265 codec on macbook air m1 mac os 15.1.1 , fcp 11 .

Having h265 files in multicam project, I can't export video. The export is simply canceled in fcp 11 and Compressor says 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.

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

I will have 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!

My issue is .mp4 files even when set to “copy to Library“ on import don’t copy like they should, they stay on the external drive, only aliases are created in the library/ original media, the media is not copied. Meanwhile my QuickTime screen captures do copy to the library See pic last two files are aliases for the .mp4s. Major bug I would say.

If possible get the third-party MediaInfo tool from the Apple Store, open one of your video files in MediaInfo, do File>Export, save as a text file. Then copy/paste the contents to a post here.

Please tell us if your MacBook Pro has an external monitor. If so give us the specifications and whether it is connected by HDMI or Thunderbolt.

Is that a yes? You trashed your settings files?

H.265 is very commonly used now. Joema’s suggestion of MediaInfo would be great.

I should point out that with one exception I have not heard of or seen this problem in FCP 11, which means it’s most likely a specific configuration of hardware and specific media in a certain type of project. Obviously it’s annoying for you, but unless it can be narrowed down to parameters, a non-reproducible issue is going to be very difficult to resolve.

I've worked on a few rare cases where this has previously happened. One involved 100/120 fps 10-bit 4:2:2 H.264 material from Sony cameras. It was fixed fairly quickly. The other involved 10-bit 4:2:2 H.264 from only the DJI Mavic 3 (all frame rates). The HEVC variant didn't have the problem. Details: https://joema.smugmug.com/FCP-Bugs-Filed/n-Fx6Pt2/i-WB9J6Mv/A

However those were 100% consistent failures on any machine of that type. This one seems more narrow and may involve yet-unidentified specific conditions.

We really need a sample clip of the specific format that causes the problem. Even if it doesn't immediately cause the problem on our machines, we can put that clip under the microscope and scrutinize it.

I've tried everything.

What exactly is everything? What and how did you try it?

FCP should not be updated while editing. A good rule of thumb is to keep a copy of your old FCP and data so you can revert to a stable version. Please test new versions before using them.