Full pipeline + real timings: Midjourney keyframes to Runway to Topaz to Resolve

by @sakuraschulzlab828 in c/behind-the-scenes · · Pipeline

People keep asking how long a 60-second piece actually takes, so here's the stopwatch truth for my last one:

Midjourney keyframes (~18 shots, 4 variations each): 2.5 hrs including the ones I threw away.
Runway Gen image-to-video, ~3 rolls per shot to get a keeper: 4 hrs of wall-clock (mostly waiting in queue).
Topaz upscale + denoise, batch overnight: 'free' time but 6 hrs of machine churn.
DaVinci edit + grade + sound: 9 hrs across two evenings.

So roughly 16 hours of my attention for 60 seconds. The 'AI is instant' crowd has never done step 4. The edit is still an edit.

917 points · 6 comments

Comments

  • @jordankimcreative · · 100 points

    Step 4 is where the actual film lives and it's the step nobody wants to learn. You can't prompt your way out of a bad edit.

  • @sashanguyen_studio · · 95 points

    The number of gorgeous clips ruined by zero sense of rhythm or cut timing is staggering. Learn to edit before you learn to prompt, genuinely.

  • @felixsantos · · 44 points

    Curious why Midjourney keyframes into Runway instead of just Runway text-to-video? The keyframe step seems like a lot of added time.

  • @jordancosta_ai · · 61 points

    Control. T2V gives me whatever it wants. Starting from a locked MJ frame means I already approved the composition before I spend video credits. Cheaper in the long run.

  • @anastasiacosta_vfx250 · · 95 points

    16 hours for 60 seconds is still faster than literally any traditional VFX pipeline for the same shots, for the record. People forget the baseline.

  • @lucasalmeidaworks493 · · 87 points

    Right? A single CG character shot used to be weeks. The complaint should be 'it's not instant', not 'it's slow'.