From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001191]: Center channel and 32-bit emulation broken when upgrading alsa-lib from 1.0.8 to 1.0.9 on nForce 4 system
Date: Wed, 15 Jun 2005 22:00:57 +0200 [thread overview]
Message-ID: <54a53e69d005ae3382b058f77323b8fd@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1191>
======================================================================
Reported By: robert
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 1191
Category: hw specific configuration
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 06-14-2005 11:45 CEST
Last Modified: 06-15-2005 22:00 CEST
======================================================================
Summary: Center channel and 32-bit emulation broken when
upgrading alsa-lib from 1.0.8 to 1.0.9 on nForce 4 system
Description:
I'm running AMD64 gentoo on an nforce4 system, audio is nVidia CK804 with
ALC850. I can emerge the newest alsa-driver package (1.0.9b), but when I
upgrade alsa-lib to 1.0.9, three things happen. First, my 32 bit sound
applications, like mplayer32, don't work with alsa anymore. Second, the
center channel on all 5.1 sound goes out. Third, the a/v synchonization
on mplayer gets hosed using alsa (oss emulation still ok.)
======================================================================
----------------------------------------------------------------------
jdthood - 06-15-05 14:01
----------------------------------------------------------------------
Do the problems go away if you disable the dmix plugin?
----------------------------------------------------------------------
robert - 06-15-05 22:00
----------------------------------------------------------------------
How does one do that?
Issue History
Date Modified Username Field Change
======================================================================
06-14-05 11:45 robert New Issue
06-15-05 14:01 jdthood Note Added: 0005023
06-15-05 22:00 robert Note Added: 0005045
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-06-15 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 20:00 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 3:12 [ALSA - lib 0001191]: Center channel and 32-bit emulation broken when upgrading alsa-lib from 1.0.8 to 1.0.9 on nForce 4 system bugtrack
2005-11-01 14:45 bugtrack
2005-08-19 1:10 bugtrack
2005-08-19 0:46 bugtrack
2005-08-18 19:33 bugtrack
2005-08-18 19:31 bugtrack
2005-08-18 19:12 bugtrack
2005-06-15 21:42 bugtrack
2005-06-15 12:01 bugtrack
2005-06-14 9:45 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=54a53e69d005ae3382b058f77323b8fd@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