At present, when the Framerate core option is set to Auto the framerate value is read directly from the frontend. This is a problem because the internal audio generation only works correctly at specific framerates - certain non-integer values cause resampling artefacts/crackling.
This PR sanitises the framerate read from the frontend, choosing the nearest value from the allowed framerate whitelist.
This pull request introduces 1 alert when merging 1b6f98a2525939029e0be6d6148098d91a8ca5ae into 905e7d0b620061a0fc1ddafb4288ef2f251f021c - view on LGTM.com
At present, when the
Framerate
core option is set toAuto
the framerate value is read directly from the frontend. This is a problem because the internal audio generation only works correctly at specific framerates - certain non-integer values cause resampling artefacts/crackling.This PR sanitises the framerate read from the frontend, choosing the nearest value from the allowed framerate whitelist.