On Thu, 15 Aug 2024 at 11:02, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Wed, Aug 14, 2024 at 08:28:06PM -0400, Marc Lavallée wrote:
I tried and it works, but I had to upgrade Pipewire to a recent version;
I tried this:
- Copied pipewire.conf to ~/.config/pipewire
- Removed the jack-dbusdetect module from context.modules
- Added the jack-tunnel module to context.modules with 2 channels
in each direction.
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.
- Start pipewire
- Jack Source and Jack Sink nodes are shown in the coppwr
'graph' window, with state = Running.
But no pipewire ports are shown in the Qjackctl connections
window. The 'Info' tabs in coppwr say Input Ports = 0 and
Output Ports = 0, even if the modules or configured for 2
channels each.
No idea what to do next.
(sorry, I'm on holidays and not really much on my computer)
Creating ports on a sink/source is part of the session manager policy.
More precisely as
part of the linking policy. Sink/source/streams can operate in
multiple modes: passthrough, DSP
or convert. The DSP mode is when port are configured with a single
channel float format and when
they are visible in JACK (we could also extend JACK to show these new
port types but many tools
tend to crash on unexpected types).
Normally Wireplumber will configure sinks/sources with their default
number of channels in DSP mode.
It will convert streams (firefox pulseaudio, ALSA clients,..) to the
DSP mode with the number of channels
of the sink they link to. This is a reasonable policy for desktop apps.
If you don't use a session manager, making a Sink/Source will thus
leave the node unconfigured. You have
however some options to do the configuration if you don't run a session manager:
1. Use the auto port config option on streams:
https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/daemon/m…
or on the sink/source
https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/daemon/m…
2. Use pw-cli to send the PortConfig to the Node manually (i don't
have an example handy).
When I get back from holidays, I'm going to make some example config
files that implement this.
For linking ports, you can use any of the jack tools you probably
already use (jack_matchmaker) or jack_connect.
Hope this helps.
Wim
--
FA
_______________________________________________
Linux-audio-dev mailing list -- linux-audio-dev(a)lists.linuxaudio.org
To unsubscribe send an email to linux-audio-dev-leave(a)lists.linuxaudio.org