Re: [linux-audio-user] jackd, zynaddsubfx and iiwusynth

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Date: Tuesday, March 4, 2003 - 4:33 am

Levi Burton writes:

> I looked at jackd options, maybe someone could explain what they do for me:

I'll try. Someone please correct me if I get any of this wrong.

-p sets the number of frames between JACK process() calls. This
must be a power of two (IIRC).

-n is the number of such periods in the buffer. P*N*4 is the size
of the JACK buffer in bytes. Larger buffers yield higher latency,
but fewer xruns.

If you need low latency, set -p and -n as low as you can without xrun
problems. Reasonably well-tuned current-generation systems with a
decent sound card and JACK running --realtime on a low-latency kernel
can handle -p 128 -n 3 reliably. Some can do better. Tuning a system
for low latency is challenging.

If you don't need low latency, set -p and -n higher to insulate
yourself from xruns.

-H tells JACK that your sound card provides capture input
monitoring.

-s tells JACK's ignore xruns reported by the ALSA driver. This
makes JACK less likely to disconnect ports when running without
--realtime.

--
Jack O'Quin
Austin, Texas, USA

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[linux-audio-user] jackd, zynaddsubfx and iiwusynth, Levi Burton, (Mon Mar 3, 1:07 pm)
Re: [linux-audio-user] jackd, zynaddsubfx and iiwusynth, Jack O'Quin, (Tue Mar 4, 4:33 am)