All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: mjander@mat.utfsm.cl
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA - 3D api interaction (OpenAL?)
Date: Mon, 01 Sep 2003 20:47:48 +0200	[thread overview]
Message-ID: <s5h65kcny5n.wl@alsa2.suse.de> (raw)
In-Reply-To: <1062440362.835.1.camel@localhost>

At Mon, 01 Sep 2003 14:19:22 -0400,
Manuel Jander wrote:
> 
> Hi,
> 
> This may sound crazy, but i'm reverse engineering the A3d engine of the
> Aureal Vortex Cards. The hardware interface is pretty simple, and i
> guess that at least some filtering and reflection rendering can be done
> in hardware with the information i was able to gather until now.
> 
> The hardest part in my opinion is the userland API. I looked at some A3D
> examples, and i really liked that API a lot. Its just like OpenGL, but
> its audio instead of light what you get. Is there any effort to
> integrate 3D capabilities into the ALSA scheme ? any extended feature
> IOCTL, or somewhat like that ?

no.

> I only know about the creative labs
> OpenAL implementation, but AFAIK, thats just a tweaked OSS driver, aand
> its not designed to be used with other soundcards that are not made by
> Crippled Labs. Any comments ?

the linux version of open-al supports only two-speaker mode.
EAX on sb live is supported only on windows.
but i think the API itself of open-al is enough generic.


the implementation of 3d things on alsa-lib would be too much, IMO.
if a hardware supports 3d effects, they can be likely implemented on
the ALSA control API, so that the upper-library can treat them
generally.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-09-01 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01 18:19 ALSA - 3D api interaction (OpenAL?) Manuel Jander
2003-09-01 18:47 ` Takashi Iwai [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=s5h65kcny5n.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mjander@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.