On Wed, 2009-04-29 at 21:12 +0800, Basil Mohamed Gohar wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/29/2009 08:21 AM, Callum Lerwick wrote: > > On Mon, 2009-04-27 at 13:59 -0400, Ben Boeckel wrote: > >>> Subject: Re: The Great Pulseaudio Mixer Debate: a > >> modest (productive) > >>> proposal > >>> From: Ben Boeckel <MathStuf gmail com> > >>> To: fedora-devel-list redhat com > >>> Date: 04/27/2009 10:12 AM > >>> > >>>> I've had X lock up or temporarily freeze and > >> kaffeine > >>>> (playing through PA via xine) still plays. The only > >> way > >>>> I've been able to get it to skip is to force > >> basically > >>>> everything into swap with programs that take up 3+GB > >> of > >>>> RAM (making markov chains from big.txt takes...quite > >> a > >>>> bit in duck-typed languages). Maybe it's the dual > >> core > >>>> 3.0GHz, but I've found it hard to skip apps using > >> PA. > >>>> PA is taking 0% CPU and kaffeine jumps to 1% playing > >>>> flac files. Also, PA hasn't even jumped towards the > >> top > >>>> of usage at all in the past few minutes. > >>> > >>> That's amazing, because I have a 3ghz dual core and > >> PA takes ~10% CPU to > >>> play FLAC from Rhythmbox and can skip if I'm doing a > >> lot of work - say > >>> ffmpeg transcoding and moving files. Intel HD audio > >> (yes, generic) > >>> Analog Devices chip. > >>> > >> Maybe its a difference between xine and gstreamer? > >> > >> % lspci | grep -i audio > >> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 > >> Family) HD Audio Controller > > > > Check your logs. This is quite possibly the difference between "My > > hardware does 44.1khz natively" and "My hardware only does 48000khz and > > playing anything but a DVD requires resampling". Later Intel chipsets > > all seem to be the latter. > > > Not sure if this is the right place to post this, but I also have a huge > CPU hit on my 4+ year old laptop, and I am sure that it handles > different sampling rates without much difficulty. > > So, my question is, what logs can I check to find out if this is > happening (if I understood the message correctly)? Hrm, pulseaudio's logging seems to have changed. You can try running "pulseaudio -k;pulseaudio -v" then dig through the spew: I: alsa-util.c: Device hw:M5455,0 doesn't support 44100 Hz, changed to 48000 Hz. I: alsa-sink.c: Successfully opened device hw:M5455,0. If you see something like that, your hardware requires resampling.
Description: This is a digitally signed message part