Hello,
qjackctl has a very good patchbay, where you can define input and output
ports and define how these should be connected. It handles both jack
ports and alsa sequencer ports.
The reason why seq24 isn't visible in aconnect or qjackctl is because
how seq24 was programmed.
There are (at least these) two ways of using the alsa sequencer api to
write sequencer data:
1. Open a connection to an existing sequencer port and writing
MIDI to that one.
2. Create an output port for the process in question and write
MIDI commands to that output port.
seq24 uses method 1. which leaves routing to the prorgam itself. IMHO,
the wrong way. The idea behind the sequencer ports is to let the user
patch his/her applications any way they like.
How about sending mail Mr. Buse (the author) to ask for a fix?
Sampo Savolainen
On Sat, 2004-09-04 at 15:02, Florian Schmidt wrote:
> Hi,
>
> i'm looking for two simple shell scripts, but since my scripting
> wizardry is [very] limited, i ask for help here.
>
> 1] this one uses jack_lsp and aconnect to find out the current
> connection state and writes it into a file somewhat like this:
>
> ---snip
> [jack]
> SuperCollider:out_1 alsa_pcm:playback_1
> SuperCollider:out_1 alsa_pcm:playback_2
> SuperCollider:out_1 bridge-1183:meter_1
> .
> .
> .
> .
> [alsa]
> seq24:out0 SuperCollider:in0
> .
> .
> .
>
> 2] The other one rebuilds the connection state from this file [first
> disconnecting everythignm, then going through above file]
>
> I know LASH is probably the way to go for this, but is it finished? is
> it usable? So i ask if anyone has already hacked up such a script[s]
> and/or has the wizardry to hack one up?
>
> Btw: does anyone know why seq24 doesn't show up in the aconnect -io -l
> output?
>
> flo
