← All ideas

KSP - Keyframe Script Python (new type key on time line - with python)

The idea is to give option on TimeLine by RCM to select a Keyframe Scrip Python t type, then can be a special icon like P (Python).

The usage of KSP is simple.. double click on icon KSP opening Python Script Editor and from this Script user can control a time line. In default KSP call adding something like:

  • bpy.types.TimeLineControl
  • bpy.types.TimeLineControl.Frame()

Regarding this feature request as:

blender.community/c/rightclickselect/2hhbbc/ - Control states for objects and animations/frames (on/off, true/false) by btns on GUI and script sorting=hot

  • The solution is more easy and complex as just in Script code can be:

in frame 10 GoToPlay(5) - it's giving indication as "jmp" or "Jump" to the frame, and can be conditions how many times as loop, but the TimeLineControl lib can indicate to Render Engine that this frame was render and just copy or rename in final post process. This can optimize a work flow around rendering.

  • By this some repeating of scenes, frames can be done more easy in relation forward, backward, etc.
  • Also some of renders can be with option to apply some additional node functions, eg. edited frame, let we say.. darker, tinted, etc.

Also it be great as RFF in link.. if each object can have own scene and time line to operate inside like instances. I think animators know how useful this can be in practice way.

  • Soo.. KSP can be as trigger for some actions around objects, bones, etc. and control variables and values as some type "infinite state machine" but under control of TimeLine instances.

  • The KSP points, keyframes can be transfered to nodes as relations for TimeLine, then can have something like VLN

blender.community/c/rightclickselect/5jhbbc/ - VLN - Virtual Logic Nodes

  • Also KSP can be used in sequencer, video editor, etc. to support control around time line, eg. curves around charts motion

  • I think that any Key icon should be "called" from GUI, to reach ID_key to manage in some way, eg. turn on/off in future

This can be be step and change around Blender. Hard job.. sure.. : )

0%

Development Status: Open

Upvote 0 Downvote 0
ManBlender
21 Apr 2024

1 Comment

Jordan-Henshaw

I'm not understanding which part of your proposal is different from what Blender already offers through bpy. I'm also far from convinced that you're the least bit familiar with bpy to begin with. Convince me.