[BUG] Pipewire manager breaks existing links

[Packetdancer]

A number of users have reported issues with Pipewire breaking their existing configurations. As these are mostly just hanging around as side commentary in other issues (notably #876 and #873), I decided I should make a new issue to track some use cases so that there's some actual concrete setups to test with (which aren't buried in comment threads on only tangentially-related Pipewire issue tickets).

So, if you are using Pipewire and SteamVR 2.16.5 (or later, as future beta builds go out), and have a scenario where you're seeing a Pipewire configuration getting "broken" in a way that isn't expected, please add a short summary here. (Maybe even a screenshot of a patchbay visualization before running SteamVR and after it starts.)

This will help actually build some tests to ensure the Pipewire management works the way people expect/want, as much as possible.

[MooshPaw]

Hey there

The issue is pretty easy to replicate, both are related and happen consistently
Requirements: Connect a Meta Quest headset via Steam Link
(There's a chance other wireless headsets are affected as well such as Pico or Vive, but haven't seen them reported, maybe due to low usage)

What happens: External applications don't connect their nodes correctly, this includes:
Discord, browser and every app outside of Steam not having audio on the HMD
WayVR not having pipewire streams connected for screenshare
Spout2VR | Pipewire video (OBS) not receiving input despite being told to connect

Spout2VR is specially noticeable on VRChat, as any loading screen will disconnect the node from the Pipewire video source on OBS and has to be manually reconnected with tools such as qpwgraph

For the hang when disconnecting, i have more success replicating the issue when I open a game and close it before quitting SteamVR. Steam is also unable to close the process and must be killed with other methods (Terminal, GUI via System monitor or Mission Center)

As far as wired headsets go, I don't have a native SteamVR HMD, but I can connect my Quest 2 via ALVR, where i don't have a single issue regarding pipewire audio or video, suggesting it's an issue with the VRLink driver

[Packetdancer]

Hang when disconnecting/exiting SteamVR is a separate issue in the tracker (and I already have a fix for that, though it's not yet pushed into any beta build).

So, to clarify: when you talk about Discord, what you mean is you have Discord wired in Pipewire to specific outputs, and when connecting via VRLink, those connections go away and Discord is left unconnected? Or do I misunderstand?

[Packetdancer]

Okay, thanks for the edits for clarification!

That gives a good starting point, and I think I see how some of this can be cleaned up. Still interested in other failing use cases if others have some.

[MooshPaw]

This might be some of the last testing i can do for the next couple weeks due to college and stuff
I think the pipewire behavior of Steam is "sandboxed", resulting in Steam being able to communicate with Steam apps, and outside apps communicating with themselves, but not with Steam

For example, if I Screenshare on discord, route discord audio to my Headphones or Speakers, use Firefox or a music app through my headphones, etc. They all get audio and behave just fine even when connected to SteamVR

If i instead tell those apps to route the audio to the HMD they fail to do so. Apps that screenshare "from Steam" (like WayVR Screenshare) fail to create any nodes

This connects to my previous report, so any games launched from Steam will also fail to create nodes, stuff like Spout2PW from a Steam Game (VRChat, Warudo, etc)

Now screensharing from discord to a steam game seems to work fine, but probably because it doesn't intersect with steam directly, and rather use XDG Portals and call the window through other methods, whereas WayVR requires the compositor provided by SteamVR

Things that remain to be tested:

• Screen capture from OBS (also using XDG Portals rather than vkcapture or Pipewire video)
• Non-Steam games launched through Steam
• More debugging for Discord screenshare, although i did manage to screenshare i didn't have anyone to tell me if there were any issues regarding performance, quality, or specially audio.

[slice-the-idiot]

is this issue specific to steam link or is it a whole steamvr wide issue?

[slice-the-idiot]

oh and i can confirm audio when trying to capture with OBS doesn't work aswell

[MooshPaw]

is this issue specific to steam link or is it a whole steamvr wide issue?

Should only be SteamVR via Steam Link, but if you find anything with other methods, you should bring them up