summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove the now-unneeded click removal buffers for the deviceChris Robinson2014-03-2310-73/+20
| | | | | | They are still there for auxiliary sends. However, they should go away soon enough too, and then we won't have to mess around with calculating extra "predictive" samples in the mixer.
* Don't feed the HRTF mix to the click removal and pending click buffersChris Robinson2014-03-231-40/+3
| | | | | The coefficients (which control the volume and panning) already use stepping to non-abruptly fade the mix.
* Step mixing gains per-sample for non-HRTF mixingChris Robinson2014-03-237-60/+212
| | | | | | | | | | | | | | | | | | | | | | | | This fades the dry mixing gains using a logarithmic curve, which should produce a smoother transition than a linear one. It functions similarly to a linear fade except that step = (target - current) / numsteps; ... gain += step; becomes step = powf(target / current, 1.0f / numsteps); ... gain *= step; where 'target' and 'current' are clamped to a lower bound that is greater than 0 (which makes no sense on a logarithmic scale). Consequently, the non-HRTF direct mixers do not do not feed into the click removal and pending click buffers, as this per-sample fading would do an adequate job of stopping clicks and pops caused by extreme gain changes. These buffers should be removed shortly.
* Move the step counter and moving flag to DirectParamsChris Robinson2014-03-235-14/+25
|
* Store the HrtfState directly in the DirectParamsChris Robinson2014-03-2310-63/+49
|
* Don't try to use __restrict as a replacement for restrictChris Robinson2014-03-231-13/+2
| | | | | The compiler it's intended for, MSVC, can't use it anyway because of problems it causes with __declspec(restrict).
* Add a stub 'soft' MIDI synth handlerChris Robinson2014-03-224-1/+147
| | | | | Eventually this one will be used to handle MIDI internally, using our own mixers and resamplers.
* Move some HRTF and mixer structs to alu.hChris Robinson2014-03-222-63/+60
|
* Use a void* for the MidiSynth Delete method paramChris Robinson2014-03-223-18/+9
|
* Use a void* for the backend Delete method paramChris Robinson2014-03-227-73/+32
|
* Use a void* for the effect state Delete method paramChris Robinson2014-03-2113-56/+40
|
* Avoid a size_t-to-ALuint conversion warningChris Robinson2014-03-211-1/+1
|
* Increase the vector reserve as needed when pushing in new itemsChris Robinson2014-03-214-25/+21
|
* Rename the vector's Max field to CapacityChris Robinson2014-03-213-15/+15
|
* Use vectors for the GenModListChris Robinson2014-03-212-167/+103
|
* Add a generic vector interface and use it for the active effect slotsChris Robinson2014-03-217-36/+95
|
* Use flexible array members to pad the device and context structsChris Robinson2014-03-202-4/+10
| | | | | This helps avoid the convoluted math otherwise required to ensure the default slot and listener, respectively, are aligned.
* Keep track of the mix countChris Robinson2014-03-192-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | The purpose of this is to provide a safe way to be able to "swap" resources used by the mixer from other threads without the need to block the mixer, as well as a way to track when mixes have occurred. The idea is two-fold: It provides a way to safely swap resources. If the mixer were to (atomically) get a reference to an object to access it from, another thread would be able allocate and prepare a new object then swap the reference to it with the stored one. The other thread would then be able to wait until (count&1) is clear, indicating the mixer is not running, before safely freeing the old object for the mixer to use the new one. It also provides a way to tell if the mixer has run. With this, a thread would be able to read multiple values, which could be altered by the mixer, without requiring a mixer lock. Comparing the before and after counts for inequality would signify if the mixer has (started to) run, indicating the values may be out of sync and should try getting them again. Of course, it will still need something like a RWLock to ensure another (non-mixer) thread doesn't try to write to the values at the same time. Note that because of the possibility of overflow, the counter is not reliable as an absolute count.
* Use a union to combine HRTF and non-HRTF mixer paramsChris Robinson2014-03-196-50/+52
|
* Select the mixer when setting the mixer-specific parametersChris Robinson2014-03-191-39/+42
|
* Store some source mixing parameters in the active source structChris Robinson2014-03-197-127/+139
|
* Use a separate struct for tracking active sourcesChris Robinson2014-03-186-34/+65
|
* Add another directory to .gitignoreChris Robinson2014-03-171-0/+1
|
* Remove some unneeded code and unnecessary macros in the OpenSL backendChris Robinson2014-03-171-73/+20
|
* Store the old-style backend funcs in the wrapperChris Robinson2014-03-174-30/+33
|
* Don't define HAVE_DYNLOAD with the IDE parserChris Robinson2014-03-171-1/+1
|
* Don't assume the default mmdevapi device is in the collectionChris Robinson2014-03-171-2/+2
|
* Avoid GCC's macro arg concat extension with IDE parsingChris Robinson2014-03-171-1/+1
|
* Return the original value from CompExchange*Chris Robinson2014-03-093-30/+27
|
* Remove the Apple-specific atomic function implementations.Chris Robinson2014-03-091-36/+0
| | | | | | I'm not sure if they're even used, but they were rather ugly and are set to get even uglier since they don't follow normal conventions (missing exchange, and cas not returning the original value).
* Update config file commentsChris Robinson2014-03-091-17/+29
|
* Use the correct array sizeChris Robinson2014-03-081-2/+2
|
* Improve int-to-float and uint-to-float conversionsChris Robinson2014-03-081-2/+2
|
* Only require MSADPCM block alignment to be a multiple of 2Chris Robinson2014-03-061-2/+2
|
* Only sign-expand the nibble when neededChris Robinson2014-03-061-4/+3
|
* Move the sample conversion routines to a separate fileChris Robinson2014-03-054-1261/+1279
|
* Implement a simplistic MSADPCM encoderChris Robinson2014-03-051-19/+47
| | | | It's not particularly good, but it's better than silence.
* Allocate enough temp space for the ADPCM decoders and encodersChris Robinson2014-03-051-4/+4
|
* Use specialized methods for converting ALshort to IMA4 and MSADPCMChris Robinson2014-03-051-2/+32
| | | | As before, to avoid unnecessary direct copies
* Use specialized methods for converting IMA4 and MSADPCM to ALshortChris Robinson2014-03-051-8/+39
| | | | | Since the decoder methods already convert to ALshort, there's no need to use a temp buffer that's just going to copy directly to the destination.
* Use maxi to clamp an int to a lower-boundChris Robinson2014-03-051-1/+1
|
* Expand the sign bit on the initial MSADPCM delta valueChris Robinson2014-03-051-0/+1
|
* Add an extension to support MSADPCM buffer formatsChris Robinson2014-03-045-28/+342
|
* Add an extension to alter the block alignment for buffer unpack/pack opsChris Robinson2014-03-044-19/+85
| | | | | | | | | | | | | | | | This is for unpacking (reading, e.g. alBufferData) and packing (writing, e.g. alGetBufferSamplesSOFT) operations. The alignments are specified in sample frames, with 0 meaning the default (65 for IMA4, 1 otherwise). IMA4 alignment must be a multiple of 8, plus 1 (e.g. alignment = n*8 + 1), otherwise an error will occur during (un)packing. Chenging the block alignment does not affect already-loaded sample data, only future unpack/pack operations... so for example, this is perfectly valid: // Load mono IMA4 data with a block alignment of 1024 bytes, or 2041 sample // frames. alBufferi(buffer, AL_UNPACK_BLOCK_ALIGNMENT_SOFT, 2041); alBufferData(buffer, AL_FORMAT_MONO_IMA4, data, data_len, srate); alBufferi(buffer, AL_UNPACK_BLOCK_ALIGNMENT_SOFT, 0);
* Parameterize the block alignmentChris Robinson2014-03-041-111/+152
|
* Use alloca for temp space decoding/encoding IMA4 blocksChris Robinson2014-03-033-4/+28
|
* Reduce explicit template declarations and ignore IMA4-to-IMA4 conversionsChris Robinson2014-03-031-159/+35
| | | | | | Since we never store IMA4 data in buffers, we should only ever convert from (user input) or to (user output) IMA4. Once we allow user-specified pack/unpack block alignment, this wouldn't be a simple memcpy anyway.
* Store the original frame size alignment in the bufferChris Robinson2014-03-033-12/+29
|
* Move PATH_MAX fallback definitions to alMain.hChris Robinson2014-02-275-31/+9
|
* Add back the missing PATH_MAX fallbackChris Robinson2014-02-271-0/+10
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-15 11:12:36 +0000