modelscope
DiffSynth-Studio
Trains and runs image, video and audio diffusion models on your own GPU
- MiniMax H3
- LTX-2.5
- Wan-Animate-2
- +7

VideoJev is an open model family (Apache-2.0) that answers questions about video without generating text: it scores candidate time intervals for 'when did X happen' and scores options for multiple-choice QA. Two checkpoints (4B and 35B-A3B) are on Hugging Face. It is fresh research code, so you need a CUDA GPU, FlashAttention 2 and the Qwen base models, and QA only works in multiple-choice form.
Best for: Builders who need fast 'when did X happen' checks or quiz-style verification over long footage — for example reviewing generated drama clips — not open-ended chat about video.
Rewritten from the README. Check the repo for the latest steps.
cd VideoJevgit clone https://github.com/MCG-NJU/VideoJev.gitsource scripts/env.shpip install -r requirements.txtmodels/Qwen3.5-4B and models/Qwen3.6-35B-A3B, or point VIDEOJEV_BASE_4B / VIDEOJEV_BASE_35B at themmodel.prepare_for_inference()AutoModel.from_pretrained("ZhuYuhan/VideoJev-4B", trust_remote_code=True, dtype=torch.bfloat16, attn_implementation="flash_attention_2")model.predict_video(processor, video, questions, fps=2.0){"task": "grounding", "query": ...}{"task": "choice", "query": ..., "options": [...]}ZhuYuhan/VideoJev-35B-A3B for the larger MoE modelOther model tooling projects people compare with VideoJev.
modelscope
Trains and runs image, video and audio diffusion models on your own GPU
wide-trace
Self-hosted studio for 38 image and video models
deepbeepmeep
Desktop app that runs open video, image and audio models on your own PC
Wan-Video
Open video models for text, image, speech and character animation
Do you maintain VideoJev? Add this badge to your README so English speakers can find our write-up.
[](https://openmicrodrama.com/projects/mcg-nju-videojev)The badge links to this page. Want your description changed? Email support@openmicrodrama.com.
Reviewed Oct 15, 2026. Appeared on arXiv (2610.18615) on 2026-10-13 with no launch post; benchmark numbers are the authors' own. We write these descriptions ourselves. The repo's own docs are the final word.