Discussing Voicemeeter Audio Interface
Posted: Sun Mar 20, 2016 9:49 am
As virtual audio device, Voicemeeter could provide a proprietary interface to process audio signal, exactly like it was an audio board. Then it could be possible for an application to process Audio signal coming in Voicemeeter, Audio signal going out from Voicemeeter and why not Audio Signal inside Voicemeeter (insert).
This could be done through VoicemeeterRemote DLL and provided by a very simple API to install a callback in your application… to be able to process signal of Voicemeeter: it means all synchronized channels in the same samplerate of Voicemeeter main stream (given by output A1 device).
nStream will say what audio stream you want to receive in your callback:
-The main stream: all Voicemeeter inputs (read only) and all outputs (r/w).
-The pre-fader insert stream: all Voicemeeter inputs before fader (r/w).
-The pre-fader BUS stream: all Voicemeeter outputs before fader (r/w).
These 3 interfaces will be independent together and independent from the remoting session (login/logout), then 3 different application could access these 3 different callback mechanisms.
This could be done through VoicemeeterRemote DLL and provided by a very simple API to install a callback in your application… to be able to process signal of Voicemeeter: it means all synchronized channels in the same samplerate of Voicemeeter main stream (given by output A1 device).
Code: Select all
VBVMR_RegisterCallback(nStream, paramstruct);
VBVMR_UnregisterCallback(nStream);
-The main stream: all Voicemeeter inputs (read only) and all outputs (r/w).
-The pre-fader insert stream: all Voicemeeter inputs before fader (r/w).
-The pre-fader BUS stream: all Voicemeeter outputs before fader (r/w).
These 3 interfaces will be independent together and independent from the remoting session (login/logout), then 3 different application could access these 3 different callback mechanisms.