From: Martin Habets <errandir_news@mph.eclipse.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Urgent question
Date: Mon, 9 Jan 2006 11:28:13 +0000 [thread overview]
Message-ID: <20060109112813.GC10770@palantir8> (raw)
In-Reply-To: <0AEFDFCCEC85B24E8051B23293C2CB640F2503@MMMSTCAE1.muac.corp.eurocontrol.int>
On Mon, Jan 09, 2006 at 11:07:36AM +0100, PIVATY Bertrand wrote:
> The sound quality looks good when using the onboard sound card provided,
> but when using any PCI sound card the sound quality is really poor.
Have you tried different PCI cards? Or is the issue with a specific
model or chipset?
> Do you have any idea of what could be the reason, or any track where we
> should investigate.
The first obvious step is to figure out if it is an application problem
or a kernel/alsa issue. I usually run 'aplay' or 'speakertest' with a simple
test file to figure that out.
If these work okay it's most likely an application problem.
> The software is running on Suse 9.0 with the last Alsa version.
This does not mean a whole lot to me. Could you send the kernel and alsa
version as reported by uname and /proc/asound/version?
--
Martin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2006-01-09 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 10:07 Urgent question PIVATY Bertrand
2006-01-09 11:17 ` James Courtier-Dutton
2006-01-09 11:28 ` Martin Habets [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 14:04 PIVATY Bertrand
2006-01-09 14:54 ` James Courtier-Dutton
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=20060109112813.GC10770@palantir8 \
--to=errandir_news@mph.eclipse.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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