From: Ben Hutchings <ben@decadent.org.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: James Andrewartha <trs80@ucc.gu.uwa.edu.au>,
Jaroslav Kysela <perex@perex.cz>,
536896@bugs.debian.org, alsa-devel@alsa-project.org
Subject: Bug#536896: linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace
Date: Mon, 12 Apr 2010 21:18:49 +0100 [thread overview]
Message-ID: <1271103529.6179.325.camel@localhost> (raw)
In-Reply-To: <s5h633xb079.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]
On Mon, 2010-04-12 at 09:26 +0200, Takashi Iwai wrote:
> At Sun, 11 Apr 2010 21:25:16 +0100,
> Ben Hutchings wrote:
> >
> > [1 <text/plain; UTF-8 (quoted-printable)>]
> > [Earlier messages can be found at http://bugs.debian.org/536896 ]
> >
> > On Mon, 2010-04-12 at 01:08 +0800, James Andrewartha wrote:
[...]
> > > Author: Takashi Iwai <tiwai@suse.de> 2008-01-09 02:08:14
> > > Committer: Jaroslav Kysela <perex@perex.cz> 2008-02-01 01:29:47
> > > Parent: d948035a928400ae127c873fbf771389bee18949 ([ALSA] Remove PCM xfer_align sw params)
> > >
> > > [ALSA] PCM - clean up snd_pcm_lib_read/write
> > >
> > > Introduce a common helper function for snd_pcm_lib_read and snd_pcm_lib_write
> > > for cleaning up the code.
> > >
> > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > > Signed-off-by: Jaroslav Kysela <perex@perex.cz>
> > >
> > > I don't know anything about this code, but I'm happy to deal with upstream
> > > if you'd prefer me to.
> >
> > The above commit is supposed to be cleanup, but it has at least one
> > semantic change: snd_pcm_mmap_control::avail_min no longer applies to
> > non-blocking file handles. I don't know whether this is was an
> > intentional or unintentional change, but it wasn't commented. I also
> > don't know whether this can explain the popping, but I expect that it
> > has changed the timing of audio I/O.
>
> The above change is essentially a fix of the buggy behavior for
> non-blocking access. avail_min is the definition for wake-up
> behavior, and it doesn't define the blocking behavior.
> But, it's possible that this changes the timing, indeed. If so, it
> implies that the app expects somehow wrongly.
Thanks for your quick response. I will reassign this bug to the
applications that were mentioned.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2010-04-12 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090714135754.4684.74223.reportbug@zarvora>
[not found] ` <20100225183435.GA8488@galadriel.inutil.org>
[not found] ` <alpine.DEB.1.10.1004120102110.24942@martello.ucc.gu.uwa.edu.au>
2010-04-11 20:25 ` Bug#536896: linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace Ben Hutchings
2010-04-12 7:26 ` Takashi Iwai
2010-04-12 20:18 ` Ben Hutchings [this message]
2010-04-29 11:04 ` James Andrewartha
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=1271103529.6179.325.camel@localhost \
--to=ben@decadent.org.uk \
--cc=536896@bugs.debian.org \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=trs80@ucc.gu.uwa.edu.au \
/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).