https://bugs.kde.org/show_bug.cgi?id=357386
Bug ID: 357386
Summary: Git master 2016-01-01 - Saved custom filter stack has
fixed keyframes
Product: kdenlive
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: evert.vors...@yandex.com
I have a pretty complicated filter stack that does not change much between
render jobs, so I saved it.
The filter stack consists of: De-fish, Levels, White balance, Saturation,
Sharpening.
None of these effects take key frames when first applied. However, when the
entire stack is saved and applied to another clip, they suddenly have key
frames. Worse, the key frames is for the frame numbers of the previous clip,
and if this happens to be after the last frame of the current clip, the effects
are applied at their highest negative setting.
Reproducible: Always
Steps to Reproduce:
1. Make a filter stack a few levels deep. Save it as a custom one.
2. Apply the filter stack to another clip, and look at the frame numbers the
effects in the stack have now suddenly gained.
3. Add one more keyframe, and delete the original keyframe.
4. The keyframes now disappear for the selected effect in the stack.
Actual Results:
Effects stack does not apply without fiddling, and looks different from the one
that was saved.
Expected Results:
The effect stack to be key frame agnostic, just like the one I saved.
This is a little annoying, and I found half a workaround by making the effect
stack on the first frame of a clip, and then saving it. Then the effect stack
is applied each time, at least. However the key frames remain until I pick a
key frame in the clip, and delete the others.
This could actually be quite a nifty feature, if it was possible to leave the
key frames add button to each effect, and then just interpolate between the key
frames if more than one key frame is added.
However, the key frames should be adjusted to the first frame of the clip that
the effect is being applied to, as specifying a key frame that is not in the
range of the clip does not make sense.
Also, the frame with the key frames in should also be hidden when there is only
one key frame, to save screen space. It is then assumed that the effect does
not change for the entire.
If the button for adding more key frames is left in, and expose the key frame
window when another key frame is added, it could be quite a feature at almost
no extra coding cost.
--
You are receiving this mail because:
You are watching all bug changes.
