|
From: Chris B. <ch...@cn...> - 2008-09-23 00:26:57
|
robs wrote: > BTW, I do intend to get round to answering this at some point. I just need to find some time to have a play with what you've done so far so I can put it in context... > > Cheers, > Rob > Since sox-commits isn't working, just letting you know I've submitted some more updates in this area over the weekend. Also, below is some more information on some changes I think I'll make. Its now possible to specify multiple effect command lines inside the --effects-file. For instance: sox --output multiple infile.wav output%n.mp3 --effects-file=splitpoints.txt can be used to split up a file into three separate files if splitpoints.txt contains: trim 0 30 trim 0 10 trim 0 40 Right now, the above will loop back to first effect line and continues creating more then 3 files until input reaches EOF. Not sure if thats the long term behavior I want yet. I'm thinking about getting ride of the --output option and force the user to specify it somehow in the effect chain. This will allow applying one or more effects to the same output file and also for splitting. For example: trim 0 3:00 silence 0 1 0:01 %1 newfile trim 0 2:30 silence 0 1 0:01 %1 newfile stop The above would allow using trim to be used to skip 3 minutes into the file and then use silence to detect end-of-track after 1 second of silence... Newfile is a queue point to start new output file. Stop is a queue point to not loop to top if input hasn't reached EOF (just an idea right now... for that matter, we could support GOTO's and variables and conditional branches. :-) ). Also, I'm thinking about adding support for this on the command line as well. ";" would be same as new line in the effects file: sox infile.wav outfile%n.mp3 trim 0 3:00 ";" silence 0 1 0:01 %1 "; " newfile; etc ";" etc Chris |