Talk:OpenAL

Listing game engines
Would it be better to just list the game engines instead of games used? It'll scale better and is a bit more informative. ENGIMa 04:52, 1 Dec 2004 (UTC)


 * I agree with this. There are good reasons to not list games. At best, technology shall be listed. This boils down to Doom3, UnrealTechnology2, Quake3 (merge Q3 and D3 with "id technology"?). I'm not sure about America's Army: Operations, Hitman 2, Freedom Fighters, Psychonauts. Because those are just mere products and doesn't add anything useful, I suggest to just pull em out. Personally I believe this is just mere marketing which is not going to add useful content to wiki.


 * My proposal is to change:

''The following games make use of OpenAL: Doom 3, Unreal 2, Unreal Tournament 2003, Unreal Tournament 2004, Jedi Knight 2, Jedi Knight: Jedi Academy, Postal 2, America's Army: Operations, Hitman 2, Freedom Fighters, Psychonauts.
 * to:

''Many games used OpenAL, notably those based on Unreal Technology 2 and games from ID-software based engines. Other games also employed this technology.''


 * Considering wiki's policy however, this change will possibly be undone in future.
 * By the way, maybe it's a nice idea to say that first AL implementations were really bad and doppler effects are still broken (if you read last mails on the mailing list, you know how much Creative is done to get it work in 1.1).
 * Please also suggest your opinion on the AL extension issue and the lack of recording.


 * MaxDZ8 12:27, 28 September 2005 (UTC)


 * According to various feedback [here] the list shall be mantained. I disagree with that but I respect Wiki's policy so I've used the compromise solution of grouping everything in a list. This should give us the best of both worlds. MaxDZ8 15:59, 6 October 2005 (UTC)

History of development section
Anyone interested in a history of development section? Loki, Creative, SWeng, the "lost" OpenAL version of Alpha Centauri? Why the Linux version uses Lisp for its config file? Ah, good times. — Preceding unsigned comment added by 66.77.144.8 (talk) 02:03, 11 November 2005 (UTC)

Creative or Loki?
I don't think it's right to say that Creative developed OpenAL. They currently host the web site and developer resources - but the original API was developed by Loki in order to port Windows games to Linux - and much of the development work was done by OpenSource enthusiasts and by Apple.

IMHO, the credit in the opening paragraph should go to Loki.

SteveBaker 13:45, 1 February 2006 (UTC)

Questionable "Portability" and Other Criticisms
I am not sure if this is appropriate to place in the main page, but OpenAL's "portability" is quite poor in my opinion. Since Creative took hold of OpenAL, development of this library has been pretty much been developed directly for Windows by Creative employees, while the ever dwindling open-source community around OpenAL takes this code and makes it work for Linux, OS X, etc. I do have experience in using the OpenAL library in the development of an audio engine simulatenously across three platforms (Linux, Windows, OS X), and that engine does not fit my definition of "cross-platform" at all in its current state. I make this claim for the following reasons:


 * The trend seems to be that once a new version of OpenAL is released for Windows, the same version is not seen for other platforms for a period of months
 * The library does not behave consistently across platforms for the same version (this is based on personal experience)
 * Documentation for older versions of OpenAL is totally absent from the OpenAL website, despite that those older versions are the most current versions for many systems
 * Function definitions are usually, but not always, consistent across platforms
 * Because of many of the above issues, the source code for a "working" OpenAl engine has to be littered with #ifdef macros to ensure correct operation

I have personally brought these issues forth to the OpenAL community (including Creative) on their mailing list, and no one there refuted my claims.

http://opensource.creative.com/pipermail/openal-devel/2006-April/004278.html

I am not sure if such criticisms (which although stated as my own, are shared by many others) belongs on the main page for this topic, as it may be seen as slanderous or as a non-neutral-point-of-view. But I am interested in discussing a proposal of putting these criticisms on the main page for OpenAL.

--RootsLINUX 03:45, 16 June 2006 (UTC)


 * Unluckily, mailing lists are to be taken with extra care, especially when you are the one posting in the mailing list, as that can be considered original research. I suggest trying to find reliable sources that verify the suggested information and cite them in the article. We need third-parties to report about this, like CNN, Ars Technica, eWeek, etc. Hope it is a bit clearer now. -- ReyBrujo 04:02, 16 June 2006 (UTC)


 * (I'm the author of the second revision of the ALUT library that is shipped with the latest versions of OpenAL - so you can't regard me as an NPOV source here!) I agree that since Creative (and to a lesser degree, Apple) took the reins, the main thrust of the development has been in support of Windows...and even more specifically - for Creative's own hardware under Windows. To some degree the API has been directed towards the hardware features that Creative's hardware has. However, in the absence of these two companies, OpenAL was a dead project. There was very little work done on it between Loki's sad demise and Creative picking it up. The Linux version certainly lags the Windows/MacOS versions quite severely and the root cause of that is that there is a separate code base for the two implementations. What really needs to be done to fix this problem is to merge the Linux, MacOSX and Windows versions into a single source base and use conditional compilation for the OS-specific differences.  This would tend to make developers think about the impact of their changes on the other platforms rather than (as now) simply diving in and changing code as if no other platforms existed. However, there are quite a few other problems with OpenAL that aren't going to get fixed unless there is a large influx of developers who don't work for either Apple or Creative. OpenGL gets around this commercial driving of the API by having an active ARB composed of hardware vendors, OS developers and application developers. OpenAL's charter says there should be an ARB - but it does not exist and has never met. SteveBaker 14:18, 16 June 2006 (UTC)

Disagreeing history
http://www.openal.org/openal_vista.html Clearly states that both Creative and Loki started it together, and straight from the horses mouth. -74.118.188.16 17:40, 15 March 2007 (UTC)

Sound card support
Would it be an idea to list (at least particially) what soundcards do work with OpenAL? If such a list exists, would someone link to it? —Preceding unsigned comment added by 212.130.70.253 (talk) 11:13, 9 September 2007 (UTC)

Wrong WikiProject?
Why is this in the VideoGames WikiProject? Shouldn't it be, just like OpenGL, in the WikiProject Computing? --DanielPharos (talk) 12:27, 11 May 2008 (UTC)

EAX?
One thing I've never understood is what the relation between EAX and OpenAL is. Is EAX still an extension to OpenAL? If I'm not mistaken, EAX 2.0 is basically a part of DirectSound3D hence it's supported by many non Creative products. EAX 3.0 - 5.0 are just extensions to DirectSound3D. If it is just an extension, has there been any effort by non Creative developers to "Extensions can be promoted to ARB (Architecture Review Board) status, indicating a standard extension which will be maintained for backwards compatibility. ARB extensions have the prospect of being added to the core API after a period of time." since it would seem to me this would make it easier for them to support EAX 5.0 in their hardware (although they may still have patent issues to contend with) Nil Einne (talk) 17:45, 24 May 2008 (UTC)


 * To make things more complicated i'd like to add EFX to the discussion. It was only mentioned on the EAX page, so i added a link from EFX to the OpenAL page and a redirect from Effects Extension. I also edited this page to shortly mention EFX and EAX, but sincerely invite anyone who understands more of it than I to change my line in a decent paragraph about the subject. Pizzaman79 (talk) 14:37, 17 February 2009 (UTC)

Implementations
Would it be useful to have a section listing the current implementations of OpenAL? Although with OpenGL this would be unreasonable, since there must be thousands (one for each driver). But OpenAL there is only a handful: The original OpenAL SI (the reference implementation) and OpenAL Soft. —Preceding unsigned comment added by Kiplingw (talk • contribs) 22:18, 12 February 2010 (UTC)

Perhaps there should be such a list because this comment is very misleading in suggesting that there are only two. Other quite distinct implementations on Windows alone include Rapture3D and specific hardware ones for NForce (OpenAL 1.0), X-Fi (OpenAL 1.1 with EFX), Audigy and other sound-cards. There's also an implementation for XBox360 which (while restricted to developers, like all console APIs) has shipped with millions of games like Race Driver GRID, DiRT, F1 2010, Fable, Brian Lara international Cricket, etc and been implemented on top of both the original console-specific XAudio and the more recent multiplatform XAudio2. Simon N Goodwin (talk) 09:51, 5 January 2012 (UTC)

Last open source release / internal algorithm
I closely inspected the code in the final open source release.

That version actually does something extremely simple - it doesn't do ANY fancy effects with the audio, time delay, doppler, what-have-you - assuming you have four speakers, all it does is weight the emission of sound from an object between the speakers depending on its position relative to the listener. That's it!

Toby Douglass (talk) 09:35, 2 October 2010 (UTC)

Open Source
How can an API be open/closed source. surely it's whether the API is a closed or open standard. It is irrelevant if implementations themselves are open/closed. IRWolfie- (talk) 15:47, 18 December 2010 (UTC)


 * It's certainly a borderline issue right now. Originally, OpenAL had a single implementation - and it was OpenSource - so at the time the article was started, OpenAL was an actual library, and it was 100% true to say that "OpenAL is an OpenSourced library".  However, relatively recently, one branch of the implementation has become closed-source - while the other remains open.  Is OpenAL now an API specification which happens to have two implementations?  Or is OpenAL still that same OpenSourced library...which now happens to have a closed source 'clone'?  I don't think it's clear at this point. SteveBaker (talk) 15:58, 18 December 2010 (UTC)

You can't call a PROPRIETARY Audio Library OPEN SOURCE Audio Library no more than you than you can call a round wheel square! What Creative has now is ClosedAL which happens to use OpenAL's API. Creative has no legal control over the True OpenAL, only the Architecture Review Board does as per the charter, and if that board doesn't truly exist then maybe OpenGL's Architecture Review Board could assume that role for audio as well as graphics. — Preceding unsigned comment added by Sly Snake (talk • contribs) 14:59, 26 February 2014 (UTC)

The standard libraries included in the OpenAL 1.1 redistributable installer are NOT closed source. https://github.com/rpavlik/openal-svn-mirror/tree/master/OpenAL-Windows This is dated from 2006 and can be compiled fully from source. 80.162.33.59 (talk) 23:00, 2 November 2021 (UTC)

Disadvantages
Currently the disadvantages is stated to be misleading. It describes that OpenAL is not fit for multi-listener and time difference of arrival applications. Please, feel free to adjust the wording such that the reader of this article knows what the scope/extend of OpenAL is, not erroneously given the reader the idea that it can be used for such applications.

Maybe it is an idea to start the page (or create a separate page) for a generic description of 3D audio rendering software: Andy (talk) 11:35, 5 August 2012 (UTC)
 * Direction (heading) effects
 * Doppler effects
 * Time difference of arrival effects (propagation delays)
 * Interaural time difference and level difference effects
 * HRTF effects (modeling human perception by head-related transfer functions)
 * Obstruction, occlusion, diffraction, reflection, scattering
 * Reverberation effects from physical objects and surfaces
 * Physical collision effects (coupling with collision detection in a physics engine: hear a ball bouncing/towards towards you)
 * Source radiation patterns
 * Spreading loss / distance attenuation
 * Atmospheric effects (humidity, temperature)
 * Multiple listeners

Drjoms (talk) 14:40, 8 January 2014 (UTC) My first on Wikipedia, so I am a bit nervous. if OpenAL is just API - it's not API's fault that nothing implemented mufti listener perspective. In fact, define mufti listener. Two people from two different computers playing networked OpenAL enabled game that use same API can be considered as multi listener? Two people playing same game from SAME computer but from 2 different processes are multi listeners? I believe this option is supposedly must be implemented in client software if different hardware is involved. At least, this is how it was originally intended. Anything that uses second set of hardware for multiplexing signal is acting as second server that takes advantage of specific API in a way. In a simplier example, I see it, this way: "This car's model has major disadvantage, it can't fly". Technically speaking it's correct, but it breaks assumption of cars, that they(generally) can't, at this moment of history, fly. API describes how something can be achieved, not code for implementation. drjoms GMT+2 15:39 7 January 2014

DevMaster.net OpenAL Tutorials
This link doesn't actually go to any OpenAL tutorials. I believe it should be removed. Any reason why it shouldn't? — Preceding unsigned comment added by Topsfield99 (talk • contribs) 21:47, 8 April 2013 (UTC)

OpenAL.org is blank and pending deletion
The page is listed in status AUTORENEWPERIOD and the contents are blank. Is this project discontinued? Anybody knows what would be the replacement front page? Yurivict (talk) 22:33, 9 November 2013 (UTC)

Notability discussion
What evidence is there that OpenAL meets WP:Notability? If there is none, then it should be deleted per Wikipedia guidelines, as I don't see any rationale for this unverified article to exist. An editor has made an analogy to OpenSL ES, but I also don't seen any evidence OpenSL ES passes notability, so that doesn't help me understand why this article should remain. Rolf H Nelson (talk) 07:11, 17 March 2016 (UTC)


 * OpenAL is included in a large number of games, both open-source and commercial, as one of the audio options. I have played some of them. Yes, it might not be as popular as the graphical equivalent it is named after, OpenGL, but along with DirectSound on Windows and CoreAudio on macOS and ALSA on Linux and OSS on BSD operating systems (the OS-level audio APIs) there are quite a number of audio APIs such as OpenAL, PulseAudio, JACK, Gstreamer, SDL/SDL2, etc. A lot of the open-source software that uses OpenAL uses it via another multimedia library called SFML that has OpenAL as a dependency. One thing I use that uses OpenAL for its audio output is the VisualBoyAdvance-M emulator for GameBoy Advance, GameBoy Color, and GameBoy, where OpenAL gets better results than DirectSound... it happens to be the best emulator for those handheld Nintendo game systems. Also there are many games listed on here that use OpenAL.


 * What I would ask you is how can such a widely used audio library as OpenAL NOT be considered notable, especially given its many years of history, the different companies involved, the fact that OpenAL support is built-in to certain operating systems like Apple macOS if I recall correctly, that it is a major product of Creative Labs which is the biggest manufacturer of sound cards and has been for decades, the large variety of software that uses it, and so on? If it is not notable we might as well remove all the other articles about cross-platform APIs and software libraries too from Wikipedia since apparently you don't think those are notable. Even if OpenAL development has stalled, it is a fairly stable API and quite a number of projects use it as a dependency and as an audio option and in many of them it works better than other options for audio output. I would say if there is any reason development on it stalled it is because their work is pretty much complete and all they need to do is fix any bugs that may arise.


 * Anyway it is nonsensical to me that you are even considering OpenAL to possibly not be notable. OBVIOUSLY it is notable. Maybe not as important as OpenGL, but still, plenty of notable software uses it for audio output and would have to use something else for audio output if OpenAL did not exist. This isn't to say that I use OpenAL personally when I code. I added audio to a game myself and I used SDL2_mixer... although SDL2_mixer has its own problems... for me the major one being difficulty getting its dependency libvorbisfile (which is part of libvorbis that is not usually installed if someone installs libvorbis). There are a lot of cross-platform audio frameworks and it is hard to find one of them that really works quite well at A) being the same across all operating systems, B) being easy to use as a dependency that can be compiled and built, C) figuring out and using its API correctly, D) actually having the features you need and not having important features missing, and E) getting the bloody thing to actually work correctly without any problems in your software that uses it as a dependency. There isn't really ANY cross-platform audio framework that meets all of those criteria well for most projects. For instance, in the game where I used SDL2_mixer for audio, it was the least worst option for my use case (which involved MIDI music among other things and many audio frameworks lack that feature which was necessary to me along with working on both Windows and all the UNIXes), I would not call it the best option. Some people find that OpenAL is the least worst option for their particular use cases, it really depends on what software you are trying to write and what meets your requirements the best. As a programmer I just find your proposal to delete this article absurd, even if OpenAL is not my audio library of choice (in fact I rejected it out of hand for the game I was working on because it did not fit the criteria for my project, namely its API was not the right sort of API that I wanted, providing features I didn't want instead of the features I did want, whereas I found SDL2_mixer was perfect for my particular use case).


 * Wikipedia is used as a resource by many programmers. Notable software libraries used by a lot of software all have articles here, any library of that kind that I can think of has an article here. Deleting this article makes absolutely no sense whatsoever, what next, are you going to delete the article on the Open Sound System still used by BSD operating systems due to the fact that OSS is old and there are better audio libraries and APIs now such as PulseAudio? Anyway, look at the list of games on OpenAL's official site that they talk about: https://openal.org/games/ Many of the top games that are considered some of the best open-source games that can be played on Linux are on that list, plus that list is incomplete, there are actually plenty of others they don't mention there. The official game of the U.S. Army, America's Army, is one of the games that uses OpenAL. How on Earth is OpenAL possibly not notable? This just makes no sense. Countless popular games that are quite notable use it and they would not have any audio were it not for OpenAL (well OK they probably would but the developers would have had to pick another audio library instead). Look at this list of games that use OpenAL: http://www.blueripplesound.com/compatible-games It has Minecraft on it among other top-ranked games! A popular game with many clones that got bought out by Microsoft! Seriously, OpenAL is used by a lot of games and it is DEFINITELY notable. You have got to be kidding me with this nonsense about it not being notable. Sure, lots of people might like it, but even in this blog post: http://camlorn.net/posts/april2014/shortcomings-of-openal.html the person complaining about OpenAL admits at the end that OpenAL is the only free/open source way to get anything like surround sound audio that they know of, and all their frustrations with OpenAL are compounded by the fact that they don't see any other option they can use for their use case (3D audio, or HRTF as the technical term goes).


 * And if something is the only open-source library providing 3D audio effects (HRTF or Head-Related Transfer Function) in widespread use, and it is used by countless popular games, obviously it is notable. I mean COME ON, you have got to be kidding me saying it's not notable. We should just get rid of the silly tag questioning OpenAL's notability, this is obviously notable. And I am someone who has called for other articles to be removed for not being notable in the past, and successfully gotten Wikipedia to take several down, I don't think everything is notable, but this DEFINITELY is. Maybe it is not the best written article on Wikipedia with the best citations to PROVE it is notable beyond any possible shadow of a doubt, but that is no reason to accuse it of not being notable and take it down. Anyway, I would like to know what possible reasoning you or anyone else might have for claiming OpenAL is not notable. A lack of newspaper articles from the local Podunk Gazette about it? Gimme a break, that's an absurd justification. The sources Wikipedia likes best, such as newspapers and magazines, do not tend to write about software libraries that are simply used as dependencies by other software. Most reporters for such publications are completely uninformed about the subject matter. This doesn't mean we should delete articles on this topic. Then again, we shouldn't create a Wikipedia article for every single project any random person starts on GitHub, we don't need a separate Wikipedia article for every single variant/fork of NetHack for instance, NetHack has its own wiki that does that. There has to be a balance. But OpenAL is widely used in enough popular software, with enough of a history, and enough of a unique niche as the only free cross-platform 3D audio library, that I think it is clearly notable enough for our general-purpose Wikipedia. Even if programmers do find OpenAL annoying to code with, that does not make it any less notable... web developers find Internet Explorer 6 annoying to code for but it is still notable. Plus OpenAL actually does work really great once programmers write code that correctly works with it... writing the code is the hard part... OpenAL produces better quality audio than the DirectSound that Microsoft uses as part of DirectX. At least, it has less of a latency problem and the buffering system works better so there is less staticky noise, in software where that can be an issue (e.g. the emulator VisualBoyAdvance-M, which lets users choose between OpenAL and DirectSound, which I have personal experience using). Plus DirectX is Windows-only... another reason OpenAL is important, it helps games be more portable, even if there are differences between the Creative Labs version of OpenAL for Windows and the OpenAL-Soft version of OpenAL for UNIX-based operating systems. Differences between Windows and UNIX-based OSes happen with all sorts of things, for instance curses libraries, with the PDcurses on Windows versus ncurses on UNIX-based OSes, but curses libraries are still notable on Wikipedia.


 * Anyway I am removing the notability tag for these reasons, as no credible argument has been made that OpenAL is not notable, and indeed, none could possibly be made because it IS notable. It is just one user tagging an article as not being notable because they don't understand why it is notable, without putting forth any reasonable arguments to justify said tagging. I have also looked at your history and you seem to be really into the OpenAI article, and it appears you stumbled by chance onto the similarly-named OpenAL article. While I do believe your edits to say that OpenAL is not notable were made in good faith, I don't think that you have any knowledge whatsoever of the subject matter of cross-platform audio libraries and APIs. This is relevant because knowledge of this topic is absolutely necessary to knowing whether or not OpenAL is a notable cross-platform audio library and API. --Yetisyny (talk) 05:23, 2 August 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on OpenAL. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20040803034419/http://www.devmaster.net/articles.php?catID=6 to http://www.devmaster.net/articles.php?catID=6

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 23:53, 4 September 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on OpenAL. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20121230175931/http://connect.creativelabs.com/openal/Documentation/The%20OpenAL%20Utility%20Toolkit.htm to http://connect.creativelabs.com/openal/Documentation/The%20OpenAL%20Utility%20Toolkit.htm
 * Added archive https://archive.is/20130119200045/http://opensource.creative.com/pipermail/openal-devel/2012-May/005903.html to http://opensource.creative.com/pipermail/openal-devel/2012-May/005903.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 12:03, 14 December 2017 (UTC)

你好
你好 103.134.96.143 (talk) 07:25, 21 February 2023 (UTC)

Trading
Trading — Preceding unsigned comment added by 2402:8100:26E3:FEF1:CCD6:9AB4:3591:919 (talk) 18:31, 6 June 2023 (UTC)