Ok maybee I am mad but I am working on some DSL exts. One of which uses the binary called play to play wav files on the command line. This is a pretty standard Linux binary feature so you can work from a console command line and just type play /path/wavfile.wav .. Most of my testing has been done on DSLv4 RC3 and RC4 using a USB install. Thats all fine but when I started trying to use the DSL exts on live CD sessions then the play does not work. There is no such file found. The file seems to be usually at /usr/share/play but on the CD it does not exist. There also seems to be no DSL ext for this one either. Why on earth isnt there a play binary on the CD ? How can I play wav files from the command line ? Any ideas ?You must realize that different distributions are tailored to their different ways... and what can be what you call a standard may not be one in another.
I think mpg123 is included in DSL... you could try that. Or else if you looked hard enough, there is a mydsl extension for it under uci. It can be hard to search sometimes... I sometimes use a search on the web pages, or use a search engine, or even a manual grep. If you don't want to do that, just make sure you also look under the uci and unc sections."play" is part of sox, which is not included with DSL. It is available as a uci extension in the mydsl repository. Since the executables (sox, soxmix, play and rec) are not added to PATH in a uci, you will need to use the full path to it, or create an alias (alias play=/opt/sox/play), or add /opt/sox to your PATH variableYep .. Ive found sox .. Did a bit of searching to find out where play comes from. Along with rec and also some bits of the lame encoder by the looks and you have sox .. Problem is that adds another 500k to the mydsl Exts .. I am trying to keep it light weight .. The binary for play is only about 6k and all I need is play frankly..
Is there any issue with just grabbing the play binary and including that in one of my Exts along with the sound files?? I have no need of sox ..
Also if the binary is so system specific then how can sox possibly work like that as its a precompiled tar.gz ..
Also why does play appear on a USB install and not on a CD boot.. The USB install just copies the image file across from the CD and makes it bootable.. There must be something more going on there however I can take a USB installed system and run it on several different machines and find that play works fine.. They all have radically different sound cards etc ..
Sorry cant buy some of the explanations as yet..afaik `play` is just a wrapper script that invokes sox. You could try my first suggestion as well...
You probably have the extension saved on your USB so it gets automatically loaded.
Quote
Also if the binary is so system specific then how can sox possibly work like that as its a precompiled tar.gz .. <snip> Sorry cant buy some of the explanations as yet..