aboutsummaryrefslogtreecommitdiffstats
path: root/OpenAL32/Include
Commit message (Collapse)AuthorAgeFilesLines
* Don't make the source state atomicChris Robinson2018-02-241-1/+1
|
* Remove the unnecessary ComputeAmbientGainsChris Robinson2018-02-181-15/+0
|
* Combine multiple functions called sequentiallyChris Robinson2018-02-111-1/+1
|
* Use a function pointer for applying the dry mix post-processChris Robinson2018-02-102-2/+7
|
* Make the Connected state atomicChris Robinson2018-02-041-1/+1
| | | | Also don't send the Disconnected event more than once.
* Provide more descriptive messages to disconnection eventsChris Robinson2018-02-031-1/+1
|
* Add a disconnected event typeChris Robinson2018-02-032-1/+2
|
* Remove the unused thunk codeChris Robinson2018-02-021-20/+0
|
* Remove the individual source queue and buffer locksChris Robinson2018-02-022-3/+0
| | | | | | | They're inherently protected by the mutex for their respective lists. Should those mutexes be replaced by rwlocks the individual locks should also be reinstated, but they're unlikely to be unless a lot of contention starts happening in the read-only case.
* Store an index to a given source's voiceChris Robinson2018-02-011-0/+5
| | | | For more efficient voice lookups when needed.
* Use a semaphore to signal the event handlerChris Robinson2018-02-011-1/+1
| | | | | | | | | | | Semaphores allow for semi-persistent signals, compared to a condition variable which requires a mutex for proper detection. A semaphore can be 'post'ed after writing some data on one thread, and another thread will be able to recognize it quickly even if the post occured in between checking for data and waiting. This more correctly fixes a race condition with events since the mixer shouldn't be using mutexes, and arbitrary wake-ups just to make sure an event wasn't missed was quite inefficient.
* Send buffer completed events when enabledChris Robinson2018-02-011-1/+1
|
* Add a thread to marshal events from the mixerChris Robinson2018-01-311-1/+14
| | | | | | To avoid having unknown user code running in the mixer thread that could significantly delay the mixed output, a lockless ringbuffer is used for the mixer to provide events that a secondary thread will pop off and process.
* Rename EventLock to make it more clear it's protecting the callbackChris Robinson2018-01-301-1/+1
|
* Make EnabledEvts atomicChris Robinson2018-01-281-1/+1
|
* Use a fixed array for the effect state factory listChris Robinson2018-01-281-3/+0
|
* Don't bother with a return value that's never usedChris Robinson2018-01-271-3/+3
|
* Move some inline functions into a header instead of copying themChris Robinson2018-01-271-4/+13
| | | | | Unfortunately does not include the Lookup* functions, which need the full type declaration to offset the pointer.
* Store filters in an array of listsChris Robinson2018-01-272-16/+10
|
* Store effects in an array of listsChris Robinson2018-01-272-15/+9
|
* Use a vector to store the effect slot pointersChris Robinson2018-01-272-15/+8
| | | | And make the ID a simple index into it (1-base, to avoid ID 0).
* Use an array lookup for source IDsChris Robinson2018-01-271-1/+11
| | | | | This is now similar to buffers, being stored in groups of 64 in a vector with the ID providing the array indices.
* Make some more functions static where they're usedChris Robinson2018-01-271-14/+0
|
* Add a ctz64 fallback using _BitScanForward when availableChris Robinson2018-01-271-1/+15
|
* Check for _BitScanForward64 before using itChris Robinson2018-01-271-4/+4
|
* Use a different method for storing and looking up buffersChris Robinson2018-01-272-11/+61
| | | | | | | | | | | | | | | | | Rather than each buffer being individually allocated with a generated 'thunk' ID that's used with a uint:ptr map, buffers are allocated in arrays of 64 within a vector. Each group of 64 has an associated 64-bit mask indicating which are free to use, and the buffer ID is comprised of the two array indices which directly locate the buffer (no searching, binary or otherwise). Currently no buffers are actually deallocated after being allocated, though they are reused. So an app that creates a ton of buffers once, then deletes them all and uses only a couple from then on, will have a bit of waste, while an app that's more consistent with the number of used buffers won't be a problem. This can be improved by removing elements of the containing vector that contain all-free buffers while there are plenty of other free buffers. Also, this method can easily be applied to other resources, like sources.
* Don't rely on alMain.h in alBuffer.hChris Robinson2018-01-262-71/+18
|
* Make some functions static that are only used in one sourceChris Robinson2018-01-261-9/+3
|
* Add the printf-format attribute to alSetErrorChris Robinson2018-01-251-1/+2
|
* Construct error messages using parameterized valuesChris Robinson2018-01-251-5/+5
|
* Use more appropriate enum values for eventsChris Robinson2018-01-241-7/+7
|
* Add a deprecated event type for alDopplerVelocityChris Robinson2018-01-241-0/+2
|
* Provide messages for the remaining AL errorsChris Robinson2018-01-241-14/+4
|
* Set the buffer load error in LoadDataChris Robinson2018-01-241-0/+5
|
* Call the event callback when an error is generatedChris Robinson2018-01-241-4/+4
| | | | | Most errors don't yet provide correct object IDs or text messages for the AL error.
* Handle event propertiesChris Robinson2018-01-231-2/+14
| | | | | This just implements the event methods insofar as tracked state. No events are generated/reported yet.
* Declare the beginnings of an event extensionChris Robinson2018-01-231-0/+23
|
* Use a new proper buffer function with a flags parameterChris Robinson2018-01-231-4/+6
| | | | | | Rather than hackily combining bit flags with the format, to increase the number of potential flags. alBufferData now behaves as if calling alBufferStorageSOFT with a flags value of 0.
* Track the buffer's mapped sectionChris Robinson2018-01-231-0/+2
|
* Add a flag for persistent mappingChris Robinson2018-01-231-0/+3
| | | | And a function to "flush" a mapped buffer
* Add a flag for alBufferData to non-destructively resize the dataChris Robinson2018-01-221-0/+2
| | | | | | Requires having the same format as the last call to alBufferData. Also only makes sense when given a NULL data pointer, as otherwise the internal data will be overwritten anyway.
* More cleanup for buffer loadingChris Robinson2018-01-212-9/+10
| | | | | Don't bother with unnecessary and unused converters, and remove some unsupported queries.
* Handle double-precision buffers in the mixerChris Robinson2018-01-211-5/+6
|
* Remove support for (signed) byte and ushort sample storageChris Robinson2018-01-211-2/+0
| | | | Also not used without buffer_samples
* Remove (u)int32 sample storage conversionChris Robinson2018-01-211-2/+0
| | | | Unused without the buffer_samples extension
* Remove the old buffer_samples functionsChris Robinson2018-01-211-17/+17
| | | | | | | The symbols are still there and exported to retain ABI compatibility, but they no longer do anything except set an AL_INVALID_OPERATION error. They're also removed from the function and enum tables, since they're not part of any supported extension.
* Fix the return type of the LPALUNMAPBUFFERSOFT typedefChris Robinson2018-01-211-1/+1
|
* Add methods to "map" a buffer's storageChris Robinson2018-01-202-0/+15
| | | | | | | | | | | | | | | | | | | | | | 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.
* Store 8-bit sample types directly as unsigned byteChris Robinson2018-01-191-1/+1
|
* Remove unnecessary private AL_SOFT_buffer_samples2 definitionsChris Robinson2018-01-192-77/+4
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-28 08:27:03 +0000