Pict
Max Output Level: -90 dBFS
- Total Posts : 38
- Joined: 2011/01/29 09:53:41
- Status: offline
Is there a way to view the CPU usage of individual plugins in Sonar?
Is there a way to view the CPU usage of individual plugins in Sonar?If there isn't does anyone know of a 3rd party utility that would do the job?The CPU meter in Sonar isn't informative enough for me.
Win7 I5 quad core 2.3Ghz 8 gigs Ram 64 bit os Many are chosen few are Pict.
|
codamedia
Max Output Level: -67 dBFS
- Total Posts : 1185
- Joined: 2005/01/24 09:58:10
- Location: Winnipeg Canada
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 10:25:51
(permalink)
"Task Manager > Processes" is the best way in Windows to see how much CPU is being used by each process - however I do not believe that will help you. I'm pretty sure Sonar shows as a single process, and the plugins just load under that process, not as individuals.
Sorry, I don't know of any 3rd party app, but someone else might...
Don't fix it in the mix ... Fix it in the take!
Desktop: Win 7 Pro 64 Bit , ASUS MB w/Intel Chipset, INTEL Q9300 Quad Core, 2.5 GHz, 8 GB RAM, ATI 5450 Video Laptop: Windows 7 Pro, i5, 8 Gig Ram Hardware: Presonus FP10 (Firepod), FaderPort, M-Audio Axiom 49, Mackie 1202 VLZ, POD X3 Live, Variax 600, etc... etc...
|
brconflict
Max Output Level: -56.5 dBFS
- Total Posts : 1891
- Joined: 2012/10/05 21:28:30
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 12:34:57
(permalink)
The problem is, that the plug-ins are just that: plugged in software extensions. They aren't stand-alone programs, but rather extensions of Sonar. Unless Sonar had a tool or CPU view that could show how its own CPU utilization is being allocated, there's really no way for the OS to see it. The plug-ins act like nothing more than an open file to Sonar, and Sonar reads all the code in that file, interpreting and using it on its own. From how to tailor the audio to meet the spec's of the plug-in, to how to render the plug-in's faceplate, Sonar does all the actual "work". The plug-in is merely code loaded into Sonar.
More, it would be way difficult to see this in Waves plug-ins, me thinks, since Waves allows Sonar to load a single WaveShell.dll for using any or all of their plug-ins.
My suggestion is this. Get used to Disabling all plug-ins (CTRL+E?), and first see if that drops your CPU usage to almost nothing. Then start re-enabling plug-ins until you see one or more of a same-type of plug-in that dramatically raises the CPU usage. You may toggle the Audio Engine in the Time Window in the Control Bar, to stop anything that may be lingering after disabling the plug-ins. You may also have to Play and Stop the Project to "wake up" the effects of the plug-ins to eat more CPU.
What's I've found in the past are older plug-ins, Modeling plug-ins, Convolution Reverbs, or free plug-ins tend to eat up more CPU than well-designed commercial standard EQ's, compressors, or Effects.
Brian Sonar Platinum, Steinberg Wavelab Pro 9, MOTU 24CoreIO w/ low-slew OP-AMP mods and BLA external clock, True P8, Audient ASP008, API 512c, Chandler Germ500, Summit 2ba-221, GAP Pre-73, Peluso 22251, Peluso 2247LE, Mackie HR824, Polk Audio SRS-SDA 2.3tl w/upgraded Soniccraft crossovers and Goertz cables, powered by Pass-X350. All wiring Star-Quad XLR or Monster Cable. Power by Monster Power Signature AVS2000 voltage stabilizer and Signature Pro Power 5100 PowerCenter on a 20A isolation shielded circuit.
|
Splat 
Max Output Level: 0 dBFS
- Total Posts : 8672
- Joined: 2010/12/29 15:28:29
- Location: Mars.
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 12:43:01
(permalink)
Exactly right, it's hard to measure the performance of an accelerator pedal and steering wheel in a car for instance. Plugins are not stand alone units unlike the things they emulate (on the whole). Cheers...
Sell by date at 9000 posts. Do not feed. @48/24 & 128 buffers latency is 367 with offset of 38. Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
|
paulo
Max Output Level: -13 dBFS
- Total Posts : 6218
- Joined: 2007/01/30 05:06:57
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 13:33:41
(permalink)
If there are some individual ones you suspect of being CPU heavy (which some are) look at the difference in usage with them switched on or off. This will give you some idea of their impact to the overall usage. If you want to get some idea of the total hit of all the plugins on a given project compare the usage with them running and and with them all bypassed.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 13:36:13
(permalink)
Stack 20 of the same plug-ins in a track, disable multi-core, and at least you can get a relative idea of which ones draw more CPU.
|
Ruben
Max Output Level: -81 dBFS
- Total Posts : 472
- Joined: 2003/11/06 08:12:42
- Location: Where they play the West Coast sound
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 18:14:39
(permalink)
The Windows 8 Task Manager does a better job of separating the plugins from Sonar and if you switch plugins back and forth you can tell which ones are using more resources.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: Is there a way to view the CPU usage of individual plugins in Sonar?
2014/01/09 20:38:37
(permalink)
No, there is no way to determine the CPU usage of individual plugins except indirectly, by comparing overall usage with and without them, and even that's only a crude approximation.
Craig's suggestion is the standard way of doing it. By sticking in a whole bunch of the same plugin, you exaggerate its contribution to overall CPU usage and thereby minimize the relative impact of other variables. Even then, you're still not really measuring CPU usage directly, but rather how much of the available CPU time was being used, which is dependent on a great many factors and can vary from moment to moment.
Even if there was some standard test for plugin efficiency, performance would still be variable depending on the plugin's modes, settings and options, and even on the audio data. For example, a compressor performs fewer calculations when the input is below its threshold than when it's above it, a soft knee requires more calculations than a hard knee, and automatic release takes more work than fixed release times. All this might make it impossible to perform a meaningful comparison of two disparate compressors.
Sadly, we're stuck with anecdotal evidence for which plugins are lightweight and which ones are CPU hogs.
 All else is in doubt, so this is the truth I cling to. My Stuff
|