Wallander
Senior Member
This is obvious speculation, but the Kontakt VST3 could have failed to cleanly enter bounce mode, making it subject to overload protection that's only supposed to operate in live mode. Setting bounce/offline mode is plugin-dependent functionality and is implemented quite differently between VST3 and VST2. The VST2 plugin explicitly asks the VST2 host about offline mode through a host callback, whereas the VST3 host supplies the VST3 plugin with the current offline state on every render call, and must be stored by the VST3 plugin between render calls.I've looked, and I couldn't see any code that would do this specifically for VST3 only... The actual voice processing code is plugin type agnostic and supports up to 16 threads.
I don't know the internals of Kontakt, but for clarity, there's no sign for us that a voice is dropped, but the audio just drops out from the disk-streaming portion being silent. The preloaded audio and release sample is still being presented.
Last edited: