Commit d51b056c authored by Clownacy's avatar Clownacy

Correct outdated variable name in documentation

'noPreZeroedOutputBuffer' was renamed to 'noPreSilencedOutputBuffer'
in v0.11.0.
parent 252de0f0
...@@ -3611,8 +3611,9 @@ Some backends have some nuance details you may want to be aware of. ...@@ -3611,8 +3611,9 @@ Some backends have some nuance details you may want to be aware of.
WASAPI and Core Audio, however other backends such as PulseAudio may naturally support it, though WASAPI and Core Audio, however other backends such as PulseAudio may naturally support it, though
not all have been tested. not all have been tested.
- The contents of the output buffer passed into the data callback will always be pre-initialized to - The contents of the output buffer passed into the data callback will always be pre-initialized to
silence unless the `noPreZeroedOutputBuffer` config variable in `ma_device_config` is set to true, silence unless the `noPreSilencedOutputBuffer` config variable in `ma_device_config` is set to
in which case it'll be undefined which will require you to write something to the entire buffer. true, in which case it'll be undefined which will require you to write something to the entire
buffer.
- By default miniaudio will automatically clip samples. This only applies when the playback sample - By default miniaudio will automatically clip samples. This only applies when the playback sample
format is configured as `ma_format_f32`. If you are doing clipping yourself, you can disable this format is configured as `ma_format_f32`. If you are doing clipping yourself, you can disable this
overhead by setting `noClip` to true in the device config. overhead by setting `noClip` to true in the device config.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment