13 Mar
2004
13 Mar
'04
1:15 p.m.
On Sat, 2004-03-13 at 08:59, Paul Winkler wrote:
On Sat, Mar 13, 2004 at 08:10:26AM -0800, Russell
Hanaghan wrote:
Got it! You guys are great!
Thanks
On Sat, 2004-03-13 at 04:20, Steve Harris wrote:
Exactly.
On Fri, Mar 12, 2004 at 08:09:14 -0800, Russell
Hanaghan wrote:
In doing this...(I went to work on figuring some of this out and
realised a shell script is kinda like a batch file on steroids) I start the gui based apps from a console so I
can run them as root. The
functions such as the midi port connections in the sequence of opening
apps is the issue. I'm also green in this area. Have never written any
scripts before...wouldn't know where to start.
A shell script is simply a text file starting with #!, and made executable
by setting the x bit (eg. chmod a+x myscript.sh)
eg.
#!
ardour mysession
otherprogram /path/to/saved/file If I
placed Qjackctl then Another app like AMS in the same script, the
interface for Qjack would freeze until I terminated AMS. Is there a
function argument or such that separates individual app calls?
Run them in the background like so:
#!/bin/sh
qjackctl &
ardour &
hydrogen &
ams & > LASH (n?e LADCCA) is probably a better
longtem solution to this problem
> (http://lash-audio-session-handler.org/), but not many apps support it
> yet.
Yep. I'd really really love LASH / LADDCA / whatever to become
as ubiquitous as JACK.