Opened 9 months ago
Last modified 9 months ago
#10941 new defect
Delay time of last frame is ignored for GIFs when using movie filter
| Reported by: | Srikanth Kotagiri | Owned by: | |
|---|---|---|---|
| Priority: | important | Component: | undetermined |
| Version: | 6.1 | Keywords: | movie, gif, vfr |
| Cc: | Srikanth Kotagiri | Blocked By: | |
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description (last modified by )
Summary of the bug:
I have a sample GIF image where the last frame has a long delay of 10 seconds and total duration of 10.15 seconds.
When I use ffmpeg -i messy.gif -vf fps=100 test.mp4, it creates an mp4 file with 1015 frames as expected. I see that the fps filter received EOF with correct timestamp.
[Parsed_fps_0 @ 0x600003488210] EOF is at pts 1015
However when I try to use the movie filter to read a GIF file the EOF packet has timestamp of 16. [Parsed_fps_0 @ 0x600000f94000] EOF is at pts 16 and the output file only has 16 frames instead of 1015.
I am attaching the GIF file, and the ffmpeg logs to this ticket. I think this is a bug in movie filter, but it could be anywhere in the source pipeline.
How to reproduce:
% ffmpeg -f lavfi -i movie=messy.gif -vf fps=100 output.mp4 //full log attached to ticket
Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker.
Source gif file with last frame delay