On Sun, 2005-06-12 at 12:16 +0200, Christoph Eckert wrote: > The situation is getting worse if you use more than one app > and you have to restart JACK itself. Then you have to reload > a lot of files into all applications and to redo a lot of > MIDI and JACK connections. If each particular application > could (maybe optionally) remember > > * the last loaded file > * the last used MIDI connections > * the last used JACK connections This is what LADCCA (LASH) is for. You start your programs, do your connections, and tell LADCCA to save the project. Later, when you ask LADCCA to restore the project, it will start the same programs, make the connections, and tell the programs to load their states from the project. There haven't been any new LADCCA releases in a while, but 0.4.0 works quite well for things like this. The problem is that only a handful of programs support LADCCA - which is strange, because for a typical program that already has functions to write and restore its state from a file you only need a few dozen lines of code to make it work. Call the initialisation function and tell LADCCA your JACK name and ALSA ID when you start the program, and write a timeout callback that checks for new LADCCA events a few times every second (Save, Restore, and Quit should be sufficient for most programs) - and that's it. http://lash-audio-session-handler.org -- Lars Luthman PGP key: http://www.d.kth.se/~d00-llu/pgp_key.php Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://music.columbia.edu/pipermail/linux-audio-user/attachments/20050612/b791c030/attachment.bin
