I have a number of stacks referencing external AIFF files running under Ubuntu 5.04.
As 5.04 uses GNOME it chews RAM a bit too much on my clanky old machines - want to change over to 6.10 with XFCE (Xubuntu) but that only supports OGG and other Open Source formats - which RR does not.
Help and suggestions gratefully recieved.
Richmond Mathewson
Linux, RR and sound files?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Sound on Linux
You could install Sweep
http://www.metadecks.org/software/sweep/index.html
or Audacity to convert them to wav format, then use aplay in a shell to play them. Or mplayer as an ogg command line player
To use a non RunRev player you can launch to file via a shell script as in:
put ("path_to_soundfile/snd01.ogg") into SNDFILE
put the shell of ("path_to_script/playsound.sh" && SNDFILE) into DUSND
The playsound.sh script could look like this
#!/bin/bash
#playsound.sh soundfile
PLAYER="/usr/bin/mplayer"
#A few lines to test if the soundfile argument is present and valid
$PLAYER $1
Or you could say
put the shell of ("/usr/bin/mplayer" && "path_to_soundfile/snd01.ogg") into DUSND
but I like to keep my shell commands outside of the script so I can change things without having to recompile the runrev app.
This will play the sound but won't do anything else in a script until it is finished.
See my post on backgrounding if you need to regain control immediately.
You can of course make playsound.sh look at lists of files to be played and play one or some depending on the value of the arguments as in
"path_to_script/playsound.sh" && SNDLIST && NUMBER_OF_SOUNDS && RANDOM_ORDER_FLAG
The shell script then would have two or three arguments as $1 $2 $3
and you process each of them accordingly.
If you have more than one argument in a put statement it is a good idea to
put the shell string into a holding variable, replace return with empty in that variable, then put the shell of the variable into DUNSND, as runrev sometimes inserts newlines into long strings which the shell sees as a command separator, not what you want.
Happy Hacking
http://www.metadecks.org/software/sweep/index.html
or Audacity to convert them to wav format, then use aplay in a shell to play them. Or mplayer as an ogg command line player
To use a non RunRev player you can launch to file via a shell script as in:
put ("path_to_soundfile/snd01.ogg") into SNDFILE
put the shell of ("path_to_script/playsound.sh" && SNDFILE) into DUSND
The playsound.sh script could look like this
#!/bin/bash
#playsound.sh soundfile
PLAYER="/usr/bin/mplayer"
#A few lines to test if the soundfile argument is present and valid
$PLAYER $1
Or you could say
put the shell of ("/usr/bin/mplayer" && "path_to_soundfile/snd01.ogg") into DUSND
but I like to keep my shell commands outside of the script so I can change things without having to recompile the runrev app.
This will play the sound but won't do anything else in a script until it is finished.
See my post on backgrounding if you need to regain control immediately.
You can of course make playsound.sh look at lists of files to be played and play one or some depending on the value of the arguments as in
"path_to_script/playsound.sh" && SNDLIST && NUMBER_OF_SOUNDS && RANDOM_ORDER_FLAG
The shell script then would have two or three arguments as $1 $2 $3
and you process each of them accordingly.
If you have more than one argument in a put statement it is a good idea to
put the shell string into a holding variable, replace return with empty in that variable, then put the shell of the variable into DUNSND, as runrev sometimes inserts newlines into long strings which the shell sees as a command separator, not what you want.
Happy Hacking
Stomfi
Brisbane
Australia
Brisbane
Australia