aboutsummaryrefslogtreecommitdiffstats
path: root/Alc/mixer_neon.c
Commit message (Collapse)AuthorAgeFilesLines
* Add a mixing function to blend HRIRsChris Robinson2017-05-031-0/+1
| | | | | | This is a bit more efficient than calling the normal HRTF mixing function twice, and helps solve the problem of the values generated from convolution not being consistent with the new HRIR.
* Handle the source offset fraction as an ALsizeiChris Robinson2017-04-081-20/+20
|
* Pre-compute the sinc4 resampler coefficient tableChris Robinson2017-04-081-4/+4
|
* Rework HRTF coefficient fadingChris Robinson2017-03-111-36/+1
| | | | | | | | | | | | | | | This improves fading between HRIRs as sources pan around. In particular, it improves the issue with individual coefficients having various rounding errors in the stepping values, as well as issues with interpolating delay values. It does this by doing two mixing passes for each source. First using the last coefficients that fade to silence, and then again using the new coefficients that fade from silence. When added together, it creates a linear fade from one to the other. Additionally, the gain is applied separately so the individual coefficients don't step with rounding errors. Although this does increase CPU cost since it's doing two mixes per source, each mix is a bit cheaper now since the stepping is simplified to a single gain value, and the overall quality is improved.
* Remove the sinc8 resampler optionChris Robinson2017-02-191-79/+4
| | | | | Perf shows less than 1 percent CPU difference from the higher quality bsinc resampler, but uses almost twice as much memory (a 128KB lookup table).
* Put BsincState in a generic unionChris Robinson2017-02-131-19/+19
|
* Porperly check for and use __builtin_assume_alignedChris Robinson2017-02-131-6/+13
|
* Clean up the bsinc mixer a bitChris Robinson2017-02-121-2/+2
|
* Add NEON-enhanced resamplersChris Robinson2017-02-121-0/+260
|
* Use ALsizei for sizes and offsets with the mixerChris Robinson2017-01-161-20/+20
| | | | | | Unsigned 32-bit offsets actually have some potential overhead on 64-bit targets for pointer/array accesses due to rules on integer wrapping. No idea how much impact it has in practice, but it's nice to be correct about it.
* Pass current and target gains directly for mixingChris Robinson2016-10-051-7/+10
|
* Make some pointer-to-array parameters constChris Robinson2016-10-041-3/+3
|
* 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
|
* Mix gain steps using SIMD with NeonChris Robinson2016-08-051-0/+24
|
* Implement a Neon-enhanced MixRowChris Robinson2016-06-011-0/+25
|
* Calculate HRTF stepping params right before mixingChris Robinson2016-02-141-19/+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.
* Use the correct realignment size for post-stepping mixingChris Robinson2015-10-181-1/+1
|
* Avoid double-checks for the stepping mixer loopsChris Robinson2015-09-301-2/+5
|
* Replace separate vaddq_f32/vmulq_f32 calls with a vmlaq_f32Chris Robinson2015-09-301-1/+1
|
* Define MixHrtf directly instead of through a SUFFIX macroChris Robinson2015-08-151-3/+2
|
* Use linear gain steppingChris Robinson2014-11-251-2/+2
|
* Use a separate method to set initial HRTF coefficientsChris Robinson2014-11-241-0/+19
|
* Partially revert "Use a different method for HRTF mixing"Chris Robinson2014-11-231-0/+32
| | | | | | | | | | | | 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-32/+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.
* Fix Neon mixer definitionChris Robinson2014-08-311-2/+2
|
* Combine the direct and send mixersChris Robinson2014-06-131-56/+16
|
* Combine some dry and wet path typesChris Robinson2014-06-131-9/+9
|
* 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
|
* Remove unnecessary ifdefsChris Robinson2014-05-041-2/+0
| | | | | mixer_sse.c and mixer_neon.c are only compiled when the relavent headers are found anyway.
* Always use the current gains when mixingChris Robinson2014-05-041-6/+8
| | | | | | 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.
* Make sure all gain steps are applied with the SSE and Neon mixersChris Robinson2014-05-031-32/+9
|
* Remove the click removal buffers for auxiliary effect slotsChris Robinson2014-03-231-1/+1
|
* Fix Neon gain step loopsChris Robinson2014-03-231-2/+2
|
* Add gain stepping to the send mixersChris Robinson2014-03-231-23/+43
|
* 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-14/+32
| | | | | | | | | | | | | | | | | | | | | | | | 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
|
* 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-231-6/+9
| | | | | | | | | This reverts commit 25b9c3d0c15e959d544f5d0ac7ea507ea5f6d69f. Conflicts: Alc/mixer_neon.c Unfortunately this also undoes the Neon-enhanced ApplyCoeffsStep method.
* Implement dry and wet mixers for NeonChris Robinson2014-01-261-3/+77
| | | | Code provided by Philippe Simons <[email protected]>.
* Apply HRTF coefficient stepping separatelyChris Robinson2013-11-101-7/+2
|
* Use C99's inline instead of __inlineChris Robinson2013-05-281-9/+9
|
* Use restrict instead of RESTRICTChris Robinson2013-05-221-5/+5
|
* Constify the direct and send parameters given to the mixerChris Robinson2012-10-151-1/+1
|
* Update HRTF codeChris Robinson2012-09-111-2/+4
| | | | | | | | | | | This update allows for much more flexibility in the HRTF data. It also allows for HRTF table file names to include "%r" to represent the device's playback rate (e.g. if you set hrtf-%r.mhr, then it will try to use hrtf-44100.mhr or hrtf-48000.mhr depending if the device's output rate is 44100 or 48000, respectively). The makehrtf utility has also been updated to support more options and input file formats, as well as the new mhr format.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-29 23:49:39 +0000