| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This avoids using an array of 1 as a flexible array member, and instead uses a
span to reference the memory after itself.
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
This is a notably faster FFT implementation for 32-bit float signals, provided
under a 3-clause BSD license.
|
| | |
|
| | |
|
| |
| |
| |
| | |
To avoid clashes when used as a sub-project
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Add gtest integration
* Update gtest fetch
* Add ctest
* Update CI
* Update CI
* enable testing
* Make tests off by default
* Update gitignore
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Improve wasapi, support uwp build
* Fix compile errors
* [UWP] Support ReadALConfig from app roaming
* [UWP] Post disconnect event when default device changed
* [UWP] Fix appveyor ci
* [WIN32] Default device change notification support
* Fix warnings
* Add event to notify the app when the default device changes
- Event type: AL_EVENT_TYPE_DEFAULT_DEVICE_CHANGED_SOFT=0x19A7
- Event callback parameters:
void _onALSoftEvent(ALenum eventType,
ALuint object, // dataFlow: 0(render), 1(capture)
ALuint param, // 0
ALsizei length, // 0
const ALchar* message, // Default device changed:<deviceId>
void* userParam);
* Fix warnings
* Fire default device changed event in mixerProc thread
* Fix compile warning
* [UWP] Improve cmake
* Revert changes
* Notify default device change by system event callback
* Revert insignificant change
* Remove duplicate call
|
| | |
|
| |
| |
| |
| |
| | |
Devices being added or removed, or the default device changing. Not all
backends report this (none do currently), but it'll be supported where it can.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Close 'left-open' IF in CMakeLists.txt
|
|\|
| |
| |
| |
| | |
Resolved Conflicts:
CMakeLists.txt
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To more aggressively control library exports. Despite the -fvisibility=hidden
flag that should hide everything by default, GNU's libstdc++ forces default
visibility for generated std namespace symbols (from template functions that
don't inline, for example), adding some standard C++ symbols to the exported
symbol list. This can cause ABI problems if an app links to OpenAL and uses one
of those symbols, as a future internal change can cause the function to not be
generated and make the symbol no longer available. There seems to be no way to
prevent this, aside from this version script.
This has the added advantage of ensuring future extension functions don't
accidentally get exported due to the ALC_API or AL_API macros making them
visible.
|
| | |
|
| |
| |
| |
| |
| | |
Setting it globally interferes with Oboe trying to use C++17 (when its built as
a sub-project), which we don't require yet.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Similar to how the bsinc filters work, but optimized for 4-point filtering. At
least the SSE version is notably faster than calculating the coefficients in
real time.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
"attribute 'attribute-name' requires at least 'standard-level'; ignored"
This hides the fact that it's not optimizing [[likely]] and [[unlikely]], even
though it could (GCC does, Clang gives a similar warning to MSVC, but is
ambiguous about whether it's still doing the optimization). There's nothing I
know to do to make MSVC do those optimizations it otherwise knows to do, so
just hide the warnings instead of pessimizing the code.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|