4 Sep
2004
4 Sep
'04
10:05 a.m.
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
4 Sep
4 Sep
10:53 a.m.
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
3:35 p.m.
On Sat, 04 Sep 2004 15:36:40 +0300
Sampo Savolainen <v2(a)iki.fi> wrote:
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.
Hmm, i tried it and it looked a little awkward. Anyways, i'd prefer the
'snapshot' paradigm. Kinda like alsactl. Something like connection_state
store -f snapshot1.state, and similar for restore..
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.
Ok, i see.. Hmm, seq24 does store the port[name]s which each of its
patterns are connected to in the seq24 file. so it's actually alright. I
just need to remember to start it up as the last one in a project.
How about sending mail Mr. Buse (the author) to ask for a fix?
Hmm, i can actually live with how it's handled now. But it would stil be
nice if it rather opened its own in/out ports and autosubscribed
[optional]..
flo
3:38 p.m.
On Sat, 4 Sep 2004 19:31:28 +0200
Florian Schmidt <mista.tapas(a)gmx.net> wrote:
I hit send to early. i'll write to him to see what he thinks..
flo
How about
sending mail Mr. Buse (the author) to ask for a fix?
Hmm, i can actually live with how it's handled now. But it would stil
be nice if it rather opened its own in/out ports and autosubscribed
[optional]..
7439
days inactive
7439
days old
linux-audio-user@lists.linuxaudio.org
3 comments
2 participants
participants (2)
-
Florian Schmidt -
Sampo Savolainen