16 Aug
2024
16 Aug
'24
3:41 p.m.
Le 2024-08-16 à 00 h 50, Len Ovens a écrit :
Note that once a ~/.jackdrc is present, and if all is closed, restarting
pipewire takes care of restarting jackd. If jackd is then stopped,
pipewire don't restart jackd, and if jacks is restarted manually (or
using QJackCtl), the tunnel does not reappear. That's probably why using
jackdbus is a "better" option.
I notice both midi.ports and audio.channels are
commented out is that
why there are three ports in each direction?
My understanding is that lines that are commented out in configs
(provided by pipewire) is a form of inline documentation with default
values.
WHat does jack.lsp -t say about:
MyPipeWireTunnel:playback_0
MyPipeWireTunnel:capture_0
Are they audio or midi?
8 bit raw midi
Does this mean they show up on the jackd graph or just
the pw jack graph?
Yes.
pipewire is
actually waiting for a ~/.jackdrc file, so once it's
created by QJackCtl, pipewire starts.
Good to know. One more question: can you start more than one jack
tunnel? Say one
for midi and one for audio? More than one audio?
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...
Marc