Re: [LAD] midi and audio connections apps output
On Wed, Apr 11, 2012 at 09:20:23AM +0400, Louigi Verona wrote: Hey guys! Hi! I was wondering if JACK, QJackCtl or Patchage or any other programs that manage audio and midi connections in JACK can output a list of connections they currently make in text format? jack_lsp -c HTH -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] midi and audio connections apps output
On Wed, Apr 11, 2012 at 02:47:11PM +0400, Louigi Verona wrote:
Please keep LAD at least CC'ed.
[jack_lsp -c]
However, this command seems to give the list of available ports. It does
not show which ones are connected.
It does show the connections, that's why jack_lsp -h says
-c, --connections List connections to/from each port
$ jack_lsp -c
[..]
system:capture_34
system:capture_35
system:capture_36
system:playback_1
PulseAudio JACK Sink:front-left
MPlayer [9864]:out_0
system:playback_2
PulseAudio JACK Sink:front-right
MPlayer [9864]:out_1
system:playback_3
system:playback_4
system:playback_5
[..]
Obviously, MPlayer [9864]:out_0 and PulseAudio JACK Sink:front-left
are both connected to system:playback_1, likewise for
system:playback_2.
In contrast, system:playback_{3,4,5..} are not connected.
--
mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] midi and audio connections apps output
Ah, thanks for clearing this up for me. I loaded a simple session and it
had numbers 1 and 2 only which I took simply for port numbers.
On Wed, Apr 11, 2012 at 3:01 PM, Adrian Knoth a...@drcomp.erfurt.thur.dewrote:
On Wed, Apr 11, 2012 at 02:47:11PM +0400, Louigi Verona wrote:
Please keep LAD at least CC'ed.
[jack_lsp -c]
However, this command seems to give the list of available ports. It does
not show which ones are connected.
It does show the connections, that's why jack_lsp -h says
-c, --connections List connections to/from each port
$ jack_lsp -c
[..]
system:capture_34
system:capture_35
system:capture_36
system:playback_1
PulseAudio JACK Sink:front-left
MPlayer [9864]:out_0
system:playback_2
PulseAudio JACK Sink:front-right
MPlayer [9864]:out_1
system:playback_3
system:playback_4
system:playback_5
[..]
Obviously, MPlayer [9864]:out_0 and PulseAudio JACK Sink:front-left
are both connected to system:playback_1, likewise for
system:playback_2.
In contrast, system:playback_{3,4,5..} are not connected.
--
mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Louigi Verona
http://www.louigiverona.ru/
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] midi and audio connections apps output
Hey guys! I was wondering if JACK, QJackCtl or Patchage or any other programs that manage audio and midi connections in JACK can output a list of connections they currently make in text format? The idea is that when scripting, you would use things like: jack_disconnect rakarrack-01:out_1 system:playback_1 jack_disconnect rakarrack-01:out_2 system:playback_2 jack_connect specimen:out_left rakarrack:in_1 jack_connect specimen:out_right rakarrack:in_2 It would be pretty cool if when using Patchage you could, for instance, ask it to output a similar connections list that you would copy and put in your script. I do notice though, that it probably would not output disconnect messages, but only connect ones. But this is still help. -- Louigi Verona http://www.louigiverona.ru/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
