nuclearmonster / openal-website Goto Github PK

Hello @rcgordon, Hello all!

I recently looked through the openal extension registry and found that extensions by OpenAL soft are not listed.

As of what I can tell, the following extensions are defined and implemented by OpenAL soft:

    AL_SOFT_block_alignment, AL_SOFT_buffer_samples, AL_SOFT_buffer_sub_data,
    AL_SOFT_deferred_updates, AL_SOFT_direct_channels, AL_SOFT_loop_points,
    AL_SOFT_MSADPCM, AL_SOFT_source_latency, AL_SOFT_source_length,
    ALC_SOFTX_device_clock, ALC_SOFTX_HRTF, ALC_SOFT_loopback,
    ALC_SOFTX_midi_interface, ALC_SOFT_pause_device

Is there a reason why they are not listed, or is there a chance that someone will do that?
Some of them seem pretty well documented: http://kcat.strangesoft.net/openal-extensions/

Thanks in advance!
Sincerely, Squareys.

Error code: 1628: Failed to complete installation.

GPT chat does not allow editing sessions within this chat, this leads to memory overflow and the number of allowed characters and, accordingly, to breakdowns and failures in communication.
overflowing the chat with information that is no longer relevant leads to an extra load on system resources and, accordingly, negatively affects the number of users in the system at the same time, as it limits the chat’s ability to communicate with them

While http://openal.org is returning the website content.

http://rgho.st/7TGdH44zD

Site version is 2.0.7.0.
You can check digital signature is "Creative Labs Inc", same as website
And please don't pack exe in zip on site.

More precisely the mentioned tab from https://openal.org redirects to https://openal.org/mailman/listinfo/openal

GPT chat does not have feedback from its developers, so any question in the chat to improve its work does not find an answer. It is not true. To improve the system, you need to be attentive to user suggestions and questions.

Documentation for use of alSourceQueueBuffers and alSourceUnqueueBuffers such as Queuing Buffers on a Source Page 14 and Multi-Channel Buffers Page 140 as well as the reference for both methods one page 59/60 states the use of alSourcei and not alGetSourcei to get info about processed buffers.

Not a huge deal, but maybe enough to throw someone off.

There should also likely be a separate issue that some kind of auto-generated HTML documentation would be preferable to the current PDF.