Commit Graph

2 Commits

Author SHA1 Message Date
Z User
724da63f7f feat: expose context_frames on the MultiTrack Project node
The number of frames copied from the previous segment as continuation
context (Context / Context Swap continuity) was hardcoded at 22. The
H3 context sampler nodes already accept 5 / 22 / 39 / 56, so the
project node now exposes the same choices as a context_frames combo:

- resolve the widget once in execute() and thread it through every
  continuation site: the ContextSwap / MotionContextHard / HiResContinuity
  graph nodes, the audio-lock prepend, the runtime latent trims, the
  passthrough context encode, and the hires/low context re-encodes
- the context continuation now generates context_frames + 12 grid-tail
  frames (was a hardcoded 34) so every supported value stays on the
  H3 temporal grid; off-grid values raise a clear error up front
- tests: widget propagation at 5 frames end-to-end in the built graph,
  off-grid rejection, schema order/options; existing 22-frame asserts
  unchanged
- docs: multitrack-schema.md documents the widget; CHANGELOG entry

Default 22 keeps every existing workflow byte-identical.
2026-10-13 16:45:41 +00:00
4ea8431cd0 init
Some checks are pending
Publish to Comfy registry / Publish Custom Node to registry (push) Waiting to run
2026-09-26 11:11:23 -07:00