All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jack O'Quin <joq@io.com>
Cc: "Asbjørn Sæbø" <asbjs@stud.ntnu.no>, alsa-devel@lists.sourceforge.net
Subject: Re: Lowest latency: JACK, or ALSA directly?
Date: Fri, 12 Nov 2004 18:01:08 +0100	[thread overview]
Message-ID: <s5hpt2jdmsr.wl@alsa2.suse.de> (raw)
In-Reply-To: <87oei3xbly.fsf@sulphur.joq.us>

At 12 Nov 2004 10:42:33 -0600,
Jack O'Quin wrote:
> 
> > (As an aside, there is another thing that is not clear to me.  A set of 
> > samples from all channels is called a frame, and a set of frames is a 
> > period.  But the total buffer is made up from a set of periods again.  
> > How does this buffer function? Does one get data from the sound card 
> > each and every period (which I believe), or only when the buffer is 
> > full?  Do you get the data from a period when it is full, or do you 
> > have to wait some periods?)
> 
> The sound card generates an interrupt at the end of each period.  This
> determines the input latency.  The hardware buffer holds multiple
> periods (you need at least two).  Its size determines the maximum
> output latency.  With JACK, there's not much reason to use more than
> two or three periods, unless you're running without realtime
> privileges.

Regarding JACK's latency:  can JACK handle more than two periods with
the minimal latency?  That is, keeping only two periods active (the
current playing and the next periods), you can achieve the same
latency even if the buffer consists of more than two periods.

I'm asking this because some boards (e.g. RME32/96) have the fixed
buffer size, and can't take the configuration as two periods per
buffer.  IIRC, JACK fills all the buffer at the first sequence, and
this results in the higher latency than necessary.

Correct me if I'm wrong.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  reply	other threads:[~2004-11-12 17:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 14:41 Lowest latency: JACK, or ALSA directly? Asbjørn Sæbø
2004-11-11 15:11 ` Jack O'Quin
2004-11-12  9:04   ` Asbjørn Sæbø
2004-11-12 16:42     ` Jack O'Quin
2004-11-12 17:01       ` Takashi Iwai [this message]
2004-11-12 17:19         ` Jack O'Quin
2004-11-17 14:55           ` Takashi Iwai
2004-11-17 17:32             ` Jack O'Quin
2004-11-17 18:28               ` Takashi Iwai
2004-11-17 19:41                 ` Takashi Iwai
2004-11-18  2:07                   ` Jack O'Quin
2004-11-18 12:38                     ` Takashi Iwai
2004-11-11 15:34 ` Paul Davis
2004-11-12  9:11   ` Asbjørn Sæbø
2004-11-12 14:47   ` Gilles Degottex
2004-11-12 15:28     ` Giuliano Pochini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hpt2jdmsr.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=asbjs@stud.ntnu.no \
    --cc=joq@io.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.