From: Glenn Maynard <g_sf@zewt.org>
To: alsa-devel@lists.sourceforge.net
Subject: Re: OpenAL- ALSA advanced features hardware support update.
Date: Sun, 21 Dec 2003 23:27:46 -0500 [thread overview]
Message-ID: <20031222042746.GF7080@zewt.org> (raw)
In-Reply-To: <1072063439.1803.31.camel@localhost>
(Oops. Sent privately unintentionally; resending to the list.)
On Sun, Dec 21, 2003 at 11:24:00PM -0400, Manuel Jander wrote:
> The same as for the first iteration of this proposal, please take some
> minutes and give some comments/suggestions back. I need feedback.
I'll give some higher level feedback: Why OpenAL?
I looked at it about a year ago, while rewriting the sound system for
a game with relatively strict sound demands. (StepMania; we wanted
hardware mixing, when possible, and sound-to-gameplay sync to be as
tight as possible, within a couple ms).
I couldn't find any active mailing lists. I couldn't even find any
indication that anyone was working on it at all. I read some of the
Windows source code, and saw what is--without exaggeration--some of
the most heinous, seizure-inducing code I've ever seen. (There were
conditionals and loops nested something like 12 levels deep. I don't
think the programmer understood the concept of the "return" keyword.)
And although the API was decent to look at, it had no way of getting an
accurate hardware play cursor, or any other mechanism to get a good idea
of the currently-playing sample (for eg. graphical sync). We couldn't
reliably sync sound with any smaller resolution than a whole buffer.
I don't think OpenAL has a future. Do you really want to invest your time
in it?
--
Glenn Maynard
-------------------------------------------------------
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 prev parent reply other threads:[~2003-12-22 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031222023843.GE7080@zewt.org>
2003-12-22 3:24 ` OpenAL- ALSA advanced features hardware support update Manuel Jander
2003-12-22 4:27 ` Glenn Maynard [this message]
2003-12-22 6:00 ` Mark Constable
2003-12-22 8:55 ` OpenAL & more Jaroslav Kysela
2003-12-22 6:44 ` OpenAL- ALSA advanced features hardware support update Manuel Jander
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=20031222042746.GF7080@zewt.org \
--to=g_sf@zewt.org \
--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.