I've had Metaplugin since version 2 came out. but with more complex things like VST instruments and anything containing samples and impulse responses, you may run into trouble. Luckily, this is usually not the case for most simple things like EQs, compressors etc. There are many more internal issues that could arise in plugins when you go past their intended sample rates. Basically the impulse is played through extremely fast and thus the cabinet emulation of such software would sound completely wrong. Now what happens if you do 16x oversampling within that kind of software and it doesn't resample the internal impulse response? You get a "mickey mouse" effect. Thus lets take an example A Guitar Amp software says that max supported sample rate is 192kHz.
My testing has proven this “sample rate support” to be baseless in most cases.It means that some plugins can have internal coding / components in such a way that they do not perform optimally, or not at all correctly, at any samplerates that are higher than what they state as supported.įor instance, older versions of various Guitar Amp emulation software that included impulse responses sometimes failed to correctly internally resample the impulses and would thus sound completely different depending on the users sampling rate. If it means aliasing, then it means a different result at different “supported” project sample rates, every time. I’m not sure what “official support” really means.
0 kommentar(er)
