Problem with Keyframes moving on their own

Aggro Sky

Newbie Joined: Dec 12, 2015 17:57 Messages: 7 Offline

Solved by

Nov 24, 2018 16:27

I've had this problem since I upgraded from PD15 and it's incredibly frustrating. No other version of Power Director has had this issue.

Often when I move keyframes around, a previous keyframe will also move. For instance, say I'd like to move an element acorss the screen, like an animation I've created. I create a keyframe at the zero mark, then move down the timeline to the 10 second mark, create a new keyframe by moving that element across the screen to that new location. However, when I go back to my first keyframe, it has seemingly moved on it's own in relation to the new keyframe I made (the element itself, not the actual keyframe). This bug doesn't happen everytime and I'm not sure exactly what causes it, but probably 75% of the time when I manipulate any and all keyframes further down the timeline, all of my previous keyframes are effected which makes it impossible to be consistent if you are trying to move any elements on the screen.

If needed, I could take a video of the problem in action. It's pretty easy to duplicate. I should also mention that I use a lot of animations with Alpha Channels enabled, which I think may have something to do with it. At any rate, it was never a problem before until PD16. I am considering upgrading to 17 but if this issue is still there I'll be switching to Adobe. It's to the point where I can barely work on video without having to go back and fix numerous keyframes which wastes massive amounts of time. Any help would be greatly apprecaited!

This message was edited 1 time. Last update was at Nov 24. 2018 16:32

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Nov 24, 2018 17:09

I know what you're talking about, and I've seen things like this happen in the last couple PD versions, including 17. Also, it's not alpha channels because I wasn't using any in the affected projects. It's definitely position keyframes, though.

In fact, I've seen actual keyframes move/disappear when I made changes downstream, but I think the underlying bug with the code is the same in both cases.

From what I remember, exiting the keyframe timeline window seemed to break the link between current and past keyframes, and I also saved the project often. I think Undo did take care of the unwanted changes (assuming that I noticed them!), and saving after I was certain things were correct was my fall-back approach.

One other thought to minimize exposure to this would be to do something different with the new keyframe rather than moving your object straight away. In your example, leave the object where it is at the start, create a new keyframe at the end, and then right click and choose Duplicate previous keyframe.

Even though that doesn't accomplish anything from an editing standpoint, it may be enough to break the unwanted linking effect. Hopefully when you do move the object to where you want it to end up, the original keyframe placement will remain unaffected.

I wish I had a better workaround, and I also wish that I'd submitted a tech support request when I first encountered the issue. I think it's worth making a video and sending the issue to Cyberlink Tech Support at this point. They don't monitor the forum, and if none of us reports the issue, it's not going to get fixed.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Aggro Sky

Newbie Joined: Dec 12, 2015 17:57 Messages: 7 Offline

Nov 24, 2018 17:16

Quote I know what you're talking about, and I've seen things like this happen in the last couple PD versions, including 17. Also, it's not alpha channels because I wasn't using any in the affected projects. It's definitely position keyframes, though.

In fact, I've seen actual keyframes move/disappear when I made changes downstream, but I think the underlying bug with the code is the same in both cases.

From what I remember, exiting the keyframe timeline window seemed to break the link between current and past keyframes, and I also saved the project often. I think Undo did take care of the unwanted changes (assuming that I noticed them!), and saving after I was certain things were correct was my fall-back approach.

One other thought to minimize exposure to this would be to do something different with the new keyframe rather than moving your object straight away. In your example, leave the object where it is at the start, create a new keyframe at the end, and then right click and choose Duplicate previous keyframe.

Even though that doesn't accomplish anything from an editing standpoint, it may be enough to break the unwanted linking effect. Hopefully when you do move the object to where you want it to end up, the original keyframe placement will remain unaffected.

I wish I had a better workaround, and I also wish that I'd submitted a tech support request when I first encountered the issue. I think it's worth making a video and sending the issue to Cyberlink Tech Support at this point. They don't monitor the forum, and if none of us reports the issue, it's not going to get fixed.

Good to know! I will make a video on the issue soon and send it their way since this NEEDS to get fixed. It is almost to the point where it ends up wasting more time than it's worth. It's a pretty serious problem when your keyframes are moving all over the place! Thanks for the tips though, I apprecaite it!

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Nov 24, 2018 17:26

Sounds good. Let us know how the keyframe/workflow ideas work out. If I get a chance this evening, I'll try them on my end as well.

Also, when you report the issue, paste the link to this thread in your description so they can see what's happened, especially if you make a video. Once you get a ticket (CS#) from Cyberlink, please post it here as that seems to close the loop.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Aggro Sky

Newbie Joined: Dec 12, 2015 17:57 Messages: 7 Offline

Nov 24, 2018 18:33

Quote Sounds good. Let us know how the keyframe/workflow ideas work out. If I get a chance this evening, I'll try them on my end as well.

Also, when you report the issue, paste the link to this thread in your description so they can see what's happened, especially if you make a video. Once you get a ticket (CS#) from Cyberlink, please post it here as that seems to close the loop.

Will do! Also FYI, I tried that method of making an extra keyframe in the center of the two, it still misplaces the first keyframe...

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Nov 24, 2018 18:52

Quote Will do! Also FYI, I tried that method of making an extra keyframe in the center of the two, it still misplaces the first keyframe...

That's a good idea, but I actually didn't actually suggest that. I wanted you to create just one new keyframe at the end of the clip, and before moving the object to the new position, apply the duplicate previous keyframe feature to it, which will copy all of the original keyframes attributes to the end location.

I'm hoping that doing that will anchor the changes you make to the new keyframe (which is what's supposed to happen) and completely disconnect it from the starting one (which is what the software bug is somehow affecting).

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Aggro Sky

Newbie Joined: Dec 12, 2015 17:57 Messages: 7 Offline

Nov 24, 2018 18:54

Quote

That's a good idea, but I actually didn't actually suggest that. I wanted you to create just one new keyframe at the end of the clip, and before moving the object to the new position, apply the duplicate previous keyframe feature to it, which will copy all of the original keyframes attributes to the end location.

I'm hoping that doing that will anchor the changes you make to the new keyframe (which is what's supposed to happen) and completely disconnect it from the starting one (which is what the software bug is somehow affecting).

Ahhh got it! I will try that as well!