From: "Martijn Sipkema" <martijn@entmoot.nl>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Lee Revell <rlrevell@joe-job.com>,
Florian Schmidt <mista.tapas@gmx.net>,
Paul Davis <paul@linuxaudiosystems.com>,
Jaroslav Kysela <perex@suse.cz>, Ingo Molnar <mingo@elte.hu>,
jackit-devel@lists.sourceforge.net,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [Jackit-devel] irq handler top half timestamps
Date: Mon, 20 Dec 2004 12:50:08 +0100 [thread overview]
Message-ID: <01a001c4e68a$0e1096a0$161b14ac@boromir> (raw)
In-Reply-To: Pine.HPX.4.33n.0412201205010.20003-100000@studcom.urz.uni-halle.de
> > > If the device uses a timer to generate interrupts at a fixed frequency
> > > then you have to manually compare the frames processed to the period
> > > size and call snd_pcm_period_elapsed if the period has indeed elapsed.
> >
> > Does that mean that ALSA will always have a large (relative to the interrupt
> > frequency) scheduling jitter for cards that interrupt at a fixed frequency?
>
> Yes, if the hardware periods don't exaclty match ALSA periods.
> (Using e.g. snd-ymfpci at 48 kHz with periods of 256 samples shouldn't
> introduce any additional jitter.)
>
> > Or is it possible to have ALSA return samples immediately after they become
> > available?
>
> The ALSA API assumes constant-sized periods. (Jack's Tascam USB
> driver bypasses the ALSA API.)
Ah, I'll have a look at that; I was able to buy a Swissonic USB studio D for
a very good price and now I want low latency with this "bad" hardware. :)
I would be nice to have ALSA support non-constant periods (transfer is a
better term in that case I think).
--ms
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-20 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041209180706.GA11397@elte.hu>
[not found] ` <200412091819.iB9IJiLX013123@localhost.localdomain>
[not found] ` <20041209183342.GB13132@elte.hu>
[not found] ` <20041209220741.7562b6a0@mango.fruits.de>
2004-12-09 21:10 ` irq handler top half timestamps Lee Revell
2004-12-10 1:35 ` Re: [Jackit-devel] " Florian Schmidt
2004-12-10 7:52 ` [Alsa-devel] " Jaroslav Kysela
2004-12-10 17:23 ` Florian Schmidt
2004-12-10 17:17 ` Re: [Jackit-devel] " Paul Davis
2004-12-10 17:54 ` [Alsa-devel] " Florian Schmidt
2004-12-10 19:00 ` Re: [Jackit-devel] " Lee Revell
2004-12-10 20:51 ` Paul Davis
2004-12-10 21:01 ` Lee Revell
2004-12-11 0:56 ` Florian Schmidt
2004-12-11 2:22 ` Florian Schmidt
2004-12-15 23:32 ` [Alsa-devel] " Florian Schmidt
2004-12-16 9:18 ` Ingo Molnar
2004-12-16 16:33 ` tapas
2004-12-16 18:35 ` Re: [Jackit-devel] " Lee Revell
2004-12-19 23:45 ` Florian Schmidt
2004-12-19 23:38 ` [Alsa-devel] " Lee Revell
2004-12-20 15:08 ` Re: [Jackit-devel] " Florian Schmidt
2004-12-21 1:30 ` [Alsa-devel] " Florian Schmidt
2004-12-21 1:49 ` Re: [Jackit-devel] " Lee Revell
2004-12-11 3:17 ` [Alsa-devel] " Lee Revell
2004-12-20 10:57 ` Re: [Jackit-devel] " Martijn Sipkema
2004-12-20 11:10 ` Clemens Ladisch
2004-12-20 11:50 ` Martijn Sipkema [this message]
2004-12-20 11:52 ` [Alsa-devel] " James Courtier-Dutton
2004-12-10 7:41 ` Jaroslav Kysela
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='01a001c4e68a$0e1096a0$161b14ac@boromir' \
--to=martijn@entmoot.nl \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=jackit-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=mista.tapas@gmx.net \
--cc=paul@linuxaudiosystems.com \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.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.