Processor overload while using key command

[difab4]

DP 9.51, iMac 2017 i7 4.2 ghz 40g ram, 500g ssd.
After assigning ‘set start time to counter’ to the T key, when press the key, ‘memory cycle’ turns on and if I repeatedly press T key to change start time, processesor overloads. But if turn on ‘memory rewind’, T key works and doesn’t turn on cycle.
Doing small projects and the processor otherwise not breaking a sweat.
Tech link conversion could not resolve.
Fresh copy of DP and OS
Thanks

[MIDI Life Crisis]

Processor overloads (or “reported” processor overloads) have been common in DP for as long as I can remember. If it is stopping playback, change the pref for that (I think it’s an audio pref). There’s also a key command to clear all overload indicators. I have to hit that fairly often.

If it is otherwise impacting critical performance issues, post what those are as there might be a solution someone can offer. FWIW, DP indicates a cpu overload every time I start up and has since at least version 5. Again, just tell DP to ignore overloads (ie - don’t allow it to stop playback) and keep the key command to clear the indicator handy.

[frankf]

Did you try another Key command? T is used by DP for temporary grouping and using it for another command might be the problem. It’s worth a try.


Sent from my iPad using Tapatalk Pro

[difab4]

Thanks guys,
I could disable the alerts but the ever present red indicator in the audio performance window turns orange then progressively redder til playback will eventually stop, but I guess I can disable the warning.
I've tried other key commands.
Motu first suggested trashing preferences which caused it to work correctly for a very short time (minutes), then reverted. They also suggested creating a new user, which seemed to work but I tested it only a short time also and didn't want to go through the process of porting everything over from the main user. I suppose I could follow this completely through.
Thoughts?
BTW for laughs, I used DP 2.7/2408 on a B/W G3 for 15 years (1999-14) and it was rock solid the whole time, simpler to use, and easier to see. Seems that along the way things got more complicated...

Thanks again

[MIDI Life Crisis]

I’m not sure we’re on the same page. I’ve never seen the performance monitor turn orange, only green until it clips and then one red segment.

[difab4]

Yes if I replicate the issue, the box next to the processing bar in the audio performance window first turns yellow then red as things get worse. Have not seen green there. The box remains empty till something not good happens.
Thanks

[sdemott]

I had the same issues. Goto: Setup > Configure Hardware & increase the "Prime Milliseconds" setting. MOTU support suggested 500 (default is 125). FWIW, in DP8 the default was 2.5 seconds (2500 ms). The highest DP9 will allow is 1000ms.

HTH

[difab4]

Thanks Steve it worked, no longer spiking processor.
Hitting the command still turns on memory cycle though, but I can live with it.

[sdemott]

Thanks Steve it worked, no longer spiking processor.
Hitting the command still turns on memory cycle though, but I can live with it.

Check the "Commands" window. Maybe Memory Cycle got re-assigned somehow. Or at least, maybe reassigning it might stop that from happening.