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: Mon, 16 Mar 2015 13:37:19 +0100	[thread overview]
Message-ID: <20150316123719.GA14161@amd> (raw)
In-Reply-To: <s5hr3sqr7nw.wl-tiwai@suse.de>

On Sun 2015-03-15 09:23:15, Takashi Iwai wrote:
> At Sun, 15 Mar 2015 09:15:44 +0100,
> Pavel Machek wrote:
> > 
> > On Sun 2015-03-15 09:12:47, Takashi Iwai wrote:
> > > At Sat, 14 Mar 2015 21:11:09 +0100,
> > > Pavel Machek wrote:
> > > > 
> > > > Hi!
> > > > 
> > > > Intel desktop machine:
> > > > 
> > > > 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High
> > > > Definition Audio Controller (rev 01)
> > > > 
> > > > Sound worked ok in both in previous kernel versions.
> > > > 
> > > > Any ideas?
> > > 
> > > How broken?  Did you get any error messages?
> > 
> > I get some funny, faint, rhytmic noises where audio should
> > be... Actually, I somehow suspect something is wrong with time during
> > video playback.
> 
> Did you try audio playback without video on chromium?

Yes. Does not work, either; I tried
http://www.thenakedscientists.com/HTML/podcasts/ .

> > > If the behavior depends on the application (e.g. ALSA vs OSS), I'd
> > > suspect rather a device permission problem at first.  There are no
> > > significant changes between 3.19 and 4.0-rc3 regarding HD-audio.
> > 
> > My system contains pulseaudio, so it is more complex than ALSA vs OSS
> > :-(.
> 
> OK, that was missing information :)
> Then there should be any difference in the kernel driver side -- it's
> only a single PA process who accesses the sound device in the very
> same manner no matter what clients are used (after all it's the
> purpose of PA).

> > Audio seems to work ok on thinkpad x60 with very very similar config.
> 
> 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.

Thanks,
									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-16 12:37 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 [this message]
2015-03-16 13:46         ` Takashi Iwai
2015-03-24 19:01           ` Pavel Machek

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=20150316123719.GA14161@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).