openshot-qt icon indicating copy to clipboard operation
openshot-qt copied to clipboard

Keyframes for properties attach to the wrong time

Open ShoofLLC opened this issue 3 years ago • 2 comments

Describe the bug: When the time is sped up (time is keyframed); Adding a property keyframe, attaches the property keyframe to an unexpected timestamp.

Steps to reproduce the behavior:

  1. Speed up a clip by 8x (a large number shows the effect better) -- Assume clip time after speeding up is 10s
  2. Go to the start of the clip and add Alpha Keyframe -> Set Alpha to 0 -- Project time: 0.0s, Clip Time: 0.0s
  3. Go the middle of the clip and add Alpha Keyframe -> Set Alpha to 1 -- Project time: 5.0s, Clip Time: 40.0s
  4. Go to the end of the clip and add Alpha Keyframe -> Set Alpha to 0 -- Project time: 10.0s, Clip Time: 80.0s

Playing the clip now will fade-in the clip for about 0.2 seconds and fade out for another 0.2 seconds, rest of the clip remains dark -- about 9 seconds dark.

Note: The GUI display value for alpha doesn't match the actual alpha value anymore, the GUI displays the expected behavior only but not the actual behavior.

Expected behavior: The clip is faded-in till half of the clip and faded out till the end.

System Details:

  • OpenShot Version : 2.6.1
  • Operating System / Distro: Ubuntu 20.04

ShoofLLC avatar Jun 20 '22 22:06 ShoofLLC

Hi, by "actual behavior" do you mean the result when you render the video?

JacksonRG avatar Jun 20 '22 23:06 JacksonRG

Hi, by "actual behavior" do you mean the result when you render the video?

yes, and the result in the preview window.

ShoofLLC avatar Jun 21 '22 05:06 ShoofLLC

Thank you so much for submitting an issue to help improve OpenShot Video Editor. We are sorry about this, but this particular issue has gone unnoticed for quite some time. To help keep the OpenShot GitHub Issue Tracker organized and focused, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

  • No activity in the past 180 days
  • No one is assigned to this issue

We'd like to ask you to help us out and determine whether this issue should be reopened.

  • If this issue is reporting a bug, please can you attempt to reproduce on the latest daily build to help us to understand whether the bug still needs our attention.
  • If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks again for your help!

stale[bot] avatar Dec 21 '22 03:12 stale[bot]

Download the latest DEV Daily Build of v3.0.0 and see if that resolved your issue.

Colorjet3 avatar Jan 01 '23 17:01 Colorjet3