One sentence becomes a 30-second cinematic reel with characters, story, music, and voice-over ā end-to-end on a single AMD Instinct MI300X. 8 stages, sequential: Qwen3.5-35B Director plans 6 shots, FLUX.2 paints character keyframes (no LoRA training), Wan2.2 animates, vision critic auto-retries bad clips, ACE-Step adds music, Kokoro narrates in 9 languages, ffmpeg mixes. Every model Apache 2.0 / MIT. Outputs commercially usable. Single MI300X end-to-end thanks to 192GB HBM3.
No reviews yetBe the first to leave a review for StudioMI300
Maker
š
Hey Product Hunt š
Built StudioMI300 solo for the AMD x lablab hackathon (May 2026). Motivation was simple: Sora and Runway produce beautiful clips but leave you with zero leverage - closed weights, vendor cloud, your output under their ToS.
I wanted to know: can the open-source stack (FLUX.2, Wan2.2, ACE-Step, Kokoro) be stitched into an autonomous end-to-end pipeline that produces a complete cinematic artifact from one prompt?
Turns out yes - if you have a single AMD MI300X with 192GB HBM3, which lets four very different architectures share one card sequentially.
What's different vs other AI video tools:
š¬ End-to-end autonomous - single sentence, no manual scene/shot writing
š¤ Director Agent emits inspectable JSON plan (edit shots, re-render selectively)
š Vision Critic auto-retries bad clips with 10-label failure taxonomy
šµ Music + 9-language narration in the same pipeline
šØ Character identity via FLUX.2 reference editing (no LoRA training step)
š¦ 100% Apache 2.0 / MIT - outputs commercially usable
Built in 7 days. Every line of optimization (FBCache 2Ć + torch.compile 1.2Ć) and every incident (AITER FP8 segfault, MagCache calibration miss) is documented publicly.
Try the live demo on HF Space (link above) or fork the code on GitHub: https://github.com/bladedevoff/s...
Would love feedback, especially from anyone who's tried to compose open-weights video stacks before. Happy to dig into architecture choices, optimization details, or the vision critic's failure taxonomy in comments.