AUDIO BUG: Audio Stream might stop, even after hours, we can suddenly get pop and cracks and/or no more sound (application needs to be restarted). It’s now sure that WASAPI Exclusive mode is not stable by design and can produce different types of bugs appearing even after hours of well working audio streaming: We have found so many issues in WASAPI (Windows Audio Session API) that we have made a kind of classification to describe them.
Voicemeeter 1.0.0.8 should let you take advantage of WASAPI Exclusive mode, bringing better sound quality and smaller latency on last Windows Operating Systems (VISTA, WIN7, WIN8 32/64 bits).Īgain we had to compile a new version to fixe latest WASAPI bugs. So while one can play sound at 44103 Hz the other can do it as 44089 Hz and these values are changing in the time and producing different hearable strange effects… However, this synchronization is usually not precise enough to connect 2 speaker system together without getting in air some “comb effect” like flange, chorus etc… You might be aware that both audio devices (A1 and A2), especially when implemented on 2 different audio boards, are playing audio according different clocks (with different time drift). This can now be done in the System Settings Dialog Box. If you want to improve monitoring synchronization, you have to introduce a delay on Output A1 (e.g. Output A1 is the main output of the audio engine and is usually in advance compared to Output A2.
2- System Settings Delay options to “synchronize” output A1 and A2. This is typically the case when connecting mono microphone to audio pro devices (usually handled by ASIO driver) providing regular stereo recording device for each couple of i/o. 1- ‘mono’ switch (L+R) on both physical inputs, useful to people using audio devices providing signal on a single channel (even for stereo device). This last Voicemeeter version (1.0.0.8) fixes different bugs (mostly due to WASAPI Exclusive mode instability) and brings 2 new functions:
0 kommentar(er)
