My M3 MacBook Pro problem with Final Cut Pro!
Vložit
- čas přidán 20. 07. 2024
- 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.
Amazon US ($70 OFF): geni.us/2YPWCK
Official Store($70 OFF): geni.us/Io7W
Ugreen Nexode GaN Chargers (up to 35% OFF): geni.us/sFA37
🛍️ Buy the M3 MacBook Pro: geni.us/10CFY
👀 M1 MacBook Air in 2023? Yes please!: • M1 Macbook Air in 2023...
📲 Get the Violet Sky wallpapers: geni.us/wDqEyl6
My Charging Partner: Ugreen Amazon store: geni.us/ugreenstore
My Case Partner: Pitaka: geni.us/Pitaka-and-Jerry
🧵www.threads.net/@jerryschulze...
===============================================
🛍️My iPhone Art geni.us/CeNA4A
🛍️Grovemade Desk Mat and Knife: geni.us/pjDLmKt (save 10% JERRY10)
UNLIMITED Cloud Backup for your Mac with Backblaze - geni.us/Xvbve
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? - Věda a technologie
I am still seeing issues and if you want to see example exports check this out: czcams.com/video/ZQLN7su0tR0/video.html
I just had this issue today using FinalCut! I'm using a solid new MacStudio I switched to my 2019 macbook pro after several export failures. So frustrating
I can confirm, M3 macbook Pro 1tb and 18gb. Still fails everytime. Looking into a refurbished m1 or m2.
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.
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.
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?
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.
Yes I am using Sony but I also tried creating optimized media for all the clips. Was hoping you would have all the answers.
You are not the only one I heard with this issue
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.
Do you think a Final Cut Pro update is going to fix the issue? Assuming is not the computer.
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!
If this is an underlying issue (ex: with the dynamic cache), it will eventually catch up with the 16GB version as well. Apple needs to fix this.
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
Return it I guess. 4 days trying to figure it out is way too long to resolve the issue.
are you finding the issue happening in other NLEs?
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.
What about when I take that same package to another device and have no issue?
Good point. I presume all computers have the same OS version. I am running the latest. Dynamic caching is likely not a root cause since my iMac does not have that capability. Memory spikes suggest the possibility of memory corruption. I will say that I was able to play the raw file in its entirety without issue.
Yep all updated to same version.
Hi I'm having a really frustrating issue with my 2023 Macbook Pro (chip M3 Max) running Mac OS SONOMA 14.2. I purchased it in December, so it's practically new and has a 16" screen, 48GB of memory, and 1TB of space (with over 800GB of free space still available). However, I'm having trouble working on my FCP project, which is only 9GB in total.
I've tried all kinds of things to fix the issue, including selecting Proxy preferred, saving my project and files on an external 10TB hard drive, and adjusting settings within FCP.
I even purchased CLEAN MY MAC software to optimize the CPU and clean up duplicate and large files, but it's still slow when I try to work on my project.
Interestingly, my music software, Logic Pro X, and other applications work super fast, so I think the problem is specifically with FCP and not my MacBook.
If anyone has a solution to this problem, I would really appreciate any help. I've provided all the details above.
Again, I dont believe it's a new Mac with 48GB ram woul be the issue.. it is super fast.
I'm grateful in advance for any idea anyone could offer.
Thanks!
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
My Sony files are constant I believe.
I think we should wait for the new version of the FCP which will be released at the end of this month
Ya, there are some new features coming, interested to see if they fix this.
@@JerrySchulze my exporting is stuck at 0%. I've done everything. Giving FCP full access to disk space, tried different clips with different format .mov or .mp4, changed rendering preference, re-installed FCP.. still could not export :((((
Ive been doing some research and trying to decide on which processor to get for editing video in FCP and Davinci resolve. I’m a newbie and the extent of my editing will be my kids athletic events and family gatherings. I dont anticipate working for MGM or doing weddings so I dont need the best of the best. Can anyone tell me based on my needs if the M3 processor will work or if it’s overkill or even not enough? I was thinking an M3 with at least 18 GB ram. I appreciate all feedback. Thanks.
Send the POS back! And that is coming from an Electrical Engineer. There is something wrong. It's obviously not software, more than likely it's in the memory swap circuit. Could be a possible trace on the board itself is bad between the memory controllers. Also I would be checking thermals. You could always remove the back of the laptop, take a Flir camera and run the same export text and check to see if it's heat related also. But in my opinion this a hardware problem and not a software problem.
My Macbook Pro M3 18GB is having the same problem when exporting any new project. Has anyone made any progress in fixing this problem?
That is frustrating.
@@JerrySchulze What I tested, projects with XAVC S 4: 2: 0 8-bit video files generated with the Sony A7SII, works without problems, but XAVC S 4: 2: 2 10 bits with the Sony A7IV, problems occur when exporting.
@@rmariga same 10 bit files for me, but my 16gb M3 Air exported all my projects just fine.
Same for me with the 18GB also, I'm calling Apple right now to report it
@@avicmedia
Please, if you get any solution or answer, let us know here.
Yikes maybe I should hold off getting M3 iMac. Maybe I should just get M2 Mac mini.
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.
Hey Jerry, thanks for the Video! I have an iMac from 2013, and he works like a smoooooth glove. It is so good. But all the Programs are now wanna update (i have Catalina installed) and so i had to look around what it would replaced. I wanted to use the iMac as my monitor and bought a new M3 Pro. So the funny thing ist, you can use the iMac as an Monitor only with 2019 models....... and my iMac from 2013 runs better Adobe Programs than the M3. I spoke with APPLE over an hour about both issues and the resolution is now: i bring the M3 back and maybe buy a M2, because it doesn't have so much problems and bugs than the M3. It is really sad. He told me i have a powerhouse with the M3, but something is wrong and it is not good and that the Catalina is the best Update yet. And the new one has many problems. So i think it is too early to buy the M3. But the color is nice and the Sound is really awesome. But with this issues that is coming i can`t work.. and that ist not nice. Thanks and i wish you a good day! - Aphrokite
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.
Hello. I am a content creator. I was gonna buy this macbook pro m3 to edit my project files in fcpx. Was this issue solved? I would like to know before purchasing. Thank you
Not for me, I returned it. For reference, I use Sony hevc 4k and muticam so change any variable and you might not have the same issue. Can still give it a shot and return if you have issues.
@@JerrySchulze Thank you for your response. I saw you did the same test on a MacBook Pro space black. Is that fine for fcpx?
Why don't we use a different editing software to narrow down whether it's a final cut or hardware issue?
I did mention in the video that I tested Premiere pro and it worked fine. I have continued to test and have been working with Apple engineers to solve the issue.
Did you turn it off and on again? 🤓
Lol
8GB is the issue an absolute joke for a "Pro" product to have it on the base should at least be 16GB. You are not even getting the most out of the M3 chip with 8GB.
agree
Sounds like a FCP issue not complying with the new dynamic caching model that hopefully should be fixed with an update soon.
shall we use adobe or sony vegas instead of final cut program if apple is having a hissy b**chy fit about that final cut program?
This should be reported to Apple.
News, with the new update it seems that the export problem has been resolved. Test and give your feedback
Any update on your take on M3 MBP with FCPX? I just got my M3pro MBP about a week ago and had my project exported, 30min 24min, 5min, and these came out w/o any problem. h.265 files shot on c-log and n-log and dji log. I was really worried but I got my M3pro MBP anyway since I have m2pro mac mini to render if this problem was still there. OH...I have 32GB Ram 512GB SSD model...so I guess I really can't say this applied to higher tier ones...
Issue is only on the 8gb model.
@@JerrySchulze thank you for the reply 👍 you could've just brushed off my comment as me talking by myself 😅
I Have the 18gb model and I have the same issue it drives me crazy
@@avicmedia really!? I don’t have the issue with the 16gb m3 air.
@@JerrySchulze Yes sometimes it works first time and sometimes I need to export 10 times if not more... And I have problems with different frames each time, it's the 16" 18GB M3 PRO. If there is no solution I will change it
Thought about buying one but I will stick to my 2015 Intel.
This is one specific issue but ANY of the M series Macs will be a really big upgrade. (Save money and buy a refurb from Apple) or even the M1 Air on sale for 750 right now. geni.us/UV1Ao
I just bought the M3 yesterday. I'm having the same problem with exporting, it's failing. Do you have a solution for this yet?
Sorry, I dont. I got an email 2 weeks ago from Apple enginners saying they were still working on it.
I did go to to the frame that was not working and deleted it. I was able to export my video.
for me, the problem frame was always different.
@@JerrySchulze Hi Jerry, any news? Apparently Apple still didn't fix it. :(
I'm planing to buy M3 pro for using Final Cut, please advise if they solve this issue or not yet?
don't take the 18GB it doesn't work
I have an m3 pro with 18GB, still having the same issue.
Would more ram work, because i plan on using the 24GB version
I didn’t have any issue with the 16gb m3 pro.
@@JerrySchulze I've now been looking at the M3 pro MacBook Pro 18GB with the default specs as an option as it seems to be better value for money it seems, I want to use it for editing 4K amd 3D work and I'm only willing to spend up to £2,000 max as it's technically my first machine and that's what I'm willing to spend
I like the M3 Pro MBP.
Problem solved?
Suggestion: Find a window
I’m thinking that the GPU memory allocation has bugs on this M3: it is more powerful and probably asks for more memory to the GPU. As only Apple thinks 8 GB of RAM is ok in 2023 (or for 2020 for that matter…), that may corrupt the workload. I’m telling that again: I won’t buy a computer with 8 GB of RAM anymore, even if Apple tries to convince me that their 8 GB are special. No they aren’t, 8 GB it’s simply too short and for office/web (8 GB it’s ok) , I don’t need a $1000 computer.
I have the Macbook Pro M3 Pro with 18gb of RAM and i have the same issue but with Davinci Resolve Studio. Its not much about the ram its something wrong with the GPU
@@kemishhermosilla8993Is this just when exporting on Resolve? do you have and links to other reports of this?
@@johngwheeler just on resolve so far
SOnoma caused me several issues, maybe this is it
I'm from Brazil, I'm experiencing this problem with my Macbook Pro M3 18GB, is there any solution? I'm frustrated, I invested a lot of money in this Macbook Pro, and I can't work. I use davince resolve and FCT. good week !
You are having an issue with resolve also?
@@JerrySchulze I have problems, when rendering when exporting, there are media off problems in different frames when exporting, I did all imaginable procedures and countless renderings, I realized that it is linked to the way the video card reads the h.265 codec h.264.
I thought about migrating to final cut so as not to lose the workflow, that's where I found your video saying that Final CUT has the same problem, which davince res.
I found some palliative means to avoid the problem, but I waste a lot of time converting files, and the other way loses 60% of the machine's performance. I hope that either Apple or Blackmagic solve this decompression problem.
It's very intriguing to go through this situation, I've been trying to solve the problem for over a month, until I came to the conclusion that it's not just my Macbook Pro M3 that has problems, I found a forum on the Blackmagic website, where else Many people have the same problems on m3 machines
SAME ISSUE!!!!! im returning it. I'm so mad at APPLE. spent 4 hours in editing and can't use any of it
Move the project to an external drive and use another computer to export. All work is not lost.
My final cut sharing(exporting) stuck at 0%. :(((( HELP
I don’t have any answers for you.
Fun fact for you. I had this same issue with Davinici.
Really? Premiere worked just fine.
It’s a bug probably
This has got to be hardware fault, surely. If other, similarly-specced computers will perform the export without problem but this one won't, then it's a problem with the computer. And there are lots of other reviews of the M3 MacBook Pro (e.g. Luke Miani, Max Tech) that include successful Final Cut Pro exports. So it must be this specific computer, not the model.
Any updates? Did Apple fix this?
I just updated to fcp 10.7 and at the first 5 exports it was fine and then again failed.
Wait a sec, I’ve been facing the same issue with my M1 MacBook Pro on Final Cut Pro, i feel those export errors could do with Final Cut Pro
What about trying DaVinci resolve ?
Havnt had the oppertunity to do that.
I have the M3 Pro with 18gb of RAM and i have the same issue, im trying to solve it with apple but they do not know whats going on. I figured out its a GPU Issue, because when i deactivate it to render, it does the job other wise it does the same as in FCP
What were you expecting when you purchase a laptop in 2023 with only 8GB? It is a memory issue. Thing starts coughing up blood when it maxes out of memory. Get a Mac Mini M2 with 24GB RAM and 1TB SSD for cheaper price and it will export all manner of videos without sweat.
Did you see that the same projects export fine on the base m2 and base M1?
I have a soft spot for Software Engineers at Apple. They're perhaps the most underpaid and least appreciated. I bet the devs of the FCP team didn't had a clue into Dynamic Caching until just a few weeks ago and now their managers are whipping their asses to solve the problem... which they didn't even create.
Needs time to bed in. New software updates and patches. Not alway wise to buy new machines, when they're launched as it can take 6 months or more to iron out the glitches. Why 8gb of ram on entry machine, that needs to be upgraded.
It’s okay guys. 8GB is just like 16GB with Mac.
Faulty hardware! Give Tim Apple a call.
Well it’s a simple solution if the program isn’t giving a false error. According to the program it told you there’s a faulty frame of video (8332 I think) go that number of frames from the beginning and remove the glitchy frame
I discussed that in the video. I did check the frame and it was different each time.
@@JerrySchulze ohhhh sorry I missed that
What I usually do in this kind of situations is export in segments (using in and out points) to try to find the section that has the problem. If that doesn’t work the only things I can think off is a plugin that’s on specific clips that’s causing issues
Every time I did the export, it was a different frame being reported as problem. There are no plug-ins installed. This is a completely fresh installation of macOS with a fresh install of final cut and that’s it.
@@JerrySchulze hopefully 10.7 will fix that. Maybe 10.6.10 isn’t M3 ready? 🤷🏻♂️
Update FCP!!!
I am using the latest.
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.
lol, this is bad.
@@JerrySchulze 😂 its either this or I don't get paid for the project😆 Surprisingly it came out really good. You really couldn't tell at all!
omg, that was a good solution 🤣 I'm thinking of buying this computer, but I use FCP a lot, I'm not sure now.
Maybe unifying everything was a bad idea apple.
there is no fix, M4 will solve this issue for sure :)
ha!
I would’ve love to see if this issue was rearing its ugly head with other video editing software. Seems like Final Cut Pro is glitching out because of how the GPU handles memory.
Its possible.
8GB of RAM. That’s the problem.
Also SOC limitations, according to research.
sory to say but thanks not the problem… i use mac mini 8gb m2 with no issue 4k 6k rendering
It's not. Same problem with 18 GB of RAM.
@@leocaptured Apple needs to fix their Macs SMH
Finally people are realizing that the 8gb is the trash hold to take the money from people without tech information. Not your case of course, but all events from apple smell like "if you dont know tech too deep, come with us and bring your money".
Maybe it’s not optimized yet for the M3 chip?
8gb of ram… that should be criminal, that was barely usable in 2020, what is Apple thinking!
Your using the 8GB Ram model that's the problem!!! It's not going to export!!
I don’t think he watched the video.
No that’s Apples problem for selling a dysfunctional computer.
I would just have Apple swap out the machine.
I am not sure it is specific to my machine.
Did Apple even test the design with its own products? Doesn’t sound like it. I’d return it. Everyone should return their less than functional product. Maybe Apple will get a clue.
Apple hardware, Apple OS, Apple apps are different teams with different agendas. The big guys and the marketing team say what they want to each other, they execute but they are probably working with M2 chips instead.
8GB of RAM isn't enough. Get 24GB. Apple tries to convince you that 8GB is enough but that's a laugh. When I use my M1 Air with 16GB, I'm always pushing 12-14GB usage. On my iMac 27" (2018) with 64GB, it consistently runs at 45-54GB of usage. Granted it's Intel and I've got FCP, PS, etc open, going with 8GB of RAM for ANY video editing is a mistake. Sorry to hear.
"PRO" doesn't mean what it used to Apple. Thanks.
Return it and buy an M2 PRO 16"
8GB of memory is not enough.
You need a minimum of 12gb ram to avoid this issue
Why is it fine on the base model m2 and m1?
Check out Ugreen Nexode 300W USB C GaN Charger using the links below.
Amazon US ($70 OFF): geni.us/2YPWCK
Official Store($70 OFF): geni.us/Io7W
Ugreen Nexode GaN Chargers (up to 35% OFF): geni.us/sFA37
👀 M1 MacBook Air in 2023? Yes please!: czcams.com/video/puQoLGY9qqw/video.html
📲 Get the Violet Sky wallpapers: geni.us/wDqEyl6
The reason for the spikes and abrupt workload end could have been a couple:
1. The new gpu memory allocator causes trouble.
2. Effectrs render on gpu. More gpu cores == more work units == more gpu ram usage.
3. Process (locks/hints the os that) the memory so parts of process memory stay in ram even if ram usage is pushed, this prevents the gpu which now uses more ram to get access to ram. And so despite there being plenty of swap to use to put final cut pro process data into, it won't be put into swap. The conflict is resolved by presumably ending the compute abruptly.
4. Some other device than gpu on the macbook uses more ram so macOS kernel uses more ram in general.
You might ask why do I see the completed effect?
What you see on the timeline could be a lower quality(while it might not be perceptually visible, it's very plausible it's done that way) render of the scene for real-time viewing on a timeline.
Additionally some effects could also be "multi-stage" and look plausible despite being lower quality.
For this example take a look at John Carmack's en.wikipedia.org/wiki/Fast_inverse_square_root#Overview_of_the_code technique used in quake 3:arena years ago(this was before cpus got the even faster built-in inverse square root instruction), it has a commented out 2nd pass accuracy increasing do-that.
An effect could have been rendered out, but it didn't went through say 2nd pass of de-noising the effect or whatever need an effect could have had that's somewhat irrelevant what exactly was it.
So in short the compute stage that was abrupt-ed could also have been preventing some specific edge case scenarios or increased accuracy of the effect(which won't always be perceivable or well defined with all uses of the effect).
Previously apple used a non-unified memory architecture.
Basically gpu had it's own memory and igpu despite using ram has been using a more of a "reserved ram" approach.
Now cpu and gpu share the memory and can lock each other out of getting that chunk of memory for their own computes, so it's harder to anticipate limits the software should use, how much memory should be locked in etc.
Is this a sincere request for help from the Mac community? Then why is ad monetization turned on for this video? And why is there a sponsor ad in this video?
I’m thinking Jerry is just trying to get views and attention.
the dude bought the computer and spent hours trying to review and diagnose this for potential consumers. i have no problem financially supporting creators through ads and sponsorships for spending time and resources evaluating tech for the general public so we dont waste our time and money as well.
It s because you re a fox.
The main problem is the god dam fucking prices.
I still has this problem 🫠
I have updated to new FCP and Ventura update and… it may be fixed now?
I’m having this issue right now also….. I’m on a 2017 pro….this is killing me.
nope
I found a solution