FS#72982 - [obs-studio] issues with assignments of default input/output channels

Attached to Project: Community Packages
Opened by Corey Lanier (MissingPerson) - Saturday, 11 December 2021, 22:43 GMT
Last edited by Jonathan Steel (jsteel) - Wednesday, 02 February 2022, 21:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

OBS Studio, when installed, sets up two audio channels for Desktop Audio output, and Mic/Aux for microphone inputs. In ALSA/PulseAudio, this configures properly. In Pipewire, this is configured improperly, with both audio channels being configured in Pipewire as the microphone input, causing audio interference across both channels.

Expected results:

Audio channels for speakers should be configured on OBS Desktop Audio Channel, and microphone input should be configured on OBS Mic/Aux channel by default.

Additional info:
* Pipewire v.0.3.40, OBS Studio v.27.1.3 (Happens in Flatpak/Snap/Community/AUR packages)
* Verified on both Arch proper with Pipewire configured as well as Arch-based distros that default to Pipewire (e.g. Garuda)
* Other distros that default to Pipewire (Fedora 35) do not encounter this issue and work with OBS Studio out of the box as expected.
* Thread on OBS Studio forums detailing issue with Pipewire, as well as current workaround here: https://obsproject.com/forum/threads/obs-taking-microphone-as-speaker.150441/

Steps to reproduce:
Install OBS Studio after configuring Pipewire on Arch (Can also be quick setup by just installing Garuda KDE Dragonized, since it defaults to Pipewire)
This task depends upon

Closed by  Jonathan Steel (jsteel)
Wednesday, 02 February 2022, 21:10 GMT
Reason for closing:  Not a bug
Additional comments about closing:  I don't believe this is a packaging issue and we haven't heard back from you.
Comment by David Runge (dvzrv) - Sunday, 12 December 2021, 14:43 GMT
@MissingPerson: Thanks for the report.

I don't think this is a packaging issue at all though, as there is no way for pipewire as a software to specify what is being done with a client by default.

These defaults are dealt with in the context of either a pipewire-session-manager (provided by either pipewire-media-session or wireplumber, where the latter is going to be the default in the future and it is safe to switch to now already) or the client (in this case obs-studio).

I'm not entirely sure what you mean by "OBS Studio, when installed, sets up two audio channels for Desktop Audio output, and Mic/Aux for microphone inputs.". By default obs-studio does not create any inputs or outputs for a profile. When creating a profile and adding e.g. an audio input capture source of type pulseaudio, the device that is being used needs to be configured properly (use e.g. pavucontrol for that). For me, creating such a (stereo) pulseaudio-based audio input capture source connects to the first two capture channels of the hardware.

My suggestions would be to install and use wireplumber as pipewire-session-manager, if you haven't done that already and afterwards properly configure your audio device in use (if required).

I will re-assign this issue to the packager of obs-studio, however I do not believe that it is a packaging error on that side either.

Loading...