Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov: fix missing extra data updating
Date: Mon, 25 Apr 2022 18:13:48 +0800
Message-ID: <tencent_9638D5C0F9B4A4697E002169A67CDAAF860A@qq.com> (raw)
In-Reply-To: <tencent_0F803A34C13E89573D9D4EE0BE5B1C345709@qq.com>



> On Mar 30, 2022, at 2:04 AM, Zhao Zhili <quinkblack@foxmail.com> wrote:
> 
> The stsc_index is checked and updated for the next sample. If the
> next sample needs to update stsd_index and stsc_index, then only
> stsc_index is updated, which leads to a missing
> AV_PKT_DATA_NEW_EXTRADATA. For example, the sample in the second
> chunk needs to update both.
> 
> entry[0]
>    first_chunk = 1
>    samples_per_chunk = 3
>    sample_description_index = 1
> entry[1]
>    first_chunk = 2
>    samples_per_chunk = 1
>    sample_description_index = 2
> entry[2]
>    first_chunk = 3
>    samples_per_chunk = 8
>    sample_description_index = 2
> 
> The fix is simple: first check and update stsd_index for current
> sample, then check and update stsc_index for the next.
> ---
> libavformat/mov.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index 6c847de164..c9d4f2ef43 100644
> --- a/libavformat/mov.c
> +++ b/libavformat/mov.c
> @@ -8591,20 +8591,20 @@ static int mov_read_packet(AVFormatContext *s, AVPacket *pkt)
> 
>     /* Multiple stsd handling. */
>     if (sc->stsc_data) {
> -        /* Keep track of the stsc index for the given sample, then check
> -        * if the stsd index is different from the last used one. */
> +        if (sc->stsc_data[sc->stsc_index].id > 0 &&
> +            sc->stsc_data[sc->stsc_index].id - 1 < sc->stsd_count &&
> +            sc->stsc_data[sc->stsc_index].id - 1 != sc->last_stsd_index) {
> +            ret = mov_change_extradata(sc, pkt);
> +            if (ret < 0)
> +                return ret;
> +        }
> +
> +        /* Update the stsc index for the next sample */
>         sc->stsc_sample++;
>         if (mov_stsc_index_valid(sc->stsc_index, sc->stsc_count) &&
>             mov_get_stsc_samples(sc, sc->stsc_index) == sc->stsc_sample) {
>             sc->stsc_index++;
>             sc->stsc_sample = 0;
> -        /* Do not check indexes after a switch. */
> -        } else if (sc->stsc_data[sc->stsc_index].id > 0 &&
> -                   sc->stsc_data[sc->stsc_index].id - 1 < sc->stsd_count &&
> -                   sc->stsc_data[sc->stsc_index].id - 1 != sc->last_stsd_index) {
> -            ret = mov_change_extradata(sc, pkt);
> -            if (ret < 0)
> -                return ret;
>         }
>     }
> 


Multi sample entry is a less used feature. Since we have it, better keep it
work. This patch fixed a corner case.

Will apply this week unless there are objections.
_______________________________________________
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".

      reply	other threads:[~2022-04-25 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 18:04 Zhao Zhili
2022-04-25 10:13 ` "zhilizhao(赵志立)" [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=tencent_9638D5C0F9B4A4697E002169A67CDAAF860A@qq.com \
    --to=quinkblack@foxmail.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