8 Jul
2007
8 Jul
'07
8:27 p.m.
Julien Claassen <julien(a)c-lab.de> writes:
Hi!
I again tried to work with lash, but failed. I should mention I only use the
console tools. I proceeded as follows:
tty1> lashd
tty2> lash_control
tty3> jackctlmmc
tty4> aconnect 16 128 # VIRMidi soundcard and jackctlmmc
tty2>
lash_control> save
(it appears to save something and says something like: telling lash server to
save project.)
When I try:
lash_control> close
lash_control> restore project-1
Doesn't do anything.
What do I do wrong? When do I exactly have to start and quit my
lash_clients? Or is the lash_control-app not yet suited to perform real saving
and loading/restoring of projects?
I'd really like to know, because I think lash can be a dead usefl thing, if
all components work as they should!
I never tried the console thingie. Some time ago lash_panel was working
for me. Questions you are asking are very good and I'd be very happy if
this thread gets some attention from lash wizards (if they exist). I
havent used lash for some time now but I think I used workflow like
this:
* start jackd
* start lashd
* start lash_panel
* start lashified apps
* interconnect them
* save and close project
* load project
* if you are lucky all lashified apps start and then get interconnected
discalimer: I havent tried this for a while. It may not work. IIRC Dave
told me once that lash_control does not work. But I may be wrong.
Is jackctlmmc working for you (does it control jack transport)?
Fact that I havent used lash for a while is becase I'm hardly missing
suitable "infrastructure" app (something like qjackctl), able to control
lash, jackd and act like graphical patchbay (like patchage). It should
be (or be able to be used as) a GTK app with dockapp (icon). It should
be able to show logs (stdout/stderr) of all "audio" apps started through
lashd (one log per app). And logs of lashd and jackd too.
AFAIK Patchage is going there. But maybe graphical patchbay should be a
separate app.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>