Chrome/chromium browser doesn’t detect microphone source from pulseaudio

Forum / NoMachine for Linux / Chrome/chromium browser doesn’t detect microphone source from pulseaudio

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #15667
    mkrisk
    Participant

    Hi,

    I am trying to make the microphone forwarding of NoMachine to work in the Chrome/Chromium browser. My setup:

    • Server side: Debian 9.1.0 (64-bit), Xfce desktop, nomachine-workstation: 5.3.10-7, chromium 60.0.3112.78-1~deb9u1, firefox 52.3.0esr, default NoMachine configuration
    • Client side: Windows 10, NoMachine Enterprise Client 5.3.10

    I start a new NoMachine “virtual desktop” session (UDP disabled) and then enable microphone in the NoMachine settings.

    When I test the microphone input in an xterm with “arecord -vv /dev/null” – the microphone works fine. However, in both Firefox (with default settings) and Chrome (with default settings) the microphone is not available. Tested on

    https://test.webrtc.org/

    https://www.onlinemictest.com/

    For Firefox the problem gets solved if I set “media.navigator.audio.full_duplex” to false in the firefox settings. The Firefox then detects “nx_voice_out.monitor” as microphone and works fine.

    With Chromium (and also Chrome) it doesn’t work and I didn’t find any setting or configuration option that would make it work. Is there something I can do to make the microphone source provided by the NoMachine pulse-audio server work with the Chromium/Chrome browser?

     

    Mikhail

     

    #16883
    Britgirl
    Keymaster

    Unfortunately, this key is not available in Chrome (Chrome developers would need to answer why that is). We’ll look into this further, and thanks very much for pointing it out.

    #19794
    Britgirl
    Keymaster

    We’ve opened a Trouble Report for this issue: https://www.nomachine.com/TR10P08889

    If you sign up to ‘notify me’ you can receive an email when the fix has been released.

Viewing 3 posts - 1 through 3 (of 3 total)

This topic was marked as solved, you can't post.