Is the default ON or OFF??? (can't get that neither from documentation nor this thread ... and haven't installed yet)
 
Anyone having project sample rate at 96 kHz tried this yet? I assume it would oversample to 192 kHz ... and work fine ... and I would hear it ;-) ... and CPU would not melt ... or am I too optimistic???

Upsampling is off by default. You have to enable on a per plugin basis.
Upsampling is active upto 192K if you need it :-) it is grayed out in projects at higher rates.
Resampling is done in fast bounce mode so it should be no problem for any cpu, though it will add load.

Noel Borthwick [Cakewalk]

Doktor Avalanche
Well I don't know of any global settings that can get changed in Sonar, that can alter sound, other than via preferences and plugin manager. Correct me if I'm wrong? Plenty of studios share DAW computers as you know...

If you have a multi user setup and care about someone changing your settings, you shouldn't be sharing the same user profile. That said all the resampling settings are stored in aud.ini (which is per user) so you can easily backup and restore the config settings if you need to. And even latency settings can "alter sound". There are some plugins that sound different at different buffer sizes. 

And then run Sonar as Administrator ;)

I've never seen a recording studio set up additional user accounts. I agree they should but if they are using old plugins such as pentagon which does not store settings in the correct area of the registry, you know life isn't that simple.

Point is up until now I knew that only that altering in preferences and plugin manager will change global settings. Changing global setting in preferences or a setting section has been standard for some time in almost every app I can think of (no doubt somebody will find something obscure to prove me wrong).

Otherwise if a global setting gets changed elsewhere it generally comes with a warning... 'All settings for this plugin will be changed are you sure?'

It's a secret...

Tom Riggs
I can state that TruePianos benefits from the upsampling. I read that many of the guitar amp sims might benefit but which ones?  I have guitar rig 3 and 4 that came with Sonar versions.
 
What about the reverbs, chorus and phasers etc that come with Sonar? Lets make a list of the plugs that seem to be improved by this new feature.
 

 
Now that we can find out, we will find out. I'd start with any instrument that uses Reaktor, like Prism. Also amp sims. Try the amp sim internal oversampling and compare with upsampling, then enable internal oversampling and do upsampling and compare that.

I've confirmed a couple of things with this new option. I had 4 tracks with the same plug and enabling upsample on 1 does indeed turn it on for all instances of the plug. Another interesting thing happened when I messed up my install of Sonar. I had to do a roll back and then D/L the current version. When I checked on the plugs I configured to upsample prior to the problem, they were still set to upsample. This is really great because it looks like one less thing to mess with after the monthly updates.

The upsample switches for each plug-in are stored at the bottom of aud.ini
For details, see the "Upsample settings" section near the bottom of http://www.cakewalk.com/D...mp;help=Mixing.25.html

Anderton
Now that we can find out, we will find out. I'd start with any instrument that uses Reaktor, like Prism. Also amp sims.

The full version of Reaktor allows for upsampling internally (and for good reason, as it's absolutely necessary sometimes!).
 
Some have stated that in the free Reaktor Player the upsampling options were grayed out, but I'm not 100% certain whether that's a configuration issue or a limitation of the free player as I have the full version.

An interesting commentary that suggests local re-sampling (which seems to be the point of this new feature) is inherently inferior to doing the whole project end to end at a higher sample rate:
https://varietyofsound.wordpress.com/2012/11/02/working-itb-at-higher-sampling-rates/
 
The specific issues discussed are related to plugins that upsample themselves, rather than to plugs that are fed locally upsampled input by their host. Of course back in the dark ages when this was written DAW's did not offer this feature. The author observed that if he re-sampled a project at a higher SR, he found it necessary to re-do the mix at the end of the process, without any detail about what he found needed fixing.
 
Can someone explain how one can determine (without using the notoriously unreliable ear) that foldover distortion has occurred during processing? It would seem that the designers of expensive plugins must have a way to do this, and should be able to provide something more than audiophilic necromancy that their products would or would not benefit from such treatment. Maybe someone at Cakewalk actually knows and has asked some of these people.
 
 

It would be nice if you could right click the synth name in the synth rack and select upsample on render...