When playing an album on bandcamp, the firefox node is destroyed and recreated between every two tracks (and also when manually moving the playhead within a track).
Problem is, the patchbay is not always updated with the new firefox node. Track still plays fine due to firefox being autoconnected to the system audio outputs. But, if I defined a custom route for firefox' audio in the patchbay, this route is not realized by qpwgraph until I perform an action which leads to a patchbay update after all. (running pw-link -l in a terminal is enough, or just moving the playhead for a second time).
To reproduce, it's easiest to play a track on bandcamp, notice the node and connection in the graph, and then move the playhead manually a bit. You'll see the firefox node disappearing and staying gone while still hearing the audio. Then run pw-link -l in terminal, and observe the firefox node reappearing.
Now, route firefox' audio to a custom location (I used jack_mixer) instead of the system output, save the patchbay and make it exclusive. Repeat the above, and notice the custom route is only reinstigated after running pw-link -l. Between moving the playhead and running pw-link -l, the audio will be routed to the system output (jack_mixer will register no sound at all in this interval).
When playing an album on bandcamp, the firefox node is destroyed and recreated between every two tracks (and also when manually moving the playhead within a track).
Problem is, the patchbay is not always updated with the new firefox node. Track still plays fine due to firefox being autoconnected to the system audio outputs. But, if I defined a custom route for firefox' audio in the patchbay, this route is not realized by qpwgraph until I perform an action which leads to a patchbay update after all. (running pw-link -l in a terminal is enough, or just moving the playhead for a second time).
To reproduce, it's easiest to play a track on bandcamp, notice the node and connection in the graph, and then move the playhead manually a bit. You'll see the firefox node disappearing and staying gone while still hearing the audio. Then run pw-link -l in terminal, and observe the firefox node reappearing.
Now, route firefox' audio to a custom location (I used jack_mixer) instead of the system output, save the patchbay and make it exclusive. Repeat the above, and notice the custom route is only reinstigated after running pw-link -l. Between moving the playhead and running pw-link -l, the audio will be routed to the system output (jack_mixer will register no sound at all in this interval).
pipewire 1.0.5 qpwgraph 0.7.8.2 Linux Mint 22