Tapani Sysimetsä wrote:
> Tapani Sysimetsä wrote:
>> David Adler wrote:
>>
>>> google comes up with this:
>>> http://www.rncbc.org/drupal/node/76
>>>
>>> best,
>>> d
>>>
>> Nice tutorial. I use patchbay constantly, it's very handy. After setting
>> the connections in patchbay (through snapshot function or otherwise),
>> remember to save and click Activate. If you have several setups, or want
>> take the settings to another system, just load the .xml file and activate.
>>
>
> Just to make it clearer: By using patchbay you can, for instance, have
> your midi keyboard connected automatically to whatever midi-jack audio
> application(s) you wish.
>
I looked into the patchbay a bit more and I do like it.
On top of an existing session, I can add
qjackctl -a /path/to/patchbaydefenition.xml
to a session script to have persistance and the
auto-connecting feature.
This requires that qjackctl isn't running, so the
full version for scripted pseudo-on-the-fly
pachbay change is:
TEST=`ps ax | grep qjackctl | grep -v grep | wc -l`
if [ $TEST = 0 ]
then
killall qjackctl
fi
qjackctl -a /path/to/patchbaydefenition.xml
I dislike the idea of manually creating sockets and plugs
but the automatic snapshots have worked so far.
Probably I'll stick to my old workflow involving jack_snapshot
and aconnect, using the patchbay just on top if required.
-- uuuh -- thats four applications involved in making
connections, as soon as Ardour is part of the session. :)
I could add jack.plumbing and patchage and...
greetings,
d
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users
