From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavf/movenc: mark mov/mp4 as supporting VFR
Date: Sat, 30 Mar 2024 09:49:07 -0300
Message-ID: <edd27fb5-5eb4-413b-a65c-f8796eb53874@gmail.com> (raw)
In-Reply-To: <20240329083509.10130-1-anton@khirnov.net>
On 3/29/2024 5:35 AM, Anton Khirnov wrote:
> ---
> libavformat/movenc.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/libavformat/movenc.c b/libavformat/movenc.c
> index b97c479cc4..30cfbf6e74 100644
> --- a/libavformat/movenc.c
> +++ b/libavformat/movenc.c
> @@ -8230,11 +8230,11 @@ const FFOutputFormat ff_mov_muxer = {
> .write_packet = mov_write_packet,
> .write_trailer = mov_write_trailer,
> .deinit = mov_free,
> + .p.flags = AVFMT_GLOBALHEADER | AVFMT_TS_NEGATIVE | AVFMT_VARIABLE_FPS
> #if FF_API_ALLOW_FLUSH
> - .p.flags = AVFMT_GLOBALHEADER | AVFMT_ALLOW_FLUSH | AVFMT_TS_NEGATIVE,
> -#else
> - .p.flags = AVFMT_GLOBALHEADER | AVFMT_TS_NEGATIVE,
> + | AVFMT_ALLOW_FLUSH
> #endif
> + ,
> .p.codec_tag = (const AVCodecTag* const []){
> ff_codec_movvideo_tags, ff_codec_movaudio_tags, ff_codec_movsubtitle_tags, 0
> },
> @@ -8282,11 +8282,11 @@ const FFOutputFormat ff_mp4_muxer = {
> .write_packet = mov_write_packet,
> .write_trailer = mov_write_trailer,
> .deinit = mov_free,
> + .p.flags = AVFMT_GLOBALHEADER | AVFMT_TS_NEGATIVE | AVFMT_VARIABLE_FPS
> #if FF_API_ALLOW_FLUSH
> - .p.flags = AVFMT_GLOBALHEADER | AVFMT_ALLOW_FLUSH | AVFMT_TS_NEGATIVE,
> -#else
> - .p.flags = AVFMT_GLOBALHEADER | AVFMT_TS_NEGATIVE,
> + | AVFMT_ALLOW_FLUSH
> #endif
> + ,
> .p.codec_tag = mp4_codec_tags_list,
> .check_bitstream = mov_check_bitstream,
> .p.priv_class = &mov_isobmff_muxer_class,
There's a custom check for these muxers in
avformat_transfer_internal_stream_timing_info() that would afaict be
disabled with this change.
_______________________________________________
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:[~2024-03-30 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 8:35 Anton Khirnov
2024-03-29 9:19 ` Gyan Doshi
2024-03-29 9:21 ` Anton Khirnov
2024-03-30 0:52 ` Michael Niedermayer
2024-07-02 9:36 ` [FFmpeg-devel] [PATCH] tests/fate/mov: add a test for VFR muxing Anton Khirnov
2024-07-06 23:57 ` Michael Niedermayer
2024-07-06 23:59 ` Michael Niedermayer
2024-03-30 12:49 ` James Almer [this message]
2024-07-02 9:37 ` [FFmpeg-devel] [PATCH] lavf/movenc: mark mov/mp4 as supporting VFR Anton Khirnov
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=edd27fb5-5eb4-413b-a65c-f8796eb53874@gmail.com \
--to=jamrial@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