CPU maxed out - mystery solved
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.
-
- Posts: 262
- Joined: Tue Oct 19, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Cincinnati, OH
Re: CPU maxed out - mystery solved
Songsmith,
You'll find as you use DP more and more that there are a couple of things one always makes sure to set in the preferences after an upgrade or clean install - for optimal performance..
One de facto setting that I have stuck to since tempo-based beat-detection was introduced in v 4.5, I believe, is "off" for automatic analysis and conversion. Fortunately, you'll only have to set it this way once (unless you need to trash your preferences, for whatever reason)...
You'll get the hang of these things as you go along.. Anyway, be glad you're not using Logic. I have a renewed love of DP after having to recently deal with that P.O.S.
You'll find as you use DP more and more that there are a couple of things one always makes sure to set in the preferences after an upgrade or clean install - for optimal performance..
One de facto setting that I have stuck to since tempo-based beat-detection was introduced in v 4.5, I believe, is "off" for automatic analysis and conversion. Fortunately, you'll only have to set it this way once (unless you need to trash your preferences, for whatever reason)...
You'll get the hang of these things as you go along.. Anyway, be glad you're not using Logic. I have a renewed love of DP after having to recently deal with that P.O.S.
Re: CPU maxed out - mystery solved
The bug - as I've explained - is that the CPU meter in DP does not report accurately, at least not on my machine. This is not a misinterpretation. This is either a bug for all users or a glitch in my system.
I have read most of the manual (which I am most grateful for and refer to constantly), but I missed the checkbox for turning on "show all processes" in the Background Processing window. In my experience, this checkbox only affects the Background Processing window display, not the CPU meter. My understanding is that the CPU meter is supposed to reasonably reflect the accurate CPU hit at any given time.
Umbrella -- since I have learned that there is a preference to turn off soundfile analysis, I've done so. Thanks to all for that suggestion. It's a good one.
I have read most of the manual (which I am most grateful for and refer to constantly), but I missed the checkbox for turning on "show all processes" in the Background Processing window. In my experience, this checkbox only affects the Background Processing window display, not the CPU meter. My understanding is that the CPU meter is supposed to reasonably reflect the accurate CPU hit at any given time.
Umbrella -- since I have learned that there is a preference to turn off soundfile analysis, I've done so. Thanks to all for that suggestion. It's a good one.
MOTU DP 7.02
Macbook Pro (2.4 Ghz Intel Core 2 Duo CPU / 4 GB RAM)
Internal HD (7200 RPM Hitachi Travelstar 320 GB)
Metric Halo MIO 2882 +DSP (or built-in audio with headphones)
Macbook Pro (2.4 Ghz Intel Core 2 Duo CPU / 4 GB RAM)
Internal HD (7200 RPM Hitachi Travelstar 320 GB)
Metric Halo MIO 2882 +DSP (or built-in audio with headphones)
Re: CPU maxed out - mystery solved
songsmith wrote:The bug - as I've explained - is that the CPU meter in DP does not report accurately, at least not on my machine. This is not a misinterpretation. This is either a bug for all users or a glitch in my system.
I have read most of the manual (which I am most grateful for and refer to constantly), but I missed the checkbox for turning on "show all processes" in the Background Processing window. In my experience, this checkbox only affects the Background Processing window display, not the CPU meter. My understanding is that the CPU meter is supposed to reasonably reflect the accurate CPU hit at any given time.
Umbrella -- since I have learned that there is a preference to turn off soundfile analysis, I've done so. Thanks to all for that suggestion. It's a good one.
wrong preference settings and lack of knowledge regarding proper setup of any app does not mean there is a bug this is just pilot error,you will learn from your mistakes much faster if you accept you don't know everything about DP rather then pointing fingers at Motu and proclaiming this is a bug all users have missed except you.
Some very knowledgeable users here are trying to help you and you keep blaming Motu and don't seem to be able to admit that you need to learn more about proper setup of DP or your Mac,this is starting to feel pointless as well as frustrating to follow this thread

KG
Last edited by kgdrum on Wed Jan 27, 2010 12:16 pm, edited 1 time in total.
2012 Mac Pro 3.46GHz 12 core 96 gig,Mojave, DP11.01,Logic 10.51, RME UCX,Great River ME-1NV,a few microphones,UAD2, Komplete 12U,U-he,Omni & way too many VI's,Synths & FX galore!, Mimic Pro w/ SD3,Focal Twin 6 monitors, Shunyata...........
- James Steele
- Site Administrator
- Posts: 22792
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: San Diego, CA - U.S.A.
- Contact:
Re: CPU maxed out - mystery solved
I don't know if turning off background analysis is in the thread about how to run a smooth DP setup. Perhaps at somepoint we can post a sticky as to the optimum settings. I agree that turning off background analysis has for years been pretty much the de-facto setting for me and most users I know. I simply don't feel comfortable having those processes going on in the background.
JamesSteeleProject.com | Facebook | Instagram | Twitter
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
- kassonica
- Posts: 5231
- Joined: Sat Oct 30, 2004 11:01 pm
- Primary DAW OS: MacOS
- Location: melbourne, Australia
- Contact:
Re: CPU maxed out - mystery solved
Agreed, I always turn mine off, but I've always wondered why it's turned on by default.James Steele wrote:I don't know if turning off background analysis is in the thread about how to run a smooth DP setup. Perhaps at somepoint we can post a sticky as to the optimum settings. I agree that turning off background analysis has for years been pretty much the de-facto setting for me and most users I know. I simply don't feel comfortable having those processes going on in the background.
Creativity, some digital stuff and analogue things that go boom. crackle, bits of wood with strings on them that go twang
Re: CPU maxed out - mystery solved
kgdrum (or anyone) -- Please try this at home and tell me what you see. Force DP to analyze a bunch of files and look at your Activity Monitor control panel. When you see CPU steadily maxing out according to Apple, go back to DP and check DP's Audio Performance CPU meter. Do you see the same report?kgdrum wrote:wrong preference settings and lack of knowledge regarding proper setup of any app does not mean there is a bug this is just pilot error,you will learn from your mistakes much faster if you accept you don't know everything about DP rather then pointing fingers at Motu and proclaiming this is a bug all users have missed except you.
Some very knowledgeable users here are trying to help you and you keep blaming Motu and don't seem to be able to admit that you need to learn more about proper setup of DP or your Mac,this is starting to feel pointless as well as frustrating to follow this thread![]()
KG
James -- thanks for the idea of posting "Turn off background analysis." in the smooth DP setup thread. I am now a fan of this choice.
May I also suggest adding turning on "show all background processes" in the Background Preferences settings (unless someone wants to share a good reason to avoid this)? It seems counterintuitive to me that a Background Process window, which I only bring up occassional to see what's happening when I'm wondering why the computer feels sluggish or why the fan just kicked on, is set by default to hide information.
MOTU DP 7.02
Macbook Pro (2.4 Ghz Intel Core 2 Duo CPU / 4 GB RAM)
Internal HD (7200 RPM Hitachi Travelstar 320 GB)
Metric Halo MIO 2882 +DSP (or built-in audio with headphones)
Macbook Pro (2.4 Ghz Intel Core 2 Duo CPU / 4 GB RAM)
Internal HD (7200 RPM Hitachi Travelstar 320 GB)
Metric Halo MIO 2882 +DSP (or built-in audio with headphones)
- HCMarkus
- Posts: 10396
- Joined: Tue Jan 10, 2006 9:01 am
- Primary DAW OS: MacOS
- Location: Rancho Bohemia, California
- Contact:
Re: CPU maxed out - mystery solved
I haven't used DP's CPU Meter for years but Apple's Activity Monitor is always visible on my desktop. Once we got multi-processor Macs, DP's meter was obsolete.
Re: CPU maxed out - mystery solved
Hi MCKarkus -- My MacBook Pro is an Intel Core 2 Duo. Does you think that would explain the difference in readout?HCMarkus wrote:I haven't used DP's CPU Meter for years but Apple's Activity Monitor is always visible on my desktop. Once we got multi-processor Macs, DP's meter was obsolete.
MOTU DP 7.02
Macbook Pro (2.4 Ghz Intel Core 2 Duo CPU / 4 GB RAM)
Internal HD (7200 RPM Hitachi Travelstar 320 GB)
Metric Halo MIO 2882 +DSP (or built-in audio with headphones)
Macbook Pro (2.4 Ghz Intel Core 2 Duo CPU / 4 GB RAM)
Internal HD (7200 RPM Hitachi Travelstar 320 GB)
Metric Halo MIO 2882 +DSP (or built-in audio with headphones)