From: Takashi Iwai <tiwai@suse.de>
To: Jason Harvey <softdevice@jasonline.co.uk>
Cc: alsa-devel@alsa-project.org, The Source <thesourcehim@gmail.com>
Subject: Re: sbxfi - What works/doesn't summary
Date: Tue, 28 Oct 2008 20:36:02 +0100 [thread overview]
Message-ID: <s5hy708h5r1.wl%tiwai@suse.de> (raw)
In-Reply-To: <490768FF.3020807@jasonline.co.uk>
At Tue, 28 Oct 2008 19:33:19 +0000,
Jason Harvey wrote:
>
> Takashi Iwai wrote:
> > At Tue, 28 Oct 2008 17:40:40 +0000,
> > Jason Harvey wrote:
> >
> >> The Source wrote:
> >>
> >>> You can't hear desktop sounds because they always use pulseaudio no
> >>> matter what sound system you select as default. For me pulseaudio
> >>> plays first sound fine after start, others are corrupt along with
> >>> sound from all other apps. I'll post hw_params later. Also pulseaudio
> >>> tends to crash often with this driver so I suppose your problem is the
> >>> same.
> >>>
> >> Can confirm that once pulse (on FC9 at least) gets involved it sounds
> >> terrible.
> >>
> >> I worked out that I had removed a package pulseaudio-esound-compat at
> >> some point in the past and never realised that it contains the symlinks
> >> that gets Gnome to start the pulse server.
> >> Once that was fixed the desktop effects started working but only out of
> >> my USB headset... and nothing I can find in the gui lets me do anything
> >> about it.
> >>
> >
> > In many cases, the pulse problem comes from the in accurate DMA position
> > calculation. PA is often too aggressively updating buffers.
> >
> Thanks, I knew there was a reason I stripped pulse out of this machine
> when I installed FC9.
> Is that a bug in pulse or is it something that will improve with the
> sbxfi driver?
Basically it's a bug of the driver.
> >> mplayer and firefox/flash sound terrible, very tinny and scratchy.
> >> This is with the base_rate=48000 option set in modprobe.conf
> >>
> >
> > Do you mean a regression with 48kHz in comparison with 96kHz?
> >
> >
> Sorry that was a bit ambiguous, I'd never tried 96kHz.
> Have just changed base_rate to 96kHz and it performs identically to 48kHz.
> Pulse mangles the sound in just the same manner at 48kHz or 96kHz.
Ah, so you meant mplayer/flash with PA backend?
> While I was poking about in my alsa configuration I noticed that there
> is no /etc/alsa/cards/SBXFi.conf
> I think pulse looks for it, get errors shown after running pulseaudio -vv
> ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition
> 'cards.SBXFi.pcm.surround51.0:CARD=0'
> Would that make any difference to anything?
> (Sorry if pulse issues are totally off-topic)
It just tries to non-existing configuration, and you can ignore it.
Takashi
next prev parent reply other threads:[~2008-10-28 19:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 11:42 sbxfi - What works/doesn't summary Jason Harvey
2008-10-28 12:47 ` The Source
2008-10-28 17:40 ` Jason Harvey
2008-10-28 19:02 ` Takashi Iwai
2008-10-28 19:33 ` Jason Harvey
2008-10-28 19:36 ` Takashi Iwai [this message]
2008-10-28 20:15 ` Jason Harvey
2008-10-29 4:28 ` The Source
2008-10-29 4:45 ` The Source
2008-10-29 5:03 ` The Source
2008-10-29 5:07 ` The Source
2008-10-29 5:15 ` The Source
2008-10-29 9:29 ` Takashi Iwai
2008-10-29 16:12 ` The Source
2008-10-29 9:31 ` Takashi Iwai
2008-10-29 15:55 ` Jason Harvey
[not found] ` <49088718.8000308@jasonline.co.uk>
2008-10-29 15:58 ` Takashi Iwai
2008-10-29 17:01 ` Jason Harvey
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=s5hy708h5r1.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=softdevice@jasonline.co.uk \
--cc=thesourcehim@gmail.com \
/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