From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001735]: OSS emulation 4-channel mode rear channels not working
Date: Fri, 30 Jun 2006 18:05:41 +0200 [thread overview]
Message-ID: <8f07e0b012ea070c11676d9b9b7b9e5b@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1735>
======================================================================
Reported By: giorby
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1735
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution: Debian sarge 3.1
Kernel Version: 2.6.15
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 01-11-2006 10:51 CET
Last Modified: 06-30-2006 18:05 CEST
======================================================================
Summary: OSS emulation 4-channel mode rear channels not
working
Description:
If I use the OSS emulation and try to play some 4-channel material, with
say mplayer or bplay, the rear channels are just a copy of the front
channels, whereas the same configuration and software worked perfectly
well with the native OSS driver. As the native OSS drivers are faded out
in favour of ALSA, I assumed that the emulation layer should be a sort of
drop-in replacement. Am I wrong?
Tested with Linux kernels 2.6.12/2.6.15.
======================================================================
----------------------------------------------------------------------
giorby - 01-11-06 11:08
----------------------------------------------------------------------
Sorry, I forgot to identify my soundcard...
/proc/asound/devices lists:
0 [Live ]: EMU10K1 - SBLive! Value [CT4832]
SBLive! Value [CT4832] (rev.6, serial:0x80271102) at
0xd400, irq 5
----------------------------------------------------------------------
jcdutton - 06-30-06 18:05
----------------------------------------------------------------------
Both the mentioned applications now support ALSA, so OSS emulation is not
required any more.
Issue History
Date Modified Username Field Change
======================================================================
01-11-06 10:51 giorby New Issue
01-11-06 10:51 giorby Distribution => Debian sarge 3.1
01-11-06 10:51 giorby Kernel Version => 2.6.15
01-11-06 11:08 giorby Note Added: 0007561
01-12-06 03:40 Adrian Bunk Issue Monitored: Adrian Bunk
06-30-06 18:05 jcdutton Status new => closed
06-30-06 18:05 jcdutton Note Added: 0010747
======================================================================
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-06-30 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 16:05 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-11 10:08 [ALSA - driver 0001735]: OSS emulation 4-channel mode rear channels not working bugtrack
2006-01-11 9:51 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=8f07e0b012ea070c11676d9b9b7b9e5b@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