Skip to content

Conversation

@bernhardschmidt
Copy link

Hardcoding the value for FF_INPUT_BUFFER_PADDING_SIZE is not safe because
upstream FFmpeg might change it (as they did in FFmpeg 4.0).

Instead, use FFmpeg's AV_INPUT_BUFFER_PADDING_SIZE if available and only
hardcode a value if FFmpeg is disabled (in which case the value doesn't
particularly matter anyway). For compatibility with older FFmpeg versions,
define AV_INPUT_BUFFER_PADDING_SIZE if hasn't been defined yet.

Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901735

Hardcoding the value for FF_INPUT_BUFFER_PADDING_SIZE is not safe because
upstream FFmpeg might change it (as they did in FFmpeg 4.0).

Instead, use FFmpeg's AV_INPUT_BUFFER_PADDING_SIZE if available and only
hardcode a value if FFmpeg is disabled (in which case the value doesn't
particularly matter anyway). For compatibility with older FFmpeg versions,
define AV_INPUT_BUFFER_PADDING_SIZE if hasn't been defined yet.

Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901735
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants