From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/ivfenc: Set the "number of frames" in IVF header
Date: Sun, 02 Jul 2023 14:58:59 +0200
Message-ID: <168830273997.21886.15153437068994510529@lain.khirnov.net> (raw)
In-Reply-To: <CAEEMt2=-A=Ox1AZcUaPfSuxiJoqUX6-3Vt_dQ7v-onm0vOE3YA@mail.gmail.com>
Quoting Ronald S. Bultje (2023-07-02 14:44:42)
> Hi,
>
> On Sun, Jul 2, 2023 at 5:35 AM Anton Khirnov <anton@khirnov.net> wrote:
>
> > Quoting Ronald S. Bultje (2023-07-02 02:03:11)
> > > I see this discussion now...
> > >
> > > I don't think I agree with the above. First of all, IVF has two fields
> > > there (it seems): duration, and n_frames.
> >
> > Got any source for that? I only see one field in
> > https://wiki.multimedia.cx/index.php/Duck_IVF
> >
>
> This somewhat-widely used tool called "ffmpeg" has used it like that for
> the past, say, 10 years. I've heard some projects or companies around the
> world use this tool, and backwards compatibility is supposedly a thing.
Yeah yeah very funny.
You claimed there are two fields. My question was where is this second
field supposed to be.
--
Anton Khirnov
_______________________________________________
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:[~2023-07-02 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 0:53 Dai, Jianhui J
2023-06-20 1:42 ` Dai, Jianhui J
2023-06-28 15:24 ` Anton Khirnov
2023-06-29 6:03 ` Dai, Jianhui J
2023-06-29 9:44 ` Anton Khirnov
2023-07-02 0:03 ` Ronald S. Bultje
2023-07-02 9:35 ` Anton Khirnov
2023-07-02 12:44 ` Ronald S. Bultje
2023-07-02 12:58 ` Anton Khirnov [this message]
2023-07-02 14:41 ` Ronald S. Bultje
2023-07-03 2:48 ` Dai, Jianhui J
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=168830273997.21886.15153437068994510529@lain.khirnov.net \
--to=anton@khirnov.net \
--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