In article , RJH
wrote:
On 14/07/2015 16:21, Jim Lesurf wrote:
In article , RJH
wrote:


The manual is long because sox can do so many things and give so much
control. But for tasks like this you can ignore most of that.


Thanks - not that difficult, then. The biggest issue for me is usually
paths.

FWIW I tend to sort that by writing simple ROX apps so I can simply drag
the files to the application icon to give them as input to a chosen
command. That makes it easy to, say, convert a batch of files by
drag-and-drop.

But for individual files when using specific less common options/commands I
tend to find that I can find them via stepping around the terminal's
command history or tab completion. (No idea if Windows has equivalents.)


TBH for many GUI programs that process audio or AB my first reaction
is to wonder if they are a front-end for sox or ffmpeg. For all I
know, 'Max' may be so.


So far as I can tell, it's this:

http://www.mega-nerd.com/libsndfile/

The rest of the components are encoders and a compressor.

I'm not sure, but my first impression is that it will have source code
and/or methods in common with sox and ALSA. If nothing else it shares the
same yukky webpage colours, etc, as 'secret rabbit'. 8-]

Jim

--
Please use the address on the audiomisc page if you wish to email me.
Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html