OpenImagingLab / OpenImagingLab/FlashVSR
Unexpected artifacts on REDS video with official FlashVSR inference
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thanks for releasing FlashVSR.
I’m observing noticeable visual artifacts when running the official infer_flashvsr_v1.1_tiny_long_video.py script on a REDS video with bicubic degradation. The input resolution is 320×180, and the output resolution is 1280×640. I attached a few example frames below.
I also observe artifacts with infer_flashvsr_v1.1_full.py, but the attached screenshots here are from the tiny long video script.
Is this expected behavior, or could something be wrong in the inference setup?
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 reproducing the reported artifacts with infer_flashvsr_v1.1_tiny_long_video.py on the REDS video using bicubic degradation, then compare with infer_flashvsr_v1.1_full.py. Check whether the 320×180 input and 1280×640 output reproduce the attached behavior; the issue is done when the cause or expected behavior is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100