My M3 MacBook Pro problem with Final Cut Pro!

The M3 MacBook Pro can’t export video with Final Cut! There are some problems.
Check out Ugreen Nexode 300W USB C GaN Charger using the links below.

===============================================

DISCLAIMER: This video and description contains affiliate links, which means that if you click on one of the product links, I may receive a small commission.

#Ugreen #UgreenNexode #UgreenNexode300W

0:00 what is the problem?
1:52 what have I tried?
4:50 what else have I tried?
5:36 what is causing it?

[andyH_England]

You are about the fourth creator that has had issues with FCP. Clearly, it needs an update. MacRumors said a fix is coming this month for M3. If I remember FCP was late with its macOS update last year as well.

[bryans]

I'm thinking this is a memory management conflict between FCP and the M3 chip that will be fixed by an update by either Apple or FCP. Regardless, it's a shame a new "Pro" laptop ships with an issue like this.

[WhittyPics]

You are not the only one I heard with this issue

[white_and_blue]

I previously bought an Intel MacBook Pro, had a tough experience with Final Cut, and was on the verge of repeating the same mistake. After watching this video, I was able to decide to purchase a MacBook Air 15-inch in the same price range. Thank you for the valuable information.

[TheFinalCutBro]

I don't have M3, but I have been consistently having this issue for nearly a year now. Definitely not as bad as you've got it, but it there have been probably 5 different videos that I didn't think I would get out in time due to this issue.

Something just occurred to me, someone suggested optimizing the media on import to see if that would help. Are you shooting on Sony? i'd be curious if that might be part of the problem? Either way, this is super frustrating, and I hope it gets resolved soon.

[marko]

The only thing I can think is the new dynamic caching is not allocating enough ram to the right place at the right moment. Can the dynamic caching be turned off to compare the difference or on older systems you could manually allocate more RAM to one particular app (meaning you have less for other apps when that one is running ) - is that still possible?

[cowpatchman]

Return it I guess. 4 days trying to figure it out is way too long to resolve the issue.

[josephregallis]

Yes, MaxTech was showing a video earlier today that compared the same computer with 8GB and 16GB of memory and the 8GB computer would not always work with programs while the one with the 16GB had no problems!

[OthMar]

I think we should wait for the new version of the FCP which will be released at the end of this month

[TechYourNeeds]

Do you think a Final Cut Pro update is going to fix the issue? Assuming is not the computer.

[gerald]

I had the same issue when using iMovie on a 2019 i9 iMac with 40 GByte of RAM. The symptoms were similar. I tried to remove frames in the suspected area but the error message would occur again at another frame. I did not see any corrupted frames visually in the reported areas. Perhaps we are dealing with a corrupted file header. My footage was recorded in 4K/60 in log format on an iPhone 15 Pro to an external Crucial X9 SSD.

[rmariga]

My Macbook Pro M3 18GB is having the same problem when exporting any new project. Has anyone made any progress in fixing this problem?

[TheDanEdwards]

What you can do? Simple. Call up Apple and tell them the problem. They'll swap out the computer for another one. Your final guess about the SSD causing a swap problem could be correct (or not). The way to test that idea is to run some other memory hog (Photoshop on a very large image perhaps) that causes a lot of swapping. Nevertheless, just have Apple swap out the machine.

[studio]

I can confirm, M3 macbook Pro 1tb and 18gb. Still fails everytime. Looking into a refurbished m1 or m2.

[FujiXH]

FCP has many Month a Ram SWAP Bug on my Mac Studio too. It has massive SWAP over 90 GB to total Crash. The M3 with 8 GB of Ram has less 30 percent Cpu Speed because without 6 GB it don't runs good. Last Year the NAND GATE and now the RAM GATE

[davidpopaart]

HERE IS A VERY SKETCH WORK AROUND IN A PINCH-. Use QuickTime player to record the the screen as the vid is playing. I then export the audio separately and then join them together in a new project. I have to do this in a current client project now- which is such a shame, however the only major issues is banding in the skies. Otherwise the image isn’t too bad. Just have to make sure there are no issues with your playback and it’s completely rendered in the timeline Ofcourse.

[witcnshum]

Use Handbrake program to convert to a constant frame rate might help before editing and yeh the 8GB causes problems and was shown comparing 8GB to higher memory’s- definitely 8GB just have find other problem

[whateverinbetween]

Why don't we use a different editing software to narrow down whether it's a final cut or hardware issue?

[sizzlemann]

Apple software developers are getting sloppy. We have the same issue in Logic Pro where we get spikes that talk about sample rates. They vary as to size as well and thats with just one software synth, loaded and running in the program, that worked just fine on an earlier OS. I know it's not an Apple Silicon issue because I get the same error in my Intel Mac. Something in the last 3 OS's is conflicting with their software. The conflict just finally got to FCP. They need to figure it out.

[PIPERBOYWILLIAMS]

SAME im returning it. I'm so mad at APPLE. spent 4 hours in editing and can't use any of it