Request: Option for program utility screen/window dedicated to project plugin cpu usage
 
My use:
I would like to know at a quick glance, based on cpu usage, if I want to disable all of my plugins or just a few hungry ones when I'm recording within a busy project and latency becomes an issue. I would also like to be able to disable or and re-enable plugins for the project within that screen. Would be very appreciated here.
 
 

Hey there,
   Could you please clarify how this would be different from the existing Performance module in the Control Bar?
 
Thanks,
Mike

mesayre
Hey there,
   Could you please clarify how this would be different from the existing Performance module in the Control Bar?
 
Thanks,
Mike

If it's like the one in Reaper, it's a listing with cpu usage per plugin

Brando

mesayre
Hey there,
   Could you please clarify how this would be different from the existing Performance module in the Control Bar?
 
Thanks,
Mike

If it's like the one in Reaper, it's a listing with cpu usage per plugin

 
Yes - Brando is correct about my request. The current performance module does give cpu information in an overview type way. But no specific details!
 
I may be in the minority for this request, but having a performance monitoring / control tool would improve how I spend some of my time mixing by helping me identify where the valuable cpu power is being allocated.
 
(Sometimes "freezing" a track isn't the best solution if I'm still fine tuning settings...)
 
 

Ah, I see. So sort of a like a "Task Manager" type thing within Sonar that might give you the option to bypass individual plugins within that same window?

At least in Reaper's case, it's just a list with individual CPU hits per plugin. Assuming this is what the OP is looking for in SONAR, it would be up to the user to determine which plug-ins would be good candidates for freezing or bouncing to free up the necessary resources. Now it's trial and error based on what the user thinks he/she can afford to freeze, and gauging the success or ineffectiveness versus the main CPU meter.
Makes a lot of sense to me personally, and would likely be most valuable to those with marginal DAW's (mine) and those who use a lot of soft-synths (me too).
 

Voted.   Like Brando I'm not running anything that resembles state of the art, but I always seem to run lots of plugins.  More efficiently zeroing in those that could free up resources the most would be very convenient. 
 

stevec
Voted.   Like Brando I'm not running anything that resembles state of the art, but I always seem to run lots of plugins.  More efficiently zeroing in those that could free up resources the most would be very convenient. 
 

 
I'm in the same DAW "wish I had more power" category with a Q9550 chip. So yes, I need to manage my resources.

Q9300 here with 8GB RAM.  Low specs by today's standards but certainly solid!  Which of course is one reason I'm always leery of upgrading...    It's a first-world issue for sure.