How do I budget GPU time for a short drama episode?
Budget from approved shots. A 30-second vertical episode might contain six five-second shots, but one close-up with dialogue can take more attempts than three establishing shots. Time a representative take for each shot type and count each retry.
Build a six-shot estimate
| Shot type | Planned shots | Takes per shot (example) | Render-time term |
|---|---|---|---|
| Establishing shot | 2 | 1 | 2 × measured wide-shot time |
| Character reaction | 2 | 2 | 4 × measured close-up time |
| Dialogue | 2 | 3 | 6 × measured dialogue-shot time |
These planning assumptions yield 12 renders for six accepted clips. Add model preparation once per rental, plus export and review time while the GPU is running. Apply the billing increment in each rental quote. Splitting the same workload over three separately billed rentals can change the total. Add separately priced storage if you retain the project. Current pricing
Which shot should I render first?
Choose the hardest cut: the same actor turning towards camera, speaking next to another character, or holding a recognizable product. Lock your reference frame and final aspect ratio. Check wardrobe, eyeline, lip timing and the first frame of the next shot. Mark each take accepted or rejected before extending the sequence.
For a dialogue pilot, the MiniMax H3 reference guide explains which inputs to prepare. The short drama production guide covers the remaining stages, including voice and edit.
What should I keep between rentals?
Keep the shot ID, exact graph and model versions, reference images, accepted take, exported clip and measured runtime together. Download or save the files you will need for revisions, open the saved copy, and release the instance. At wrap, divide settled GPU charges by the duration of footage that made the edit; log storage separately.
Download the six-shot example CSV to edit the timecodes, take counts and acceptance checks.