fluffy_little_something wrote:But sound-wise they are no match for good non-SE synths in my view.
The fact that a plugin was made with SE is totally irrelevant with regard to its sound.
The idea that it could actually matter is as wrong as it would be to say that
- Plugins sound better on MacOS than on Windows
- Plugins sound better in Samplitude than in StudioOne
- RTAS plugins sound better than VST plugins
- Delphi plugins sound better than C++ plugins
- Plugins sound better in summer than in winter
Because SE is simply a host and therefore a 'neutral entity' as far as sound is concerned. In other words it does not have a sound of its own, it simply executes the code that you tell it to execute in order to produce
sound, just like your OS does when you run your DAW and like your DAW does when you run an instrument plugin.
So if a plugin doesnt sound good then its not because it is a C++ VST plugin made with SE thats being run on Windows in StudioOne in winter. Its because the audio-code thats being executed by
SE doesnt produce a good sound. If the code would produce a better sound by calculating things differently then the plugin would sound better too, in fact it couldnt be any other way because 1+1 always
equals 2 regardless of OS, DAW, plugin format, whatever.
(Just make the test. SE loads VST plugins too, so load your favorite synth into SE, attach MIDI In and Audio Out and then save it as a new VST plugin. See if your favorite synth sounds any different now that it has been turned into a SE plugin. Of course it wont because the audio code hasnt changed, its just that SE is now passing it to the host much like a VST chainer would. And its exactly the same with SE modules, which too are DLLs just like your favorite synth, only with a .sem file extension.)