[1725-SteamAudio] Mic Noise when remote user using Voicemeeter
tracked
Tony_Lewis
When remote user using mic though voicemeeter as mic input, their voice get noise added.
This issue not happen if they are on live/Open Beta build.
Remote user need to select Voicemeeter as voice input, while local user need to be on SteamAudio Beta branch.
Noise got added is something clearly noticable.
Log In
Tony_Lewis
Update: regarding this issue, some user pointing that root of cause be Voicemeeter try to use multi core inproper way, simply limit to use single core may fix it's issue.
(not tested myself so this is just idea)
［JP］Kyo
Tony_Lewis It's not that VoiceMeeter doesn't handle multi-cores properly, and there's no such fact.
The reality is that audiodg.exe, which is one of the central processes that make up the OS's audio processing, is weak against interrupt processing during high load, and this is a problem faced by Windows Audio Service (APO).
In environments using virtual mixers, DSP, etc., when the internal buffer size of the audio device is too small to be inappropriate for that environment, the buffer is insufficient due to frequent interrupt processing, and sound problems occur.
As a countermeasure against this phenomenon, fixing audiodg.exe to a physical thread improves resistance to interrupt processing, and it is simply easier to stabilize sound.
It is described as “noise occurs,”
I think the cause will change depending on what kind of sound is being made specifically.
Is the sound interrupted? Do you hear the sounds overlapping?
Is there white noise on it?
Either way, whether it's a physical audio interface or a VoiceMeeter virtual device, from Unity's point of view, they're just one of the audio devices that can be viewed via the Windows Audio API.
Therefore, it is not an effect due to differences in VRChat's build, but I think it is due to the user's environment settings, etc., but how about?
Tony_Lewis
［JP］KyoThanks for detailed clarifications. yeah I understand the issue. but things is someone need to contact Microsoft to ask for patch then.
(They works out better when contacted by business contact so)
It is white noise issue and not setting of end user issue as it seems.
(Got few advanced user with this issue so it is unlikely in this case)
As per as detailed reason why it happen, it is bug by Microsoft Windows.
As this issue only happen in Steam Audio (aka current Open Beta) branch,
Steam Audio branch has something add up transaction over audiodg.exe and voicemeeter just add up last mile stone to get this issue happen which lead to cause issue.
StormRel
marked this post as
tracked