OpenImagingLab / OpenImagingLab/FlashVSR
New comfy node for FlashVSR (supports int8, mitigates OOM)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
I attempted to implement the LCSA logic as faithfully as possible, and also worked on compatibility with ComfyUI Dynamic VRAM and dedicated int8 convrot format.
This allows me to upscale to 1080p reliably on an RTX 4050 6GB VRAM 16GB RAM laptop where otherwise would OOM with other nodes.
This also supports Sparge Attention and the modified comfy kitchen library in https://github.com/Zironic/H3-Optimizations
I do notice that on fine details there seems to be seed dependent temporal inconsistencies. For example, an edge which is clear on the LQ video will have poor stability on the upscaled video, an issue that doesn't really appear when upscaling single images. Not sure if this is impact of the data I'm testing it on (low res MiniMax H3 clips using Turbo LoRAs) or something else; testing with online FlashVSR providers seems to result in similar issues.
My repo is here https://github.com/Pizzawookiee/ComfyUI-FlashVSR-Stock
My int8 convrot checkpoint is on Hugging Face: https://huggingface.co/pizzawookiee/FlashVSR-1.1/tree/main
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the external ComfyUI-FlashVSR-Stock repository and the linked Hugging Face checkpoint to understand the existing node and int8 format. Clarify whether the goal is upstream integration, and define the target files, tests, compatibility requirements, and acceptance criteria before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, computer-vision
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100