|
Avid Pro Audio CommunityHow to Join & Post Community Terms of Use Help Us Help YouKnowledge Base Search Community Search Learn & Support |
#1
|
|||
|
|||
Catalina issue with large edit sessions?
Hi there- first post here, have looked everywhere to see if anyone else has experienced this issue:
I'm an audiobook editor, and typically my sessions are not complex mix-wise, with typically one or two mono audio tracks, a handful of (mostly native) plugins for dynamic processing, sometimes one or two Waves and Izotope plugins, and my project workflow is typically around 10 hours or so of audio (16 or 24 bit mono wav) in a session, which by the end has thousands of micro-edits where ive placed room tone where its needed etc. This has not been an issue in the 7-8 years or so ive been working like this, going back to PT11 on an 11" Macbook Air. However. Due to a battery malfunction in my 2018 MBP (running Mojave), and an inability to get it fixed anywhere due to lockdown, i was forced to purchase a new machine so i could keep working. My new MBP (16" 2.3 i9) is running Catalina by default. I installed PT 2020.5 and opened a session i was previously working on. It plays fine, but the instant i tried to do *anything* (cut, copy, paste, save) it instantly beach-balls, hanging for 1-2 minutes, while the audio continues to play (but screen frozen etc). I created a blank session, imported unedited audio (several hours worth), no plugins- works fine. Added some third party plugins- works fine. Performed some simple edits (some cuts etc)- works fine. Apply some more complex edits (strip silence, overlay audio to new track on top of a room tone file)- the bad behaviour returns. I uninstalled 2020.5, tried it with 2020.3- same behaviour. I tried it with 2019.6 (as i read that version is compatible with Catalina)- same issue. Ive deduced that for whatever reason, Catalina does not want to co-operate with my edit sessions. Unfortunately, Apple have made it impossible to obtain the installer for Mojave, so i cannot switch out the OS (unavailable iin the UK, for some reason), and Apple support have been useless. The MBP is brand new, diagnostics state that it is healthy, and ive test run other audio software (Ableton), creating 20-30 tracks all containing hours of audio and running CPU heavy plugins to really stress it out, and the machine handles it perfectly, so its literally just Pro Tools thats the issue.. has anyone else experienced this?? As this affects my ability to work im really stressing out over this,,!! |
#2
|
|||
|
|||
CPU spike- Catalina / 2020.5
Hi
Clarification of my previous post; Im trying to run PT 2020.5 on a 2019 MBP 16 (16GB, 2.3 i9, OSX Catalina 10.15.5) but im getting a CPU spike of 110% every time i do *anything* other than press play, rendering PT useless.- im an audiobook editor so edit single track sessions of mono audio, very light on mixing and rarely any third party plugins (the edit sessions are typically large tho at average 10 hours with thousands of micro edits). This is handled absolutely smoothly on my old MBP 2014 runing Mojave, but on the brand new machine its a dead loss. Ive tried 2020.3 and 2019.12 also, exactly the same happens. Diagnostics on the machine come back perfect, and other audio applications such as Live (pushed deliberately hard) work as they should. Im replicating all my settings from my other machine (buffer, cache etc) and am now at a loss. Whats going on, is there something im overlooking? Has anyone else experienced this? |
#3
|
|||
|
|||
Re: CPU spike- Catalina / 2020.5
I have the same software, on a new six-core iMac, and am seeing lots of CPU spikes that I didn't get before with previous versions of PT and macOS. Not so bad that it's totally useless, but pretty bad. Also sometimes on session open, the whole program hangs as soon as the session windows appear. Some sessions won't open without 4 or 5 attempts.
|
#4
|
|||
|
|||
Re: CPU spike- Catalina / 2020.5
I wish Avid would write a code to pinpoint the plugin(s) that are causing these persistent 9173 errors!
I did a clean install when I got my 7,1. Spent over a week testing 3rd party plugins and I still get the cpu errors! Such an expensive DAW and these errors still exist. This is nuts!
__________________
PT Ultimate 2024.3 PT HDX MacPro 7,1 (Intel) 16 Core 96 GB ram macOS Ventura 13.4 Somehow, musicians are now technicians! |
#5
|
|||
|
|||
Re: CPU spike- Catalina / 2020.5
Quote:
Turning off hyperthreading is a well-known and widely used workaround to minimize CPU spike errors. I am well versed with multithreaded coding; it's highly unlikely that the enabled/disabled state of hyperthreading can cause any problem in a plugin. When I decrease the number of CPUs available to Pro Tools (using the Instruments app), I see fewer CPU spike errors. I have some test cases which only work correctly with two (or one) CPU cores enable (out of the 12 virtual cores normally available in my Mac). Come on: with fewer CPU cores available, I should see *more* CPU spikes since there is less silicon available to do work. When the total CPU meter shows a 100+% spike, I *never* see an individual core's CPU meter at anything over 20%. For a CPU spike to be seen as "Not enough CPU available" by PT, an individual CPU core would have to be overloaded. I never see that. And I see CPU spikes all the time these days (since PT 2020.5). Here's my theory: PT is calculating the "total CPU usage" incorrectly, and is using that erroneous calculation to throw "CPU Spike / Not enough CPU available" errors. If there are 6 cores, the max CPU usage really is 600% (as shown in most other CPU meters I know). If you want to normalize that to "100% is the max", then you should divide the total current usage by the number of CPU cores. For example if all 6 cores are running at 20%, add those up and you get a total of 120% usage. That's not an overload. You should divide that 120% by 6 and get, you guessed it, 20% total usage, which is not an overload. I'm sure that Pro Tools is not doing that. That's why things *appear* to get better in this area when you turn off hyperthreading or reduce the number of CPU cores. What happens in both of those cases is, you reduce the *total* number of CPU cycles in any given period. If the "total CPU usage" meter were correctly normalized to account for the number of cores being used, then the "total CPU usage" would not change when you turned off hyperthreading or reduced the number of cores. That's my theory. |
#6
|
|||
|
|||
Re: Catalina issue with large edit sessions?
Quote:
Forrester
__________________
Pro Tools Ultimate 2023.12, HDX1 Mac Studio M2 Ultra - macOS 14.2 |
#7
|
|||
|
|||
Re: CPU spike- Catalina / 2020.5
Quote:
Quote:
All this you are doing with looking at CPU meters and worrying about what they report is likely a complete waste of time. I doubt anybody here really know how those meters actually work and what they really show. (And the moment you turn on hyperthreading the meters just cannot make sense). Before jumping in and playing with hyperthreading and disabling cores have you tried to exclude third party plugins? You exclude them by removing them from Pro Tools, not guessign what problem are or are not by looking at CPU meters. If you have a test session using no third party plugins that generates errors on 2020.5 that go away as you reduce the number of CPU cores please share it, I'll try it on my 6/12 core i9 MacBook Pro, and I expect Avid would want to see it. |
#8
|
|||
|
|||
Re: CPU spike- Catalina / 2020.5
Quote:
[Could a mod merge this thread with http://duc.avid.com/showthread.php?t=410607] --- Basic things to look for here are covered in many threads on DUC and under "help us help you" up the top of each DUC web page. Is your system fully optimized? do every last thing no matter how painful for now. You can back off later, but for now do it all, including disable bluetooth, disable wifi, etc. What IO buffer size and sample rate are you running at? If you can set it to a large size that is stable, then reduce until it becomes unstable and do more troubleshooting at that buffer size trying to get it more stable. How did you get stuff setup on the new Mac? Did you use the system migration utility to migrate from your old Mac? What did you move with that utility? What apps and plugins and drivers did you install from scratch? What audio interface and driver version? Where are you recording sessions to? (disk issues can cause CPU errors). Make sure your disk cache is set to a few GB not "normal". I assume that will fully caches your sessions. The run thought, testing after each step: Trash prefs using Peter Gates utility. (and keep doing this between other tests). Move all .aaxplugin files out of the plugin folder (/Library/Application\ Support/Avid/Audio/Plug-Ins). And Trash Prefs again. Pro Tools will put back the default plugins when it starts. (And importantly it does not only matter if you use any plugin in your session or not... we care if you have removed all third party plugins installed on your system (and potentially all Avid plugins if you have incorrectly upgraded Pro Tools)... plugins don't need to be instantiated in your session to cause all types of problems, they just need to be installed in Pro Tools). Test using Build-In Output as the playback engine Test starting with an empty session, not from a template. Create a new macOS Admin User and test from that account. At this point test it all, from this account, with all third party plugins removed, using built in output as the playback engine, with a new amptu session, after trashing prefs etc. You might want to try a clean reinstall of macOS and clean install of Pro Tools and ILM and nothing else at all and see if that works... do that on test container on your boot drive (if you are comfortable with administering the system/APFS disk management) or on a external SSD. And if you get this far and are still stuck you should be opening a support incident with Avid. I'd also be sure to turn off remote telemetry since it's known to cause other issues on 2020.5. If this is a new MBP 16" I think they only ever ran Catalina so worrying about getting an installer off Apple is a waste of time. Chasing Apple and running tests on the Mac hardware is likely a waste of time. You have lots of basic troubleshooting to do before suspecting the hardware. Last edited by Darryl Ramm; 06-14-2020 at 02:23 AM. |
#10
|
|||
|
|||
Re: CPU spike- Catalina / 2020.5
Quote:
Quote:
Quote:
Thanks. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Protools 2020 Mac Catalina Just Crashes | JimmyD150155 | Pro Tools 2020 | 12 | 05-02-2020 12:06 AM |
Is 2020 better w Catalina? | Rectifried | Pro Tools 2020 | 13 | 04-06-2020 09:28 AM |
Downmixer in 2020.3 (Catalina) | Michael Carnes | Pro Tools 2020 | 5 | 04-05-2020 04:51 PM |
Cannot install Pro Tools 2020.3.0 on Catalina in any which way | moyno85 | Pro Tools 2020 | 3 | 04-04-2020 03:41 AM |
2020.3 Catalina video support | andystar | Pro Tools 2020 | 4 | 04-01-2020 11:43 AM |