Support per-session PipeWire servers as clients to system-wide PipeWire server.
I don't know whether this is already possible because I just started learning PipeWire.
I want to be able to play sound from system cronjobs through PipeWire, but I also want to play sound in desktop environments.
One system-wide PipeWire server can do the job, but some things like portal require session d-bus which lives in each login session.
Thus, system-wide PipeWire server cannot use portal if per-session PipeWire servers are not clients to the system-wide PipeWire server.
Per-session pipewire servers should not add latency to system-wide pipewire server.
I could make system-wide PipeWire server and per-session PipeWire servers use ALSA dmix, but ALSA dmix adds latency. I want to minimize latency.