An idea - general oversampling rendering/freezing VST instruments - what do you think?

Made some experiments today, after reading something about which samplerate to run VST instrument in and thereby the full project.
 
The samples are at my question about RapturePro here:
http://forum.cakewalk.com/Rapture-Pro-any-enhancements-of-sound-engine-and-resample-algos-m3206885.aspx#3206885
 
So loading your VSTi inside Metaplugin is all you have to do and use 2x oversampling setting there.
Quite noticable improvement if you ask me. A little cleaner and smoother sounding.
 
Also listen for the artifacts below the actual strings, the mumbeling rumbeling noise going on there. Probably aliasing stuff and some harmonic beating probably due to that. Note that both samples above are rendered using sinc interpolation on DP for rendering.
 
Looking with a analyzer, you see at 20k-22k as drop due to the filtering of oversampling. But that is beyond what even babies here anyway. I certainly don't hear it.
 
So I thought - why not have general oversampling doing any freezing of synths - or rendering project as well?
What do you think?
 
You just run your project in your normal 44/48 or whatever - and get this as a transparent feature.
I guess a preferences setting or something is needed - maybe in plugin manager for each instrument or something.
 
I do my VST instruments inside Metaplugin to get this oversampling - but would be nice as a transparent feature for everybody.
 
You can also get this, taking you midi tracks into a project set at 96k and render audio. Then import it into your full project. But isn't this as a transparent feature soooo much nicer.
 
Does any host have oversampled freeze?
 
So make this thread hot to make Bakers notice it.
Sonar already got the best implementation of freezing I saw anywhere - you get the audio available for further work.
So make Sonar even more far ahead of everybody else.

Good input, thanks.
I ran(and bought) T4, and is not going to be another guinney pig for Jules JUCE libraries, even if I they are sold per se.
Ran T NFR 1.5 10 years ago but chose Sonar 4 Studio at that time.
Waited, and waited for Mackie to give release point on T2.
 
Only thing I miss in Sonar, compared to T is the project manager - or what they called it.
Among the more developed as I saw it 18 months ago.
I wouldn't mind something like that in Sonar - a real area to just manage projects.
 
Rack builder in T I have in Metaplugin.

I don't know if the stretch libraries used in Sonar(is it some izotope algo?) do oversampling to create less artifacts?
 
But if to use anywhere - all plugins involved must also support the oversampling rate.
48kx8=384k and not many plugins actually support that.
 
And 4 times is 192k which not all support either. But 2 times to 88k/96k would work I think.
 
I remember that some of Waves plugins in Gold Bundle got 96k - just 18 months ago. Ultrapitch and Doppler still was 48k then. Quite a few of Waves stuff still have max 96k.
 
But if using a dozen vst instruments many would probably benefit from oversampling. And each sounding noticably better will make quite a contribution to a full mix sounding very much better - a cumulating effect. Just like using a little better mikes+preamps would - if used on every track of recorded audio.

Noel and I have discussed this. It's more difficult to implement than it looks initially, but it not impossible to implement by any means.

lfm
I ran(and bought) T4, and is not going to be another guinney pig for Jules JUCE libraries, even if I they are sold per se.
Ran T NFR 1.5 10 years ago but chose Sonar 4 Studio at that time.
Waited, and waited for Mackie to give release point on T2.

T4 was really just a fix release, polishing some rough edges in T3. But then Jules got Tracktion back from Mackie and he's really been going to town! T5 was a whole new DAW, and now T6 has recently been released. It's still got a way to go before it catches up with the likes of SONAR, but at the rate it's going, Tracktion is gonna be a real contender again.