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

Hmm.
 
There's a synth, AAS String Studio, with which I use a dll wrapper called vstOversampler. You can fish the thing out on gearslutz if curious. It makes a drastic, night & day difference. We're talking can't even recognize the patch. Thing is, since it's so different, if the oversampling were to be only applied at the bouncing stage, I wouldn't know at all what the sound would come out like. I wonder how often this would be a concern.

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.

Spencer
Hmm.
 
There's a synth, AAS String Studio, with which I use a dll wrapper called vstOversampler. You can fish the thing out on gearslutz if curious. It makes a drastic, night & day difference. We're talking can't even recognize the patch. Thing is, since it's so different, if the oversampling were to be only applied at the bouncing stage, I wouldn't know at all what the sound would come out like. I wonder how often this would be a concern.

You can freeze to check it out.

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

buh?
 
And for all these years I was under the impression that working above 48khz was useless cork sniffery... or so I was told.
 
So I dropped down my working samplerates from 96khz to 48. This was wrong?
 
Well at least now I know and have a solution to the "problem". Good thing I haven't gone all in on some of my more important projects yet at 48k. I'm assuming due to the ultra wacky nature of the plugs/sounds I like I am just the sort of dude this would affect (drum samples, amp sims, bass synths... oof).

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.

aaand now I have a question...
 
If 48 is what is needed to accurately capture sound that humans can hear (20khz x 2 to satisfy that Nyquist fellow plus a bit extra for good measure) what does that mean once it starts interacting with some of these fancier plugins?
 
Is audio that's recorded at 48khz going to interact with a 96khz plug the same way an audio file recorded at 96khz is?
 
To put it more simply... should I go back to sniffing corks?

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.

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