|
From: Doug C. <idi...@us...> - 2010-05-25 05:57:16
|
Yes, at least some of the latency is due to SoX. The latency will be at least one "buffer" worth of data but more likely two (or more, depending on the implementation details of the input and output modules being used). You might be able to reduce the latency by using smaller buffers via the --buffer switch, i.e. --buffer 1024 On Mon, May 24, 2010 at 10:29 PM, <pj...@pj...> wrote: > Chris Bagwell wrote: > > Just add a "-t alsa" right before the alsa device name in your > > command below. Since no file extension, SoX needs to be given > > a hint at what your input is. > > Excellent: > ~> sox -r 44100 -c 2 -e s -t alsa hw:4,0 -d > works just fine... except that there's about 0.25 sec latency. > If I don't specify the rate: > ~> sox -c 2 -e s -t alsa hw:4,0 -d > (or if I specify it correctly as 48000), then there's "only" about > 0.14 sec latency. > Is this due to sox ? If so, can I reduce it further ? > > Is there a way I can connect hw:4,0 directly to hw:0,0 to see > how much latency there is in alsa and the kernel-modules ? > (E.g. at the midi-level, I can do it with aconnect...) > > Regards, Peter Billam > > http://www.pjb.com.au pj...@pj... (03) 6278 9410 > "Was der Meister nicht kann, vermöcht es der Knabe, hätt er > ihm immer gehorcht?" Siegfried to Mime, from Act 1 Scene 2 > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Sox-users mailing list > Sox...@li... > https://lists.sourceforge.net/lists/listinfo/sox-users > |