Bug 404575 - One frame lag
Summary: One frame lag
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 4.1.7
Platform: Homebrew (macOS) macOS
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-19 21:37 UTC by Brianna
Modified: 2019-05-10 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brianna 2019-02-19 21:37:01 UTC
Basically it it just lagging behind by one frame.


STEPS TO REPRODUCE
1. Make 3+ frames
2. Draw on the frames
3. Play the animation

OBSERVED RESULT
In one document, it worked properly and did not lag, I duplicated it except in CMYK instead of RGB and it did not work. the other 4 did not work, they lagged, they were all either in CMYK or RGB. I don't know why that would effect anything but just thought I'd mention it. When I would press play, they did exactly what I expected (aside from the first one) by lagging behind by one frame. I would press the play button and it would play, but then once it hit frame 2 it would not change. Once it hit frame 3, it changed to Frame 2.

EXPECTED RESULT
Exactly what happened above ^^^

SOFTWARE/OS VERSIONS
MacBook Pro (Retina, 13-inch, Early 2015)
Processor: 2.7 GHz Intel Core i5
Memory: 8 GB 1867 MHz DDR3
Startup Disk: Macintosh HD
Graphics: Intel Iris Graphics 6100 1536 MB

ADDITIONAL INFORMATION
I'm not entirely sure what happened with the first recreation, as it worked perfectly fine, the rest, however, didn't. Once I render the animation, it plays perfectly fine, it's just in the program that it has this 1 frame behind issue. I have gone to the chatroom and they tried to help me as best as they could, but nothing worked, I have also looked through the forums and found the exact same problem which was fixed by changing the cache storage backend, but that didn't work for me either.
Comment 1 wolthera 2019-03-06 09:25:43 UTC
hey, could you share a test file? Maybe we can learn something from the file.
Comment 2 wolthera 2019-04-08 14:40:28 UTC
I have been wondering about this, were you by any change using a fill layer?
Comment 3 vanyossi 2019-04-10 17:46:40 UTC
I have the same MBP as you but I cannot reproduce this issue.

We need more info.

I tried simple file
and File with fill and clone layers
Comment 4 Bug Janitor Service 2019-04-25 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2019-05-10 04:33:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!