Re: [LAD] [LAU] Descent synth as dssi

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Burkhard Wölfel <versuchsanstalt@...>
Cc: linux-audio-user <linux-audio-user@...>, linux-audio-dev <linux-audio-dev@...>, Ken Restivo <ken@...>
Date: Tuesday, March 9, 2010 - 7:43 pm

2010/3/9 Burkhard Wölfel :

Since I always use shell scripts to get as close as I can to a
particular set-up state, I would love to see more support for that, to
the point that it doesn't have to look like scripting to an end user.
For example, each app could respond to a message to return its state
in shell-script form, like a ~/.jackdrc file, and the session saver
would simply append these to a startup script that it can run behind
the scenes to restore the session. Of course, active connections
among apps need to be uniquely identified in some way (OSC?), and apps
should be able to accept connection specifications that are not
immediately "ready", etc., so that the segments can be run in any


"Anybody who knows all about nothing knows everything" -- Leonard Susskind
Linux-audio-dev mailing list

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAD] [LAU] Descent synth as dssi, Burkhard Wölfel, (Tue Mar 9, 6:04 pm)
Re: [LAD] [LAU] Descent synth as dssi, Julius Smith, (Tue Mar 9, 7:43 pm)
Re: [LAD] [LAU] Descent synth as dssi, Paul Davis, (Tue Mar 9, 7:52 pm)