Fix stale path references in comments after the restructure

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Maxed-Out-99
2026-07-10 06:47:04 -07:00
co-authored by Claude Fable 5
parent 59ea942a80
commit 7306278ccd
6 changed files with 8 additions and 8 deletions
+1 -1
View File
@@ -10,7 +10,7 @@ The taeltx model is auto-discovered in the vae / vae_approx model folders. If
it isn't found, it is downloaded to the configured vae model folder.
Sends MXD_live_preview_start / MXD_live_preview_frame / MXD_live_preview_saved
websocket events consumed by web/live_preview_panel_mxd.js. Final clips are
websocket events consumed by web/nodes/live_preview_panel.js. Final clips are
saved to <output>/live_previews.
TAE decode path borrowed from kjnodes / VideoHelperSuite.
+2 -2
View File
@@ -11,11 +11,11 @@ JSON, base64-encoded JPEG frames) -- deliberately NOT the `VHS_latentpreview` /
default single-image preview both also listen on. Sharing that channel turned
out to be unreliable: whichever of us/VHS/core happened to register its
listener first could swallow the event before the others saw it, so the
frontend panel (web/live_preview_panel_mxd.js) would sometimes just never
frontend panel (web/nodes/live_preview_panel.js) would sometimes just never
render. A fully private channel has no such collision risk.
Enabled per-run via the `MXD_latentpreview` flag in the workflow's
extra_pnginfo, set by web/video_preview_mxd.js.
extra_pnginfo, set by web/nodes/video_preview.js.
Also patches `latent_preview.prepare_callback` to save the final frame batch
of any run with this preview enabled to
+1 -1
View File
@@ -4,7 +4,7 @@ import { app } from "../../../scripts/app.js";
// way reference/conditioning-image nodes reveal a new empty slot once the
// current last one is plugged in. Backend declares foreground_1 (required)
// plus foreground_2..foreground_6 (optional) as individual IMAGE sockets (see
// MAX_FOREGROUNDS in combine_materials_ffgo_mxd.py) so arbitrarily-sized RGBA
// MAX_FOREGROUNDS in nodes/ffgo.py) so arbitrarily-sized RGBA
// cutouts never have to be batched into one uniform IMAGE tensor.
//
// MAX_FOREGROUNDS must stay in sync with the Python-side constant — it's a
+1 -1
View File
@@ -11,7 +11,7 @@ import { api } from "../../../scripts/api.js";
// freely draggable (grab the header) and resizable (grab any edge/corner),
// with both position/size and collapsed state remembered across reloads.
//
// Backend (video_preview_mxd.py / ltxnodes.py) streams frames over its own
// Backend (system/live_preview.py / nodes/ltx/preview.py) streams frames over its own
// private MXD_live_preview_start / MXD_live_preview_frame websocket events
// (plain JSON, base64 JPEG -- not the shared VHS_latentpreview/b_preview
// channel, which turned out to be an unreliable place to listen: whichever
+1 -1
View File
@@ -4,7 +4,7 @@ import { app } from "../../../scripts/app.js";
// alternative to MAXEDOUT_MODEL_STORAGE / model_storage_config.json for
// people who'd rather not touch a config file. Purely a convenience UI --
// the actual registration happens at import time in
// model_paths_autoregister_mxd.py, which reads this setting back out of
// system/model_paths.py, which reads this setting back out of
// user/default/comfy.settings.json, so a change here only takes effect
// after restarting the ComfyUI server.
app.registerExtension({
+2 -2
View File
@@ -1,12 +1,12 @@
import { app } from "../../../scripts/app.js";
// Adds a global "preview any sampler as it renders" toggle, backed by
// video_preview_mxd.py's general get_previewer hook. Writes its own
// system/live_preview.py's general get_previewer hook. Writes its own
// MXD_latentpreview / MXD_latentpreviewrate workflow-extra keys, deliberately
// separate from VHS's own VHS_latentpreview/VHS_latentpreviewrate keys, so
// this toggle and VideoHelperSuite's identically-named setting don't fight
// over the same flag -- each hook only wraps the previewer when ITS OWN flag
// is on. The actual rendering (web/live_preview_panel_mxd.js) is a global
// is on. The actual rendering (web/nodes/live_preview_panel.js) is a global
// floating panel, not a per-node widget, so it isn't affected by which
// workflow tab is open.
app.registerExtension({