Selecting virtual input devices is affected by system input device
- PipeWire version (
pipewire --version
): 0.3.49 - Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
): Arch Linux - Desktop Environment: KDE Plasma
- Kernel version (
uname -r
): 5.17.1-arch1-1
Description of Problem:
After running a system update, involving updating pipewire, removing all my old configs and making new ones, I see inconsistent behaviour regarding selecting virtual devices in applications.
I'm using a Behringer UMC204HD, with this config in https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-devices#behringer-umc404hd-micguitar-virtual-sources in /etc/pipewire/pipewire.conf.d/behringer.conf, 404 changed to 204. I used this setup earlier to run my mic through EasyEffects and guitar through Guitarix.
My application and system settings interact in odd ways, this is my usual setup:
which after my update produces no sound when monitoring EasyEffects output. Selecting "UMC Microphone" or "UMC204HD 192k Pro" in KDE will let it produce output and it does not playback input from the guitar port. Selecting "UMC Guitar" will use the guitar port for input, unless I select "UMC Microphone" first, in which case it will use the microphone. Selecting "UMC204HD 192k Pro" in the EasyEffects options will behave as expected (Guitar and mic input, regardless of KDE settings). Selecting "UMC Guitar" in the EasyEffects options will input guitar with "UMC Guitar" in KDE, microphone with "UMC Microphone", microphone and guitar with "UMC204HD 192k Pro" and nothing with "EasyEffects Source".
This is not solely an EasyEffects issue, as Guitarix similarly also cares about which input device I've selected in KDE. I can't really make sense of this behaviour, but it seems weird and connected to virtual devices or at the very least, how my virtual devices are configured.
The expected behaviour is that I should be able to choose any input device in an application and it would use that as input, regardless of what my system settings have configured.
Additional Info (as attachments):
-
pw-dump > pw-dump.log
: pw-dump.log I suppose I haven't actually concluded this is caused solely by pipewire and could not possibly be a KDE issue, but at this point I'm not sure how I would verify that.