From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/vvc: Fix emulation prevention byte handling
Date: Sat, 27 Jan 2024 13:22:40 +0800
Message-ID: <CAFXK13dYGT25bUtbViZJF3cmn6c1YncVhADdDvtto9mqN9mtUA@mail.gmail.com> (raw)
In-Reply-To: <20240126162043.59687-1-post@frankplowman.com>
On Sat, Jan 27, 2024 at 12:21 AM <post@frankplowman.com> wrote:
> From: Frank Plowman <post@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 <post@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-request@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-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2024-01-27 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 16:20 post
2024-01-27 5:22 ` Nuo Mi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFXK13dYGT25bUtbViZJF3cmn6c1YncVhADdDvtto9mqN9mtUA@mail.gmail.com \
--to=nuomi2021@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git