Commit Graph

3 Commits

Author SHA1 Message Date
Z User
0a9416b91a feat: expose context_frames on Moxie MultiTrack Project
MoxieProject subclasses EasyMultiTrackProject and runs the same
continuation engine, but its consolidated schema hid the new
context_frames widget added to the parent node in 724da63 - so the
overlap stayed locked at 22 for the node end users actually see.

- add the same context_frames combo (5/22/39/56, default 22) between
  steps and seed on Moxie MultiTrack Project; execute() already
  forwards kwargs through to the base engine untouched
- baked euler/beta sampling stack unchanged: sampling_plan stays
  'custom', sampling_mode stays 'single'
- tests: MoxieProject schema order/options, execute passthrough proof
  (widget reaches the base engine, baked settings never clobber it),
  and the moxie_nodes schema assert updated for the new widget; test
  harness gains a comfy.samplers stub and ControlAfterGenerate.randomize
- docs: multitrack-schema.md notes the widget on MoxieProject;
  CHANGELOG updated

Default 22 keeps every existing MoxieProject workflow identical.
2026-10-14 05:12:39 +00:00
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