note that having jackdbus running doesn't tell you a thing, whether your A/V system is under pipewire service or else...
try this: systemctl --user status pipewire
big question here is, are you actually running genuine jackd OR the so called pipewire-jack substitution where pipewire seamlessly emulate the ol'jack service and infrastructure?
onto the later case, if it's true, then let me tell that pipewire-jack still falls short on some niche situations, most specially on the jack-transport/timebase sync (better say async) situation... and it still have shortcomings on most recent rc ones (v0.3.85 here), so that's why I suggested you to get the qtractor transport mode to not listen to it--it's still not on par to true-jack. nuff said ;)
note that having jackdbus running doesn't tell you a thing, whether your A/V system is under pipewire service or else...
try this:
systemctl --user status pipewirebig question here is, are you actually running genuine jackd OR the so called pipewire-jack substitution where pipewire seamlessly emulate the ol'jack service and infrastructure?
onto the later case, if it's true, then let me tell that pipewire-jack still falls short on some niche situations, most specially on the jack-transport/timebase sync (better say async) situation... and it still have shortcomings on most recent rc ones (v0.3.85 here), so that's why I suggested you to get the qtractor transport mode to not listen to it--it's still not on par to true-jack. nuff said ;)
you've been advised ;)
hyu.