From: Nuo Mi <nuomi2021@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v5 0/6] Add mp4 and ts support for vvc Date: Wed, 31 Jan 2024 22:23:04 +0800 Message-ID: <CAFXK13dZgERoVuRdznkCJf_ESnYhpyQRPc0oq6_M0-hswF5+vg@mail.gmail.com> (raw) In-Reply-To: <TYSPR06MB64332CA582062DFB5F286F4FAA7D2@TYSPR06MB6433.apcprd06.prod.outlook.com> On Tue, Jan 30, 2024 at 8:49 PM Nuo Mi <nuomi2021@gmail.com> wrote: > Changes since v4: > mp4: return patch welcome for CENC nal units (Thomas) > mp4: reintroduce vvc back into ff_codec_movvideo_tags since the mp4 > demuxer relies on it. (James) > > Nuo Mi (4): > avformat/mpegtsenc: refact mpegts_check_bitstream to loop up table > avformat/mpegtsenc: refact, move h264, hevc startcode checking to > check_h26x_startcode > avformat/mpegtsenc: refact, remove h264, hevc magic numbers for > nal_type > avformat/mpegtsenc: refact out h26x_prefix_aud > > Thomas Siedel (2): > avformat/mp4: add muxer support for H266/VVC > avformat/mpegts: add ts stream types for H266/VVC > > configure | 2 +- > libavformat/Makefile | 6 +- > libavformat/isom.c | 1 + > libavformat/isom_tags.c | 3 + > libavformat/mov.c | 6 + > libavformat/movenc.c | 40 +- > libavformat/mpeg.c | 3 + > libavformat/mpeg.h | 1 + > libavformat/mpegts.c | 2 + > libavformat/mpegts.h | 1 + > libavformat/mpegtsenc.c | 173 ++++--- > libavformat/vvc.c | 971 ++++++++++++++++++++++++++++++++++++++++ > libavformat/vvc.h | 99 ++++ > 13 files changed, 1241 insertions(+), 67 deletions(-) > create mode 100644 libavformat/vvc.c > create mode 100644 libavformat/vvc.h > Applied. Thank you all for your reviews and comments > > -- > 2.25.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".
prev parent reply other threads:[~2024-01-31 14:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-30 12:48 Nuo Mi 2024-01-31 14:23 ` 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=CAFXK13dZgERoVuRdznkCJf_ESnYhpyQRPc0oq6_M0-hswF5+vg@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