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

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.

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.

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

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.

WelI this is what I mean.. start a new project, insert plugin X and it defaults to on. Insert plugin Y and it defaults to off. How this gets defined is in plugin manager...

Doktor Avalanche
WelI this is what I mean.. start a new project, insert plugin X and it defaults to on. Insert plugin Y and it defaults to off. How this gets defined is in plugin manager...

Unless I'm misunderstanding you that's how it works, except that instead of checking it in the plug-in manager, you check it in the effect itself...which come to think of it is more efficient, because presumably you'll have the plug-in GUI and don't have to go open the plug-in manager and call up the effect. If you've chosen the option to upsample, it will remain set to upsample whenever you insert the plug-in into any project.

Anderton

Doktor Avalanche
WelI this is what I mean.. start a new project, insert plugin X and it defaults to on. Insert plugin Y and it defaults to off. How this gets defined is in plugin manager...

Unless I'm misunderstanding you that's how it works, except that instead of checking it in the plug-in manager, you check it in the effect itself...which come to think of it is more efficient, because presumably you'll have the plug-in GUI and don't have to go open the plug-in manager and call up the effect. If you've chosen the option to upsample, it will remain set to upsample whenever you insert the plug-in into any project.

Sounds good but...

Ok so what happens if I've changed some plugin settings on a new project.

Then next week I decide to bring up another project which is the final mix of a project I was working on last year. Just so happens I'm using the same plugins.... Will I have lost my mix?

Another scenario...

I'm working on Sonar at Abbey Roach studios today using Sonar. Fred is using the same studio tomorrow and inadvertantly changes the settings. We are working on seperate projects. I'm back in the studio the next day...

Doktor Avalanche
Ok so what happens if I've changed some plugin settings on a new project.

Then next week I decide to bring up another project which is the final mix of a project I was working on last year. Just so happens I'm using the same plugins.... Will I have lost my mix?

 
Depends on whether using upsampling makes a huge difference in the sound. So I think what you're asking for is a "disable all upsampling" button, right? Only problem with that is if you forget which plug-ins really benefit from it...so maybe what you want is presets of which plug-ins do or do not resample.
 
However if your experience is like mine, you'll find it's needed for a limited number of plug-ins, and the improvement in sound quality will tend to make you want to leave it on once you've identified "suspect" plugs.

Another scenario...

I'm working on Sonar at Abbey Roach studios today using Sonar. Fred is using the same studio tomorrow and inadvertantly changes the settings. We are working on seperate projects. I'm back in the studio the next day...

 
Well, that's an easy one: tell Fred to keep his effing hands off your computer.

In theory, at the higher sampling rate the foldover distortion is out of the audio range. So that's why you don't hear it.

I think you mean 20 Hz to 24 kHz beep. 

John

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".
 
 

 
I suspect that in the more obvious cases we would just naturally choose not to use plugins that sound "bad" because of the problems this addresses.
 
But in some cases, for some people it will be of benefit.

lfm
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.

 
Thats an error in the help - we had originally planned for it to be there but it didn't make sense..

I understand we now have up sampling when needed but why this feature instead of so many other things that have been requested.
Or was this something easily done on the road to another feature down the track some time?

Presumably someone designed the plugin. Perhaps he had enough understanding of digital signal processing to make that design, efficient, if not accurate to the result he had intended. Part of his design process might have been to design in upsampling where he felt that it would benefit the result of the anti-aliasing filters he also built in, or perhaps he was too stupid or lazy, or too concerned about the performance hit it would take. In any case, those filters would have been designed to work at the frequency he expected to encounter in the input to the plugin. Does it follow that providing his plugin with input frequencies beyond their design range will improve the performance of what might have been a delicately tuned system? If the result of providing an extreme oversampling at the input stage does produce an audible difference, does that indicate that doing so has resulted in a more accurate signal processing output?