Package: pipewire Version: 0.3.43-2 Severity: normal Dear Maintainer,
After upgrading pipewire (and related pipewire-pulse packages etc.) from 0.3.42-1 to 0.3.43-2, my audio input from my webcam was suddenly not working anymore (as in: WebRTC-based applications were complaining about not being able to use microphone input). In `pavucontrol`, under "Input Devices", it was impossible to set the device as the default input - it always switched back to "monitor of built-in audio analog stereo" or something like that. After some trial and error, I found out about the "Pro Audio" profile, and it turns out, this profile was somehow selected (without user interaction). Switching my webcam back to "Mono Input" made it possible to use again, as in before versions. Reading the pipewire FAQ, it seems the "Pro Audio" profile is not really meant to be used for devices like webcams: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#what-is-the-pro-audio-profile Would it be possible to not switch to it automatically, or only switch to it for devices that are actually compatible with this profile? Thanks, Alexander -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire depends on: ii init-system-helpers 1.61 ii libpipewire-0.3-modules 0.3.43-2 ii pipewire-bin 0.3.43-2 pipewire recommends no packages. pipewire suggests no packages. -- no debconf information
