Before you start
- Selected recipe: LTX-2 video with generated audio, provider version 0.1.6, at the selected recipe revision.
- Failure location: The reported failing node and error, sufficient to distinguish video VAE decoding at node 109 from loading, sampling, audio decoding, or video output.
Start with the failing video decoder
Try to recover a video decode that runs out of memory by reducing the spatial tile size at the existing VAEDecodeTiled node 109. Start with LTX-2 video with generated audio, version 0.1.6, and the reported failing node. The recipe already uses tiled decoding; this intervention makes its tiles smaller.
The intended deliverable is Sweet Tea Preview Video, exposed as output:75. A successful retry must both reach that output and produce imagery you can use. The retained sources establish the control and its stage of action, but provide no measured memory savings or guarantee that the retry will complete.
Where does the out-of-memory failure occur?
- VAEDecodeTiled node 109: The published smaller_decode_tiles adaptation applies to this video decode stage.Continue
- Loading or sampling: Changing node 109's tile_size leaves model loading and denoising memory unaffected. Diagnose the reported loader or sampler separately.Continue
- Audio decode, video output, or unclear location: Locate the reported failing node first. Node 144 is a separate audio decoder; node 109's spatial tile setting does not control it.Continue
What the saved decoder controls mean
Node 109 receives samples from LTXVSeparateAVLatent node 110, slot 0, and vae from CheckpointLoaderSimple node 116, slot 2. It produces decoded IMAGE frames at slot 0. Those frames enter images on CreateVideo node 108, which also receives the separately decoded audio from node 144. Node 108's video then enters video on SweetTeaPreviewVideo node 75.
The saved spatial controls are tile_size = 512 and overlap = 64. tile_size determines the spatial tile dimensions requested for decoding; overlap determines the overlap between tiles. The implementation converts tile dimensions using the VAE compression factors and calls decode_tiled. Smaller tiles change the spatial work handled by each tile, which is the mechanism behind the existing memory-reduction adaptation. They can also change seams and decode work; the sources establish no numerical memory or speed prediction.
The implementation reduces overlap to one quarter of tile size when tile_size is less than four times overlap. At the proposed tile_size = 256 with overlap = 64, the values are exactly at that boundary, so this guard does not reduce overlap.
The saved video controls are temporal_size = 4096 and temporal_overlap = 8: the node schema describes these as frames decoded at a time and frames of temporal overlap for video VAEs. The published adaptation changes only the spatial tile_size; it does not establish a temporal tuning recommendation.
Apply the published smaller-tile adaptation
The existing tiled_decode rule, revision 2026-10-09.1, is bound to node 109 as tiled_decode:109. The recipe's published smaller_decode_tiles adaptation, revision 2026-10-09.1, uses binding decode_tiles:109 and applies when failure.stage is decode. Use that existing annotation for this selected revision.
Node 109 is marked hidden by default within the Text to Video (LTX 2.0) subgraph, scope root:92. Locate its internal controls if your editor exposes them; the source pack does not establish the exact UI navigation. For this retry, retain the saved overlap and temporal settings and the rest of the recipe configuration so the spatial tile change can be assessed on its own. Completion and output quality remain uncertain until the retry.
- Set tile_size on VAEDecodeTiled node 109 from its saved value of 512 to 256.
Look for: The existing decoder requests smaller spatial tiles. This is an attempted decode-memory remedy, not a guaranteed successful run.
- Retry the recipe. If it completes, inspect Sweet Tea Preview Video at output:75: pause on frames to look for visible tile boundaries or discontinuities, then play the video to judge whether those artifacts affect the result. If it fails, record the reported failing node before choosing another remedy.
Look for: A decision based on whether decoding completed and whether the resulting video has acceptable seams, or a localized failure for further diagnosis.
Outputs: output:75
- Smaller decode tiles: tile_size 256
- Applies the published spatial decode adaptation at node 109. Tiled decoding remains in use; seams and decode work may change. Loading and denoising memory are unaffected.
Keep the result or diagnose the remaining failure
Keep the smaller setting if the retry completes and the imagery is acceptable. Completion demonstrates that this particular run reached the output; it does not establish a memory reduction measurement or a capacity recommendation.
The retained preparation evidence has no measured profiles, scoped GPU or RAM recommendation, or comparable timing. It also leaves dependency preparation incomplete. Neither the guide title nor the published adaptation establishes total-machine fit. These instructions are scoped to the selected recipe revision and the retained ComfyUI implementation.
- Restore saved tile_size 512
- Returns node 109 to its saved spatial tile size for a comparison or rollback. The original decode-memory failure may recur.
Decoding completes, but visible seams make the video unusable.
Smaller spatial tiles can change seams in the decoded imagery.
Check: The retry reaches output:75, but frame inspection reveals tile boundaries or discontinuities.
Restore tile_size to the saved 512 for comparison if that setting can complete. Keep overlap at 64 for this comparison. If 512 still runs out of memory, this guide establishes no setting that guarantees both completion and acceptable seams.
Node 109 still runs out of memory with tile_size 256.
The adaptation changes spatial tiled decoding only and does not guarantee sufficient memory for the decode.
Check: The new error still identifies VAEDecodeTiled node 109 after the tile_size change.
Confirm the retry used tile_size 256 and retain the failing-node details with the workload settings. Further tuning requires evidence beyond the published adaptation; the retained sources provide no guaranteed next tile or temporal setting.
The error identifies a loader, sampler, audio decoder, or video output node.
Node 109's tile_size controls video-frame VAE decoding. It leaves loading and denoising memory unaffected and does not control the separate audio decoder or video output stage.
Check: The reported failure is outside node 109: for example, CheckpointLoaderSimple node 116, SamplerCustomAdvanced nodes 124 or 111, LTXVAudioVAEDecode node 144, or SweetTeaPreviewVideo node 75.
Diagnose the reported stage using its actual error. For missing-model errors, address recipe dependency availability first. Do not use the spatial decode adaptation as evidence that those stages or the whole recipe fit the machine.
Recipes and setup
What you need
- Model files
- 25.2 GiB known subtotal
Remaining hardware or download-size estimates are not available yet.
Where this approach stops
- Numerical memory savings or decode-time predictions
- Model-loading or denoising memory remedies
- Guaranteed GPU or system RAM fit
- Compatibility claims for other LTX recipes or VAE implementations
