Re: Catching output from OpenAL
Re: Catching output from OpenAL
- Subject: Re: Catching output from OpenAL
- From: Paul Davis <email@hidden>
- Date: Mon, 6 Dec 2010 11:20:08 -0500
On Mon, Dec 6, 2010 at 11:14 AM, Zack Morris <email@hidden> wrote:
> IMHO issues like this are serious enough that it's maybe time to fork OpenAL for the modern world where audio isn't much more than 5% of an application's
> overhead, and it's more important to have full control. I would also like to see a general purpose wrapper around CoreAudio and AudioUnits, written in the
> down-to-earth style of more recent APIs like SDL or Ogg Vorbis. Off the top of my head, it would look something like this:
What is fundamentally wrong with OpenAL is that it isn't a pull model
API like ... well, like everything else under the sun these days that
is used for realtime low latency audio playback (CoreAudio,
AudioUnits, VST, JACK, ASIO, WaveRT, PortAudio ... even SDL .. you
name it). BTW, Ogg Vorbis is not an API for playing or capturing
audio.
OpenAL models a few useful (and not exactly hard to implement) DSP
features but doesn't offer any control over latency or signal routing.
Its fundamentally the wrong model to be writing modern audio apps
with.
--p
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden