Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[PulseAudio] Chrome/Chromium doesn't work correctly with the plugin #29

Closed
werman opened this issue Jun 25, 2020 · 2 comments · Fixed by #38
Closed

[PulseAudio] Chrome/Chromium doesn't work correctly with the plugin #29

werman opened this issue Jun 25, 2020 · 2 comments · Fixed by #38

Comments

@werman
Copy link
Owner

werman commented Jun 25, 2020

It is observed that Chrome/Chromium doesn't work correctly with the monitor of null sink we create, not only it doesn't use it - it doesn't use the raw output of the mic.

Also see https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/120
@werman werman pinned this issue Jun 25, 2020
@lawl
Copy link
Contributor

lawl commented Jul 1, 2020 •
edited
Loading

I've stumbled across a solution for this here

Running:

pacmd load-module module-remap-source master=mic_denoised_out.monitor source_name=mic_remap source_properties="device.description='Denoised_Microphone'"

Creates an input source that I can just select in programs (instead of forcing it on them with pavucontrol. Side note: Couldn't get it to accept 'Denoised Microphone' with a space. But otherwise works fine for me.

Side note 2: I had no problem forcing the monitor on chromium with pavucontrol.

@werman
Copy link
Owner Author

werman commented Jul 1, 2020

Thanks for letting me know!

@lkiesow lkiesow mentioned this issue Jul 5, 2020
Merged
@werman werman closed this as completed in #38 Jul 5, 2020
graph-inc pushed a commit to graph-inc/xpra that referenced this issue Sep 11, 2023
Create Xpra-Mic-Source pulseaudio remapped source for Chromium
5ff47fc 
Applications like Chrome and Chromium do not accept to record from a
monitor device, like "Monitor of Xpra Microphone" device, as reported
at Xpra-org#1221
or werman/noise-suppression-for-voice#29
and so they report that no microphone is connected.

A remapped device resolves this issue by creating a normal (non-monitor)
source device.

The name of the remapped device is **Xpra-Mic-Source** and not
**Xpra-Microphone-Source** because the `get_pulse_device` function from
the `xpra/audio/gstreamer_util.py` file expects to find exactly one
sink device match when looking after the **Xpra-Microphone** name.
totaam pushed a commit to Xpra-org/xpra that referenced this issue Sep 11, 2023
@totaam
Create Xpra-Mic-Source pulseaudio remapped source for Chromium
c53a983 
Applications like Chrome and Chromium do not accept to record from a
monitor device, like "Monitor of Xpra Microphone" device, as reported
at #1221
or werman/noise-suppression-for-voice#29
and so they report that no microphone is connected.

A remapped device resolves this issue by creating a normal (non-monitor)
source device.

The name of the remapped device is **Xpra-Mic-Source** and not
**Xpra-Microphone-Source** because the `get_pulse_device` function from
the `xpra/audio/gstreamer_util.py` file expects to find exactly one
sink device match when looking after the **Xpra-Microphone** name.
@bobobo199733 bobobo199733 mentioned this issue Mar 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update PulseAudio Documentation lkiesow/noise-suppression-for-voice
2 participants
@lawl @werman