Bug 447610 - One of the frames in the animation plays back corrupted after moving them a few spaces over.
Summary: One of the frames in the animation plays back corrupted after moving them a f...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 5.0.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2021-12-28 19:12 UTC by popingsarah
Modified: 2023-02-04 04:58 UTC (History)
3 users (show)

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


Attachments
Showing the corruption in playback (1.38 MB, video/x-matroska)
2021-12-28 19:12 UTC, popingsarah
Details

Note You need to log in before you can comment on or make changes to this bug.
Description popingsarah 2021-12-28 19:12:29 UTC
Created attachment 144914 [details]
Showing the corruption in playback

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. Draw frames
2. Move them a few spaces over
3. Use playback

OBSERVED RESULT
One of the frames looks corrupted on playback

EXPECTED RESULT
For it to play back normally

SOFTWARE/OS VERSIONS
Windows: Windows 10

ADDITIONAL INFORMATION
Even cutting that frame out and replacing it did nothing to fix it.
Comment 1 Eoin O'Neill 2022-01-03 21:05:01 UTC
Could you provide us with some hardware specs? This seems to be an OpenGL or Angle issue with cached playback.
Comment 2 popingsarah 2022-01-03 21:14:39 UTC
(In reply to Eoin O'Neill from comment #1)
> Could you provide us with some hardware specs? This seems to be an OpenGL or
> Angle issue with cached playback.

Sure, what specs do you need?
Comment 3 Eoin O'Neill 2022-01-03 22:14:00 UTC
Hi popingsarah,

If you could provide the following information, it would help us quite a lot.
1) Please give us any information regarding your cpu or gpu (model, driver, etc.) so we can try similar vendors or models if possible.
2) If you could provide us a test file, like the one in the video that can have the issue reproduced, that would help with trying to reproduce it on our end.
3) Lastly, please tell us your current settings in the following preferences windows: 
   `Settings > Configure Krita... > Display > Canvas Acceleration`
   `Settings > Configure Krita... > Performance > Animation Cache`

Thanks,
Eoin.
Comment 4 popingsarah 2022-01-03 22:43:24 UTC
(In reply to Eoin O'Neill from comment #3)
> Hi popingsarah,
> 
> If you could provide the following information, it would help us quite a lot.
> 1) Please give us any information regarding your cpu or gpu (model, driver,
> etc.) so we can try similar vendors or models if possible.
> 2) If you could provide us a test file, like the one in the video that can
> have the issue reproduced, that would help with trying to reproduce it on
> our end.
> 3) Lastly, please tell us your current settings in the following preferences
> windows: 
>    `Settings > Configure Krita... > Display > Canvas Acceleration`
>    `Settings > Configure Krita... > Performance > Animation Cache`
> 
> Thanks,
> Eoin.

1) In device manager it says: AMD Radeon R7 Graphics (driver version 27.20.20903.8001) 
    But for more specifics in msinfo it says in processor AMD Pro A8-8650B R7
2) I will attach the krita file it happened to (though I will say, the issue is only within krita playback, when it is exported as an mp4, as I did afterwards, you cannot see the corrupted frame). 
3) Canvas Acceleration: 
                                       Renderer- Auto (Direct3D 11 via ANGLE)
                                       Scaling mode- High Quality Filtering
                                       Use texture buffer- on
    Animation Cache:
                                       Cache storage backend- In memory
                                       Limit cache frame size- 2500px
                                       Use region of interest- 25%
                                       Enable background cache generation- on
Comment 5 popingsarah 2022-01-03 22:49:45 UTC
(In reply to Eoin O'Neill from comment #3)
I tried to attach the krita file but the "add an attachment" feature here says the file is too large.
Comment 6 Bug Janitor Service 2022-01-04 04:35:02 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 7 Eoin O'Neill 2022-01-18 22:01:49 UTC
So those settings don't look like anything I don't have going on in my system. I'll have to see if someone else has hardware similar to yours where we can try to reproduce this issue. One last thing you could try is updating your current driver (it looks like your version is from May of last year, and there might be newer graphics drivers available.) You can also try limiting the frame cache to 1000px and see if that resolves any caching relates issues (it could be that your graphics card is out of memory on longer animations, but in which case we should still probably find ways of preventing this kind of issue.) If the 1000px frame limit works, you could see if on-disk caching at 2500px helps resolve this issue too!

I'm sorry that I couldn't be of more help,
Eoin.
Comment 8 Emmet O'Neill 2023-01-05 00:52:57 UTC
I made a similar test animation but I'm not able to reproduce this issue on either Linux or Windows with various settings.
It could be that I'm on an nVidia GPU, but I had Eoin test it on his AMD GPU and he wasn't able to reproduce it either.

Is this still something that affects you on more recent versions of Krita, Sarah?

For now I'll be setting this to "needs info" /  "works for me", but it's no problem to reopen this bug report if the issue is still affecting people.
Comment 9 Bug Janitor Service 2023-01-20 05:07:49 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 10 Bug Janitor Service 2023-02-04 04:58:56 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!