Comfy-Org / Comfy-Org/ComfyUI

Getting stuck on Vae ENcode rendering LTX V2V workflow on both local and ComfyUI Cloud. (used to render same WF jsut fine several days ago)

Open
#12,970 4 comments 0 reactions 1 assignee Claimed by @rattus128 View on GitHub
Potential Bug
Dominant language
Python
Stars
133k
Forks
15.7k
Avg merge
1d 7h
Merged PRs (30d)
158

Description

### Custom Node Testing

- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

Normal rendering

### Actual Behavior

Getting stuck on Vae ENcode rendering LTX V2V workflow on both local and ComfyUI Cloud. (used to render same WF just fine several days ago). Loweing frames count to below 73 and its working but setting biger -0 it stuck or even crashes. I have used this WF many times without an y problems but after updates it does not work anymore.

### Steps to Reproduce

Image

### Debug Logs

```powershell
got prompt
Found quantization metadata version 1
Detected mixed precision quantization
Using mixed precision operations
model weight dtype torch.bfloat16, manual cast: torch.bfloat16
model_type FLUX
VAE load device: cuda:0, offload device: cpu, dtype: torch.bfloat16
no CLIP/text encoder weights in checkpoint, the text encoder model will not be loaded.
Requested to load VideoVAE
0 models unloaded.
Model VideoVAE prepared for dynamic VRAM loading. 2331MB Staged. 0 patches attached.
Warning: Ran out of memory when regular VAE encoding, retrying with tiled VAE encoding.
```

### Other

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.