Bug 361273 - Changing from one keyframable transition to another keyframable transition looses all keyframes
Summary: Changing from one keyframable transition to another keyframable transition lo...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (show other bugs)
Version: 16.08.1
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-01 12:37 UTC by Wegwerf
Modified: 2019-09-24 04:33 UTC (History)
4 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 Wegwerf 2016-04-01 12:37:14 UTC
When switching between, for instance, affine and composite transitions, all keyframes get completely lost. This means that for a more complex keyframe setup after switching between transition types all keyframes need to be setup manually again.

For instance, a keyframe export and import to an external file could be helpful, as well as keeping at least the common parameters and the timecode of the keyframes across switching keyframable transititions.

Reproducible: Always

Steps to Reproduce:
1. Add color clip and create affine transition on it.
2. Add several keyframes to this affine transition.
3. Change transition properties from affine to composite.

Actual Results:  
All keyframes lost.

Expected Results:  
Keyframes kept intact with those parameters that are also available for the new transition.
Comment 1 farid 2016-10-05 00:36:38 UTC
I confirm in 16.08.1, but maybe this is by design?
Comment 2 Wegwerf 2016-10-05 19:30:36 UTC
Yes and no. We should at least keep the keyframes with geometry and opacity information when switching between dynamic compositing transitions; and this is the kind of switching I'm referring to in this report.
Comment 3 emohr 2019-08-25 12:24:55 UTC
Please try with the current Kdenlive AppImage version 19.08.0a to see if there are any packaging issues https://files.kde.org/kdenlive/release/ 

If the problem/issue doesn't occur when using the AppImage, then it's your configuration or packaging.
Comment 4 Bug Janitor Service 2019-09-09 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-09-24 04:33:09 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!