Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upImprove multi-speaker and multi-mic support #3914
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 20, 2018
Member
See Pulseaudio Volume Control, by default accessible as "Audio Mixer" in volume control applet. If you have multiple cards, you can choose per-VM what card should be used. And in Input Devices / Output Devices you can choose a port.
|
See Pulseaudio Volume Control, by default accessible as "Audio Mixer" in volume control applet. If you have multiple cards, you can choose per-VM what card should be used. And in Input Devices / Output Devices you can choose a port. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
3hhh
May 20, 2018
I had seen that, but not noticed the buttons to switch sinks & sources... -_-
Thanks a lot Marek & sorry for bringing this up then - it's apparently invalid.
3hhh
commented
May 20, 2018
|
I had seen that, but not noticed the buttons to switch sinks & sources... -_- Thanks a lot Marek & sorry for bringing this up then - it's apparently invalid. |
3hhh commentedMay 20, 2018
•
edited
Edited 3 times
-
3hhh
edited May 20, 2018 (most recent)
-
3hhh
edited May 20, 2018
-
3hhh
edited May 20, 2018
Qubes OS version:
3.2, 4.x
Description
Currently the support for speakers and mic is limited to the pulseaudio default device.
Speakers
Toggling output devices and ports during runtime of an AppVM requires a user to do something like that:
This is only suitable for power users. In particular I didn't find any Qubes-specific tool to simplify that.
Only setting the default will only change it for newly started VMs.
Microphones
The situation is identical here. In particular Qubes only supports forwarding the pulse default microphone to an AppVM via its GUI application. Other microphones are not displayed in the GUI.
General notes:
Maybe some Qubes application to control which sound input or output device incl. port is assigned to which VM would help here. Maybe it could even be integrated in the qubes-vm-settings similar to the Devices tab.
Related issues:
#2724