synho

swamptooth


hm. yeah this is kinda weird because even the sonitus verbs hit the cpu and don't let go... odd.  anyway sorry the breverb plugs are hitting your machine at 15%.  That's pretty unreasonable for only 5 instances on one audio track so if this is something you're thinking of doing going forward i might take a look at a new machine. 

Please explain me why I need  a new machine for  Sonar X2 if other world-class DAW's can works perfectly on my current machine?
 

Sorry, but if i had a world class daw that worked perfectly on my machine (define perfect) i wouldn't be on a forum compalining about the one that didn't/// i'd be writing.

There is no built in ability for any VST2 plugins to ignore sections of silent audio. The best you can do is bypass the plugin. 
VST3 has a way for plugins to know when a buffer is silent. DX plugins have had that feature since the dark ages of computing in the 90's :)

Noel Borthwick [Cakewalk
]

There is no built in ability for any VST2 plugins to ignore sections of silent audio. The best you can do is bypass the plugin. 
VST3 has a way for plugins to know when a buffer is silent. DX plugins have had that feature since the dark ages of computing in the 90's :)

Does prochannel modules works on VST2 protocol?

Jim Roseberry

Even if i have 200 tracks in the project with "Saturation Knob" on each?

Yeah, I get test scenarios...   
But would you use 200 simultaneous tracks (all with saturation effect) in a real production?
If so, that would be a mess...


BTW, You have the ability to apply effects "per-clip" in X2.
If you do this, they only load the CPU when the clip is actually playing.

Are you sure about this Jim? I know up to sonar 7 clip effects bin utilized CPU continuously even before and after the clip. Has this changed?

Noel Borthwick [Cakewalk
]

There is no built in ability for any VST2 plugins to ignore sections of silent audio. The best you can do is bypass the plugin. 
VST3 has a way for plugins to know when a buffer is silent. DX plugins have had that feature since the dark ages of computing in the 90's :)

Maybe Dx could take advantage of this but I know of none which throttled CPU usage in sonar. They always consumed the same amount of CPU regardless of clip present. Besides, Dx is out of the race unfortunately. 

Are you sure about this Jim? I know up to sonar 7 clip effects bin utilized CPU continuously even before and after the clip. Has this changed?

Well... I stand corrected.   


Just tried in X2a and you are correct.
The clip-based EFX do indeed load the CPU (prior to and after the clip).


I'm running a 3770k at 4.5GHz.
Had to stack four instances of Phoenix Verb on a clip to get the CPU to jump 3%
That 3% was constant.  The load existed prior to the clip... and after the clip was finished.

Must have been thinking back to my Samplitude days...   

Jim Roseberry

Even if i have 200 tracks in the project with "Saturation Knob" on each?

Yeah, I get test scenarios...   
But would you use 200 simultaneous tracks (all with saturation effect) in a real production?
If so, that would be a mess...


BTW, You have the ability to apply effects "per-clip" in X2.
If you do this, they only load the CPU when the clip is actually playing.

I have checked  effect "per-clip" in X2.
1.Not working for me too .....
2.Prochannel modules are not available in the   "per-clip"  selection  

I have checked  effect "per-clip" in X2. 1.Not working for me too ..... 2.Prochannel modules are not available in the   "per-clip"  selection  

Not working... or not releasing the CPU when the clip is not playing?
Per-clip EFX works fine here... but doesn't release the CPU when the clip isn't playing.

Clip effects are streamed silence when the clip is not playing. Its necessary to render effects tails and also to maintain sync when delay compensated plugins are present.

Even in VST3 silence processing is optional - its an optional plugin feature and not something you get automatically through VST3. Same with sample accurate automation. Most VST3 plugins do not support it. 

Noel Borthwick [Cakewalk
]

There is no built in ability for any VST2 plugins to ignore sections of silent audio. The best you can do is bypass the plugin. 
VST3 has a way for plugins to know when a buffer is silent. DX plugins have had that feature since the dark ages of computing in the 90's :)

Hi Noel,
 
I'm guessing though that the feature wasn't implemented uniformly on dx plugs.  I was wondering if the OP was having a problem with breverb in  particular, so i decided to try out a comparison to the sonitus reverb (a dx plugin) and still got the cpu loaded at a more or less constant rate, after starting audio, that didn't adjust downward on an empty audio track.  the levels on my machine were comparable, so i don't worry too much.  i do worry about 5 instances of breverb causing 15% cpu utilization... i wish we knew the ops system specs because several folks could offer feedback, i'm sure.