hello! im trying to do some simple tweening using the animation curves docker, and i use very few keyframes for this. however whenever i save and open the file again, i find that a new keyframe has been added in between the ones i made myself, on every single frame.
i created only two keyframes for each axis of movement, at the start and end of these chains. all these extra points make it very annoying to adjust the movement, so advice is appreciated ^∙^
(im using krita 5.2.6 on windows, and im trying to use tweening to move the frame to the side on the x axis.)
This is worrying.
It happens with 5.2.5 and 5.2.6 when you do Image → Scale Image to New Size or Image → Resize Canvas or use the Crop Tool.
I’m surprised it hasn’t been noticed until now.
Did you do any of those things?
The inserted keyframes do not accurately represent parameter values for the frames if Bezier curved interpolation has been used.
Also, with the Crop Tool, the values are totally wrong even though the resulting animation seems to work.
This addition of keyframes does not happen with the 5.1.5 appimage.
I haven’t checked between 5.1.5 and 5.2.5 to see when it happened.
With 5.1.5, there were errors in keyframe values after Resize so I didn’t use Resize Canvas during an animation.
What we see with 5.2.5, 5.2.6 may have been an attempt to fix the problem.
The workaround is to not do Scale, Resize or Crop.
You can do those by rendering out an intermediate .png sequence, Import the sequence back into a new image then do the Scale, Resize or Crop operations on that.
Can you create a formal bug report for this and post the link in a reply here?
thanks for the quick reply!! i did resize the canvas, but that was quite a while before i made this frame/inserted these keyframes. i’ll test out a few more things and then submit a report, tho this is my first time doing that so it might take a while.
in the mean time, is there a quick way to delete many keyframes in the animation curves docker? ive been selecting them with shift and deleting but that is very slow
Do you find that the inserted keyframes have the correct values for linear interpolation?
I see the keyframes added as soon as I do a Scale, Resize or Crop.
You may have had a non-mask layer selected when you did one of those operations and so didn’t notice at the time.
I’ve changed the category to Developer Questions in the hope of getting early comment from the developers.
im testing a few more image functions to see if there are any more glitches like this. some of them ive never used before so i might be missing a few bugs there.
while resizing the image seems to cause no problems, other functions create brand new messes. resizing the image causes problems too. more on that in a moment
rotating the image (image → rotate 90 to the left) adds new keyframes on every frame, as well as completely changing their values. Shear image also does this, tho with less extreme value changes.
Mirror image causes no changes. Offset image causes no changes.
ok. tried resizing the image again. and it crashed.
trying again, resizing the image by one pixel and no offset. no problems at all.
resizing by one pixel and with 0.5 offsets makes the keyframes go haywire again. again adding keyframes every frame. the x and y lines went up a bunch too (due to the offset?). undoing the resizing undoes the x and y lines moving, but does not remove the many keyframes added.
wavelet decompose does nothing unexpected.
should i limit my bug report to the initial problem i mentioned? because frankly alot of this seems beyond my scope to describe, let alone test thoroughly.
I think you should just report the cases you’ve observed so far.
The developers will be able to do a detailed investigation and will know the sort of things to look at.
You can include a link to this topic, in the bug report, for reference.
I’ve Confirmed this bug report and added my own observations.
The bug was introduced in version 5.2.3 as tested with the Linux appimage.
You could try using the 5.2.2 portable .zip package for Windows if you’re finding it disruptive and/or annoying: https://download.kde.org/Attic/krita/5.2.2/krita-x64-5.2.2.zip
(Don’t try using it at the same time as you’re running the installed 5.2.6 version.
It is possible to do it but that could be regarded as ‘interesting but foolish’)
Here are some screenshots to illustrate the problem, as referred to in the bug report.
