[LAD] Re: Pipewire

Marc Lavallée <[email protected]> Thu, 15 Aug 2024 09:43:13 -0400
Newsgroups gmane.linux.audio.devel
Message-ID <[email protected]>
Le 2024-08-15 à 05 h 02, Fons Adriaensen a écrit :
> Jack is running with the dbus interface disabled.
> Rationale: I don't want any apps to control Jack, and dbus
> is not needed to become a Jack client.

A  Jack client named Pipewire with capture and playback ports shows in 
the graph window of QJackCtl.

And jack_lsp is reporting:

PipeWire:playback_FL
PipeWire:playback_FR
PipeWire:playback_0
PipeWire:capture_FL
PipeWire:capture_FR
PipeWire:capture_0

Output of the pw-dump command have many related config variables (or 
states); maybe you can use this information to craft a config that would 
not require jackdbus, so I suggest to enable jackdbus in order to better 
investigate.

Looking at the source, jackdbus is used to manage a pipewire sink/source:

https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/modules/module-jackdbus-detect.c

And also to inform the jack-tunnel module with parameters:

https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/modules/module-jack-tunnel.c

It looks like the parameters can also be provided by the pipewire config.

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]