Maxed-Out-99
7fb6cec7ea
Add video handling and prep utilities across nodes and UI. - mediacomparers.py: add MxdVideoComparer (saves previews, shows A/B videos) and import folder_paths/os/time; register the new node and display name. - wan22nodes.py: refactor WAN 2.2 scaling with _wan22_pick_bucket and _wan22_scale_image_core, add _select_frames_start_end, expose faster passthrough for scale(), add video prep nodes (WAN22_I2V_Video_Prep_MXD and advanced variant) that scale videos and return start/end/selected frames, improve CombineVideos_MXD audio handling to support multiple audio payload shapes and batching, and mark PreviewVideoMXD as an output node; register new nodes and display names. - Add new node file wan_svi_first_last_mxd.py: WAN 2.2 First/Last I2V SVI node that prepares SVI conditioning (anchors, padding, masks) and returns latent samples. - __init__.py: include wan_svi_first_last_mxd in dynamic imports so new node is discovered. - web/js/image_comparer.js: extend UI to support video/media (playback, sizing, URL builder, mixed image/video lists) and update widget rendering logic for media types. - pyproject.toml: bump package version to 1.8.1. These changes add end-to-end video support (preview, compare, prep for WAN 2.2 workflows), improve robustness of audio concatenation, and introduce an SVI-first/last conditioning node for WAN pipelines.
ComfyUI-MaxedOut
Custom ComfyUI nodes used in Maxed Out workflows (SDXL, Flux, Wan 2.2, etc.).
Included Nodes
- Core MaxedOut nodes from
maxedoutnodes.py - Media comparer nodes from
mediacomparers.py - WAN 2.2 nodes from
wan22nodes.py Lora Loader MXD(merged fromComfyUI-LoraLoader-MXD)
Lora Loader MXD Merge
Lora Loader MXD is now integrated directly into this repository.
Compatibility and behavior retained:
- Node type remains
Lora Loader MXD - API namespace remains
/loraloader-mxd/api/... - Sidecar metadata compatibility remains
*.rgthree-info.json - Frontend extension name remains
mxd.PowerLoraLoader
Migration Notes
- Existing
ComfyUI-LoraLoader-MXDinstalls are supported by a one-release compatibility shim. - During transition, keep both repos installed if needed; the standalone shim defers to this merged provider to avoid duplicate registration.
- After the transition release window, the standalone repo can be removed.