I've had it happen at the same frequency with no 3rd party plugins installed vs having a ton of 3rd party plugins and the behavior is the same.Download Final Cut Pro 10 free latest full version complete direct download link DMG image Setup for macOS Big Sur with Intel M1. I'm assuming this is some type of bug in FCPX as I can't imagine it being my install. Not unusable because the work-around seems to do its thing. I use it for work and am paid per project I complete, so this is a nuisance. Workaround: If I cancel the render, delete all generated render files and transcoded media, close Final Cut and re-open it, re-render the file and export, the CPU usage again spikes, but this time, Final Cut is using about 80% of my CPU and it flies through the export around 900MB/s. If I check iStat Menu, Final Cut X is only using about 15% of my CPU and the export crawls (when this happens, I get barely 100MB/s).I export to ProRes 422 HQ - my CPU usage will spike (I'm exporting from NVME to another NVME, so on average it moves around 900 MB/s when it's running fine).I render everything (media is also transcoded).
Let me stress, it only happens once in a while: The issue I'm having which is really odd and only happens a handful of times with projects. I typically render my clips before I start working on them and let the background render do it's thing before exporting (it's an 18 core Intel machine with a Vega 64 I'm on- so typically it doesn't take long). So I noticed a weird phenomenon with Final Cut in Monterey overall (having tried all the Monterey updates, all the FCPX updates and even a fresh re-install of MacOS, it's still doing this).
I just hope they sort this shit out because yeah, as you said, edits are taking three times longer at least.
When FCP backs up every so often, it also seems to really kneecap the waveforms. My best advice I can honestly say if you’re having the problem too? Quit the program and reopen it any time the waveform times start to get too bad. I submitted a bug report to Apple and I hope others are as well because yeah, editing like this is untenable and completely halts productivity. As well as moved the Final Cut Pro cache location to a separate drive even. At this point I’ve made sure “Show Reference Waveforms” isn’t checked, I optimized my footage (never had to before 10.6), I even transcoded it to ProRes proxy. Uninstalling and reinstalling did help a bit for a while but quickly in my next project started acting up with the waveforms again. Yeah, I hate to break it to you but I should really do another edit on my comment. Improves stability when dragging clip ranges to Keyword Collections.Improves stability when previewing effects in the Effects browser.Improves stability when opening projects from the browser.Improves stability when removing audio effects in the inspector.Improves reliability during playback of AC3 audio.Fixes an issue in the Export File share destination where the Video Codec setting was unavailable after choosing Computer as the format.Fixes an issue where the Command-Z keyboard shortcut would not perform an Undo if Language was set to Spanish in System Preferences.Improves performance when opening large libraries.Fixes an issue that could prevent successful import of FCPXML 1.9 and 1.10 files.Final Cut Pro 10.6.1 has been released, which appears to have fixed the crashing and slowness. Those of you experiencing crashing and serious slowdowns following the initial 10.6 release, can now get back to work on their projects.
0 kommentar(er)
