Cloud LTXV Separate AV Latent

Everything LTX-2 samples comes back as one joint audio-video latent, and you can't decode that with a single VAE. The video half needs the image VAE, the audio half needs the audio VAE, and before either can run you have to pull the blob apart. Cloud LTXV Separate AV Latent is that split, contributing an LTXVSeparateAVLatent step to the cloud workflow JSON.

It's the mirror image of Cloud LTXV Concat AV Latent, and the two of them frame the whole AV sampling chain: concat before the sampler, separate after it. You'll hit this node the moment your LTX-2 cloud workflow gets past "does it generate at all" and into "wait, where's the sound?" - the answer is in here, waiting to be split out.

Inputs

One input: av_latent, a CLOUD_LATENT - the joint AV latent straight out of your sampler.

Outputs are the two halves:

• video_latent - feed this into Cloud VAE Decode (or the LTX decode path) for the frames.
• audio_latent - feed this into Cloud LTXV Audio VAE Decode, then Cloud Fetch Audio, to get actual sound.

Installation

Same pack as everything else here:

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

Copy config.json.example to config.json, paste an API key from https://platform.comfy.org/profile/api-keys, restart. ComfyUI Manager has it under "ComfyUI-CloudAPI-worker"; deps are just requests, Pillow, safetensors.

Gotchas

• The return trip is mandatory. Skip Separate and feed the joint latent straight to a video VAE decode and you'll get garbage - the tensors are interleaved, not stacked cleanly. Local LTX-2 templates always pair Separate after sampling; do the same here.
• Both outputs are still CLOUD_LATENT handles, i.e. workflow JSON references, not tensors. They only become pixels/audio after they pass through a terminal bridge that actually runs the cloud job and fetches the result.
• It's the newest part of an already small proof-of-concept pack (posted on r/comfyui in 2026), so if the AV chain behaves oddly, compare against the example_LTX_workflow.json in the repo - that's the graph the author actually tested.