12 Mar
2004
12 Mar
'04
11:10 p.m.
Was wondering if it is possible to write a relatively simple startup
script to start Jackd, AlsaModular synth with my specific file/patch
(AMS will start Jack on its own too) then patch capture 1 & 2 to AMS
then AMS to PCM's out, and then "wire" my midisport 2x2 port "A"
to AMS
midi in?
It would be nice to boot at the gig, click on an icon and have
everything come up. Also, I run everything 'su root' in a console too.
thanks
P.S. Running Mandrake 9.2
13 Mar
13 Mar
12:03 a.m.
On Saturday 13 March 2004 3:02 am, Russell Hanaghan wrote:
Was wondering if it is possible to write a relatively
simple startup
script to start Jackd, AlsaModular synth with my specific file/patch
(AMS will start Jack on its own too) then patch capture 1 & 2 to AMS
then AMS to PCM's out, and then "wire" my midisport 2x2 port "A"
to AMS
midi in?
It would be nice to boot at the gig, click on an icon and have
everything come up. Also, I run everything 'su root' in a console too.
Er, if you run everything from a console, then surely you simply put all those
commands into a bash script, just the way you would type them. Or am I being
too simplistic here?
?-)
tim hall
12:16 a.m.
On Fri, 2004-03-12 at 19:54, tim hall wrote:
On Saturday 13 March 2004 3:02 am, Russell Hanaghan
wrote:
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.
R
Was wondering if it is possible to write a
relatively simple startup
script to start Jackd, AlsaModular synth with my specific file/patch
(AMS will start Jack on its own too) then patch capture 1 & 2 to AMS
then AMS to PCM's out, and then "wire" my midisport 2x2 port "A"
to AMS
midi in?
It would be nice to boot at the gig, click on an icon and have
everything come up. Also, I run everything 'su root' in a console too.
Er, if you run everything from a console, then surely you simply put all those
commands into a bash script, just the way you would type them. Or am I being
too simplistic here?
?-)
tim hall
7:32 a.m.
I've got a couple of startup scripts posted:
http://myweb.cableone.net/eviltwin69/ALSA_JACK_ARDOUR.html
They're probably a bit out ouf date but you'll get the idea.
Jan
On Fri, 2004-03-12 at 22:09, Russell Hanaghan wrote:
On Fri, 2004-03-12 at 19:54, tim hall wrote:
On Saturday 13 March 2004 3:02 am, Russell
Hanaghan wrote:
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.
R
Was wondering if it is possible to write a
relatively simple startup
script to start Jackd, AlsaModular synth with my specific file/patch
(AMS will start Jack on its own too) then patch capture 1 & 2 to AMS
then AMS to PCM's out, and then "wire" my midisport 2x2 port "A"
to AMS
midi in?
It would be nice to boot at the gig, click on an icon and have
everything come up. Also, I run everything 'su root' in a console too.
Er, if you run everything from a console, then surely you simply put all those
commands into a bash script, just the way you would type them. Or am I being
too simplistic here?
?-)
tim hall
8:25 a.m.
On Fri, Mar 12, 2004 at 08:09:14 -0800, Russell Hanaghan wrote:
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
Last time I look though I couldn't find a way to pass a saved file to AMS,
thats was a while ago, and someonme might have fixed it since then.
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.
- Steve
12:17 p.m.
On Sat, 2004-03-13 at 04:20, Steve Harris wrote:
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) 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?
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
Last time I look though I couldn't find a way to pass a saved file to AMS,
thats was a while ago, and someonme might have fixed it since then.
Got this working...use 'ams --jack --preset /home/me/filename'. works no
worries!
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.
- Steve
12:59 p.m.
Hello,
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) 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?
try & at the end of the line, i.e.:
qjackctl &
Not sure it will help, but it just might.
Yours, Mikhail Ramendik
1:04 p.m.
On Sat, Mar 13, 2004 at 08:10:26AM -0800, Russell Hanaghan wrote:
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.
--
Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's FEMTO SPASTIC LIUTENANT!
(random hero from isometric.spaceninja.com)
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. 
1:25 p.m.
You probably need to delay starting the clients until jackd is up and
running.
> #!/bin/sh
>
> qjackctl &
sleep 2 # wait for JACK to start
> ardour &
> hydrogen &
> ams &
Also, if ardour will be making the port connections, it probably needs
to start last, following another sleep.
--
joq
1:41 p.m.
On Sat, 2004-03-13 at 09:19, Jack O'Quin wrote:
You probably need to delay starting the clients until
jackd is up and
running.
Will
try this. Still having some probs with the firing sequence of
Qjackctl, AMS and Galan.
> #!/bin/sh
>
> qjackctl &
sleep 2 # wait for JACK to start > ardour
&
> hydrogen &
> ams "If I add file here, does it mess up the syntax?"&
Also, if ardour will be making the port connections, it probably needs
to start last, following another sleep.
2:19 p.m.
On Sat, Mar 13, 2004 at 09:33:42AM -0800, Russell Hanaghan wrote:
On Sat, 2004-03-13 at 09:19, Jack O'Quin wrote:
Shell script syntax is exactly the same as command line syntax.
So, if in doubt about what something in a shell script does... type it!
I highly recommend taking a few hours to really explore shell scripting.
In the long run your life with unix will be greatly improved by it,
even if you don't write (or read) them very often, because
you'll learn things about the shell that are good to know at
the command line. And there are shell scripts all over the place!
For example, everything in /etc/init.d is a shell script.
Here's a nice little tutorial:
http://steve-parker.org/sh/sh.shtml
--
Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's THE HOPPING NEWBIE!
(random hero from isometric.spaceninja.com)
You probably need to delay starting the clients
until jackd is up and
running.
Will
try this. Still having some probs with the firing sequence of
Qjackctl, AMS and Galan.
> > > ardour &
> > > hydrogen &
> > > ams "If I add file here, does it mess up the syntax?"&
> #!/bin/sh
>
> qjackctl &
sleep 2 # wait for JACK to start
1:47 p.m.
On Sat, 2004-03-13 at 09:19, Jack O'Quin wrote:
You probably need to delay starting the clients until
jackd is up and
running.
Disregard last post. This worked like a charm!!
As in humor...timing is everything! :)
Now for that "tips" script to run at the Pub! :))
R~
> #!/bin/sh
>
> qjackctl &
sleep 2 # wait for JACK to start > ardour
&
> hydrogen &
> ams &
Also, if ardour will be making the port connections, it probably needs
to start last, following another sleep.
5:24 p.m.
One other thing. If you have an app that reads input other than on the
command line you can do that by redirecting from the shell script
thusly:
application <<EOF
input line 1
input line 2
input line 3
.
.
.
input line N
EOF
You don't have to use EOF either. You can use any unique string.
Jan
On Sat, 2004-03-13 at 06:20, Steve Harris wrote:
On Fri, Mar 12, 2004 at 08:09:14 -0800, Russell
Hanaghan wrote:
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
Last time I look though I couldn't find a way to pass a saved file to AMS,
thats was a while ago, and someonme might have fixed it since then.
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.
- Steve 
8:33 a.m.
venerdì, 12 marzo 2004 alle 20:09:14, Russell Hanaghan ha scritto:
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.
You have just to create a text file with this as the first line:
#!/bin/bash
and then put all the commands as if you were write them in the console. thn
save the file and give it the execute permission:
$ chmod +x myscript.sh
So you can launch it as "./myscript.sh"
For automating MIDI connections you should use "aconnect" (man aconnect for
details) which is a text based program. You can use "aconnect -lio" to
find out what are the MIDI port names on your system (after all
the apps you need are started, in the correct order).
R
HTH ciao
--
Emiliano Grilli
Linux user #209089
http://www.emillo.net
12:45 p.m.
On Sat, 2004-03-13 at 04:27, Emiliano Grilli wrote:
venerdì, 12 marzo 2004 alle 20:09:14, Russell Hanaghan
ha scritto:
The patchbay fuctions in Qjackctl worked great for this actually. For
both midi and audio.
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.
You have just to create a text file with this as the first line:
#!/bin/bash
and then put all the commands as if you were write them in the console. thn
save the file and give it the execute permission:
$ chmod +x myscript.sh
So you can launch it as "./myscript.sh"
For automating MIDI connections you should use "aconnect" (man aconnect for
details) which is a text based program. You can use "aconnect -lio" to
find out what are the MIDI port names on your system (after all
the apps you need are started, in the correct order). R
HTH ciao 
9:02 p.m.
Hallo,
Russell Hanaghan hat gesagt: // Russell Hanaghan wrote:
On Sat, 2004-03-13 at 04:27, Emiliano Grilli wrote:
But then why go through the whole shell script issue and then stopping
halfway? ;) aconnect and jack_connect are really great to use in a
shell script. You can start qjackctl for later editing anyway.
And I'd really reconsider running everything as root, BTW. It is a
large security issue to run too many things as root. Type one wrong
command and you're in great trouble.
Capabilities or the realtime module and proper chmod'ing will give you
all live reliability you'd probably want without any need to be root.
ciao
--
Frank Barknecht _ ______footils.org__
For automating MIDI connections you should use
"aconnect" (man
aconnect for details) which is a text based program. You can use
"aconnect -lio" to find out what are the MIDI port names on your
system (after all the apps you need are started, in the correct
order).
The patchbay fuctions in Qjackctl worked great for this actually. For
both midi and audio.
7565
days inactive
7566
days old
linux-audio-user@lists.linuxaudio.org
16 comments
9 participants
participants (9)
-
Emiliano Grilli -
Frank Barknecht -
Jack O'Quin -
Jan Depner -
Mikhail Ramendik -
Paul Winkler -
Russell Hanaghan -
Steve Harris -
tim hall