No, with frame/period of 2 it also *seems* to work.
I tried jack_delay, it returns me this whatever frames/period I try.
What that means?
capture latency = 1024
playback_latency = 1024
Signal below threshold...
Signal below threshold...
Signal below threshold...
Signal below threshold...
Signal below threshold...
Signal below threshold...
2011/4/2, Robin Gareus <robin(a)gareus.org>rg>:
On 04/03/2011 12:52 AM, Bernardo Barros wrote:
I would be very embarrassed if I'm fooling
myself, but from what I
read the information provided by qjackctl, is this really the latency
of the audio system as low as 0.08ms with frames/period of 2! :S
must be a typo: 2*16/ 44100Hz = 0.725ms = ~0.8ms
Measure it with 'jack_delay' [1]. The number given in qjackctl's setup
dialog is the nominal latency; and the time between two jack cycles.
Usually there's additional latency due to [PCI|USB] bus overhead,
sound-card & ALSA buffering, DAC/ADCs, etc. - around 1 ms round-trip for
PCI devices.
http://wiki.linuxaudio.org/wiki/jack_latency_tests
have fun,
robin
[1]
http://kokkinizita.linuxaudio.org/linuxaudio/index.html