Closed haudiobe closed 3 years ago
The spec is clear, you must have this info in the avcc box for these profiles - that's an FFMPEG problem - use gpac :)
I would rather fix this in ffmpeg though if possible ;-) as it is referred to as reference implementation these days ….
I'd agree it's an ffmpeg bug. The code was probably written without access to the spec.
It wouldn't be possible to relax, as it's not a restriction it's part of the bitstream format. If you remove it from teh specification you would break everything else.
This was fixed in https://github.com/FFmpeg/FFmpeg/commit/16fa513392adbdd786776d12258f39ad81149a19 and https://github.com/FFmpeg/FFmpeg/commit/18507b48825da45055f7ba1f933aa64cf90de253 which are present in ffmpeg 4.3
@jamrial thanks - we will check this!
The CMAF group agreed to close the issue.
In M54520, content was generated with FFMPEG. The content was verified with the conformance software for the second edition of CMAF.
One observed error is documented in clause 3.3.1: "Validate_AVCConfigRecord: Not enough bits left in the bitstream for further attribute validation"
The content was encoded with AVC high profile (100) and for this case there is expected extra bits in the second part of the code, but this is missing the content. That is why it gives “Not enough bits left” to read the extra information. The reason that this is missing is that ffmpeg seems to not add this by default.
Question for discussion: Is it an FFMPEG problem or is it an overrestrictive specification in part 15? Please comment