Problem
I wanted to ask whether gesture-to-keyframes recording would fit the Studio roadmap.
When authoring programmatic videos, I sometimes want motion that feels hand-directed instead of starting from only numeric inputs or presets. For example, selecting an element, pressing record, moving it directly in the preview, and turning that gesture into editable animation keyframes.
Hyperframes Studio already has element selection, manual drag editing, GSAP motion metadata, and keyframe editing, so this seems like it might be a natural extension of the current authoring workflow.
Proposed solution
A small MVP could be limited to:
- select one element in Studio
- record only
x / y motion
- sample pointer movement while the playhead advances
- simplify the sampled points before writing them
- save the result as editable GSAP keyframes
I would expect users to refine the generated keyframes afterward rather than treat the recording as a final result.
Alternatives considered
The current explicit keyframe and preset-based workflow is more deterministic and easier to reason about. Another option would be to keep gesture recording outside Studio and let users paste generated GSAP keyframes manually.
I would not expect an initial version to cover rotation, scale, smoothing controls, webcam/pose capture, or full motion-path authoring. Those could stay out of scope unless this direction proves useful.
Additional context
I previously built a similar workflow in a Remotion-based project and found it useful for quickly sketching organic motion before refining the generated keyframes. Reference concept: https://x.com/vericontext/status/2058952147157627103?s=20
Would this be useful for Hyperframes Studio, or would you prefer motion authoring to stay closer to explicit keyframe/preset editing for now?
Problem
I wanted to ask whether gesture-to-keyframes recording would fit the Studio roadmap.
When authoring programmatic videos, I sometimes want motion that feels hand-directed instead of starting from only numeric inputs or presets. For example, selecting an element, pressing record, moving it directly in the preview, and turning that gesture into editable animation keyframes.
Hyperframes Studio already has element selection, manual drag editing, GSAP motion metadata, and keyframe editing, so this seems like it might be a natural extension of the current authoring workflow.
Proposed solution
A small MVP could be limited to:
x/ymotionI would expect users to refine the generated keyframes afterward rather than treat the recording as a final result.
Alternatives considered
The current explicit keyframe and preset-based workflow is more deterministic and easier to reason about. Another option would be to keep gesture recording outside Studio and let users paste generated GSAP keyframes manually.
I would not expect an initial version to cover rotation, scale, smoothing controls, webcam/pose capture, or full motion-path authoring. Those could stay out of scope unless this direction proves useful.
Additional context
I previously built a similar workflow in a Remotion-based project and found it useful for quickly sketching organic motion before refining the generated keyframes. Reference concept: https://x.com/vericontext/status/2058952147157627103?s=20
Would this be useful for Hyperframes Studio, or would you prefer motion authoring to stay closer to explicit keyframe/preset editing for now?