From: R Chan <rspchan@starhub.net.sg>
To: alsa-devel@lists.sourceforge.net
Subject: Transgaming comments on Alsa for WineX
Date: Sun, 21 Dec 2003 09:29:16 +0800 [thread overview]
Message-ID: <3FE4F76C.2070204@starhub.net.sg> (raw)
Transgaming have investigated Alsa 1 as a sound option to for WineX.
http://www.transgaming.com/showthread.php?news=98
Excerpt
" ALSA, of particular interest to TransGaming's Linux audience, does not
provide
much of an added benefit over OSS. The primary speed advantage, hardware
mixing,
a slower kludgy implementation use due to the fact that looping sound
doesn't appear
to be supported; although full duplex support should be easier to
provide than with OSS.
The major drawback of ALSA is that its mmap interface is not compatible
with what is
required for DirectSound unless undocumented interfaces are used. All in
all it appears
that using ALSA would provide some speed advantages for newer cards, but
to be
done properly would require a rewrite of the winealsa driver. Thus we
would suggest
that, for the time being, people continue to use the OSS emulation layer of
ALSA with "MMap" = "Y" enabled in their config file to get the best
performance if it's supported on their sound card."
Apart from mmap which I guess is architectural and quite difficult to
change, what about their
comments on looping sound - useful?
Cheers
Richard
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next reply other threads:[~2003-12-21 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 1:29 R Chan [this message]
2003-12-21 2:24 ` Transgaming comments on Alsa for WineX James Courtier-Dutton
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=3FE4F76C.2070204@starhub.net.sg \
--to=rspchan@starhub.net.sg \
--cc=alsa-devel@lists.sourceforge.net \
/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.