On Sun, 30 Jan 2022 12:34:41 +0000 John Murphy wrote:
So; I can carry on using QjackCtl and its Patchbay, or
work via a meterbridge,
Even Sox plays (and gets its wires made):
$ play -n synth sine 440
The linkage looks like:
$ pw-link -l
alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX0
|<- ALSA plug-in [sox]:output_FL
alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX1
|<- ALSA plug-in [sox]:output_FR
ALSA plug-in [sox]:output_FL
|-> alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX0
ALSA plug-in [sox]:output_FR
|-> alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX1
Which is hardly different to the links I make manually for jack-play:
$ jack-play -u a48k.wav
$ pw-link -l
alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX0
|<- jack-play:out_1
alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX1
|<- jack-play:out_2
jack-play:out_1
|-> alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX0
jack-play:out_2
|-> alsa_output.usb-EDIROL_M-16DX-00.pro-output-0:playback_AUX1
But I do see that the connecting links show up dotted in Helvium.
pw-play works, of course, but has no jack_transport awareness option.
Could someone with Pipewire just test that jack-play doesn't play for them
either (without going via a meterbridge) before I post it as a bug?
--
John.