On Aug 09 14:05:32, shane.bla...@callfire.com wrote: > Hello I have an application that processes audio as rec writes the file.
Does this mean that rec(1) writes into a pipe and your application is reading that pipe? > rec is buffering the data before it writes and I get > the updates about 2 or 3 seconds late. How do you know that? How exactly are you reading what rec(1) is writing? > I have played with the --buffer pram and I not been able to see a > difference. > > I would like to tell rec to write the data as soon as it gets it or reduce > the file write buffer size. That's what --buffer is supposed to do ... > I have silence detection on > rec -c 1 -r 8000 --buffer 4096 currentRecording.wav silence 1 0.0001 2.1% 1 > 15.0 2.6% > > The writes look like this > > Size of currentRecording.wav = 24576 Size of currentRecording.wav = 36864 > *Size* *of* *currentRecording.wav* *=* *45056* *Size* *of* * > currentRecording.wav* *=* *77824* The steps are indeed multiples of 4096. Can you try with other --buffer to see if the data becomes available to your application in the chunks that rec(1) is writing? ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ SoX-devel mailing list SoX-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-devel
