Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix B-Format HRTF decoding | Chris Robinson | 2015-09-23 | 1 | -5/+8 |
| | |||||
* | Use N3D scaling instead of FuMa | Chris Robinson | 2015-09-23 | 1 | -4/+4 |
| | |||||
* | Allow the hrtf_tables option to be device-specific | Chris Robinson | 2015-09-20 | 1 | -8/+7 |
| | |||||
* | Rename F_2PI to F_TAU | Chris Robinson | 2015-09-13 | 1 | -3/+3 |
| | |||||
* | Allow for device-specific config values | Chris Robinson | 2015-08-28 | 1 | -2/+2 |
| | |||||
* | Use ACN ordering for ambisonics coefficients arrays | Chris Robinson | 2015-08-28 | 1 | -3/+3 |
| | | | | | | Note that it still uses FuMa scalings internally. Coefficients loaded from config files specify if they're FuMa (in both ordering and scaling) or N3D, and will get reordered or rescaled as needed. | ||||
* | Fix the HRTF B-Format decoder's W coefficient | Chris Robinson | 2015-02-14 | 1 | -18/+5 |
| | | | | | And limit it to first-order again, since there will likely need to be extra scalings applied. | ||||
* | Calculate HRTF coefficients for all B-Format channels at once | Chris Robinson | 2015-02-10 | 1 | -29/+61 |
| | | | | | | It's possible to calculate HRTF coefficients for full third-order ambisonics now, but it's still not possible to use them here without upmixing first-order content. | ||||
* | Pass the (FuMa) channel number to GetBFormatHrtfCoeffs | Chris Robinson | 2015-02-10 | 1 | -6/+7 |
| | |||||
* | Correct conversion from polar to cartesian coords for HRTF | Chris Robinson | 2015-02-10 | 1 | -3/+3 |
| | | | | | A functional no-op (cos(a) == cos(-a), -sin(a) == sin(-a)), but Ambisonics expects the azimuth angle to go counter-clockwise. | ||||
* | Use B-Format for HRTF's virtual output format | Chris Robinson | 2015-02-09 | 1 | -1/+83 |
| | | | | | | | | This adds the ability to directly decode B-Format with HRTF, though only first- order (WXYZ) for now. Second- and third-order would be easilly doable, however we'd need to be able to up-mix first-order content (from the BFORMAT2D and BFORMAT3D buffer formats) since it would be inappropriate to decode lower-order content with a higher-order decoder. | ||||
* | Make CalcHrtfDelta more generic | Chris Robinson | 2014-11-24 | 1 | -34/+1 |
| | |||||
* | Rename step to steps | Chris Robinson | 2014-11-24 | 1 | -4/+4 |
| | |||||
* | Swap delta and step, remove double semicolons | Chris Robinson | 2014-11-23 | 1 | -15/+15 |
| | |||||
* | Partially revert "Use a different method for HRTF mixing" | Chris Robinson | 2014-11-23 | 1 | -10/+204 |
| | | | | | | | | | | | | 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 mixing | Chris Robinson | 2014-11-22 | 1 | -210/+12 |
| | | | | | | | | | | | | | | | | | | | | | | | 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. | ||||
* | Update COPYING to the latest ↵ | François Cami | 2014-08-18 | 1 | -2/+2 |
| | | | | https://www.gnu.org/licenses/old-licenses/lgpl-2.0.txt to fix the FSF' address Fix the FSF' address in the source | ||||
* | Properly scale the first HRTF pass-through coefficient | Chris Robinson | 2014-07-17 | 1 | -4/+8 |
| | | | | | Coefficients are scaled by 32767. For pass-through, this is attenuated by sqrt(0.5) to maintain a consistent perceived volume. | ||||
* | Cleanup some HRTF code | Chris Robinson | 2014-07-16 | 1 | -68/+53 |
| | | | | Use loops instead of duplicating code, rewrite some lines to be clearer. | ||||
* | Fix omni-directional moving HRTF coeffs | Chris Robinson | 2014-07-14 | 1 | -4/+4 |
| | |||||
* | Add a source radius property that determines the directionality of a sound | Chris Robinson | 2014-07-11 | 1 | -32/+56 |
| | | | | | | | | | At 0 distance from the listener, the sound is omni-directional. As the source and listener become 'radius' units apart, the sound becomes more directional. With HRTF, an omni-directional sound is handled using 0-delay, pass-through filter coefficients, which is blended with the real delay and coefficients as needed to become more directional. | ||||
* | Only set the needed HRTF coefficients | Chris Robinson | 2014-06-21 | 1 | -2/+2 |
| | |||||
* | Don't pass the device to HRTF methods | Chris Robinson | 2014-06-20 | 1 | -9/+8 |
| | |||||
* | Move PATH_MAX fallback definitions to alMain.h | Chris Robinson | 2014-02-27 | 1 | -10/+0 |
| | |||||
* | Add back the missing PATH_MAX fallback | Chris Robinson | 2014-02-27 | 1 | -0/+10 |
| | |||||
* | Move OpenDataFile to helpers.c so other sources can use it | Chris Robinson | 2014-02-27 | 1 | -131/+0 |
| | |||||
* | Don't fallback to relative filename handling if opening as absolute fails | Chris Robinson | 2014-02-26 | 1 | -26/+27 |
| | |||||
* | Expand environment variables for all config option values when loading | Chris Robinson | 2014-02-26 | 1 | -30/+1 |
| | |||||
* | Support environment variables in the hrtf_tables config value | Chris Robinson | 2014-02-25 | 1 | -4/+34 |
| | |||||
* | Move HRTF macros and function declarations to a separate header | Chris Robinson | 2014-02-23 | 1 | -0/+1 |
| | |||||
* | Move the default hrtf table to an external file | Chris Robinson | 2014-02-23 | 1 | -30/+12 |
| | |||||
* | Add a return value to FindHrtfFormat | Chris Robinson | 2014-02-23 | 1 | -1/+2 |
| | |||||
* | Search system-dependant data paths for relative hrtf table filenames | Chris Robinson | 2014-02-23 | 1 | -1/+126 |
| | |||||
* | Use a helper macro for pi*2 | Chris Robinson | 2013-10-08 | 1 | -1/+1 |
| | |||||
* | Allow enabling HRTF through a context creation attribute | Chris Robinson | 2013-05-31 | 1 | -0/+24 |
| | |||||
* | Fix a type mismatch | Chris Robinson | 2012-10-07 | 1 | -1/+2 |
| | |||||
* | Improve a couple error traces with the HRTF loader | Chris Robinson | 2012-09-18 | 1 | -2/+2 |
| | |||||
* | Restore support for the previous mhr format | Chris Robinson | 2012-09-12 | 1 | -146/+330 |
| | |||||
* | Update fnamelist after handling % markers | Chris Robinson | 2012-09-12 | 1 | -0/+1 |
| | |||||
* | Use PATH_MAX for the fname length | Chris Robinson | 2012-09-12 | 1 | -1/+7 |
| | |||||
* | Improve parsing hrtf_tables filenames | Chris Robinson | 2012-09-12 | 1 | -32/+38 |
| | |||||
* | Update HRTF code | Chris Robinson | 2012-09-11 | 1 | -197/+330 |
| | | | | | | | | | | | 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. | ||||
* | Use a more efficient method to blend HRTF delays and coefficients | Chris Robinson | 2012-08-11 | 1 | -26/+42 |
| | |||||
* | Interpolate between HRTF delay samples using the delay fraction | Chris Robinson | 2012-07-20 | 1 | -4/+4 |
| | |||||
* | Increase the directional change sensitivity for the HRTF delta | Chris Robinson | 2012-07-20 | 1 | -1/+1 |
| | |||||
* | Use wrappers for float-typed math functions | Chris Robinson | 2012-06-29 | 1 | -6/+6 |
| | |||||
* | Use the correct loop count for reading the elevation offsets from external ↵ | Chris Robinson | 2012-03-17 | 1 | -1/+1 |
| | | | | HRTF files | ||||
* | Don't assume the calculated HRTF delta for the gain difference is less than 1 | Chris Robinson | 2012-03-12 | 1 | -2/+3 |
| | |||||
* | Add a text file explaining OpenAL Soft's HRTF support and data file format | Chris Robinson | 2012-03-11 | 1 | -15/+0 |
| | |||||
* | Don't use a double when calculating the HRTF coefficients | Chris Robinson | 2011-10-02 | 1 | -6/+6 |
| |