On Wednesday 26 July 2007 16:52, linux-audio-user-request@xxxxxxxxxxxxxxxxxxxx wrote: > Message: 5 > Date: Thu, 26 Jul 2007 00:14:47 +0200 > From: Florian Schmidt <mista.tapas@xxxxxxx> > Subject: [ANN] lash_wrap - A small LASH wrapper > To: linux-audio-dev@xxxxxxxxxxxxxxxxxxxx > Cc: A list for linux audio users > <linux-audio-user@xxxxxxxxxxxxxxxxxxxx> > Message-ID: <200707260014.47956.mista.tapas@xxxxxxx> > Content-Type: text/plain; charset="us-ascii" > > > Hi, > > i planned to write this for quite a while and finally got to it [though > it's not 100% working yet - It's a small program. If experienced unix > hackers might look over y use of waitpit i'd be happy :)]: > > lash_wrap > > It's a small program which can be used to "smuggle" non LASH apps into a > LASH session provided they meet some requirements: > > - If they are jack clients, there must be a way of determining the jack > client name at startup time > > - If they are ALSA seq clients the client ID must be known at client > startup time or their alsa seq name must be uniquely determined > > - They must require a way to specify their state via the commandline (e.g. > we can tell ardour to load a certain ardour session at startup) > > So here's how i would smuggle ardour2 into a LASH session: > > lash_wrap -j ardour -- ardour2 ~/sound/ardour/brazil/brazil.ardour > > The -j [--jack-name] option tells lash_wrap it must register the jack > name "ardour" with LASH. the "--" seperates the options for lash_wrap from > the commandline to start the program in question. > > If we wanted also all ALSA SEQ connections of ardour to be restored we > could do: > > lash_wrap -a ardour -j ardour -- ardour2 > ~/sound/ardour/brazil/brazil.ardour > > The -a [--alsa-name] option specifies a name which will be used to find out > the client ID of ardour by regularly searching all ALSA clients until one > named "ardour" is found. This ID is then passed to LASH. > > CAUTION!!!! YOU MIGHT LOSE WORK!! READ ON: > > - lash_wrap does not care for saving the state of the app in question. So > before hitting "close" in your favourite LASH session handler, be sure to > save the session in e.g. ardour manually. > > - if the passed jack or alsa client names do not match for whatever > reasons, then connections won't be restored properly. > > You have been warned. Nonetheless this might be useful for people who > otherwise use scripts to manage their audio sessions. Just to say thank you for lash_wrap. Seems to work as you stated. I tried it with Ardour, Audacity and ReZound and as long as you save your work before closing it works well. Thank you! _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
