From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: USB audio devices
Date: Wed, 10 Mar 2004 10:41:24 +0100 [thread overview]
Message-ID: <s5hr7w1m43f.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0403101006120.28347@pnote.perex-int.cz>
At Wed, 10 Mar 2004 10:08:26 +0100 (CET),
Jaroslav wrote:
>
> On Wed, 10 Mar 2004, Clemens Ladisch wrote:
>
> > Jaroslav Kysela wrote:
> >
> > > On Tue, 9 Mar 2004, Takashi Iwai wrote:
> > >
> > > > BTW, the USB audio is another headache. the current ALSA PCM model isn't
> > > > perfectly suitable for the devices like USB audio.
> > >
> > > Unfortunately I don't see a better model.
> >
> > Conceptually, USB devices have variable-sized periods. The question
> > is whether we actually want to allow this in the API. Probably not.
>
> What this does mean? I though that the period size is specified with time
> (1ms) for USB, isn't it? I think that we can describe this constraint
> with the refine algorithm.
the period "time" is constant but the sample numbers in this period
varies from time to time because of tuncation to integer or due to
sync mode. so far, we assume that the samples in a period is
constant.
we have some cases which we can't handle properly:
1) the period time is constant but the period size is variable
e.g. USB-audio
2) the period size is constant but the period time is variable
e.g. synchronization with another stream or clock source
vari-speed stream
3) both period size and time are variable
??? not known
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-10 9:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 14:51 PCM hw mixing with volume Ove Kaaven
2004-03-07 16:36 ` Manuel Jander
2004-03-07 16:41 ` Jaroslav Kysela
2004-03-08 16:20 ` Paul Davis
2004-03-08 21:29 ` Ove Kaaven
2004-03-09 14:26 ` Paul Davis
2004-03-09 14:59 ` Takashi Iwai
2004-03-09 17:31 ` USB audio devices Jaroslav Kysela
2004-03-10 8:26 ` Clemens Ladisch
2004-03-10 9:08 ` Jaroslav Kysela
2004-03-10 9:41 ` Takashi Iwai [this message]
2004-03-10 20:04 ` Karsten Wiese
2004-03-11 0:13 ` Patrick Shirkey
2004-03-11 8:09 ` Clemens Ladisch
2004-03-10 9:41 ` Clemens Ladisch
2004-03-10 16:34 ` Takashi Iwai
2004-03-10 17:46 ` Clemens Ladisch
2004-03-11 8:14 ` Clemens Ladisch
2004-03-09 17:25 ` PCM hw mixing with volume Ove Kaaven
2004-03-09 20:24 ` Manuel Jander
2004-03-10 9:46 ` Giuliano Pochini
2004-03-10 14:16 ` Ove Kaaven
2004-03-10 14:40 ` Ove Kaaven
2004-03-10 14:53 ` Paul Davis
2004-03-10 15:08 ` Takashi Iwai
2004-03-10 16:05 ` Ove Kaaven
2004-03-10 15:55 ` Giuliano Pochini
2004-03-10 16:56 ` Ove Kaaven
2004-03-11 9:24 ` Giuliano Pochini
2004-03-10 17:28 ` Takashi Iwai
2004-03-10 18:47 ` James Courtier-Dutton
2004-03-11 5:15 ` Manuel Jander
2004-03-11 7:13 ` snd_intel8x0 fails after ACPI sleep gte654n
2004-03-13 18:13 ` Christoph Lukas
2004-03-11 5:00 ` PCM hw mixing with volume Manuel Jander
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=s5hr7w1m43f.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=perex@suse.cz \
/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.