Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/gifdec: cleanup
Date: Sun, 21 May 2023 17:06:02 -0300
Message-ID: <c3703a39-c349-6b9d-3c51-82651b179402@gmail.com> (raw)
In-Reply-To: <CAPYw7P5tQigzJ4DVBU5rvvBcOaW5rOC9L5zaVt=7tFgHjOHRxQ@mail.gmail.com>

On 5/21/2023 5:02 PM, Paul B Mahol wrote:
> On 5/21/23, James Almer <jamrial@gmail.com> wrote:
>> On 5/21/2023 4:25 PM, Paul B Mahol wrote:
>>> On 5/21/23, Paul B Mahol <onemda@gmail.com> wrote:
>>>> Attached patches.
>>>>
>>>> This finally removes giant hacks in gif demuxer and allows using gif
>>>> files via pipe reliably.
>>>>
>>>
>>> Better patches attached, no more sets time_base in gif parser.
>>
>> Samples report 100fps now.
> 
> gif is VFR, and that is max fps it supports.

But none of these samples are 100fps, and the fate ref changes look like 
you made them all CFR 100fps, with a lot of duplicated frames to achieve 
that where required.
_______________________________________________
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:[~2023-05-21 20:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21  9:38 Paul B Mahol
2023-05-21 10:05 ` Anton Khirnov
2023-05-21 11:24 ` Paul B Mahol
2023-05-21 17:36   ` Michael Niedermayer
2023-05-21 17:59     ` Paul B Mahol
2023-05-21 19:25 ` Paul B Mahol
2023-05-21 19:37   ` James Almer
2023-05-21 20:02     ` Paul B Mahol
2023-05-21 20:06       ` James Almer [this message]
2023-05-21 21:42         ` Paul B Mahol
2023-05-22 15:49 ` Paul B Mahol
2023-05-22 16:04   ` James Almer
2023-05-22 16:07   ` James Almer
2023-05-22 16:10     ` Anton Khirnov
2023-05-22 16:19 ` Paul B Mahol
2023-05-22 20:01   ` James Almer
2023-05-23 21:51   ` Michael Niedermayer

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=c3703a39-c349-6b9d-3c51-82651b179402@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