CPU Playback meter Spikes
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This is really strange & I'm not going to be cocky about it, but I MAY have fixed the CPU spiking problem in 4.6 when I went to a consolidated window set-up. For reasons that remain mysterious (to me -- I'm an idiot), in songs that had previously spiked (some of them a mere 2 audio tracks) the CPU levels stayed low once I went to a consolidated window. Prior to 4.6, I used 4.12, so the consolidated window is new to me. I'll let you know if this continues to make a difference.
- dynamix
- Posts: 185
- Joined: Tue Mar 29, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Jersey Side
- Contact:
For me, running all my plugins - happens first play every time, just as the cursor hits the data in the tracks and the music starts. That CPU overload message comes up. I just hit continue. Then, never again.
Still, a pain. Its as if the computer is just lazying around and "Whoa, holy cow, you mean I have to do some work now?" Then it snaps out of the lazy spell and is pretty much ready to handle the work load throughout the session.
Still, a pain. Its as if the computer is just lazying around and "Whoa, holy cow, you mean I have to do some work now?" Then it snaps out of the lazy spell and is pretty much ready to handle the work load throughout the session.
http://www.dvbmusic.com
Dual 2 Ghz G5, MOTU 896, OS 10.3.9, DP 4.6, Mach 5, Kontakt 2.2, MX4, Reason 3.0.5, GPO, Absynth 4.0.2, B4 Organ II 2.0.3,. MacBook Pro 2.33 GHz Intel Core 2 Duo - 4 GB 667 MHz DDR2 SDRAM w/ MOTU Traveler & MOTU Bag w/ OS 10.4.10, DP 5.12
Dual 2 Ghz G5, MOTU 896, OS 10.3.9, DP 4.6, Mach 5, Kontakt 2.2, MX4, Reason 3.0.5, GPO, Absynth 4.0.2, B4 Organ II 2.0.3,. MacBook Pro 2.33 GHz Intel Core 2 Duo - 4 GB 667 MHz DDR2 SDRAM w/ MOTU Traveler & MOTU Bag w/ OS 10.4.10, DP 5.12
- Timeline
- Posts: 4910
- Joined: Tue Nov 09, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Fort Atkinson Hebron, Wisconsin...
- Contact:
Heat can cause it.
UAD-1 can also load it up.
If your computer is too slow after streamlining OSX, just wait about a week. New quad processor macs are coming out.
UAD-1 can also load it up.
If your computer is too slow after streamlining OSX, just wait about a week. New quad processor macs are coming out.
2009 Intel 12 core 3.46, 64GB, OSX.10.14.6, Mojave, DP11, MTPAV, Key-station 49,(2) RME FF800,
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
DA-3000 DSF-5.6mhz, Mackie Control. Hofa DDP Pro, FB@ http://www.facebook.com/garybrandt2
- Shooshie
- Posts: 19820
- Joined: Sat Oct 16, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Dallas
- Contact:
There are a number of things that temporarily fix the CPU spiking problem, but for most people they eventually come back. My problem with that goes away when I change the hardware setup, but returns about 5 minutes later. It has only begun doing this (again) in 10.3.9 and Tiger, and in DP 4.5. While I was using 10.3.2 or so, with DP 4.12, the problem went away for a long time.ernie5 wrote:This is really strange & I'm not going to be cocky about it, but I MAY have fixed the CPU spiking problem in 4.6 when I went to a consolidated window set-up. For reasons that remain mysterious (to me -- I'm an idiot), in songs that had previously spiked (some of them a mere 2 audio tracks) the CPU levels stayed low once I went to a consolidated window. Prior to 4.6, I used 4.12, so the consolidated window is new to me. I'll let you know if this continues to make a difference.
Another "fix" was to use the Aggregate Device setup in Apple's Audio-MIDI Setup, but this caused some strange bugs to emerge for a lot of people, myself included. I had to reinstall my entire OS and software on a clean disk to get past those bugs.
I'd love to know your complete setup, and how your prefs are set, especially hardware, buffer, work priority, host multiplier, and other audio setup prefs.
Shooshie
|l| OS X 10.12.6 |l| DP 10.0 |l| 2.4 GHz 12-Core MacPro Mid-2012 |l| 40GB RAM |l| Mach5.3 |l| Waves 9.x |l| Altiverb |l| Ivory 2 New York Steinway |l| Wallander WIVI 2.30 Winds, Brass, Saxes |l| Garritan Aria |l| VSL 5.3.1 and VSL Pro 2.3.1 |l| Yamaha WX-5 MIDI Wind Controller |l| Roland FC-300 |l|
I confess that I have played WWII online and those people there are really optimizing that game. The discussion here reminds me about that game. Spikes and CTD and eventually they fixed it. It was some kind of memory management problem. It was fine a while and then the game started to act jerky.
Getting a faster computer will quite likely not fix this if your computer runs at 30-40%.
Just my thought.
Getting a faster computer will quite likely not fix this if your computer runs at 30-40%.
Just my thought.
From MOTU:
Check your Background Processing. I'd recommend setting your preferences to:
- Wait until analysis is needed
- Mute old soundbites
- Show both high & low priority tasks
- Disable automatic beat & tempo detection
- Never look for beat & tempo automatically
Josh Hetrick
MOTU Tech
I'll have to check all of this stuff when I get to my studio computer tonight. I believe my buffer is set at 512, though.
Check your Background Processing. I'd recommend setting your preferences to:
- Wait until analysis is needed
- Mute old soundbites
- Show both high & low priority tasks
- Disable automatic beat & tempo detection
- Never look for beat & tempo automatically
Josh Hetrick
MOTU Tech
I'll have to check all of this stuff when I get to my studio computer tonight. I believe my buffer is set at 512, though.
FYI: I have the UAD-1 card, with the 4.0 version of the software. I have a dual mirror 1.25 GHz G4, 2 GBs of RAM, DP 4.6, running Altiverb 5.1, Waves, Kontakt, Trilogy and I have no problems.
I hope this is helpful.
I do have Mach 5 and it is a CPU hog. I get spikes with it and the TC Firewire powercore.
Take care,
Papisax
I hope this is helpful.
I do have Mach 5 and it is a CPU hog. I get spikes with it and the TC Firewire powercore.
Take care,
Papisax
Quit Apple Dashboard
OS 10.14.6, iMac i7.3,5 with 32 GB Ram, 828x, Miditimepiece AV, DP 10.00 (ger.)
MachFive 3, MSi, Ethno 1, Omnisphere 2, Sampletank 4, Forest Kingdom II, Desert Winds, EWQLSO-Silver, Real Guitar 2, VLP120, PLP120, VCP120, Liquid Saxophones, Elastic, The Resource, Wave Arts PowerSuite 4+5 and Master Restoration, Kontaktplayer, Absynth 5, Ni Action Strings etc.
MachFive 3, MSi, Ethno 1, Omnisphere 2, Sampletank 4, Forest Kingdom II, Desert Winds, EWQLSO-Silver, Real Guitar 2, VLP120, PLP120, VCP120, Liquid Saxophones, Elastic, The Resource, Wave Arts PowerSuite 4+5 and Master Restoration, Kontaktplayer, Absynth 5, Ni Action Strings etc.
I have optimized the system so Dashboard is disabled. Along with startup apps. File / printer sharing and firewall (I have a hardware Firewall). Discs defragged and I have run Onyx scripts and system optimiser. The energy saver is disabled. I did reset nvram and repaired permissions and all of the stuff that you need to get a mean lean system.Harry wrote:Quit Apple Dashboard
Quitting dashboard made the system faster, no doubt about it.