On 2019-10-29 13:30, Nils Wallgren wrote:
Thanks for the reply!
Most intructions seems to be on Os and it is quite hard to find
I meant for macOS, sorry
Scrolling through the manual but It still seems that I cannot use the
normal rec
I cant just write rec but have to use sox -t waveaudio .. (as you
suggested. Same thing with play.
Tried this in the command prompt: play SC_191028_105931.aiff and get
the message
'play' is not recognized as an internal or external command,
operable program or batch file.
I'm wondering were you got sox from, and in what form. When I installed
it
there was a choice of an installer, or a zip. I chose the latter
because
when I unzipped it, I could see what the various files it contained
were,
read the relevant notes and do what they said. Maybe, with an
installer,
it's not that obvious?
In my notes on how I installed sox here, it says that in a file named
README.win32.txt the text said that if one wants to have the "play" and
"rec" commands work, once has simply to make copies of the sox.exe file
named play.exe and rec.exe.
That means that when you issue a 'play' command for example the program
that runs is identical to what would run if you issued a 'sox' command,
but I expect the program code looks at the command used to run itself,
and thus sees if you invoked the 'play' or 'sox' or 'rec' one.
I had completely forgotten that the same is true if you want "soxi" to
work - you need to copy "sox.exe" as "soxi.exe". That's certainly
worth doing because running soxi against an audio file will tell you
about what's actually in the file.
Certainly a response like "'play' is not recognized as an internal
or external command, operable program or batch file." means that
there's no "play.exe" (or play.bat or various other possibilities)
in any of the folders defined on 'PATH' in your system. It sounds
to me as if you've not got sox 'installed' properly.
When I write sox in the prompt I get a lot of information but this
kind of line stood out:
sox FAIL sox: Not enough input filenames specified
What you should have got was a summary of the call syntax for sox.
I expect you got it because you didn't specify any, or the right
combination of, parameters after the sox command itself.
You need to look at the examples in the manual.
Sox won't start a gui-based dialog with you, nor will it make the
command window go into "sox mode" and then expect a series of sox
subcommands. You provide ALL the filenames and other parameters
on one long command line, then sox does all of what you asked for,
then it stops.
Some of the examples in the manual are quite complicated, with many
separate steps in them, but you don't need to try to be clever right
at the start.
--
Jeremy Nicoll - my opinions are my own
_______________________________________________
Sox-users mailing list
Sox-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/sox-users
