Commit Graph

9 Commits

Author SHA1 Message Date
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
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
Z User
22310bef00 fix: compose the project timeline at its native size and restore full resolution before any combine output
The compose step previously built the timeline at the manifest
resolution while staging segments are written at the (hidden) half-res
sampling size, so ffmpeg's overlay pasted the smaller segments into the
top-left quarter of a black full-res canvas and the combine's restore
gate saw frames already at the manifest size and never fired.

- compose_h3_project_video now probes the timeline segments and composes
  at the size they all share (_uniform_probed_size; manifest dims remain
  the fallback for mixed/unknown sizes)
- restore_project_video_resolution (utils/rtx_vsr.py) fast-probes the
  composed file, and when it differs from the manifest decodes once,
  upscales (RTX VSR, Lanczos fallback, exact size) and rebuilds the
  video so VIDEO, images, audio and fps all carry the editor-selected
  resolution; any failure keeps the original video
- the restore lives in the base combine so MoxieCombine (images slot)
  and the legacy GetVideoComponents wiring are both covered; the
  duplicated images gate in MoxieCombine is gone
2026-09-27 02:18:11 +00:00
Z User
563322a3e2 feat: simple hidden half-res sampling, restored at the video combine
Single-pass projects condition and sample at exactly half the
editor-selected resolution (plain integer halving, no dimension
policies). Moxie Project Video Combine restores the exact editor
resolution on the combined frames right before its images output,
driven by the fresh project manifest so a stale frontend widget can
never misgate it.

- utils/rtx_vsr.py: RTX VSR core (Apache 2.0, from
  Comfy-Org/Nvidia_RTX_Nodes_ComfyUI) + Lanczos fallback; the gate is
  simply 'frames differ from the manifest resolution'
- nodes/project.py: halve first-pass dims for single mode only;
  dual-pass, SelfLift, passthrough and audio-only keep the editor size
- moxie_combine.py: restore before the images output
- scripts/test_rtx_upscale_integration.py: 17 standalone checks
2026-09-27 01:18:33 +00:00
Z User
f94ee3e40b Revert "feat: hidden half-res sampling with RTX VSR output restore"
This reverts commit bd26656732.
2026-09-27 01:13:26 +00:00
Z User
bd26656732 feat: hidden half-res sampling with RTX VSR output restore
Single-pass MultiTrack projects now condition and sample at half the
editor-selected resolution; Moxie Project Video Combine restores the
exact editor resolution on the combined frames before export, so the
editor resolution remains what the user sees and gets.

- utils/rtx_vsr.py (new): RTX Video Super Resolution core adapted from
  Comfy-Org/Nvidia_RTX_Nodes_ComfyUI (Apache 2.0) driving the optional
  nvidia-vfx package per frame, with automatic Lanczos fallback and
  exact-size correction; owns the sampling-dimension policy and the
  project_data gating so only half-res signatures are upscaled
- nodes/project.py: gate half-res conditioning/sampling to single-pass
  mode (dual-pass, SelfLift, passthrough, audio-only unchanged)
- moxie_combine.py: restore editor resolution right before the images
  output; VIDEO preview output passthrough unchanged
- scripts/test_rtx_upscale_integration.py: standalone sanity checks
  (no ComfyUI/torch needed) for the dimension policy and gating
2026-09-27 00:27:37 +00:00
Z User
fc040c1645 feat: translate all cache/task console logs to English
MultiTrack and H3 conditioning cache logging printed Chinese labels
(ProjectMedia/SegmentMedia statuses, timing and cache-size breakdowns).
Translate every console-facing string to English so the ComfyUI log is
fully English-readable:

- cache status values are now 'cache-hit' / 'first-load' (was Chinese),
  including the _all_media_caches_hit sentinel comparison and the
  _easy_media_cache_status data written into tracks_info
- cache size breakdown now reads 'file(...)=conditioning(...)+...'
  with English category labels
- timing/stage messages, video-track compositing and locked-audio
  extraction messages, and llama.cpp install errors are English
- fullwidth '|' in the media_loading timing line replaced with ASCII
- test assertions updated to the new English strings

No behavioral changes beyond the log/status wording; the Chinese
prompt-reference syntax (@图片N etc.) and LLM prompt templates are
intentionally untouched as they are functional.
2026-09-26 23:27:09 +00:00
Z User
27041a8a9f feat: scrub EasyMedia/MiniMax branding from all user-facing output
Console, errors, tooltips, descriptions and display names no longer
reveal the pack heritage or the underlying model family:

- [EasyMedia]/[Easy Media] console prefixes -> [Moxie] (11 files)
- New console privacy filter (utils/log.py, installed at pack import):
  rewrites MiniMax variants in every displayed logging record, including
  ComfyUI core lines like 'Model MiniMaxH3 prepared for dynamic VRAM
  loading', %-args and matching tracebacks. api.minimaxi.com is protected
  so cloud-API errors stay accurate.
- Node display names rebranded (node_ids untouched, workflows safe):
  'MiniMax H3 To Video' -> 'Moxie To Video', etc.
- ~40 error/tooltip/description strings reworded to Moxie terms.
- CLIP error no longer names CLIPType.MINIMAX; test match updated.

Unchanged on purpose (breaking if touched): node_ids/class names,
combo value 'MiniMax' (workflow payloads), internal dict keys
(minimax_keyframes/minimax_refs), llm_api cloud provider strings,
class-name logic checks, source-only docstrings.
2026-09-26 23:05:24 +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