[GH-ISSUE #1279] [Bug] The coding progress rate exceeds 100% #940

Closed
opened 2026-02-26 09:33:06 +03:00 by kerem · 2 comments
Owner

Originally created by @inoyakaigor on GitHub (Feb 7, 2024).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1279

Originally assigned to: @NickeManarin on GitHub.

Describe the bug
Often percenatge of encoding process exceed 100%

To Reproduce
Steps to reproduce the behavior:
Just tryed to save a video with these config
screen to gif

Expected behavior
Progress must not exceed 100%

Screenshots
Link to video (Can't attach because it exceed GH file size limit)
But there is most important frame:
videoframe_70020

Desktop (please complete the following information):

  • OS: Win 11
  • Version 2.40.1
  • ffmpeg 6.1.1

Additional context
The video was shot when I set the latest version of ffmpeg 6.1.1 but I've met this bug with in box ffmpeg 4

Originally created by @inoyakaigor on GitHub (Feb 7, 2024). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1279 Originally assigned to: @NickeManarin on GitHub. **Describe the bug** Often percenatge of encoding process exceed 100% **To Reproduce** Steps to reproduce the behavior: Just tryed to save a video with these config ![screen to gif](https://github.com/NickeManarin/ScreenToGif/assets/1235286/c9682ff2-4e91-4cb1-b0ed-721af5fef607) **Expected behavior** Progress must not exceed 100% **Screenshots** [Link to video](https://inoy.dev/files/video_2024-02-07_15-36-07.mp4) (Can't attach because it exceed GH file size limit) But there is most important frame: ![videoframe_70020](https://github.com/NickeManarin/ScreenToGif/assets/1235286/65ec122a-2866-4dbc-a566-7b8886651be3) **Desktop (please complete the following information):** - OS: Win 11 - Version 2.40.1 - ffmpeg 6.1.1 **Additional context** The video was shot when I set the latest version of ffmpeg 6.1.1 but I've met this bug with in box ffmpeg 4
kerem 2026-02-26 09:33:06 +03:00
Author
Owner

@pawlos commented on GitHub (Mar 10, 2024):

Yeah, there's an issue when the ffmpeg encoder produces duplicated frames. The returned frame count number is such case can be greater then one that was passed. We should consider reducing the frame number by the duplicated ones. I'll create a PR to fix this.

<!-- gh-comment-id:1987167604 --> @pawlos commented on GitHub (Mar 10, 2024): Yeah, there's an issue when the ffmpeg encoder produces duplicated frames. The returned frame count number is such case can be greater then one that was passed. We should consider reducing the frame number by the duplicated ones. I'll create a PR to fix this.
Author
Owner

@pawlos commented on GitHub (Mar 10, 2024):

Ok, this is a bit more interesting that initially anticipated.

One of the output lines from ffmpeg:

frame= 1 fps=0.0 q=32.7 size= 0kB time=-00:00:00.04 bitrate=N/A dup=12 drop=0 speed=N/A

So it's not just a matter of removing the dup's as that would produce problems on the other end. Values below 0%. Investigating.

<!-- gh-comment-id:1987372524 --> @pawlos commented on GitHub (Mar 10, 2024): Ok, this is a bit more interesting that initially anticipated. One of the output lines from ffmpeg: > frame= 1 fps=0.0 q=32.7 size= 0kB time=-00:00:00.04 bitrate=N/A dup=12 drop=0 speed=N/A So it's not just a matter of removing the dup's as that would produce problems on the other end. Values below 0%. Investigating.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ScreenToGif#940
No description provided.