On Sat, 04 Sep 2004 15:36:40 +0300 Sampo Savolainen <v2@xxxxxx> 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
