High failure rate in T2AV generation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- audio-video-rtc, machine-learning
Research direction
Start in pipeline_mova.py, focusing on the prepare_latents stage where the pure white PIL.Image is loaded, encoded, and concatenated for standard T2V generation. Reproduce the MOVA T2V/T2AV flow and compare successful videos with the corrupted solid-color outputs. Done means the generation process no longer produces the reported latent-collapse failures at the stated rate.
Written by the indexing model from the issue text.
Description
Describe
When using the MOVA pipeline for pure T2V/T2AV generation, I am experiencing a highly unstable generation process. Approximately 40% of the generated videos result in corrupted, solid-color outputs (the entire video is just a flat color with no coherent structures or details).
Following the standard T2V approach for MOVA, I am passing a pure white PIL.Image as the image condition to the pipeline. I strongly suspect the issue lies in how the pipeline_mova.py loads, encodes, or concatenates this pure white frame in the prepare_latents stage, leading to a latent collapse during the diffusion process.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from OpenMOSS/MOVA
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
resource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hesreallyhim/awesome-claude-code#3214 · 1 comment ·
Maintainers usually reply within 1 day
-
room-commons replace accepts an empty old string and silently prepends the new text to the pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
doobidoo/mcp-memory-service#1650 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ml-explore/mlx-lm#2002 ·
Maintainers usually reply within 2 days