From: Lee Revell <rlrevell@joe-job.com>
To: jpshark <jpomanto@satx.rr.com>
Cc: alsa list <alsa-user@lists.sourceforge.net>,
alsa-devel@sc8-sf-spam1.sourceforge.net,
James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: doom 3 sounds also messed up
Date: Thu, 10 Mar 2005 12:09:47 -0500 [thread overview]
Message-ID: <1110474587.12805.23.camel@mindpipe> (raw)
In-Reply-To: <1110474067.6829.9.camel@linux.site>
On Thu, 2005-03-10 at 11:01 -0600, jpshark wrote:
> Lee, I don't know why Gnome is using 44100 if it's suppose to default to
> 48000. It's version 2.6 with SuSE 9.2 on a fresh install (yesterday).
> You said I'll have to use the ALSA plug layer to get 48000. I don't know
> what you mean. Can you explain? Please make it newb friendly. Thanks.
Sorry, though I do use it, I don't know the internals of Gnome well
enough to comment further. Maybe someone else can help?
Really, the root cause of all these problems with the Audigy LS driver
is that it's almost 100% reverse engineered. It's impressive that James
got it to work so well. But apparently people are buying Audigy LS
hardware and expecting it to work as well as a real SBLive or Audigy.
That's just not going to happen until Creative gives us some more docs
(or even better, a driver, but fat chance). There are some pretty good
reverse engineers on alsa-devel but a reverse engineered driver will
just never work as well as one written with proper docs.
Maybe we should update the soundcard matrix to make it clear that the
Audigy LS is not supported on the same level as the emu10k1/2.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
parent reply other threads:[~2005-03-10 17:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1110474067.6829.9.camel@linux.site>]
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=1110474587.12805.23.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@sc8-sf-spam1.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=jpomanto@satx.rr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.