VST Oversampler 1.4 (with SSE/3DNow! support)

[novaflash]

quick report :
windows XP - AMD athlon 2200 xp
host : minihost, chainer

work fine (i've built a little vst insert plug. to check the stream after and before)

[Chris Walton]

1.1 stops cubase from loading. It goes though loading the plugins but when its about to open it just shuts down. After I remove the .os dlls it loads fine.

It's times like these I wish Steinberg had a demo

Thanks for trying though.

[Chris Walton]

quick report :
windows XP - AMD athlon 2200 xp
host : minihost, chainer

work fine (i've built a little vst insert plug. to check the stream after and before)

Thanks.

[MaxJoy]

Quick report 2: Orion still crashes immediately when loading an oversampled synth.

[punkrockdude]

The one I used was downloaded just an hour ago or so. In Cakewalk Sonar 6 demo it is reported as a risky plugin. Regards

[sc_a]

Not works in Win ME.

I Rename As say Instruction, But not Load my plugin. I Check for correct rename, It Correct, But not load. Pop up Say:

invalid dll name - rename me to <plugin>.os.dll


But I did rename Correct:
Claw.dll
Claw.os.dll

Not load, Pop Up say invalid ...


Sad. Help. I check Vsthost, Ext ... All same. Bad Karma?

[Genetic_Junk]

1.1 stops cubase from loading. It goes though loading the plugins but when its about to open it just shuts down. After I remove the .os dlls it loads fine.

It's times like these I wish Steinberg had a demo

Thanks for trying though.

Not a big deal for me. Work-around: I add the energyxt.os dlls into the XT folder after cubase loads and then load them into the normal energyxt as a plugin.

[RunBeerRun]

Wow a big difference, much brighter.

Tested to work in Savihost.

[punkrockdude]

I am noticeing a quite big difference with my Sonalksis Essential plugins. Squashing stuff with the compressor sounds alot better. I hope this is no imagination and that I will hear/think the same tomorrow when I've had some sleep.

[metamorphosis]

it only means that if your software synth supports the higher sample rate, it will run at that rate. If you set the card to 192khz and your synth supports a max of 44 it will run at 44.

... I still don't get it. If the host's running at 44k, and you put this on a synth, it has to downsample it again to 44k - maybe the synth sounds better at 88k, but you're introducing downsampling aliasing by doing so (am I right? No?). And then you've just got a 44k signal again, which, depending on how the synth in question works, it either going to sound better or worse than what the synth itself would have came up with at 44k.

And if the synth itself can't run at higher samplerates, it's pointless as there's no way to change the internal mechanisms of that synth to make it run at a higher rate (I am correct here and I know it).

More to the point, why not just work at 44k and render at 88k? What's the advantage of having something sounds -slightly- better only while you're mixing it?
I don't get it-
could somebody explain this to me?
Cheers-

[Chris Walton]

... I still don't get it. If the host's running at 44k, and you put this on a synth, it has to downsample it again to 44k - maybe the synth sounds better at 88k, but you're introducing downsampling aliasing by doing so (am I right? No?). And then you've just got a 44k signal again, which, depending on how the synth in question works, it either going to sound better or worse than what the synth itself would have came up with at 44k.

Nope. Read again my description in the original post...

The oversampler "hosts" another VST plugin, and oversamples it by 2. Because of this, aliasing has twice the frequency range to unfold, which means that the aliasing that enters back into the audible domain is much less, and upon downsampling, the upper range (containing only aliasing) is discarded.

And if the synth itself can't run at higher samplerates, it's pointless as there's no way to change the internal mechanisms of that synth to make it run at a higher rate (I am correct here and I know it).

I'd say 99% of synths support any samplerate.

More to the point, why not just work at 44k and render at 88k? What's the advantage of having something sounds -slightly- better only while you're mixing it?
I don't get it-
could somebody explain this to me?

Cheers-[/quote]

You can't get back quality by upsampling. If you downsample to 44.1khz and upsample again to 88.2khz you lose all the high frequency stuff that used to be between 22.05khz and 44.1khz (Nyquist theory), and upsampling it back to 88.khz won't get it back (in fact, that might actually _create_ aliasing, if the upsampling filter isn't good!).

EDIT: To add onto the creating aliasing part - this wouldn't occur in the actual upsampling step, but in any non-linear process that happens afterwards, because of intermodulation distortion.

[disturb]

looking forward to try this, i remember being pretty amazed at the difference in sound quality when making some edits at 96khz.

[tony tony chopper]

I'd say 99% of synths support any samplerate

note that I'm sure that a lot of plugins don't really like different instances running at different samplerates, even if the VST specs require it (our own plugins have optimizations that prevent this, that's the reason I didn't build oversampling in FL)

[punkrockdude]

I am noticeing some high frequency attenuation when using this plugin. It does so with any plugin I use. Use a bright track with alot of upper frequencies, I used an overhead track and I clearly heard the high hat become duller and Voxengo SPAN tells the same thing.

[tonAP]

I'd say 99% of synths support any samplerate

note that I'm sure that a lot of plugins don't really like different instances running at different samplerates

In fact I'm getting freeze by this