Re: [FFmpeg-devel] [PATCH 1/2] avformat/mov: fix frag_index.current out of sync

From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: nachiket.programmer@gmail.com
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/mov: fix frag_index.current out of sync
Date: Thu, 11 Aug 2022 15:06:50 +0800
Message-ID: <tencent_AD131A684E73E2B369D5D989180EAE454F05@qq.com> (raw)
In-Reply-To: <tencent_FC35CB817C341F3FBF56AF9C34E0585AE409@qq.com>

> On Jul 31, 2022, at 1:14 AM, Zhao Zhili <quinkblack@foxmail.com> wrote:
> 
> From: Zhao Zhili <zhilizhao@tencent.com>
> 
> frag_index.current is used by cenc_filter, and is updated inside
> mov_read_moof. It can out of sync regarding to mov_read_packet.
> 
> Partly fix ticket #9807.
> ---
> libavformat/mov.c | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
> 
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> index a09a762d91..ce12a9e4f1 100644
> --- a/libavformat/mov.c
> +++ b/libavformat/mov.c
> @@ -7095,6 +7095,31 @@ static int cenc_decrypt(MOVContext *c, MOVStreamContext *sc, AVEncryptionInfo *s
>     }
> }

Ping for review.

By the way, there is a fate failure on patchwork which is unlikely
introduced by this patchset (It happened on another patch before).
So how to make patchwork rerun the fate test without resending the
patch again?
_______________________________________________
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".