Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frame timing on gifs is one frame early #28316

Open
omgitsraven opened this issue Aug 25, 2024 · 1 comment
Open

Frame timing on gifs is one frame early #28316

omgitsraven opened this issue Aug 25, 2024 · 1 comment
Labels

Comments

@omgitsraven
Copy link

Steps to reproduce

  1. Look at the following gif in your browser: https://ravenworks.ca/temp/timingtest.gif
  2. Note that "1" and "5" stay on screen for longer
  3. Drag the gif into telegram, to send it "in a quick way"
  4. Look at the animation in telegram; it will likely show the numbers "4" and "8" for longer instead! (Sometimes it displays correctly at first, until you've clicked to zoom in, and then it will be broken from then on.)

Expected behaviour

The frames that are set to display for longer should display for longer.

Actual behaviour

The frame BEFORE the frame that is meant to show for longer, shows for longer instead.

Operating system

Windows 10, 19045

Version of Telegram Desktop

5.4.1

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

@telegramdesktop telegramdesktop deleted a comment Aug 26, 2024
@telegramdesktop telegramdesktop deleted a comment Aug 26, 2024
@telegramdesktop telegramdesktop deleted a comment Aug 26, 2024
@LWChris
Copy link

LWChris commented Sep 13, 2024

Still confirmed in version 5.5.4.

Two notes:

  1. Dragging the GIF from the browser into Telegram sent a png, I had to save the GIF on my computer to send it.
  2. The animation is correct in the preview while attaching, and breaks once it was sent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants
@LWChris @omgitsraven and others