Re: [SoX-users] quickest way to chop up long files

[a1s2d3f4 <ana...@ho...>]

Sorry, of course I did mean =2500.  Typing too quick late at night.

Yes, unfortunately, I am mixing together 4 channels - 4 separate WAV files -
so, I  guess what you are suggesting won't work.  But , if you don't mind,
I'd like to hear the "skip over" solution for single file input "not from
standard input".  (Mind you, I am using Win32).




Ulrich Klauer-2 wrote:
> 
> 
> 
>> When I use [code] sox <infile> <outfile> trim 10 260, it's ok.  But
>> when
>> it's trim 2000 2500, it takes forever.
> 
> 1. This will produce a file of length 2500 seconds. I guess what you want
> to say is "trim 2000 =2500".
> 
> 2. There is a way for trim to quickly jump over the first 2000 seconds,
> but it won't work if you are reading from standard input, using more than
> one input file, or doing any processing before the trim effect. Are you
> doing any of this?
> 
> Ulrich
> Is this really the exact way you're calling SoX, 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Sox-users mailing list
> Sox...@li...
> https://lists.sourceforge.net/lists/listinfo/sox-users
> 
> 

-- 
View this message in context: http://old.nabble.com/quickest-way-to-chop-up-long-files-tp34371297p34380066.html
Sent from the SoX mailing list archive at Nabble.com.