- 02 Jul, 2021 11 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
* The old logging callback has been deprecated and will be removed in version 0.11. * MA_LOG_LEVEL_DEBUG has been added and MA_LOG_LEVEL_VERBOSE deprecated. * The MA_LOG_LEVEL option has been deprecated. All log levels are now posted to the logging callbacks, except for MA_LOG_LEVEL_DEBUG which is only posted if MA_DEBUG_OUTPUT is enabled. The new logging system works by creating a `ma_log` object. You then register callbacks that will be fired when a log message is posted. You can register up to 4 callbacks. You the specify a pointer to this log object in the context config. This replaces the `logCallback` variable. The old logging system was specific to context's and device's, however with the introduction of new APIs this is no longer appropriate. The new logging system is completely generic with a simple user-data pointer being used for application-specific data. This commit adds some helper APIs for retrieving a pointer to the context's log object: * ma_context_get_log() * ma_device_get_log() * ma_device_get_context() The MA_DEBUG_OUTPUT option has been improved for Android builds. With the new system, __android_log_print() will be used instead of printf(). -
David Reid authored
-
- 01 Jul, 2021 20 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
Public issue https://github.com/mackron/miniaudio/issues/323
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
This is no longer used. New code should use `ma_audio_buffer`.
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
- 30 Jun, 2021 9 commits
-
-
David Reid authored
-
David Reid authored
-
David Reid authored
With this change, MA_AT_END should only ever be returned the number of bytes or frames returned is equal to 0.
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
-
David Reid authored
Use MA_AT_END instead. Use of MA_END_OF_FILE is too easily confused with MA_AT_END, and MA_AT_END is a more generally applicable.
-
David Reid authored
-