Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thomas Siedel <thomas.ff@spin-digital.com>
To: Nuo Mi <nuomi2021@gmail.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 1/6] avformat: add muxer support for H266/VVC
Date: Mon, 29 Jan 2024 11:41:47 +0100
Message-ID: <CAD25kL5_Vg1PbrsOMONDY0Q71+oX198yoRh4hfArC_ZV2BfOpA@mail.gmail.com> (raw)
In-Reply-To: <CAFXK13c4ukmCL6W9_NJH38u+Lrt_a-e5kdRHmWpoOOgRzj1ijQ@mail.gmail.com>

On Sat, 27 Jan 2024 at 16:57, Nuo Mi <nuomi2021@gmail.com> wrote:

>
>
> On Sat, Jan 27, 2024 at 10:38 PM James Almer <jamrial@gmail.com> wrote:
>
>> On 1/27/2024 1:15 AM, Nuo Mi wrote:
>> > diff --git a/libavformat/isom_tags.c b/libavformat/isom_tags.c
>> > index a575b7c160..705811e950 100644
>> > --- a/libavformat/isom_tags.c
>> > +++ b/libavformat/isom_tags.c
>> > @@ -123,6 +123,9 @@ const AVCodecTag ff_codec_movvideo_tags[] = {
>> >       { AV_CODEC_ID_HEVC, MKTAG('d', 'v', 'h', 'e') }, /* HEVC-based
>> Dolby Vision derived from hev1 */
>> >                                                        /* dvh1 is
>> handled within mov.c */
>> >
>> > +    { AV_CODEC_ID_VVC, MKTAG('v', 'v', 'i', '1') },  /* VVC/H.266
>> which indicates parameter sets may be in ES */
>> > +    { AV_CODEC_ID_VVC, MKTAG('v', 'v', 'c', '1') },  /* VVC/H.266
>> which indicates parameter shall not be in ES */
>> > +
>> >       { AV_CODEC_ID_H264, MKTAG('a', 'v', 'c', '1') }, /* AVC-1/H.264 */
>> >       { AV_CODEC_ID_H264, MKTAG('a', 'v', 'c', '2') },
>> >       { AV_CODEC_ID_H264, MKTAG('a', 'v', 'c', '3') },
>>
>
>
>>
>> This list is for mov only, not mp4. You're already adding these two
>> entries to codec_mp4_tags[] bellow, for ISOBMFF.
>>
> Hi James,
> Thank you for the review.
> I guess not, @Thomas Siedel <thomas.ff@spin-digital.com> ,  could you
> give us some insights?
> thank you.
>
>>
>> Are these defined anywhere in Apple's documentation?
>>
>
For mov I was only copy&pasting it from mp4 to be honest, without checking
the Apple documentation, sorry for that.

Therefore I guess these 2 entries should be removed from the
ff_codec_movvideo_tags table.
_______________________________________________
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:[~2024-01-29 10:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240127041512.14079-1-nuomi2021@gmail.com>
2024-01-27  4:15 ` Nuo Mi
2024-01-27 14:38   ` James Almer
2024-01-27 15:57     ` Nuo Mi
2024-01-29 10:41       ` Thomas Siedel [this message]
2024-01-30  6:26     ` Nuo Mi
2024-01-27  4:15 ` [FFmpeg-devel] [PATCH v3 2/6] avformat/mpegtsenc: refact mpegts_check_bitstream to loop up table Nuo Mi
2024-01-27 14:45   ` Andreas Rheinhardt
2024-01-27 15:54     ` Nuo Mi
2024-01-27  4:15 ` [FFmpeg-devel] [PATCH v3 3/6] avformat/mpegtsenc: refact, move h264, hevc startcode checking to check_h26x_startcode Nuo Mi
2024-01-27  4:15 ` [FFmpeg-devel] [PATCH v3 4/6] avformat/mpegtsenc: refact, remove h264, hevc magic numbers for nal_type Nuo Mi
2024-01-27  4:15 ` [FFmpeg-devel] [PATCH v3 5/6] avformat/mpegtsenc: refact out h26x_prefix_aud Nuo Mi
2024-01-27  4:15 ` [FFmpeg-devel] [PATCH v3 6/6] avformat: add ts stream types for H266/VVC Nuo Mi
2024-01-28  8:43   ` Marton Balint

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=CAD25kL5_Vg1PbrsOMONDY0Q71+oX198yoRh4hfArC_ZV2BfOpA@mail.gmail.com \
    --to=thomas.ff@spin-digital.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=nuomi2021@gmail.com \
    /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