LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@perex.cz, alsa-devel@alsa-project.org,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 4.0-rc3: sound broken in chromium but not in mpg123
Date: Tue, 24 Mar 2015 20:01:59 +0100	[thread overview]
Message-ID: <20150324190158.GA29071@amd> (raw)
In-Reply-To: <s5hoanthx6z.wl-tiwai@suse.de>

Hi!

> > > OK, then another thing I would check is to try different sample rates
> > > (e.g. via playing WAV files over PA).
> > 
> > Like this?
> > 
> > pavel@amd:/usr/share$ pacat ./sounds/alsa/Front_Right.wav
> > pavel@amd:/usr/share$ pacat --rate=48000 ./sounds/alsa/Front_Right.wav
> > pavel@amd:/usr/share$ pacat --rate=44100 ./sounds/alsa/Front_Right.wav
> > pavel@amd:/usr/share$ pacat --rate=32000 ./sounds/alsa/Front_Right.wav
> > pavel@amd:/usr/share$ pacat --rate=16000 ./sounds/alsa/Front_Right.wav
> > pavel@amd:/usr/share$ pacat --rate=8000 ./sounds/alsa/Front_Right.wav
> > 
> > This seems to have behaved as expected.
> 
> Hmm.  You might see a difference when comparing
> /proc/asound/card*/pcm0p/sub0/* files between working and broken
> cases (while playing something).
> 
> Other than that, I have no idea.  A bisection would be needed, I'm
> afraid.

:-(.

To make it more fun, it now appeared on x60... it looks like it has
something to do with starting browser early after boot.

Restarting the browser seems to fix it.

Best regards,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2015-03-24 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 20:11 Pavel Machek
2015-03-15  8:12 ` Takashi Iwai
2015-03-15  8:15   ` Pavel Machek
2015-03-15  8:23     ` Takashi Iwai
2015-03-16 12:37       ` Pavel Machek
2015-03-16 13:46         ` Takashi Iwai
2015-03-24 19:01           ` Pavel Machek [this message]

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=20150324190158.GA29071@amd \
    --to=pavel@ucw.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    --subject='Re: 4.0-rc3: sound broken in chromium but not in mpg123' \
    /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

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).