Bug 480530 - Every time I try to play my animation test from my animation timeline it glitches and shows pieces of two frames cut off in the centre of the drawing at the same time... it even shows past drawings that i deleted from the frame also cut in half.
Summary: Every time I try to play my animation test from my animation timeline it glit...
Status: RESOLVED DUPLICATE of bug 481244
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: unspecified
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Loéva
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-30 10:22 UTC by Loéva
Modified: 2024-02-26 17:00 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
drawn frames vs glitching animation playback (43 bytes, text/plain)
2024-01-30 10:31 UTC, Loéva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Loéva 2024-01-30 10:22:04 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. press the play/pause button in Animation timeline
2. you can see that the animated frames don't correspond to the actual drawn frames (cut off pieces from two frames show at the same time).
3. By pausing the animation at the right moment, you can see the glitch in the frames for a few seconds before it returns to the actual drawn frame.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Loéva 2024-01-30 10:31:49 UTC
Created attachment 165345 [details]
drawn frames vs glitching animation playback
Comment 2 Doug 2024-01-31 04:52:39 UTC
Moving bug report to Application: Krita
Comment 3 Dmitry Kazakov 2024-02-26 17:00:58 UTC
Hi, Loeva!

Thank you for the report! I have just fixed the issue! :)

*** This bug has been marked as a duplicate of bug 481244 ***