Cloud LTXV Audio VAE Loader

In the LTX-2 AV world, audio isn't generated by a second model bolted on after the fact - it shares a latent space with the video, and the audio VAE is a separate thing you load explicitly. This node is the loader for that: Cloud LTXV Audio VAE Loader contributes an LTXVAudioVAELoader step to the cloud workflow JSON and returns a CLOUD_AUDIO_VAE handle.

The handle type matters more than you'd think. The pack's author made audio VAE a distinct type on purpose, and the source comment says why: it's treated as a separate handle so you can't wire it into nodes expecting a regular image VAE. CLOUD_AUDIO_VAE only plugs into the audio-latent nodes - Cloud LTXV Empty Latent Audio, Cloud LTXV Audio VAE Decode. That type-safety is a small kindness in a pack that's otherwise rough around the edges.

Inputs

Just one, and it's a plain STRING rather than a dropdown: ckpt_name, defaulting to stable-audio-open-1.0.safetensors. Same reasoning as the LTX text encoder loader - the cloud's audio VAE options list is huge, so the author accepts any string and lets the cloud validate it.

Output is a single Audio VAE handle of type CLOUD_AUDIO_VAE.

Installation

Standard for this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Dobidop/ComfyUI-CloudAPI-worker

Then copy config.json.example to config.json, drop in an API key from https://platform.comfy.org/profile/api-keys, restart. Manager-installable as "ComfyUI-CloudAPI-worker"; dependencies are requests, Pillow, safetensors - no weights to fetch, it all runs cloud-side.

Gotchas

• No dropdown means exact filenames: a stale or mistyped ckpt_name fails with a cloud-side API error. If you're unsure what the cloud has, run Cloud List Models with folder=vae (or check the example_LTX_workflow.json included in the repo) to see real filenames.
• The default filename is a reasonable guess, not a promise - the actual set of audio VAEs available on Comfy Cloud shifts, so treat the default as a starting point.
• Whole-pack reminder: proof of concept, small community project (the author shared it on r/comfyui in 2026). The audio path is the newest bit, so lean on the example workflow when the connections get confusing.