Bug #3448
x264 encoding errors in syslog
0%
Description
After setting up a stream profile tu transcode into "libx264: libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10" I see plenty of output in syslog while transcoding, it follows a pattern :
24x "libav : specified frame type is not compatible with max B-frames"
1x "libav : specified frame type (5) at 17027 is not compatible with keyframe interval" (17027 is an incrementing number)
Using x265 encoding I don't see these warnings/errors.
History
Updated by Jaroslav Kysela almost 9 years ago
Updated by - Status changed from New to Invalid
Fix the ffmpeg libraries.. These log lines are from the ffmpeg code.
Updated by Dietmar Konermann almost 9 years ago
Updated by get also my log spammed with these messages... WARNING level
2016-01-07 18:24:34.675 [WARNING]:libav: specified frame type is not compatible with max B-frames
2016-01-07 18:24:34.701 [WARNING]:libav: specified frame type is not compatible with max B-frames
2016-01-07 18:24:34.740 [WARNING]:libav: specified frame type is not compatible with max B-frames
2016-01-07 18:24:34.794 [WARNING]:libav: specified frame type is not compatible with max B-frames
maybe this could be changed to DEBUG or even TRACE level?
Updated by C K almost 9 years ago
Updated by Dietmar Konermann wrote:
get also my log spammed with these messages... WARNING level
2016-01-07 18:24:34.675 [WARNING]:libav: specified frame type is not compatible with max B-frames
2016-01-07 18:24:34.701 [WARNING]:libav: specified frame type is not compatible with max B-frames
2016-01-07 18:24:34.740 [WARNING]:libav: specified frame type is not compatible with max B-frames
2016-01-07 18:24:34.794 [WARNING]:libav: specified frame type is not compatible with max B-framesmaybe this could be changed to DEBUG or even TRACE level?
Yes, very annoying. Perhaps the log can be suppressed?