aboutsummaryrefslogtreecommitdiffstats
path: root/Alc
Commit message (Collapse)AuthorAgeFilesLines
* Add some integer casts, and a range checkChris Robinson2014-03-232-3/+8
|
* Remove the now-unneeded click removal buffers for the deviceChris Robinson2014-03-238-66/+19
| | | | | | 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-236-58/+205
| | | | | | | | | | | | | | | | | | | | | | | | 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-233-10/+19
|
* Store the HrtfState directly in the DirectParamsChris Robinson2014-03-237-32/+31
|
* Add a stub 'soft' MIDI synth handlerChris Robinson2014-03-222-0/+143
| | | | | Eventually this one will be used to handle MIDI internally, using our own mixers and resamplers.
* 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-2111-54/+34
|
* 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-213-24/+20
|
* 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-214-9/+75
|
* Use flexible array members to pad the device and context structsChris Robinson2014-03-201-4/+4
| | | | | 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-191-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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-195-41/+41
|
* 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-193-85/+97
|
* Use a separate struct for tracking active sourcesChris Robinson2014-03-182-15/+27
|
* 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-173-29/+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
|
* 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).
* Add an extension to support MSADPCM buffer formatsChris Robinson2014-03-041-1/+3
|
* Add an extension to alter the block alignment for buffer unpack/pack opsChris Robinson2014-03-041-3/+5
| | | | | | | | | | | | | | | | 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);
* Move PATH_MAX fallback definitions to alMain.hChris Robinson2014-02-274-31/+0
|
* Add back the missing PATH_MAX fallbackChris Robinson2014-02-271-0/+10
|
* Move OpenDataFile to helpers.c so other sources can use itChris Robinson2014-02-272-131/+133
|
* Add an explicit cast to make Windows happyChris Robinson2014-02-261-2/+2
|
* Don't fallback to relative filename handling if opening as absolute failsChris Robinson2014-02-261-26/+27
|
* Expand environment variables for all config option values when loadingChris Robinson2014-02-262-31/+77
|
* Support environment variables in the hrtf_tables config valueChris Robinson2014-02-251-4/+34
|
* Attempt to restore the Neon-enhanced ApplyCoeffsStep methodChris Robinson2014-02-231-7/+21
| | | | Unable to test, but it hopefully works.
* Revert "Apply HRTF coefficient stepping separately"Chris Robinson2014-02-234-19/+74
| | | | | | | | | This reverts commit 25b9c3d0c15e959d544f5d0ac7ea507ea5f6d69f. Conflicts: Alc/mixer_neon.c Unfortunately this also undoes the Neon-enhanced ApplyCoeffsStep method.
* Move HRTF macros and function declarations to a separate headerChris Robinson2014-02-234-0/+31
|
* Move the default hrtf table to an external fileChris Robinson2014-02-232-878/+12
|
* Add a return value to FindHrtfFormatChris Robinson2014-02-232-7/+9
|
* Check the hrtf config option earlierChris Robinson2014-02-231-8/+8
| | | | | This is to make sure it tries to find an HRTF-compatible format before reseting the device, just like when using ALC_HRTF_SOFT.
* Avoid checking the hrtf config option twiceChris Robinson2014-02-231-2/+3
|
* Search system-dependant data paths for relative hrtf table filenamesChris Robinson2014-02-231-1/+126
|
* Avoid using a global static buffer for config loadingChris Robinson2014-02-231-3/+51
|
* Fix indentationChris Robinson2014-02-231-20/+20
|
* Fix a race condition in the mmdevapi message queue threadChris Robinson2014-02-091-0/+6
|
* Add some extra traces to the mmdevapi backendChris Robinson2014-02-091-0/+8
| | | | Trying to track down the cause of some reported errors.
* Change the autowah to have a cutoff range of 20Hz to 20KHzChris Robinson2014-02-071-1/+1
| | | | | | This is the same as allowed in the SF2 spec for its filter cutoff generator, which can be used for a wah effect in MIDI. It makes sense to use a similar range here.
* Fix some typesChris Robinson2014-02-072-4/+4
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-30 10:30:22 +0000