From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000320]: FL is FL+FR and FR is FR+FL
Date: Tue, 8 Jun 2004 08:40:11 +0200 [thread overview]
Message-ID: <8f137439a459a288264fc422b55d1129@bugtrack.alsa-project.org> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=0000320
======================================================================
Reported By: Voluspa
Assigned To:
======================================================================
Project: ALSA - driver
Bug ID: 320
Category: PCI - emu10k1
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: Homebrew
Kernel Version: 2.6.6
======================================================================
Date Submitted: 06-01-2004 10:12 CEST
Last Modified: 06-08-2004 08:40 CEST
======================================================================
Summary: FL is FL+FR and FR is FR+FL
Description:
Card: Sound Blaster Live!
Chip: SigmaTel STAC9758/59
Between 1.0.5rc1 and 1.0.5a the Front Left and Front Right signals are
combined, which creates real crappy sound:
Front Left speaker = Front Left + Front Right
Front Right speaker = Front Right + Front Left
Checking the new "Surround Mix" in alsamixer gets even more confusing:
Front Left speaker = Front Left + Front Right + Center
Front Right speaker = Front Right + Front Left + LFE
There are no differences between the 1.0.5rc1 and 1.0.5a in the
proc/asound/card0/codec97#0/ac97#0-0+regs
Btw, the alsamixer options are getting really out of hand...
Eg a new option called just "Front" (I keep it off since I can't hear any
difference).
Mvh
Mats Johannesson
======================================================================
----------------------------------------------------------------------
pzad - 06-08-2004 08:40 CEST
----------------------------------------------------------------------
I think this AC97 codec problem.
Bug History
Date Modified Username Field Change
======================================================================
06-01-04 10:12 Voluspa New Bug
06-01-04 10:12 Voluspa Distribution => Homebrew
06-01-04 10:12 Voluspa Kernel Version => 2.6.6
06-08-04 08:40 pzad Bugnote Added: 0001294
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
next reply other threads:[~2004-06-08 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 6:40 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 13:21 [ALSA - driver 0000320]: FL is FL+FR and FR is FR+FL noreply
2004-06-24 8:48 noreply
2004-06-28 7:14 noreply
2004-06-30 7:00 noreply
2004-06-30 13:36 noreply
2004-07-01 7:43 noreply
2004-09-24 11:32 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=8f137439a459a288264fc422b55d1129@bugtrack.alsa-project.org \
--to=noreply@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 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.