From: "Zhao Zhili" <quinkblack@foxmail.com> To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3] avformat/movenc: correct write_colr warning placement Date: Wed, 14 Dec 2022 22:33:01 +0800 Message-ID: <tencent_62EBD36255C8C906EEA6A553D3034842B305@qq.com> (raw) In-Reply-To: <3abce8f2-01b8-ec69-3f64-5123b7219ef3@gyani.pro> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Gyan Doshi > Sent: 2022年12月14日 20:49 > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH v3] avformat/movenc: correct write_colr warning placement > > > > On 2022-12-14 06:10 pm, "zhilizhao(赵志立)" wrote: > > > >> On Dec 14, 2022, at 19:58, Gyan Doshi <ffmpeg@gyani.pro> wrote: > >> > >> The old warning is no longer applicable in the inner block after > >> c5b20cfe19. > >> --- > >> libavformat/movenc.c | 5 +++-- > >> 1 file changed, 3 insertions(+), 2 deletions(-) > >> > >> diff --git a/libavformat/movenc.c b/libavformat/movenc.c > >> index 7b00e65cdd..c427109609 100644 > >> --- a/libavformat/movenc.c > >> +++ b/libavformat/movenc.c > >> @@ -2330,10 +2330,11 @@ static int mov_write_video_tag(AVFormatContext *s, AVIOContext *pb, MOVMuxContex > >> av_stream_get_side_data(track->st, AV_PKT_DATA_ICC_PROFILE, NULL)) { > >> int prefer_icc = mov->flags & FF_MOV_FLAG_PREFER_ICC || !has_color_info; > >> mov_write_colr_tag(pb, track, prefer_icc); > >> - } else if (mov->flags & FF_MOV_FLAG_WRITE_COLR) { > >> - av_log(mov->fc, AV_LOG_WARNING, "Not writing 'colr' atom. Format is not MOV or MP4.\n"); > >> } > >> + } else if (mov->flags & FF_MOV_FLAG_WRITE_COLR) { > >> + av_log(mov->fc, AV_LOG_WARNING, "Not writing 'colr' atom. Format is not MOV or MP4 or AVIF.\n"); > > LGTM except the indentation. > > Do you mean the log line? Yes. You can fix it locally before push. > > > > > >> } > >> + > >> if (track->mode == MODE_MOV || track->mode == MODE_MP4) { > >> mov_write_clli_tag(pb, track); > >> mov_write_mdcv_tag(pb, track); > >> -- > >> 2.36.1 > >> > >> _______________________________________________ > >> 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". > > _______________________________________________ > 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".
next prev parent reply other threads:[~2022-12-14 14:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-12 4:41 [FFmpeg-devel] [PATCH v2] avformat/movenc: remove write_colr warning Gyan Doshi 2022-12-14 10:51 ` Gyan Doshi 2022-12-14 11:31 ` "zhilizhao(赵志立)" 2022-12-14 11:58 ` [FFmpeg-devel] [PATCH v3] avformat/movenc: correct write_colr warning placement Gyan Doshi 2022-12-14 12:40 ` "zhilizhao(赵志立)" 2022-12-14 12:48 ` Gyan Doshi 2022-12-14 14:33 ` Zhao Zhili [this message] 2022-12-15 10:00 ` Gyan Doshi
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_62EBD36255C8C906EEA6A553D3034842B305@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