From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [PATCH 1/3] sound: Add a quirk to enforce period_bytes
Date: Mon, 16 Jun 2014 09:22:08 -0400 [thread overview]
Message-ID: <CAGoCfiw3du9rXFvDfsUYLu4Ru6mbdWa+LtAyYupXosM0n-71NA@mail.gmail.com> (raw)
In-Reply-To: <539E9F25.7030504@ladisch.de>
> This looks like a workaround for a userspace bug that would affect all
> USB audio devices. What period/buffer sizes are xawtv/tvtime trying to
> use?
I have similar concerns, although I don't know what the right solution
is. For example, the last time Mauro tweaked the latency in tvtime,
it broke support for all cx231xx devices (note that tvtime and xawtv
share essentially the same ALSA code):
http://git.linuxtv.org/cgit.cgi/tvtime.git/commit/?id=3d58ba563bfcc350c180b59a94cec746ccad6ebe
It seems like there is definitely something wrong with the
latency/period selection in both applications, but we need some
insight from people who are better familiar with the ALSA subsystem
for advice on the "right" way to do low latency audio capture (i.e.
properly negotiating minimal latency in a way that works with all
devices).
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2014-06-16 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 16:16 [PATCH 0/3] Auvitek au0828 fixups Mauro Carvalho Chehab
2014-06-14 16:16 ` [PATCH 1/3] sound: Add a quirk to enforce period_bytes Mauro Carvalho Chehab
2014-06-16 7:39 ` [alsa-devel] " Clemens Ladisch
2014-06-16 13:22 ` Devin Heitmueller [this message]
2014-06-16 15:05 ` Mauro Carvalho Chehab
2014-06-18 8:20 ` Clemens Ladisch
2014-06-16 14:21 ` Mauro Carvalho Chehab
2014-06-16 14:38 ` Alexander E. Patrakov
2014-06-16 16:24 ` Mauro Carvalho Chehab
2014-06-16 17:16 ` Alexander E. Patrakov
2014-06-16 18:59 ` Mauro Carvalho Chehab
2014-06-16 19:04 ` Devin Heitmueller
2014-06-16 19:22 ` Mauro Carvalho Chehab
2014-06-18 8:21 ` Clemens Ladisch
2014-06-14 16:16 ` [PATCH 2/3] sound: simplify au0828 quirk table Mauro Carvalho Chehab
2014-06-14 16:16 ` [PATCH 3/3] sound: Update au0828 quirks table Mauro Carvalho Chehab
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=CAGoCfiw3du9rXFvDfsUYLu4Ru6mbdWa+LtAyYupXosM0n-71NA@mail.gmail.com \
--to=dheitmueller@kernellabs.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mchehab@infradead.org \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).