Clip Apply Path

Overview

Applies an animation clip created with keyframe_clip to an actual path. Instead of only previewing motion in the editor, it sends a Path transformed at the specified time downstream to path_stroke or another node. This connects clip motion to the final rendered appearance.

Usage tips

• The go-to final-output chain is keyframe_clip.clip + source path → clip_apply_path → path_stroke → animation_render. The clip motion is baked into a spritesheet at final rendering quality.
• Connect Time Source to progress to synchronize it with the animation renderer's clock. For manual scrubbing, connect Float Input to progress.

Related nodes

• keyframe_clip — supplies the clip to apply
• clip_apply_image — image counterpart
• path_stroke / path_fill — render the path after application
• animation_render — final bake

Technical details

The current implementation handles only these tracks:

• PathPoint
• ShapeHandle

The expected source types are:

• BezierPath
• MultiPath

Track targets are resolved from target.channel and the segmentIndex / pointKey / layerIndex fields in target.metadata. It directly overwrites the corresponding points or handles and does not yet provide additional transformation modes.

Examples

1. BezierPath
2. RecordTake
3. KeyframeClip
4. ClipApplyPath
5. PathStroke

Connections:

• RecordTake.layer -> KeyframeClip.layer
• BezierPath.path -> ClipApplyPath.path
• KeyframeClip.clip -> ClipApplyPath.clip
• Float Input.output -> ClipApplyPath.time

Moving Float Input now applies the recorded path-point motion to the actual path.

Time and unsupported tracks

• The only time input is progress (normalized 0–1). Connect Time Source to progress. The legacy absolute-seconds time pin has been removed; old connections are rewired to progress on load.
• Points/handles missing from the target Path, unresolved metadata, and unsupported tracks are skipped while the original path remains usable. summary reports applied and skipped counts, and warnings reports tracks_skipped.