aboutsummaryrefslogtreecommitdiffstats
path: root/Alc/mixer_c.c
Commit message (Collapse)AuthorAgeFilesLines
* Rename MatrixMixerFunc to RowMixerFuncChris Robinson2016-09-021-2/+2
|
* Use a more specialized mixer function for B-Format to HRTFChris Robinson2016-08-121-0/+1
|
* Add some more restrict keywordsChris Robinson2016-07-261-1/+1
|
* Rename input_gain to b0Chris Robinson2016-07-261-4/+4
|
* Improve the filter processing functionChris Robinson2016-06-031-2/+35
|
* Use SSE for applying the HQ B-Format decoder matricesChris Robinson2016-05-311-0/+21
|
* Calculate HRTF stepping params right before mixingChris Robinson2016-02-141-12/+0
| | | | | This means we track the current params and the target params, rather than the target params and the stepping. This closer matches the non-HRTF mixers.
* Manually inline and condense the bsinc resamplerChris Robinson2015-11-051-37/+27
|
* Implement a band-limited sinc resamplerChris Robinson2015-11-051-3/+53
| | | | | | | | This is essentially a 12-point sinc resampler, unless it's resampling to a rate higher than the output, at which point it will vary between 12 and 24 points and do anti-aliasing to avoid/reduce frequencies going over nyquist. Code provided by Christopher Fitzgerald.
* Replace the sinc6 resampler with sinc8, and make SSE versionsChris Robinson2015-10-111-3/+3
|
* Avoid double-checks for the stepping mixer loopsChris Robinson2015-09-301-1/+2
|
* Implement a 6-point sinc-lanczos filterChris Robinson2015-09-291-0/+3
|
* Replace the cubic resampler with a 4-point sinc/lanczos filterChris Robinson2015-09-271-3/+3
|
* Define MixHrtf directly instead of through a SUFFIX macroChris Robinson2015-08-151-2/+2
|
* Don't assert the increment value in the copy32 resamplerChris Robinson2015-02-151-2/+1
|
* Use a lookup table to do cubic resamplingChris Robinson2014-12-151-1/+1
|
* Use linear gain steppingChris Robinson2014-11-251-2/+2
|
* Use a separate method to set initial HRTF coefficientsChris Robinson2014-11-241-0/+12
|
* Partially revert "Use a different method for HRTF mixing"Chris Robinson2014-11-231-0/+17
| | | | | | | | | | | | The sound localization with virtual channel mixing was just too poor, so while it's more costly to do per-source HRTF mixing, it's unavoidable if you want good localization. This is only partially reverted because having the virtual channel is still beneficial, particularly with B-Format rendering and effect mixing which otherwise skip HRTF processing. As before, the number of virtual channels can potentially be customized, specifying more or less channels depending on the system's needs.
* Use a different method for HRTF mixingChris Robinson2014-11-221-17/+0
| | | | | | | | | | | | | | | | | | | | | | | This new method mixes sources normally into a 14-channel buffer with the channels placed all around the listener. HRTF is then applied to the channels given their positions and written to a 2-channel buffer, which gets written out to the device. This method has the benefit that HRTF processing becomes more scalable. The costly HRTF filters are applied to the 14-channel buffer after the mix is done, turning it into a post-process with a fixed overhead. Mixing sources is done with normal non-HRTF methods, so increasing the number of playing sources only incurs normal mixing costs. Another benefit is that it improves B-Format playback since the soundfield gets mixed into speakers covering all three dimensions, which then get filtered based on their locations. The main downside to this is that the spatial resolution of the HRTF dataset does not play a big role anymore. However, the hope is that with ambisonics- based panning, the perceptual position of panned sounds will still be good. It is also an option to increase the number of virtual channels for systems that can handle it, or maybe even decrease it for weaker systems.
* Check the absolute gain value for silenceChris Robinson2014-10-311-1/+1
| | | | | Future B-Format support will be using negative gains, which still need to be applied.
* Combine the direct and send mixersChris Robinson2014-06-131-42/+13
|
* Combine some dry and wet path typesChris Robinson2014-06-131-9/+9
|
* Copy samples if needed in the 'copy' resamplerChris Robinson2014-05-211-9/+15
|
* Return a sample pointer from resamplersChris Robinson2014-05-191-8/+7
| | | | Both resampling and filtering now avoid copying samples when they no-op.
* Don't pass the SendParams to the wet-path mixerChris Robinson2014-05-181-8/+6
|
* Don't pass the DirectParams to the dry-path mixerChris Robinson2014-05-181-7/+6
|
* Pass some DirectParams as function parametersChris Robinson2014-05-181-4/+3
|
* Add a ALfilterState method to process multiple samples at onceChris Robinson2014-05-181-0/+8
|
* Always use the current gains when mixingChris Robinson2014-05-041-4/+6
| | | | | | The current gain gets explicitly set to the target when the stepping is finished to ensure the target is still used. This way, however, will allow for asynchronously 'canceling' a fade by setting the counter to 0.
* Remove the last bits of the predictive sample processingChris Robinson2014-03-231-2/+2
|
* Remove the click removal buffers for auxiliary effect slotsChris Robinson2014-03-231-1/+1
|
* Identity gain step is 1, not 0Chris Robinson2014-03-231-1/+1
|
* Add gain stepping to the send mixersChris Robinson2014-03-231-16/+24
|
* Remove the now-unneeded click removal buffers for the deviceChris Robinson2014-03-231-1/+1
| | | | | | 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.
* Step mixing gains per-sample for non-HRTF mixingChris Robinson2014-03-231-12/+18
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* Store the HrtfState directly in the DirectParamsChris Robinson2014-03-231-2/+2
|
* Use a union to combine HRTF and non-HRTF mixer paramsChris Robinson2014-03-191-1/+1
|
* Revert "Apply HRTF coefficient stepping separately"Chris Robinson2014-02-231-2/+7
| | | | | | | | | This reverts commit 25b9c3d0c15e959d544f5d0ac7ea507ea5f6d69f. Conflicts: Alc/mixer_neon.c Unfortunately this also undoes the Neon-enhanced ApplyCoeffsStep method.
* Apply HRTF coefficient stepping separatelyChris Robinson2013-11-101-7/+2
|
* Use an UNUSED macro instead of void-tagging unused parametersChris Robinson2013-10-071-4/+3
|
* Use a macro for the silence thresholdChris Robinson2013-10-061-2/+2
|
* Don't store the effect slot in SendParamsChris Robinson2013-10-061-10/+10
| | | | This makes it much more like DirectParams.
* Use a separate value for the maximum buffer channelsChris Robinson2013-07-231-2/+2
| | | | | | | Unlike the device, input buffers are accessed based on channel numbers instead of enums. This means the maximum number of channels they hold depends on the number of channels any one format can have, rather than the total number of recognized channels. Currently, this is 8 for 7.1.
* Use C99's inline instead of __inlineChris Robinson2013-05-281-12/+12
|
* Use restrict instead of RESTRICTChris Robinson2013-05-221-15/+15
|
* Constify the direct and send parameters given to the mixerChris Robinson2012-10-151-3/+3
|
* Remove the unused Device parameterChris Robinson2012-10-141-3/+1
|
* Store the output buffers in the DirectParams structChris Robinson2012-10-141-3/+4
|
* Remove the now-unused Source parameter from the DryMix methodsChris Robinson2012-10-141-2/+1
|