[LAD] Re: Pipewire
Marc Lavallée <[email protected]> Fri, 16 Aug 2024 15:08:58 -0400
| Newsgroups | gmane.linux.audio.devel |
|---|---|
| Message-ID | <[email protected]> |
Le 2024-08-16 à 09 h 41, Marc Lavallée a écrit : > I don't known, but It's possible to add more audio channels if using > defined audio positions (which mean that 64 channels need to have a > set of 64 defined audio positions). I was unable to add more midi > channels. Maybe jackdbus is required... Le 2024-08-16 à 11 h 24, Fons Adriaensen a écrit : > 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. I also noticed but did not mention. For a set of playback_UNK pipewire sinks, there's only one playback_UNK jack client. > 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. There's a spa_audio_channel enumeration : https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/spa/include/spa/param/audio/raw.h AUX0 to AUX63 can be used to define an audio.position set. > And why the ports only appear when wireplumber is started > (but remain when it is terminated) is still a mystery. Or in a my experience, why they *disappear* when wireplumber is started. Marc _______________________________________________ Linux-audio-dev mailing list -- linux-audio-dev-cunTk1MwBs/[email protected] To unsubscribe send an email to linux-audio-dev-leave-cunTk1MwBs/[email protected]