Forum Discussion

Andy_Bowles's avatar
Andy_Bowles
Copper Contributor
Dec 29, 2021

Raw audio capture flag

In other Chromium-based browsers there is a flag "Raw audio capture", described as

"Enable/Disable the usage of WASAPI raw audio capture. When enabled, the audio stream is a 'raw' stream that bypasses all signal processing except for endpoint specific, always-on processing in the Audio Processing Object (APO), driver, and hardware."

 

I can't see this listed in edge://flags . Is there another way to disable "Raw audio capture"?

 

Background - this is why I want to disable it:

- For some Lenovo laptops that have a Conexant sound-card, in a WebRTC application, using any Chromium-based browser, the microphone volume is so quiet as to be inaudible. Changing the audio driver to a generic driver makes it slightly better, but still unusable.

- In other Chromium-based browsers, disabling "Raw audio capture" solves the problem, presumably because Conexant's signal-processing boosts the volume.

- Here is a discussion of the problem, in the context of Google Meet:

https://support.google.com/meet/thread/114537938/microphone-stopped-working-for-laptops-with-conexant-audio?hl=en

Our application is a different one, but we have the same problem.

 

  • You can disable Raw audio capture by using this command line
    "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=WASAPIRawAudioCapture
  • ChongWeiXiang's avatar
    ChongWeiXiang
    Brass Contributor
    You can disable Raw audio capture by using this command line
    "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=WASAPIRawAudioCapture
    • LeSou69's avatar
      LeSou69
      Copper Contributor
      Would you mind to be more precise? I did it by just copy and paste both on CMD and the Run Box, but this just open another window from Edge, then I tested my mic on Meet in that windows but it didn't work, so I probably did it wrong.
      • Andy_Bowles's avatar
        Andy_Bowles
        Copper Contributor
        I did it by changing the properties of the shortcut, then restarting Edge. It worked for me (but I decided it was too difficult to try to get our customers to do this).

Resources