Cloud LTXV Conditioning

LTX-2 cares about frame rate the way a film director cares about the camera speed - it's baked into the conditioning, not just metadata on the output. Cloud LTXV Conditioning is the node that sets it, contributing an LTXVConditioning step to the cloud workflow JSON that stamps frame_rate onto your positive and negative conditioning.

If you've ever run an LTX video locally, you know the drill: the text-encoded positive/negative come in, and a conditioning node attaches the video-specific parameters before sampling. This is the cloud version of that middle step. It's one of those nodes you add because the workflow template has it, set the frame rate to match the rest of your graph, and never touch again.

Inputs

• positive and negative - CLOUD_CONDITIONING handles from a Cloud CLIP Text Encode (in an LTX-2 chain, that's fed by the Cloud LTXAV Text Encoder Loader).
• frame_rate - a FLOAT, default 25, range 0–1000. This is the knob that matters. Match it to the frame rate you set on your empty video latent - 25 is the standard default, but if your latent was built at 24 or 30, set this to the same number. Mismatches are how you get clips that play at the wrong speed or drift.

Outputs: a new positive and negative pair of CLOUD_CONDITIONING handles for the sampler.

Installation

Part of the ComfyUI-CloudAPI-worker pack:

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. Manager-installable as "ComfyUI-CloudAPI-worker"; deps: requests, Pillow, safetensors.

Gotchas

• Keep the frame rate consistent across the whole chain - conditioning, empty video latent, and the audio latent all carry their own frame-rate settings, and they all need to agree.
• This node doesn't run anything by itself. It builds JSON for the terminal node to submit; if nothing downstream is wired to a terminal sampler, you'll see nothing happen.
• Proof-of-concept pack (the author posted it on r/comfyui in 2026 as a "very basic proof of concept"). The LTX-2 path is validated mostly against the included example workflow, so when the graph gets weird, that's your reference.