Skip to content

Fix Low VRAM Audio VAE loader returning an unusable model - #562

Open
Henry Kroll III (themanyone) wants to merge 2 commits into
Lightricks:masterfrom
themanyone:lowvram_pr
Open

Henry Kroll III (themanyone) wants to merge 2 commits into
Lightricks:masterfrom
themanyone:lowvram_pr

Conversation

@themanyone

Copy link
Copy Markdown

When running ComfyUI with --lowvram after update low_vram_loaders.py fails with
TypeError: AudioVAE.__init__() takes 2 positional arguments but 3 were given
err.txt

The fix

The node instantiated the internal AudioVAE module directly with the state dict, which raised a TypeError (the constructor only accepts metadata) and, even when given metadata alone, produced a bare model with no weights instead of a VAE. Loading now goes through the public VAE wrapper like the core audio VAE loader, so the node returns a working VAE that downstream audio encode/decode nodes can use.

💘 Generated with Crush

Assisted-by: Crush:deepseek-v4-flash

Tested by: themanyone with heavy LTX 3.5 ia2v workflow in ComfyUI --lowvram

[INFO] Prompt executed in 588.98 seconds

CPU: 8-core AMD Ryzen 9 5900HX with Radeon Graphics (-MT MCP-)
speed/min/max: 1100/423/4683 MHz Kernel: 7.2.5-100.fc43.x86_64 x86_64
Up: 12h 24m Mem: 9.21/31.23 GiB (29.5%) Storage: 1.84 TiB (48.7% used)
Procs: 474 Shell: Bash inxi: 3.3.41
Graphics:
Device-1: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] driver: nvidia
v: 615.71.09

The node instantiated the internal AudioVAE module directly with the
state dict, which raised a TypeError (the constructor only accepts
metadata) and, even when given metadata alone, produced a bare model
with no weights instead of a VAE. Loading now goes through the public
VAE wrapper like the core audio VAE loader, so the node returns a
working VAE that downstream audio encode/decode nodes can use.

💘 Generated with Crush

Assisted-by: Crush:deepseek-v4-flash
@themanyone

Henry Kroll III (themanyone) commented Sep 19, 2026 •

Copy link
Copy Markdown
Author

There was another err2.txt which started happening after an update a while back.

Working around it by inserting LTXVVAE Force Float32 node upstream of the LTXV Audio VAE Encode. Will post more information if I can figure out what's causing it.

Cheers!

Bring in tiled fusion sampler and workflow updates from upstream,
resolving any overlapping changes in favor of upstream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant