Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: lance.lmwang@gmail.com
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] 5.0 blocking issues
Date: Mon, 10 Jan 2022 17:04:54 +0800
Message-ID: <20220110090454.GA28967@gmail.com> (raw)
In-Reply-To: <tencent_73A1570F9D4EE04E5BA83449804034E73F09@qq.com>

On Mon, Jan 10, 2022 at 11:09:11AM +0800, "zhilizhao(赵志立)" wrote:
> 
> 
> > On Jan 9, 2022, at 12:30 AM, Michael Niedermayer <michael@niedermayer.cc> wrote:
> > 
> > Hi all
> > 
> > This is a simple go/no go call
> > if you know of something that still should go into 5.0 please reply here
> > with a list of what you are working on and a timelimit until when you
> > will be done with it
> 
> A regression issue: avformat/movenc: fix duration in mdhd box
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_7D4D80DC34DB3F53572F9D76E0EE5AEE3509@qq.com/

https://patchwork.ffmpeg.org/check/48152/
Make fate failed? 
make: *** [fate-copy-trac3074] Error 1
make: *** [fate-mov-mp4-disposition-mpegts-remux] Error 1
make: *** [fate-mov-cover-image] Error 1


> 
> ------------------------------------------------------------------------
> The following movenc patches may take some time to review, they can be
> backported after 5.0 release.
> 
> Assert failure issues:
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_9373ABED4E3F70552D699AF7400F9A699F08@qq.com/
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_20A6D1A7E4EABB13321C520B8C662F90AA06@qq.com/
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_4C6B9A1C40F19A919F39AB344E6D70062D08@qq.com/
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_763895C15DB500687202E9685A7D2EAE4E0A@qq.com/
> 
> Invalid tfra box:
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_E47115C78906AEAD65415302C85B53E07305@qq.com/
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_8B85435318484473E3736FB5D029090EBB05@qq.com/
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_4134BB3E1556699C8EE1305B003463801009@qq.com/
> _______________________________________________
> 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".

-- 
Thanks,
Limin Wang
_______________________________________________
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-01-10  9:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 16:30 Michael Niedermayer
2022-01-08 16:36 ` Romain Beauxis
2022-01-08 18:55 ` Soft Works
2022-01-08 21:31 ` Lynne
2022-01-10  3:09 ` "zhilizhao(赵志立)"
2022-01-10  9:04   ` lance.lmwang [this message]
2022-01-10 10:32   ` "zhilizhao(赵志立)"
2022-01-10 16:55 ` Anton Khirnov
2022-01-10 18:12 ` Andreas Rheinhardt
2022-01-12  6:37 ` Lynne
2022-01-12 16:30   ` Michael Niedermayer
2022-01-12 16:36     ` Nicolas George
2022-01-12 16:41       ` James Almer
2022-01-12 16:47         ` Nicolas George
2022-01-12 17:30           ` Jean-Baptiste Kempf
2022-01-12 17:58             ` Nicolas George
2022-01-12 23:17         ` Michael Niedermayer
2022-01-12 21:35     ` Soft Works
2022-01-13  4:02       ` Xiang, Haihao
2022-01-13 11:34         ` James Almer

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=20220110090454.GA28967@gmail.com \
    --to=lance.lmwang@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