Summary: | Flatten layers with animation frame provide a strange result | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | grum999 |
Component: | Animation | Assignee: | Emmet O'Neill <emmetoneill.pdx> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ahab.greybeard, eoinoneill1991, tamtamy.tymona |
Priority: | NOR | ||
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Before layer has been flattened
Result after layer has been flattened |
Description
grum999
2020-08-02 07:38:36 UTC
Created attachment 130568 [details]
Before layer has been flattened
Created attachment 130569 [details]
Result after layer has been flattened
I can confirm this for the 4.3.0 and 5.0.0 Aug01 prealpha (git a72eb74) appimages on Debian 10. It's not neccessary to shift the duplicated layer frames to the right. The artifacts appear for a transformed non-shifted duplicate or for a transformed original layer. The artifacts are fragments of past or future frames. They are permanent parts of the image. They are created by the layer flattening operation. I was concentrating on the artifacts in Comment 3. I also see the spurious keyframe at frame-0 which is a copy of the first frame of the original layer, usually with a part missing. After shifting frames, a blank keyframe is created at frame-0 and this can not be removed. The layer flattening operation creates the spurious content of frame-0 which then is a not-empty keyframe. Again, a duplicate layer is not needed. This happens for a frames shift and transform of the original layer followed by layer flattening. This bug report is somewhat of a high priority because this is the only way to move/transform multiple frames at once. Merging down later is important (to be able to transform later, too, or to be able to just transform some keys and then go back etc.), and it shouldn't introduce any artifacts. We've changed some of the way merging animated content works and it seems like it may have resulted in this being fixed. I've tried to reproduce it on a handful of test files in my collection and can't seem to get the artifacts anymore. If you come across this error again, please save, reopen this issue, and submit a example file! |