[openal] API redesign for ease of use?

Daniel Gibson metalcaedes at gmail.com
Tue Jul 28 14:56:48 EDT 2015

On 07/28/2015 07:30 PM, Victorious wrote:
> Hi,
> OpenAl-soft is currently compatible with the original OpenAl spec. Its c-style API is not as user-friendly as it could be; for example, having to know which variant of alSourcei, alSourcef, etc to use and constants to modify properties. Functions also don't return any errors encountered, requiring you to explicitly check for it. See these posts as well:
> http://camlorn.net/posts/april2014/shortcomings-of-openal.html
> http://camlorn.net/posts/december2014/horror-of-audio-output.html
> Has an API redesign been considered? How important would compatibility  with the spec be?

Many of these problems sound like they could be "fixed" by writing a 
wrapper around OpenAL with a user-friendlier API (whatever it may look 


More information about the openal mailing list