Description
When JamesDSP is running, newly opened applications always route their audio
output to the JamesDSP virtual sink, even when a different physical device is
set as the default sink in WirePlumber.
Environment
- JamesDSP version: jamesdsp 2.7.0-0-g30a30aa (Pipewire flavor)
- PipeWire version: 1.6.5
- WirePlumber version: wireplumber Compiled with libwireplumber 0.5.14 Linked with libwireplumber 0.5.14]
- Distribution: Omarchy (Arch linux)
Steps to reproduce
- Set a physical audio device as default sink via
wpctl set-default <id>
(confirmed in wpctl status with * marker and in
Default Configured Devices section)
- Launch JamesDSP
- Open any audio application
- Observe in
wpctl status → Streams that the new stream routes to
JamesDSP Sink instead of the configured default sink
Expected behavior
New audio streams should respect the system default sink configured in
WirePlumber. JamesDSP should not automatically intercept streams unless
explicitly selected by the user or configured to do so.
Actual behavior
JamesDSP virtual sink takes over all new streams. The only workaround is to
manually reroute streams using a tool like wiremix after each application launch.
Workaround
Manually reassign streams via wiremix or pw-metadata after each application
launch. Not viable as a long-term solution.
Description
When JamesDSP is running, newly opened applications always route their audio
output to the JamesDSP virtual sink, even when a different physical device is
set as the default sink in WirePlumber.
Environment
Steps to reproduce
wpctl set-default <id>(confirmed in
wpctl statuswith*marker and inDefault Configured Devicessection)wpctl status→ Streams that the new stream routes toJamesDSP Sinkinstead of the configured default sinkExpected behavior
New audio streams should respect the system default sink configured in
WirePlumber. JamesDSP should not automatically intercept streams unless
explicitly selected by the user or configured to do so.
Actual behavior
JamesDSP virtual sink takes over all new streams. The only workaround is to
manually reroute streams using a tool like wiremix after each application launch.
Workaround
Manually reassign streams via wiremix or
pw-metadataafter each applicationlaunch. Not viable as a long-term solution.