On Sat, Jan 27, 2024 at 12:21 AM <p...@frankplowman.com> wrote: > From: Frank Plowman <p...@frankplowman.com> > > nal->skipped_bytes_pos contains the positions of errors relative to the > start of the slice header, whereas the position they were tested against > is relative to the start of the slice data, i.e. one byte after the end > of the slice header. > > Patch fixes this by storing the size of the slice header in H266RawSlice > and adding it to the position given by the GetBitContext before > comparing to skipped_bytes_pos. This fixes AVERROR_INVALIDDATAs for > various valid bitstreams, such as the LMCS_B_Dolby_2 conformance > bitstream. > > Signed-off-by: Frank Plowman <p...@frankplowman.com> > Hi Frank, Thanks for the patch. The decode md5 still mismatch with reference for LMCS_B_Dolby_2 Do you happen to know why?
--- > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
