On Wed, May 02, 2012 at 04:51:03PM -1000, Joel Roth wrote:
Which is not completely wrong, just a little inaccurate.
Suppose you configure for 2 periods. The the following happens:
Capture A B C D E F
Processing - A B C D E
Playback - - A B C D
For 3 periods, this becomes:
Capture A B C D E F
Processing - A B C D E
Playback - - - A B C
And for 4 periods:
Capture A B C D E F
Processing - A B C D E
Playback - - - - A B
The advantage of having more that 2 periods is that processing
can be late without ill consequences, e.g. for 3 periods
Capture A B C D E F
Processing - - A B C D
Playback - - - A B C
still works fine. That is, the ALSA API allows this. It's not 100%
clear to me if Jack would allow it, as it has some internal checks
for things being 'on time'.
Jack2's async mode (also the default) adds one period of latency,
things are as if you had configured for one more period. That is
because of doing
1. Read from capture device
2. Process
3. Write to playback device
in each cycle, it does
1. Read from capture device
2. Write result of previous cycle to playback device
3. Process
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
LINUX® is a registered trademark of Linus Torvalds in the USA and other countries.
Linuxaudio.org logo copyright Thorsten Wilms © 2006.
Hosting provided by the Virginia Tech Department of Music and DISIS.