From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001009]: NVidia CK8S 8ch: a center speaker is always silent in native alsa mode (through alsa-lib), works with oss emulation though
Date: Thu, 7 Apr 2005 16:28:13 +0200 [thread overview]
Message-ID: <db7dc8edaa274ba7e25b57168cc2ae82@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1009>
======================================================================
Reported By: modax
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1009
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Debian unstable
Kernel Version: vanilla 2.6.11.5 with self-compiled alsa-driver
1.0.9rc1
======================================================================
Date Submitted: 03-22-2005 22:34 CET
Last Modified: 04-07-2005 16:28 CEST
======================================================================
Summary: NVidia CK8S 8ch: a center speaker is always silent
in native alsa mode (through alsa-lib), works with oss emulation though
Description:
A center speaker stays quiet while playing 5.1 audio directly through
alsa-lib (eg. with kaffeine (xine) or mplayer using alsa plugin). As a
result, I'm unable to hear what people are speaking in movies because the
speech is usually sent to the center speaker (correct me if i'm wrong. i'm
new to all this 5.1 business). Anyway, adjusting the volume,
muting/unmuting "Center" section, enabling/disabling "Mic As Center/LFE"
doesn't have any effect on the center speaker. It stays silent. However,
as I noted in the summary, the center speaker works with oss audio driver
of xine/mplayer (using oss emulation). However, that mode is not perfect
as the center speaker plays the role of left surround and vice versa. In
addition, a right surround speaker stays always silent (i guess that's
because the RS channel needs to be swapped with LFE; at least I got this
impression by having a look at
/usr/share/alsa/cards/NForce.conf:surround51). To sum up, my problem is
that I can't get the center speaker (which, I guess, is channel 2 on my
hardware) working with native alsa apps playing ac3/5.1 audio.
======================================================================
----------------------------------------------------------------------
modax - 04-04-05 09:59
----------------------------------------------------------------------
This bug is a dupe of
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=0000891. I have seperate
sockets for surround,
center and side channels (8ch) on my board. Disabling hooks helped to get
the center speaker & LFE back. Forcing and especially *locking* "Line-In
As Surround" and "Mic As Center/LFE" is not an universal solution anymore.
It may confuse lots of people. What you should do at least is *not to
lock* those switches. Locking effect is not reflected by mixers and people
like me may get confused because turning on/off the switches doesn't make
any difference although actually it would if locking were disabled. Please
disable locking or better yet do not force those switches on. Thanks!
----------------------------------------------------------------------
tiwai - 04-07-05 16:28
----------------------------------------------------------------------
Disabling locks are fine. I'll fix this issue later (hopefully in time for
1.0.9), though.
The question is whether the current channel routing is correct.
Can you confirm it's OK?
Issue History
Date Modified Username Field Change
======================================================================
03-22-05 22:34 modax New Issue
03-22-05 22:34 modax Distribution => Debian unstable
03-22-05 22:34 modax Kernel Version => vanilla 2.6.11.5 with
self-compiled alsa-driver 1.0.9rc1
03-23-05 13:01 tiwai Note Added: 0004156
03-25-05 00:37 modax Note Added: 0004204
03-25-05 00:37 modax File Added: bug-1009.tar.gz
03-30-05 18:22 tiwai Note Added: 0004268
03-30-05 18:22 tiwai File Added: nforce-conf-test.diff
03-30-05 23:28 modax Note Added: 0004275
04-03-05 17:47 modax Note Added: 0004311
04-04-05 09:59 modax Note Added: 0004324
04-07-05 16:28 tiwai Note Added: 0004358
======================================================================
-------------------------------------------------------
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
next reply other threads:[~2005-04-07 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 14:28 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:59 [ALSA - driver 0001009]: NVidia CK8S 8ch: a center speaker is always silent in native alsa mode (through alsa-lib), works with oss emulation though bugtrack
2005-12-30 23:13 bugtrack
2005-04-24 22:03 bugtrack
2005-04-07 23:55 bugtrack
2005-04-04 7:59 bugtrack
2005-04-03 15:47 bugtrack
2005-03-30 21:28 bugtrack
2005-03-30 16:22 bugtrack
2005-03-24 23:37 bugtrack
2005-03-23 12:01 bugtrack
2005-03-22 21:34 bugtrack
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=db7dc8edaa274ba7e25b57168cc2ae82@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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