Black video clips - FInal cut pro 11 problem

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.

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.

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.

Replication of this issue is elusive because it requires either (1) A prior library version containing the affected clip types be upgraded to FCP 11 or (2) The prior version library XML or project XML be loaded in the FCP 11 library.

Just importing the clips to FCP 11 and manually creating new projects with those clips works OK. That is why so many people cannot reproduce it. The issue only happens during the upgrade or if loading the prior version XML to the FCP library.

Once the black clip problem happens in an upgraded FCP 11 library, a prior-version (1.12) Library XML or project XML can be exported and loaded to FCP 10.8.1, and the clips and projects will appear OK.

Can you please upload to a file-sharing site an unaltered clip from that camera that displays the problem on your machine?

This category of problem tends to be specific to specific variants of camera codecs. Due to not having clips from specific cameras when filing a formal bug with Apple, we've had cases where a problem was not fixed for certain cameras.

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.

@Pickcodes: what camera, what codec and what frame rate? Can you please upload to a file sharing site a clip showing this? We want to avoid making a fix that does not include your camera's specific codec due to not having a test clip.

I currently have two clips: one from ironphreik, a Lumix S5XII: 1080p, 119.88 fps, 10-bit 4:2:2, H.264, 398 megabit/sec, and one from iHeimo, a Lumix GH6: UHD 4k, 100.0 fps, 10-bit 4:2:0, HEVC, 295 megabit/sec.

visualdemon reported this problem on the Nikon Z9, but we never got a clip or even MediaInfo data.

In previous similar cases, a fix was made on one variant of a 10-bit Long GOP codec from some cameras but not another camera, for which we could not obtain a sample clip. If anyone is experiencing this problem on their camera, please upload an unaltered clip to a file-sharing site so I can include it in the bug report. That will help ensure it gets fixed for your specific camera.

I am uploading one of the clips that turned black after updating to FC11:

https://we.tl/t-nUD610dg1c

It is a 4k 120fps footage from Panasonic Lumix GH7 that was already slowed down in the project to 25% (4 times)

Please give the complete specifications of the media and the computer you’re using.

Try disabling(V key) adjustment layers. Is it displayed correctly?