Legal shot planner
Split 15 or 30 seconds into contiguous 5–15 second provider jobs.
H3 as a shot engine, not the whole application
MiniMax H3 Video inside a Metered Music-Video Workflow
Plan legal H3 shots, freeze the approved creative context, reserve credits per shot, persist provider tasks, and review private outputs before final composition.
5–15 second shots · visual references · immutable quote · private R2 output
MiniMaxMusic Studio is an independent third-party service and is not the official MiniMax website.
MUSIC-TO-MV PROJECTPRIVATE
01
Choose a generated song or upload an authorized MP3/WAV.
02
Select a 15- or 30-second highlight, output ratio, and visual direction.
03
Generate and edit a versioned storyboard before any H3 job is submitted.
04
Attach validated reference images and approve an immutable server quote.
05
Render each H3 shot independently, review it privately, and rerender only what needs work.
06
Compose a final H.264/AAC MP4 with the original song as the only master audio.
The hard part is orchestration around the model
A production H3 integration must account for duration and reference constraints, asynchronous task state, private input URLs, provider output persistence, duplicate-submission risk, technical-failure refunds, per-shot rerenders, and eventual final media composition.
MiniMaxMusic Studio separates those responsibilities. The H3 provider validates requests and queries tasks; the product layer owns project authorization, immutable quotes, credit reservations, attempts, reconciliation, output validation, private storage, review, locking, and export.
H3 production controls
Reference validation
Use owner-checked private images after object and magic-byte validation.
Per-shot ledger
Reserve, settle, release, rerender, and audit credits at Attempt level.
Private result persistence
Validate provider MP4 results and copy them into owner-scoped R2 paths.
Approve, quote, render, reconcile, review
No browser action can choose provider task ids, output keys, costs, or settlement values.
- 01Choose a generated song or upload an authorized MP3/WAV.
- 02Select a 15- or 30-second highlight, output ratio, and visual direction.
- 03Generate and edit a versioned storyboard before any H3 job is submitted.
- 04Attach validated reference images and approve an immutable server quote.
- 05Render each H3 shot independently, review it privately, and rerender only what needs work.
- 06Compose a final H.264/AAC MP4 with the original song as the only master audio.
H3 visual directions
Cinematic narrative
Build an emotional progression with motivated camera movement.
Anime illustration
Use character and style references for a coherent illustrated world.
Abstract motion
Drive material and scale changes from musical energy.
Animated cover
Preserve a cover composition while adding controlled atmosphere.
MiniMax H3 workflow FAQ
01Does H3 generate the complete final MV file?+
H3 generates independent visual shots. A separate compositor joins those shots and remuxes the original song into the finished MP4.
02What happens before H3 rendering starts?+
You select a music range, generate a versioned storyboard, edit every shot, apply validated visual references, approve the storyboard, and request a server-side quote. No H3 job starts merely because a song was uploaded.
03How are final videos assembled?+
Successful private H3 shots are normalized and concatenated by a dedicated FFmpeg compositor. H3 audio is ignored; the selected portion of the original song becomes the only master soundtrack.
04Which formats are available first?+
The first production formats are a 15-second teaser and a 30-second social clip in 16:9, 9:16, or 1:1. The project architecture is designed to support longer formats later without treating them as one opaque generation.