From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - liboss 0001518]: dmix plugin doesn´t work with OSS kernel emulation
Date: Tue, 20 Dec 2005 01:20:08 +0100 [thread overview]
Message-ID: <f451a5886193564f76cca267b0edd6c9@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1518>
======================================================================
Reported By: kyromaster
Assigned To:
======================================================================
Project: ALSA - liboss
Issue ID: 1518
Category:
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 10-31-2005 01:22 CET
Last Modified: 12-20-2005 01:20 CET
======================================================================
Summary: dmix plugin doesn´t work with OSS kernel emulation
Description:
I hope this isn´t misplaced here, but IMHO this is a bug in the
architecture. Many people have those crappy AC97 codecs without hardware
mixing and want to use OSS apps beside their ALSA ones (like teamspeak
together with games). dmix works but not with the kernel emulation, and
"aoss" is not easy enough for newbies and also doesn´t work with all
apps.
So will dmix support be added to the kernel OSS emulation layer?+
======================================================================
----------------------------------------------------------------------
rlrevell - 10-31-05 05:18
----------------------------------------------------------------------
It's not possible because dmix runs in userspace. The solution is for the
distros to run all OSS apps with "aoss" so newbies don't have to deal with
it at all. If aoss does not work with some apps it's either a bug in aoss
or a bug in those apps and should be reported here.
----------------------------------------------------------------------
rlrevell - 12-20-05 01:20
----------------------------------------------------------------------
Not a bug
Issue History
Date Modified Username Field Change
======================================================================
10-31-05 01:22 kyromaster New Issue
10-31-05 05:18 rlrevell Note Added: 0006582
12-20-05 01:20 rlrevell Status new => closed
12-20-05 01:20 rlrevell Note Added: 0007098
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-20 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 0:20 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-30 23:22 [ALSA - liboss 0001518]: dmix plugin doesn´t work with OSS kernel emulation bugtrack
2005-12-20 1:04 bugtrack
2005-12-20 0:43 bugtrack
2005-10-31 4:18 bugtrack
2005-10-31 0:22 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=f451a5886193564f76cca267b0edd6c9@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