From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: manuel.jander@mat.utfsm.cl
Cc: Alsa Devel list <alsa-devel@lists.sourceforge.net>
Subject: Re: OpenAL - ALSA interface proposal. I request for comments...
Date: Mon, 15 Dec 2003 03:20:35 +0000 [thread overview]
Message-ID: <3FDD2883.7060106@superbug.demon.co.uk> (raw)
In-Reply-To: <1071455606.17638.45.camel@localhost>
Manuel Jander wrote:
> Hi,
>
> Since there is almost nothing else to do to support the Aureal Vortex
> 3D processor on Linux, just as i announced some time ago i started
> designing a OpenAL interface for ALSA. The design is meant to be
> applicable to other hardware too.
>
> I made a preliminary description, from what i have done so far, because
> i want to allow other more experienced people to comment and give input
> to this.
>
> I posted it in plain text. I hope that is compatible enough.
> http://galadriel.mat.utfsm.cl/~mjander/aureal/alsa/OpenAL-ALSA.txt
>
> Well, please give it a read, and tell what do you think about. Thank you
> very much.
>
> Best Regards
It does not seem like you have read much about alsa. The interface
between alsa-kernel and alsa-lib is liable to change at any point
whereas the alsa-lib to application api might change, but will always
ABI compatible.
If there are features of a sound card that you cannot access via
alsa-lib, just find ways to add them to alsa-lib first. Everything
needed on the hardware should be accessible via alsa-lib.
Cheers
James
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
prev parent reply other threads:[~2003-12-15 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 2:33 OpenAL - ALSA interface proposal. I request for comments Manuel Jander
2003-12-15 2:34 ` Paul Davis
2003-12-15 3:20 ` James Courtier-Dutton [this message]
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=3FDD2883.7060106@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=manuel.jander@mat.utfsm.cl \
/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.