OpenImagingLab / OpenImagingLab/FlashVSR
OOM for high-fps video
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
For the video of 9s, 1160*1548, using flashvsr 1.1 full on A100, for fps 30 and fps60, it works, but for fps larger than 60, it always outputs OOM. Why it can not be regarded as long video when using higher fps? And what's the reason for it and how to solve it?
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
No file, test, or entry point is named. Start by reproducing the reported 9-second, 1160×1548 video on an A100 with FlashVSR 1.1 at 30, 60, and above 60 fps, then inspect the memory behavior and document a confirmed cause, workaround, or required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100