From: Ryan Underwood <nemesis-lists@icequake.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: alsa hw params on SB Pro
Date: Sun, 20 Feb 2005 01:19:46 -0600 [thread overview]
Message-ID: <20050220071945.GD22658@dbz.icequake.net> (raw)
In-Reply-To: <Pine.HPX.4.33n.0502141038070.20014-200000@studcom.urz.uni-halle.de>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
On Mon, Feb 14, 2005 at 10:43:47AM +0100, Clemens Ladisch wrote:
>
> Probably you've been using some device using the plug plugin.
Yes, this is true. Perhaps I misunderstood the purpose of the plughw
device. I thought it is so ALSA lib can internally convert
application's data into a suitable hardware format. In the case of SB
Pro, it would seem reasonable that if the app is giving a 44.1KHz 2ch
stream, plughw layer would convert either to 22KHz or to 1ch for the
underlying hardware, since otherwise the playback will completely fail.
So far, I haven't found the way to make this work correctly. I think it
can be done with asound.conf if it is really not the job of alsa-lib,
but I don't know how to only convert >22KHz streams to 1ch while leaving
other streams as 2ch.
Problem with using hw:0 directly is that this is not really a flexible
hardware in supported stream formats (U8 samples only, for example, as
well as max 2ch rate at 22KHz). So plughw is much preferable in this
respect for app compatibility.
If there is a question why an old SBPro is still being used, well, it's
the built-in sound chip on a laptop... in fact, it is part of a CS4232
chip, but the WSS component of that chip does not work correctly with
either snd-cs4232 or snd-ad1848 - eventually after playing some sound
(sometimes for a long while), the chip locks up and must be power cycled
to restore the WSS component. I suspect it is a problem in the
hardware, but it is very strange that e.g. SBPro and OPL components do
continue to work afterwards. The message that I get when I attempt to
reload snd-cs4232 is:
Feb 19 19:00:37 localhost kernel: ALSA
../../alsa-kernel/isa/cs423x/cs4231_lib.c:386: cs4231_mce_down - auto
calibration time out (1)
which provides no real help, just that the CS4248 hardware seems to have
stopped responding.
--
Ryan Underwood, <nemesis@icequake.net>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-02-20 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 5:36 alsa hw params on SB Pro Ryan Underwood
2005-02-10 17:17 ` Takashi Iwai
2005-02-10 17:29 ` Giuliano Pochini
2005-02-14 9:43 ` Clemens Ladisch
2005-02-20 7:19 ` Ryan Underwood [this message]
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=20050220071945.GD22658@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--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 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.