I just noticed - helpfile says there is to be a field in plugin manager for this render-options - but it's not in my install anyway.
 
But I tested, it does stick as a global setting once set from plugin gui.
 
so no cow on the ice....
 
The old saying "all daws sound as good" is not true anymore...Sonar sound better...

John
Why would there be a problem with the way its always been? Where is the oversampling meaningful, in what pert of the spectrum? I am a bit doubtful as to its necessity. 
  

It's desirable or necessary for plugins that do processing that creates frequencies greater than 1/2 the sample rate but do not upsample internally for whatever reason (even though they should).
 
For instance any plugin that creates distortion, saturation, etc. as well as some synths that create funky waveforms with loads of high frequency content. As I believe was discussed in the other thread, this might also include things like aggressive limiting.
 
Basically for plugins that don't do it themselves, the high frequencies get filtered out instead of folding over (aliasing/imaging) into the audible range.

drewfx1
 
It's desirable or necessary for plugins that do processing that creates frequencies greater than 1/2 the sample rate but do not upsample internally for whatever reason (even though they should).
 
For instance any plugin that creates distortion, saturation, etc. as well as some synths that create funky waveforms with loads of high frequency content. As I believe was discussed in the other thread, this might also include things like aggressive limiting.
 
Basically for plugins that don't do it themselves, the high frequencies get filtered out instead of folding over (aliasing/imaging) into the audible range.

Next time I'm having you write the eZine copy 

Sooooo........ it's 20-40% better?

drewfx1

John
Why would there be a problem with the way its always been? Where is the oversampling meaningful, in what pert of the spectrum? I am a bit doubtful as to its necessity. 
  

It's desirable or necessary for plugins that do processing that creates frequencies greater than 1/2 the sample rate but do not upsample internally for whatever reason (even though they should).
 
For instance any plugin that creates distortion, saturation, etc. as well as some synths that create funky waveforms with loads of high frequency content. As I believe was discussed in the other thread, this might also include things like aggressive limiting.
 
Basically for plugins that don't do it themselves, the high frequencies get filtered out instead of folding over (aliasing/imaging) into the audible range.

How do we know which plugs do & which ones don't?

It seems that every plugin has the menu option (see the eZine) to upsample on render, but if it doesn't work then you know that plugin can't upsample.

I don't think there's any way fro Sonar to know. We'll have to take note of which plugins we set to do this as its a permanent global setting until unchecked.

Will having the setting checked have a detrimental effect in other hosts? Maybe create an instability or something? Obviously not planned but was it tested?

It's been mentioned that the feature works best on material with a fair bit of HF detail.
 
So..... what if I'm using the same synth for 2 different uses - one for bass & one for percussion? Think Dim Pro etc.

The setting is not permanent. You could freeze one instance with upsample enabled and one without or both set the same. It may not make a difference.

mudgel

Will having the setting checked have a detrimental effect in other hosts? Maybe create an instability or something? Obviously not planned but was it tested?

It is a setting in SONAR not in the plug-in. Plug-ins will run as they always have in other hosts.

I was thinking more when I export an entire project. I don't want to start freezing individual synths before exporting.