aboutsummaryrefslogtreecommitdiffstats
path: root/OpenAL32/Include/alMain.h
Commit message (Collapse)AuthorAgeFilesLines
* Add methods to "map" a buffer's storageChris Robinson2018-01-201-0/+12
| | | | | | | | | | | | | | | | | | | | | | Requires the MAP_READ_BIT or MAP_WRITE_BIT flags to be OR'd with the format upon a call to alBufferData, to enable mappable storage for the given access types. This will fail if the format requires internal conversion and doesn't resemble the original input data, so the app can be guaranteed the size, type, and layout of the original data is the same as what's in storage. Then alMapBufferSOFT may be called with appropriate bit flags to get a readable and/or writable pointer to the buffer's sample storage. alUnmapBufferSOFT must be called when access is finished. It is currently invalid to map a buffer that is attached to a source, or to attach a buffer to a source that is currently mapped. This restriction may be eased in the future, at least to allow read- only access while in use (perhaps also to allow writing, if coherency can be achieved). Currently the access flags occupy the upper 8 bits of a 32-bit bitfield to avoid clashing with format enum values, which don't use more than 16 or 17 bits. This means any future formats are limited to 24-bit enum values, and also means only 8 flags are possible when declaring storage. The alternative would be to add a new function (alBufferStorage?) with a separate flags parameter.
* Remove unnecessary private AL_SOFT_buffer_samples2 definitionsChris Robinson2018-01-191-73/+0
|
* Define DECL_VLA where it's usedChris Robinson2018-01-161-6/+0
|
* Finalize ALC_SOFT_device_clockChris Robinson2018-01-151-15/+0
|
* Avoid unnecessarily using type aliasesChris Robinson2018-01-141-6/+0
|
* Remove the SAFE_CONST macroChris Robinson2018-01-141-42/+0
| | | | | Seems compilers are now allowing a pointer-to-type-array to implicitly convert to pointer-to-const-type-array.
* Avoid fixed-PATH_MAX-size buffersChris Robinson2018-01-131-8/+0
| | | | | Windows still needs to use MAX_PATH in a couple places, but that macro's guaranteed there.
* Move the FORCE_ALIGN macro to threads.hChris Robinson2018-01-121-10/+0
|
* Make a couple functions inlineChris Robinson2018-01-121-7/+3
|
* Define a function where it's usedChris Robinson2018-01-111-18/+0
|
* Move logging declarations to a separate headerChris Robinson2018-01-111-57/+2
|
* Avoid including alMain.h in ringbuffer.cChris Robinson2018-01-111-14/+0
|
* Move a forward declaration to the othersChris Robinson2018-01-111-2/+1
|
* Move the EffectList array to alEffect.c/hChris Robinson2018-01-111-8/+0
|
* Move the ringbuffer declarations to a separate headerChris Robinson2018-01-111-20/+0
| | | | And rename alcRing.c to ringbuffer.c for consistency.
* Move the FPU mode declarations to a separate headerChris Robinson2018-01-111-32/+0
| | | | Also don't use inheritance with FPUCtl.
* Move the config function declarations to their own headerChris Robinson2018-01-111-10/+0
| | | | And rename alcConfig.c to alconfig.c for consistency.
* Move the CPU capability flags to a separate headerChris Robinson2018-01-111-11/+0
|
* Move the compressor/limiter declarations to their own headerChris Robinson2018-01-111-28/+0
|
* Move the polymorphic/inheritance macros to a separate headerChris Robinson2018-01-111-94/+1
|
* Move some HRTF structures to hrtf.hChris Robinson2018-01-111-30/+2
|
* Avoid using macros to access anonymous structuresChris Robinson2018-01-111-33/+40
|
* Rename the device's temp buffer storage to be more genericChris Robinson2018-01-091-5/+2
|
* Move the UNEXPECTED macro to the main header and rename itChris Robinson2018-01-071-0/+8
|
* Add queries to get the source offset with the device clockChris Robinson2017-12-031-0/+2
|
* Avoid a separate function to query ambisonic mode supportChris Robinson2017-09-271-12/+8
| | | | | | Now FuMa and ACN channel orders are required, as are FuMa, SN3D, and N3D normalization schemes. An integer query (alcGetIntegerv) is added for the maximum ambisonic order.
* Re-update effect slots when context properties changeChris Robinson2017-09-271-1/+11
| | | | | Also keep all free property update structs together in the context instead of per-object.
* Don't update context and listener props unnecessarilyChris Robinson2017-09-271-0/+2
|
* Update the context state properties separatelyChris Robinson2017-09-271-0/+5
| | | | | | | | | | | | | The context state properties are less likely to change compared to the listener state, and future changes may prefer more infrequent updates to the context state. Note that this puts the MetersPerUnit in as a context state, even though it's handled through the listener functions. Considering the infrequency that it's updated at (generally set just once for the context's lifetime), it makes more sense to put it there than with the more frequently updated listener properties. The aforementioned future changes would also prefer MetersPerUnit to not be updated unnecessarily.
* Manually save and restore the FPU rounding mode on WindowsChris Robinson2017-09-191-0/+3
| | | | | | | Apparently there is a bug with at least MinGW-W64 where fegetenv and fesetenv do not properly save and restore the FPU rounding mode, resulting in the rounding mode remaining as round-to-zero after certain function calls. I do not know if this also affects MSVC, but better safe than sorry for now.
* Add a front-stablizer config option for surround sound modesChris Robinson2017-07-311-0/+3
| | | | | | | | | | | | This improves a stereo (front-left + front-right) sound "image" by generating a front-center channel signal. Done correctly, it helps reduce the comb effects and phase errors associated with using only two speakers to simulate center sounds. Note that it shouldn't be used if the front-center channel is already included in the positional audio mix (the dialog effect is okay). In general, it may actually be better to exclude the front-center channel from the positional audio mix and use this to generate front-center output.
* Use macros to set and restore the mixer FPU modeChris Robinson2017-07-131-0/+11
|
* Store the default effect slot in the contextChris Robinson2017-07-131-7/+4
|
* Store the QSA backend's ExtraData in the wrapper structChris Robinson2017-06-291-2/+0
|
* Remove the fastf2u conversion functionChris Robinson2017-06-271-5/+0
|
* Clean up some messy rounding codeChris Robinson2017-06-261-0/+18
|
* "Convert" the QSA backend to the new APIChris Robinson2017-06-181-19/+0
| | | | | | | | | | I say "convert" because it takes the lazy way and essentially just embeds the wrappers into the backend. It's done this way because I lack the means to check any changes, even syntactically. This also means the device's ExtraData field is still needed. However, this does mean all the backends are now using the new API. Code related to the old interface can now be removed.
* Make the dithering depth configurableChris Robinson2017-06-171-1/+1
|
* Add a new compressor/limiterChris Robinson2017-05-271-2/+30
| | | | | | This is just for the output limiter right now, but in the future can be used for the compressor EFX effect. The parameters are also hardcoded, but can be made configurable after 1.18.
* Finalize ALC_SOFT_output_limiterChris Robinson2017-05-251-5/+0
|
* Add an option to dither 8- and 16-bit outputChris Robinson2017-05-231-0/+4
|
* Finalize AL_SOFT_source_spatializeChris Robinson2017-05-111-6/+0
|
* Update AL_SOURCE_SPATIALIZE_SOFT valueChris Robinson2017-05-061-1/+1
| | | | | | Though it didn't strictly clash since it was for a different component (global state vs source property), 0x1213 was used by AL_RESAMPLER_NAME_SOFT. Probably best to avoid duplicate property values regardless.
* Calculate the output limiter gain using the RMSChris Robinson2017-05-051-1/+2
|
* Start an extension to change the source's spatialize propertyChris Robinson2017-05-051-0/+6
|
* Finalize AL_SOFT_source_resamplerChris Robinson2017-05-031-13/+0
|
* Start an extension to toggle the output limiterChris Robinson2017-04-301-0/+5
|
* Implement a limiter on the device outputChris Robinson2017-04-261-0/+2
| | | | | | This reduces the output volume when the mixed samples extend outside of -1,+1, to prevent excessive clipping. It can reduce the volume by -80dB in 50ms, and increase it by +80dB in 1s (it will not go below -80dB or above 0dB).
* Remove const from _Atomic vars to make Clang happyChris Robinson2017-04-211-0/+14
| | | | | | | | Clang does not allow using C11's atomic_load on const _Atomic variables. Previously it just disabled use of C11 atomics if atomic_load didn't work on a const _Atomic variable, but I think I'd prefer to have Clang use C11 atomics for the added features (more explicit memory ordering) even if it means a few instances of breaking const.
* Use more sensible values for the source resampler enumsChris Robinson2017-04-211-4/+4
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-29 15:38:40 +0000