MOTUnation.com

I know this is probably 10,000th-plus post on this issue, but what do you have to do to get a plugin to completely stop using CPU in DP?

Disabling the track doesn't work for me. Disabling & Bypassing doesn't do it. Disabling & Bypassing & Turning off the track's Automation Recording/Play doesn't do it?

I there any way to do this?

I see it in my Effects Performance window using up CPU no matter what I do?

Thanks!

Hmmm... that's truly bizarre. I you actually *disable* as opposed to simply "play disabling" a track, it shouldn't be using ANY CPU. I need to look at this.

Sure sounds like you are Muting (Arrow), not Disabling (Round.)

What I meant was taking a track out of play?

Is there another way to disable?

I don't have a right-clickable mouse, so I kind of forget I can do that, but control-clicking the track doesn't show a viable option.

Thanks!

JSmith1234567 wrote: ↑Tue Jul 25, 2023 11:55 am What I meant was taking a track out of play?

Is there another way to disable?

I don't have a right-clickable mouse, so I kind of forget I can do that, but control-clicking the track doesn't show a viable option.

Thanks!

Accidentally deleted you screenshot... sorry. Hazards of being Admin is sometimes I mean to "Quote" a post and I accidentally choose "Edit."

Anyway, you should have a column called "ENA" for "Enable." Click the little blue ball to disable the track.




If you don't see the "ENA" column, double click on the the column headers in the Track Overview and it should open the prefs panel. Make sure "Enable" (red arrow) is checked. That should allow you to truly "disable" a track freeing up CPU from plugins on that track.

As you may already know, V-rack is your friend when it comes to save CPU.
Most of my CPU-hog plugins lay in V-racks.
Disabling a V-rack does free CPU. And disabling V-rack is just a click away.

Applies only to bus-FX (reverb, delay, etc) and master-track compressors (Unisum, Ozone, etc).
Hope this helps.

daniel.sneed wrote: ↑Tue Jul 25, 2023 1:26 pmApplies only to... master-track compressors (Unisum, Ozone, etc).
Hope this helps.

Yep... I need to adopt that workflow as the plugins in my Master Fader track affect latency of VIs when tracking.

Note that unless CPU is a problem, muting is better than disabling. Muting just changes the output level to zero. Disabling removes the resources for the signal path, so when you enable the track again, there will be a delay and probably some glitches while the signal path is re-established.

bayswater wrote:Note that unless CPU is a problem, muting is better than disabling.

Indeed. Although I think the OP was concerned primarily about the CPU hit?

Thank you all!

I just did that and it indeed works.

I didn't have Enable in my Tracks Window preferences before.

Didn't actually know it existed.

This is terrific as I can now keep all sorts of parallels loaded and just enable them if I need them.

Thanks again!

This is still fantastic, but the only odd thing about it is that if I have a plugin open on the desktop. disabling the track makes it go blank as expected, but after re-enabling the track, the GUI is still blank.

If I close the GUI and reopen it, it's not blank anymore?

Not a dealbreaker, but weird!

JSmith1234567 wrote: ↑Wed Jul 26, 2023 6:48 am This is still fantastic, but the only odd thing about it is that if I have a plugin open on the desktop. disabling the track makes it go blank as expected, but after re-enabling the track, the GUI is still blank.

If I close the GUI and reopen it, it's not blank anymore?

Not a dealbreaker, but weird!

Hmmm... sounds like a bug. I bet it's probably certain plugins and not all of them, right? Your signature says you're on DP 11.03, is that correct? You can try DP 11.22 and see if it gets better. You CAN have more than one version of DP on your Mac at once. Just be sure to rename DP 11.03 first. Before running the DP 11.22 installer, change the name of the app in the Finder from "Digital Performer" to "Digital Performer 11.03." Then run the DP 11.22 installer and it will not overwrite your older version. The new version will appear as "Digital Performer." Out of habit, and caution, I always append the version number to the name of the DP app after installing in case I want to revert to using an older version.

Isn't why the VST3 version came in to existence?
(Lower or disable CPU usage when not in use)

Regards.

James Steele wrote: ↑Tue Jul 25, 2023 4:52 pm

bayswater wrote:Note that unless CPU is a problem, muting is better than disabling.

Indeed. Although I think the OP was concerned primarily about the CPU hit?

Quite possibly. My comment was for general consumption.

bayswater wrote: ↑Wed Jul 26, 2023 6:28 pm

James Steele wrote: ↑Tue Jul 25, 2023 4:52 pm

bayswater wrote:Note that unless CPU is a problem, muting is better than disabling.

Indeed. Although I think the OP was concerned primarily about the CPU hit?

Quite possibly. My comment was for general consumption.

Ahhh... well it was yummy!