Remove Extra Keyframe without changing tha Graph Editor

[iamsibtehassan]

Hey there,

So, I'm trying to make a character walk by the screen for a project and I need the character in .json format. I'm using Bodymovin' and the whole new DUIK Bessel for the purpose. The problem is when I Bake the Walk Cycle to the layers(using Bake Parent Transform Plugin) It puts a keyframe on each frame and each property(position, scale, rotation) even if it's not needed. All I'm trying to do is make the extra keyframes go away without Messing the Graph Editor.

Is there any way I could do that?

Hope to get a Quick Reply *fingers crossed*

[Martin_Ritter]

The idea of "baking" expressions is to make a keyframe to every frame. As far as I know, there is no way to add an "intelligence" to this process which analyzes the expression and create keys only there they are needed.

If a property never changes, you can just click on the stopwatch to remove all the keys.

Why can't you just leave it the way it is with all the keyframes?

Cheers,

Martin

[iamsibtehassan]

I had to do that because boodymovin' doesn't support DUIK rigs because it uses parent-child method to rig the character, so I had to bake the whole property on the original character files to make the animation go through bodymovin'.

The only problem I am facing right now is the .json file it makes is too heavy for the app because the baker bakes keyframes on the object every frame based on its position, rotation on every instance, for Example: if the X-positon is easy-eased, Baker will make a keyframe for each frame.

[Mylenium]

Well, to be blunt, if keyframe efficiency is required, than using automated scripts and expressions certainly isn't the way to do it to begin with. The answer is good old hand animation where only keyframes are created when you realyl need them.

Mylenium

[iamsibtehassan]

Or I should manually Delete the Unwanted keyframes, which will require some time

[Martin_Ritter]

I see.

You can get rid of keyframes when an property is never altered, as I said before. But I don't know any comfortable way to get rid of all those unnecessary keyframes on the properties, which are altered, since the logic behind baking expression is just to calculate the final value and put this into a keyframes.

To get a result with "as much keyframes as needed" you'll need an discrete cosine transformation algorithm (and you sinus wave in the screenshot is just a perfect example of how it works) which replicates the input with as less samples as possible. MP3 and JPEG is working this way.

However... I can only think of duplicating every layer and recreating the motion by hand with keyframes, as you would do it without DUIK. This is monkeywork, but you can isolate the two layers in questions, but their opacity to 50% and than it should be a straight forward rotation-and-positioning thing.

And once you got the first cycle, you can just copy-paste the keyframes.

Cheers,

Martin

[iamsibtehassan]

I Think that's the way to go unless there is a plugin for this purpose.
Thanks.

[Martin_Ritter]

I would keep all the keyframes as reference. Once you start deleting them, you don't know how your animation used to look like.

I don't know any script for this purpose (but it seems to be an interesting way to spend a couple of weeks/months creating one - serious!).

Always keep in mind, that you only have to take care of the first cycle. After that, it's only repeating (unless you did fancy walkcycling stuff...).

Headphones on, good music and your done in a couple of hours - Good luck!

[iamsibtehassan]

Great! Thanks for the help guys

[market175789165]

There's an animation Kleaner (in the animation tab, the icon of a broom) in the Duik Bassel- one of its functions is removing unnecessary keyframes - I think it could work