Final Cut Pro version 10.6 extremely slow!!!

I wish that were the case, you see, it’s been this way ever since I cleared space. Nearly 240gb and still having major audio issues. Like you ever heard when frequencies don’t match up, or it takes hours to load a timeline. It’s not the space. I know my own machine.

I was not posting for a resolution, however I appreciate your response, Tom, I was simply hoping to add to the record of folks who are experiencing this audio issue on the latest version of fcp seems to be on Big Sur and Monterey according to others.

hey, can you please help me to get the 10.5.4 version of FCP and also facing creepy issues with both 10.6 and 10.6.1, am fed up with this build now I am getting to hate working on FCPX. I even Installed Davinci but learning new software will take its time as you know it. Really appreciate if you could help me

hey bro, I have an older MBP with Catalina, but still can't download it. it just pops the warning and nothing else is happening, I mean the 10.5.4 version doesn't start downloading, is there any other way to bypass it or something?

Thanks for the information. This is very discouraging, to say the least. I was hoping my new 16" maxed out M1+, which is in the mail to me for early December delivery, would handle it easily. Sounds like it is time to go to Davinci Resolve or Premiere as the path now.

I have never been a fan of Premiere since it exhibits all the user-viscious interfaces Adobe loves to consistently build into all its products. Davinci Resolve, on the other hand, seems to be the love child of FCP and Premiere. Making the transition (major FCP plug-in investments already made and now down the drain not-with-standing) will not be all that daunting.

Suffice it to say, Steve would never have allowed a useless set of two consecutive releases like this to happen. The entire FCP dev team (and Product Manager, in particular) would have all been fired by now. I am at a total loss to understand what is happening on the FCP dev team. Was the new built-in motion-tracking their downfall? What was it? They should have left things at 5.4ish before they were absolutely certain that had an app that, at the least, works. FCP has had some near-death calls as a product in the past when Apple went to the new FCP interface. It was at that time almost all film schools threw it out and went back to Avid or Premiere but it had grown back in popularity, since then. So this is a huge setback. The transition to Davinci Resolve will not be all that hard. I recommend at least trying it out since it is free.

Now all I need to find out first is if Davinci Resolve has the same performance problems on the new M1+ platform. Based on data I have collected thus far it seems it is fine but merits further investigation. I know Premiere runs OK on M1 based on what I have heard. Davinci Resolve seems to beat it out in certain benchmarks (e.g., rendering time). But that is for other Forums to pursue :-) This transition seems like losing an old friend. Shame on the Apple FCP team and what a major defeat and setback for Apple and its FCP user base. But they have iPhones to sell so FCP must once again be the ugly step-child product these days.

To quote Steve "it just works". That is what should be the case with the two most recent FCP releases. The previous ones did. As consumers, it shouldn't be that hard to figure out. Buying niche diagnostic tools like (whatever Etre is) won't help things. I, for example, am running a plain-Jane setup, stripped down to FCP only and I have never heard of problems like these being reported here. I have brazenly assumed since the app has gotten more complex (and larger) that one just needs to throw more horsepower (and money) and upgrade to more recent powerful options now available. That is why I ordered the new 16" maxed-out MacBook Pro. Not here yet but had been hoping. Still, we have these discouraging reports of people on brand new maxed out machines like the one I have on order having these issues not found on releases two versions prior. "It should just work".

You did say there are a lot of effects. Some can task the processor a lot more than others.

Noise reduction is one that is extremely processor intensive, and can increase the export times by quite a lot, for example.

Hi,

Thank you for trying to help me.

First I have to say, I am similar with all these effects and used them many times and I have an idea how long FCP takes to render these in a similar timeline. It had to be max half an hour in this case. Let say a little more. But 2,5 hours!? Absolutely no. I've made much more complex edits & exports before.

Second, I've let EtreCheck prepare a report (which is attached). But if I can read the results correctly, there is no reason for such a render-scandal :) The machine is new (~1 week) and many software are not even launched once yet. Because I am in a hurry to finish this movie, I could no nearly nothing else.

At least: I am using FCP since years. The last updates have made the SW a little shaky. More sudden crashes after very simple moves etc.. And after the last update the SW is unacceptable unreliable. I have worked sometimes weeks long without any problem before (on a Mac Pro Late 2013 cylinder). I am sure that current FCP version has basic problems and we here or EtreCheck or anyone else cannot solve these. :)

I hope I am very very wrong and my system has problems which I have to solve.

Thanks again & regards.

umit

Here the EtreCheck report:

Hi & thanks for the answer.

Big Sur: I will go over to Monterey. Shall I stay on Big Sur?

Wacom driver is up to date. For the new system I've downloaded and installed for a week or so. It has never caused problems on any of my systems. If it works it works:)

Paragon software is for NTFS disks of other people where I have to put some finished movies, documents etc. sometimes. I am using this option only for copying something from finder. Never exporting directly from any software.

Thanks again.

umit

Hi,

I am using some built-in and some 3rd party effects. Mostly color correction (wheels, curves etc.) or some grunge or old movie FX. Yes, there are many on the timeline. But, both the built-in noise reduction of FCP or Neat Video (version 5) are used many times on my timelines and even if you don't rendered these before export, they don't prolong the export time dramatically. Yes they make a difference but not 5times more.

My project is a HD (1080p) ProRes with clips with different frame sizes and codecs (optimized, mostly mp4s from older footage), many ProRes exports from Motion, 3-4 Mark III footage, uncomp. 16b 48 KHz AIFF files and a few .png or .jpgs. Parts of the timeline are compound clips with some titles. This is an usual timeline for me (I make documentaries). I never had an 2,5 hours export session where I had to wait sometimes 5 min for the 54% goes to 55%.

I have to mention too that the "render-everything-in-every-possible-opportunity-again"-syndrome of FCP is on its top-highest form now. :) You can never find your timeline rendered if you quit and launch you project with a many-times-rendered timeline.

Working with FCP(X) was so joyful and confortable; why this pain now?..

Thank you for trying to help me.

Regards

umit

Export settings. Please give as exact information as you can so others can see if they reproduce the problem. My first test with the built in Noise effect in 4K media going to H.264 do not show what you’re seeing using a 2019 MBP.

Hi,

I've forgotten this, you're right. Sorry. Export settings are the same as the project: ProRes + uncomp. audio 48 KHz.

And I've forgotten some other element on the timeline: English subtitles (made on the "Basic Titel" template with Myriad Semibold font with some blurred outline). They were two versions of the export: With and without subtitles. Without subtitles the export took app. 1,5 hour. And with the subtitles 2,5 hour. But, again, I've made many movies with such subtitles before and there was no such difference. (A frame with subtitle is attached.)

About the noise reduction: Yes, rendering of this effect takes some time. But It was only on a few clips in a 1h timeline. This cannot be the cause of the huge render time. It could maybe affect it some % but this is all.

Or maybe I cannot understand why you are focusing on it..?

Thanks, regards.

Well they haven't sorted it, new MacBook Pro as fasts you can get and Final Cut is absolutely useless, its scrambles clips, is so as **** so why did Im pay £4200 for a computer system that doesn't work

Sort it out Apple, your new version MacOS Monterery is utterly hopeless as I can't sort out Final Cut and am probably going to bin it and not recommend it

I have no idea what that is but will google all I get missing plugins on some files and not others but ball are the same plus it won't relink files and is **** of a slow with the spinning wheel of death, thought the M1plus chip would really get Final Cut zooming along but its worse than men old 2015 Mac which says a lot

Unfortunately this is a brand new December 2020 MacBook Pro top of the range with absolutely no issues, seems Monterey has a glitch when it comes to Final Cut and for the life of me I can't sort it out, I'm not that clever with all the ins and outs of the computer world

Same 10.6 version in both OSs?