when under PipeWire (PW), QjackCtl functions as a JACK client only--state is "Active" instead of "Started" in the main display--therefore you may well use the Graph, the Connections and the Patchbay without compromise; however, when in pure JACK client mode, all the Setup/Settings have no use nor meaning whatsoever: they serve only for you to start the JACK (jackd(bus)) server or service under QjackCtl premises, which is a huge mistake when PW is in charge and you don't control any aspect of the PW sub-systems with QjackCtl, ever.
Qtractor is, has been and always will be a pure JACK client, so it will work either under genuine JACK server (jackd(bus) or under the PW's JACK substitution sub-system. JACK is still the recommended way for all things pro-audio low-latency infrastructure, while PW is slowly catching-up but there are plenty of issues with the said substitution, still short from perfect, although complete at the API level, at run-time it still has some rough edges...
but if you're only targeting consumer workflows and desktop audio, you're perfectly fine now with PW. You won't miss PulseAudio the least :)
when under PipeWire (PW), QjackCtl functions as a JACK client only--state is "Active" instead of "Started" in the main display--therefore you may well use the Graph, the Connections and the Patchbay without compromise; however, when in pure JACK client mode, all the Setup/Settings have no use nor meaning whatsoever: they serve only for you to start the JACK (jackd(bus)) server or service under QjackCtl premises, which is a huge mistake when PW is in charge and you don't control any aspect of the PW sub-systems with QjackCtl, ever.
Qtractor is, has been and always will be a pure JACK client, so it will work either under genuine JACK server (jackd(bus) or under the PW's JACK substitution sub-system. JACK is still the recommended way for all things pro-audio low-latency infrastructure, while PW is slowly catching-up but there are plenty of issues with the said substitution, still short from perfect, although complete at the API level, at run-time it still has some rough edges...
but if you're only targeting consumer workflows and desktop audio, you're perfectly fine now with PW. You won't miss PulseAudio the least :)
cheers