Quote:
Originally Posted by lawrence_o  Dudes,
When it comes to making plug-ins there are a few thing you should know:
1) there's the framework that comes with it and that handles how audio is to be read, processed and written back to a buffer so the audio App can read the processed data.
2) The part where the processing is done, is the exact same for a given VST, RTAS or TDM plug-in!! THe only differences can be found in delay-compensation reporting and automation handling. If that's done inefficient, processing might be interrupted causing clicks or heavy CPU-loads. however, I've never seen or experience this in my plug-ins.
I really don't understand how a given manufacturer's plugins are experienced to sound differently depending on their VST-RTAS-AU-TDM format. In fact, most of them use frameworks that only do the DSP processing meaning the sound processing and leave the rest up to compile time packaging depending on the versions (meaning library choices etc.)
If it sounds differently, it ain't due to the algorythms...
Kind regards
Lawrence |
When I said I can imagine a difference between RTAS and TDM I wasn't referring to the plugin processing, I was referring the way TDM handles audio opposed to native.
I don't know what the difference is but I could sometimes hear one, even if it's a small one. And don't think that TDM sounds better because it's more expensive!
Now to say VST sound second rate to RTAS and AU and whatever or the other way round is BS.