Page 1 of 1
Posted: Sat Nov 26, 2005 2:03 am
by Kymeia
Is it possible to make a plugin for Scope that does this - it would be great to use with synths, samplers and VSTi's to make them more analog in sound - many VSTi's already use optional oversampling (eg Sytrus, Vanguard, Z3TA) but it always has a high price in terms of CPU overheads.
Posted: Sat Nov 26, 2005 5:24 am
by djmicron
flexor can do the job.
Posted: Sat Nov 26, 2005 9:24 am
by Kymeia
How?
Posted: Sat Nov 26, 2005 10:36 am
by djmicron
just use some of the flexor's modules to obtain a warm sound.
For example, try my audio unison in the modular patches section.
To be honest there is not a vst instrument with the warmth of the most of scope synthesizers and effects this is also true with the 2x oversampling, that double the internal sampling rate of the plug in, but using scope, we don't need it ...
Micron
<font size=-1>[ This Message was edited by: djmicron on 2005-11-26 10:45 ]</font>
Posted: Sat Nov 26, 2005 12:09 pm
by alfonso
Flexor filters and saturation modules are really good for anything goes through.
Posted: Wed Nov 30, 2005 10:08 am
by at0m
Hoi,
Apart from digital synthesis aliasing in audible spectrum when working at 44.1 kHz, The difference in percieved warmth also lies in the inherent instability of analog modules, best example is the change of sound as the machine warms up. I like to fake this instability by using some modulation to randomise parameters just a tiny bit. Mind, however, that this goes by expense of DSP use -just like oversampling- and thus won't always be popular on regular DSP devices. For your modulars, however...
djmicron and alfonso talk about flexor's filters, but there's also flexor's oscillators, whose (non)aliasing properties are described
here.
Afaik, the only plugins using a technique of oversampling on the platform are Sonic Timeworks' filters and EQ's. They go for 64bit precision internally, but their samplerate remains the same, so this isn't the anti-aliasing oversampling you're after...
On the other hand, there is (and will be) no such thing as an oversampling module, you will have to construct it for each occasion. If possible, each and every atom involved should be rewritten. Therefor I suggest slaving Scope to a 88.2kHz device, and downsampling it later. Using 88.2kHz, aliasing will be above audibly spectrum and as such percieved inexisting. For each and every plugin, without reprogramming the whole system.
Hope this explains a bit,
at0m.