| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
C++ specifies that unknown attributes should be ignored and aren't an error.
Clang issues a warning when encountering a known attribute from newer standard
version than the target version. GCC recognizes attributes from newer standard
versions it's aware of, allowing improved compilation capabilities. Hopefully
Clang (and MSVC) will take advantage since it recognizes them, even if they
weren't standardized for the target version, but there's no need to warn about
known attributes in either case.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Build utils/makemhr on update
This workflow builds makemhr.exe including dependencies (libmysofa, zlib, etc) whenever anything under utils/makemhr or the workflow is updated.
It also uploads artifacts and [(pre)releases it with its own tag](https://github.com/ThreeDeeJay/openal-soft/releases/tag/makemhr) for a [permanent, up-to-date download link](https://github.com/ThreeDeeJay/openal-soft/releases/download/makemhr/makemhr.zip).
* Clone latest libmysofa release tag without history
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to the programming guide and the specification, those functions
may be used by extensions. However, Creative's hardware OpenAL chose
to not implement stub functions for those that they do not use. Currently
they use only alBufferi for X-RAM related functions.
Other implementations, such as OpenAL Soft and wrap_oal implement stub
functions for those methods therefore they work.
This commit turns those functions optional, just like they were in the
old FOSS router. Consumers of the router will receive a nullptr as expected
for not implemented methods if they load them using alGetProcAddress, which
I believe is the correct way to do so. That is, the context must be current
before loading al* functions.
|
| |
|
|
|
|
| |
Instead of our own custom FindSDL2.cmake
|
|
|
|
|
| |
This should make FindPulseAudio.cmake more compatible with PulseAudio's own
PulseAudioConfig.cmake.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This allows mixing at various samples rates that WASAPI doesn't otherwise
support. This is mostly helpful for users that have unnecessarily high device
rates (96 or 192khz), and lets the ALC_FREQUENCY attribute or frequency config
option set a lower mixing rate for more efficient processing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I don't know how different sound APIs handle 7.1.4 ("Atmos" or "Auro3D")
output, but currently it simply specifies the additional channels with the
height channel labels. This isn't likely how it works for a virtualized channel
bed, for playing over other with-height configurations (7.1.2, 5.1.4, etc), but
this should be an okay start.
|
|
|
|
|
|
|
|
| |
This starts a source at a particular device clock time, rounded to the nearest
sample (really, 4th sample for SIMD reasons), allowing to start a sound at a
particular point in the output instead of the next update.
Unlike using negative offsets, this is not affected by pitch/velocity.
|
| |
|
| |
|
|
|
|
|
|
| |
This allows a voice/source to start with a delay, more accurately than simply
waiting to call alSourcePlay. The delay is affected by pitch and velocity,
making it useful to simulate distant sounds that take time to be heard.
|
|
|
|
|
|
|
| |
Now that it doesn't cause the distortion like before, the IIR implementation
provides a very wide pass-band with the lowest CPU requirements. If maintaining
the original phase is important, fir256 and fir512 are still available, given
whether lower CPU use or a wider pass-band is more important.
|
| |
|
| |
|
|
|
|
|
|
| |
There is a surprisingly noticeable amount of static caused by the IIR filter in
particular circumstances. The 256-point filter is only slightly slower, but the
frequency response should be good enough to use as a default for now.
|
|
|
|
| |
Also better detail the IIR implementation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
> Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/upload-artifact
This should fix 2 of the 3 warnings here: https://github.com/kcat/openal-soft/actions/runs/3303596206
by updating to this https://github.com/actions/upload-artifact/releases/tag/v3.1.1
The third warning is more of a heads up of the macOS runner being updated so it should go away eventually
|
| |
|