Commit Graph

6 Commits

Author SHA1 Message Date
Z User
ce03875c69 feat: enable automatic spatial tiling on Moxie MultiTrack Project Slow
Bake enabled_tiling with tile_count 0 (automatic) into the Slow node's
second pass: the engine picks the tile count from the available
accelerator memory and bypasses tiling entirely when the full evaluation
fits. This brings 1920x1080 output within reach of 12 GB cards and
AMD/Intel GPUs - the tiling machinery only uses device-agnostic ComfyUI
memory helpers.

- _h3_tiling_config now accepts tile_count 0 (automatic) alongside 2-8
- easy h3SamplingPreviewSampler schema allows tile_count min 0
- tests: tiling config parsing, baked Slow passthrough, second-pass
  graph receives tile_count 0, sampler schema range
- docs: CHANGELOG + multitrack-schema reference
2026-10-14 23:37:47 +00:00
Z User
43d5bf9a1e feat: expose the latent upscaler as an upscale_model widget on Moxie MultiTrack Project Slow
The Slow node previously baked the upscaler checkpoint filename
(minimax_h3_latent_upscaler_3d_fp16.safetensors) into its settings with
no place on the node to choose it. The checkpoint is now a proper
upscale_model combo widget placed with the model components (after
audio_vae):

- options are None plus every file under ComfyUI/models/latent_upscale_models/
  (the bundled default is always kept selectable so the combo default is
  valid even before the checkpoint is downloaded)
- picking None (or an empty string, e.g. from a converted primitive
  socket) raises a clear error instead of silently falling back to the
  decode/RTX-resize/re-encode path this node exists to avoid
- workflows saved before the widget existed fall back to the bundled
  checkpoint, so they run unchanged
- engine untouched: the value flows through the existing
  kwargs.get('upscale_model') read; baked settings simply stop
  overriding it (base BAKED_PROJECT_SETTINGS copy pops the key)
- MoxieProject gains a _component_inputs() schema hook so subclasses can
  slot inputs in with the model components; base node schema unchanged
- tests: schema spot/ordering, folder listing without duplicates, widget
  passthrough, pre-widget fallback to the bundled checkpoint, None/empty
  rejection; CHANGELOG + multitrack-schema.md updated
2026-10-14 22:37:59 +00:00
Z User
5a3b03ef61 feat: add Moxie MultiTrack Project Slow with latent-upscale refine pass
New project node variant (MoxieProjectSlow, display name 'Moxie
MultiTrack Project Slow') that replaces the RTX VSR pixel restore with
a latent upscaler plus a short refine pass:

- identical UX to MoxieProject: end users only set steps and seed (plus
  the shared context_frames overlap); schema mirrors the base node via
  a shared _project_inputs() helper
- first pass stays at the hidden half resolution (engine gains a
  _h3_first_pass_resolution_scale class hook, overriding the previous
  sampling_mode == 'single' hardcode; MoxieProjectSlow returns 0.5
  under dual mode)
- the half-res latent is upscaled to the final (editor) size by the H3
  latent upscaler (minimax_h3_latent_upscaler_3d_fp16.safetensors,
  models/latent_upscale_models) and refined with a hidden 2-step euler
  pass at 0.33 denoise; the schedule replicates KSampler.set_steps
  (int(steps/denoise) total steps, last steps+1 sigmas) without relying
  on the denoise kwarg that newer comfy.samplers builds dropped
- baked settings: sampling_mode dual, upscale_by 1.0 (final size IS the
  editor size), upscale_model as above; the engine's upscale-skip
  condition now compares actual first-pass vs target dimensions instead
  of upscale_by <= 1, which is behavior-identical for every existing
  configuration
- segments are saved at the project resolution, so the Video Combine
  restore passes through untouched - no RTX VSR anywhere
- MoxieProject refactor: component check and baked settings moved into
  reusable helpers (_require_moxie_components, _baked_project_settings
  classmethod) so the subclass composes cleanly; messages unchanged
- tests: Slow schema mirror, execute passthrough (sigma schedule math,
  baked settings, context_frames forwarding, first-pass schedule), the
  resolution-scale hook, and the denoise truncation helper
- docs: CHANGELOG entry, multitrack-schema.md note
2026-10-14 22:14:07 +00:00
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