FCP 120fps footage shows black

After upgrading to macOS Ventura 13.4 when I'm in Final Cut my Slow motion footage is all black screen.

Also doesn't play in Quick time.

But it does play in VLC

this is all Mp4 footage from a Sony FX3


Does anyone have the same issue???

I have a M2 MacBook Pro and everything Is up to date

Posted on May 21, 2023 4:45 PM

Reply
Question marked as Top-ranking reply

Posted on Jun 5, 2023 5:49 AM

Note: On Sony media, this bug only affects 10-bit 4:2:2 XAVC-S at 100 or 120 fps. It does NOT affect 10-bit 4:2:2 XAVC-HS at 100 or 120 fps. I believe all Sony cameras that can shoot the XAVC-S codec at that bit depth and chroma subsampling can also shoot the XAVC-HS variant.


On Apple Silicon Macs, the XAVC-HS version seems to run smoother and there is no quality loss.


For existing XAVC-S material with those parameters, the only solution is transcoding or downgrading to Ventura 13.3.1(a). But for all new material, shooting XAVC-HS could be an immediate solution.


Although the problem has been most widely reported on this XAVC-S variant, it seems to exist on some other codecs such as DJI 5k 10-bit 4:2:0 H-264at 23.98 and 29.97 fps.

52 replies

Jun 17, 2023 1:01 AM in response to roskoe275

I also have been struggling with this! Honestly my best suggestion is to simply use Premiere or Davinci until Apple resolves this issue. I thought about going through the hassle of installing an earlier version of macOS but I would recommend just switching over to a different software in the meantime if you're comfortable doing so.


Best of luck

Jan 2, 2024 8:56 AM in response to ST1LTZ

The ProRes Raw issue is not the same problem as discussed in this thread. It's not restricted to Nikon Z cameras - it's a wdespread problem that only appears on some Macs. It's a bug in FCP10.7 and to date there is no fix, just workarounds. The easiest workaround is to go back to 10.6.10 or earlier if you can. There are four other threads in the forum about this.

May 22, 2023 4:02 AM in response to roskoe275

This is pretty standard behaviour with Apple updates. If you have any critical functionality, especially involving 3rd party products, you need to have a "burner" or testing system where you apply those latest updates. Then, when (not if) it breaks, you can continue to use your production system until the problem gets fixed. Don't upgrade your production system until you have absolute confidence that the version you have been testing will meet your requirements.


This likely means double the hardware and software costs. It won't cost you that much in time, but it will require extra effort to apply updates and test on a regular basis.

May 22, 2023 5:37 AM in response to RothVideos

RothVideos wrote:

Getting another system just for updates doesn't fit in everyone's budget when the business is solely running by the owner.

If you can't afford a testing system, then you also can't afford those "free" system updates.

This shouldn't be acceptable

It's been acceptable for at least a decade. As Apple ramps up the update schedule and frequency, its products grow ever more popular. Why is that?

needs to be addressed asap, right now I literally cannot work because of this.

It may, or may not, be fixed in two months. The only "asap" updates that Apple provides are "security" updates. Those only exist due to intense pressure from competitors who hack Apple products and then publish the results in mass media. You're never going to read about 120fps video input on CNN.


This is just another variation on the bank loan problem. If you owe $1000 to the bank and can't pay, that's your problem. If you owe $1,000,000,000 and can't pay, that's the bank's problem. If the latest Apple update bricked 400 million iPhones, that problem would get fixed "asap". But sole proprietors using 3rd party video products? That's no one's priority except yours.


This is a user-to-user support forum. I can't fix Apple's products. I can't make Apple fix them. I can't speed up the update cycle. Literally the only thing I can do is give you suggestions on how to better deal with the problem. Unfortunately, right now, you've got a problem. Apple's big developer conference is in two weeks. If this were November, then you would have a good chance of getting an update by January or February. But late May? Apple's only going to be concerned with macOS 14 for the next few months. Well, not really. Apple's only going to be concerned with iOS 17 for the next few months. Then they'll throw a few crumbs to the Mac. They might fix this bug. They might make it worse.


At this point, you have 3 options:

1) Live with it. Don't use those camera settings. Use an older/other computer to change the encoding. Whatever you have to do.

2) Roll back to Monterey. I don't know if you'll be able to roll back to an earlier version of Ventura or not. Maybe check your local snapshots. Maybe Time Machine? I just don't know. But I can guarantee that if your computer runs Monterey, you can roll back to it. Hopefully the same bug doesn't exist in the most recent version of Monterey or you'll likely have the same roll back problem.

3) Bite the bullet and get that testing system now. If you buy a new machine right now, it won't have version 13.4 on it. You'll be able to configure it in a day or so and get back to work. Your old computer is now your testing system. At some point, you might be able to swap them if your new system isn't as good as the 13.4 one.

Jun 3, 2023 8:10 AM in response to potsy_15

The point Matti was making is that manure happens and professionals or any experienced person should be aware of that and have backups.


Only a complete novice will leave automatic updates on and everyone should keep a backup copy of FCP for this very reason.


It has been known since before the inception of computers that anything new has to be treated with caution and you always need to provide yourself with the ability to revert to an earlier version of whatever is being updated.

Jun 6, 2023 12:15 PM in response to joema

I am testing all permutations of UHD 4k, DCI 4k and 5.1k from the DJI Mavic 3. That includes both H264 and H265 (HEVC), MP4 and MOV and all frame rates on each combination of settings.


I think there may be some settings that permit 5.1k to work on the current Ventura 13.4 situation but I need to verify this. Even if so that doesn't solve the problem for already-shot 5.1k material.


There may be some issues if an import includes one of these "problem" clips, and you create proxies or optimized media either later or as part of the import. It apparently can put some FCP worker threads in a deadlocked state and afterward you may be unable to delete some media. In that case the background tasks icon will have a dark color (neither finished or busy). If you open that and cancel the background tasks, it seems to recover.

May 23, 2023 4:30 AM in response to Ian R. Brown

Ian R. Brown wrote:

Having multiple computers is the ideal solution as you can have them open simultaneously and don't have to spend a couple of minutes booting from one volume to another but for many people a second computer (especially a Mac) is not an option.

Most of the people reporting this problem are saying they are professionals who need this for their business. In that case, there are different expectations.


For consumers, the only option is rolling back to a previous version of the operating system and kicking the auto-upgrade habit. Or just not using this functionality for a couple of months, applying one more update, and then kicking the auto-upgrade habit. Of course, there is absolutely no guarantee that this hypothetical August upgrade isn't going to break something else. That's the point - always keep the user running after the next fix.


I realize that no one wants to hear that. They want Apple to FIX THIS NOW! That simply isn't going to happen. It's like yoga. They are going to have to sit with the discomfort, aware of the bug, without judgement. It's a two-month long pigeon pose.

Jun 3, 2023 7:09 AM in response to etresoft

This exactly.


The issue is having of hundreds of hours of footage that has been captured in the past and projects that have already been in production. Happened to me yesterday. Client needed changes made to a project from last year, opened it and all clips shot in that format were now black with only audio. This is a major issue for professionals that needs fixed immediately.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

FCP 120fps footage shows black

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.