There is no option to enable the feature in the stand alone version of Rapture, for instance. I just checked.

No it will only work inside Sonar as its a Sonar feature that shows up in the plugin.

scook
The Windows menu is being modified dynamically by the SONAR. It is not something that persists outside of SONAR. The option has to be associated with the plug-in because it affects how SONAR needs to treat the plug-in. It does not mean the plug-in itself is modified in any way. The setting and menu option to maintain the setting only exists within the SONAR environment.

Yes I understand all those points. Thanks. I'll leave it there.

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 shouldn't be necessary for properly designed plugins, but many aren't. Basically anything that messes with dynamics (including EQs) need to be oversampled. By the very nature of the processing, new high frequency harmonics will be introduced. In a band limited system, which digital sampling of course is, that will then alias back down to lower frequency content. Only way around that is to oversample, and filter, which is the right way to do it.
 
Now as to if this will matter, well depends on the content, the plugin used, and the magnitude of the change. It certainly can. There are plenty of cases where you can toggle oversampling and easily hear a difference.
 
This basically just lets you force that using the host for plugins that won't do it.

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

 
Generally a plugin will either have "upsampling" or "quality" settings or something like that, or it will be mentioned in the plugin's documentation or marketing spiel that it oversamples/upsamples internally. 
 
 

 
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.

Barring bugs or incompatibilities, I wouldn't expect it to make things worse in the many cases where it offered no benefit (unless you were deliberately going for a grungier sound). It would basically just waste a bunch of CPU processing at a higher rate and then filtering out stuff that isn't there in the first place.

Anderton
Next time I'm having you write the eZine copy 

 

Getting away from the 'some plugins'.... Which plugins?
 
Ta.

drewfx1
 
 
Barring bugs or incompatibilities, I wouldn't expect it to make things worse in the many cases where it offered no benefit (unless you were deliberately going for a grungier sound). It would basically just waste a bunch of CPU processing at a higher rate and then filtering out stuff that isn't there in the first place.

This is along the same lines as my thinking. I am at present unconvinced. I have been quite happy with the output for all the synths I use. I have never thought "gee this would sound better with oversampling".
 
 

Well if proven to work it seems to me a key feature missing (understandable as this is the first iteration) is the ability to set this override on certain plugins as a default (this could be specified in plugin manager) so everytime a particular plugin is used the setting is ticked. Set and forget if you like.

A list of plugins that may benefit from this setting could be compiled too (would probably take a community effort) and these lists could be imported. However this still leads to the question... Which plugins?

Still I wish more time was spent on existing pre Platinum features.

The setting is persistent across sessions and projects.