TOPIC:

Hi everyone!

from when I use the files of the A7s III 4k 10bit I had always the same problem when I tried to export every wedding timeline that I did. The ram just start go up till a message appear "system run out of memory" and after that fcpx send a message that export has failed and after that:
Error: RequestCVPixelBufferForFrame returned: 3 for absolute frame: 616 (dosen't matter the number of the frame is totally random)

I always fixed that bug playng a song in fcpx that in some way force fcpx to refresh is memory and doing that 5-6 time every export he succeded in the export (I know it's sound weird but it's work in that way)

I have a mac mini m1 with 16 gb of ram with macos monterey (my wife have a m1 max with the same mac os and she have the same problem, but having more ram she need to do it 1 or 2 time every export)

Now after the new realese of final cut come out I thought about upgrade mine mac m1. I also upgraded the mac-os.

Well, the bug still there and awesome notice.... the trick I used before wont work now, because if before you could see the ram go up "activity monitor" like in the pic imgur.com/a/C1NqgF0 now the ram refresh alone but fcpx wont export and keep doing that error.

I wanna cry.....

Someone have any idea how to fix this?

Btw sorry for my bad english

Are you using any third-party plugins? Which ones? Also please tell us the FCP version and MacOS version on your M1 Mac Mini and M1 Max.

I have two A7SIII cameras and often edit 4k/23.98 10-bit 4:2:2 XAVC-S, XAVC-HS and XAVC SI. So far I have not seen this problem. Which of those 10-bit 4:2:2 codecs did you use and what frame rate?

There were some significant memory leak issues on earlier versions of Monterey. At a minimum I'd suggest upgrading to FCP 10.6.6 and Monterey 12.6.6. If you are on Ventura, state what version (on both machines).

Thank you for your reply!
No plugin, at least in the mac mini m1.
mac mini m1 Ventura 13.4 fcpx 10.6.6
M1 max monterey 12.6 fcpx 10.6.4

xavcs 4k 280m 4:2:2 10bit 100 fps
xavcs 4k 200m 4:2:2 10bit 50 fps

The problem come out when in the timeline there is a lot of short clip (like 1 or 2 seconds or less of different file) and a lot of audio...

btw now, I can't even see the file at 100 fps, it show me back screen

There is a known problem in13.4. You can either convert the media in Handbrake, from back the system to 13.3, or wait for the OS to be fixed.

I have the exact same problem for about two years now, both with my M1 MacBook Pro and my Intel iMac 5K 2017!

The problem only happens with Sony’s latest 10 bit footage, recorded with a7siii, a7iv, FX3 etc.

Have you managed to find a solution? I have tried to play back the timeline when it exports every so often, to somehow “empty” the RAM or buffer so the export won’t fail, but this isn’t working every time! The problem seem very random…

You just need to play a song in the broswer of fcpx and it's always work... the problem is if you upgrade, then the ticks wont work anymore

What do you mean by upgrade? I have the latest version of fcp 10.6.6, and the latest version of macOS Ventura 13.4.1

oh! You already upgrade to ventura... I have 2 mac mini one still on monterey and with that looking at activity monitor when the ram go up you just need to play a song in the browser of fcpx and the ram reset... if I do that a couple of time i can export.
With ventura seems that dosent work anymore... I just tried to upgrade to the beta version of Sonoma "i did that only because I dont use that second mac" and if you export after you had render everything seems works... I didnt try to do the same thing on ventura, now I will downgrade and try it

My S3 and FCP have also run into this problem frequently. A temporary solution I've found is to identify the specific clip that is triggering the error, and generate optimized media for it. This enables me to export the project successfully.

And when exporting, select Apple Device( m4v format.) Even if the export gets interrupted, the successfully exported portions will be saved (allowing you to concatenate multiple exports and identify which clip is causing issues).