On Fri, Aug 16, 2024 at 10:23:51AM -0400, Marc Lavallée wrote: > It looks like wireplumber is an integral part of pipewire.
I don't think that is actually the case and stil hope that *someone* can point out what I should do in order to make it work as desired. > (rant alert) > > This system is adding to the complexity of the Linux audio stack. Even the > syntax of config files is different. It is certainly complex, and whatever documentation is there is isn't very useful. Meanwhile I've noticed another problem with the Jack Tunnel: the port names on the Jack side are apparently taken from the 'audio.position' property. Only a limited set of names (the consumer surround channels) seem to be accepted, every thing else results in 'PW:playback_UNK' and all following ports fail to be created. Assuming that all audio must be 'speaker signals' doesn't make any sense - they could be anything. Maybe there is a property to set these names, but only $DEITY knows. And why the ports only appear when wireplumber is started (but remain when it is terminated) is still a mystery. -- FA _______________________________________________ Linux-audio-dev mailing list -- linux-audio-dev@lists.linuxaudio.org To unsubscribe send an email to linux-audio-dev-le...@lists.linuxaudio.org
