Native PipeWire module

[teodly]

I started writing one in the past (this is the last version for the curious) but couldn't get adaptive resampling to work so shifted my focus to ALSA I/O plugin. Tonight, reading the PipeWire RTP documentation, I discovered that it should be possible to have adaptive resampling on sources other that ALSA audio interfaces:

sess.latency.msec then defines the ideal fill level of the ring buffer. If the fill level is above or below this, then a DLL is used to adjust the consumption of the buffer contents

https://docs.pipewire.org/page_module_rtp_source.html

I wonder whether native PipeWire module would have any benefit over the current approach with ALSA I/O plugin.

General stability and immunity to xruns? Personally, I would prefer to focus on the ALSA plugin stability, as JACK users would also benefit from these improvements.

Maybe naming channels in PW graph when they are renamed in DC? But that could be already done by an independent script.

Maybe exposing Dante devices in PW graph and allocating local Inferno channels automatically when these devices are connected to local nodes? Great UX for PW users, confusion generator for Dante pros used to DVS.

[MeestorX]

I would love to see this. My understanding is that jack is the "old way" of doing things, that pipewire/wireplumber is the way going forward. What do I know though, my first time doing anything at all with pw was when I found this module!

Using it under alsa seems to be working fine, now that I've figured a lot of it out, but I would LOVE to be able to get even lower latency if a native pw method would allow that?