AI film creators report large labor demands despite low generation costs

• Javi López’s 17-minute Nemoris pilot reportedly required six months, more than 7,000 generations, 12 hours of generated footage, and about $20,000 in tokens, according to MayorKingAI’s report on the pilot.
• A separate Odyssey production breakdown counted 3,627 images and 3,043 videos over nine days, while PJaccetturo’s thread said the studio usually has 10 people working full-time.
• A 10-day Nexus film was budgeted at $29,575 in PJaccetturo’s budget post, with later replies separating animation spend from crew, editorial, writing, producing, and look-development work.
• The working unit is an editable shot, not a finished generation: PJaccetturo’s workflow thread starts edits while generations are still arriving, while MayorKingAI’s reply describes cutting together the strongest moments from failed longer clips.
• Production scale is not uniform. An r/aivideo creator described a solo 30-minute sci-fi film at 1,321 generations and 14,802 credits in an r/aivideo post.

A production breakdown for the Odyssey pilot lists 3,627 images, 3,043 videos, and a $2,677 generation bill. Magnific’s video-node documentation describes a workspace where creators generate, combine, and upscale clips across more than 40 models. The work between those operations is storyboarding, asset selection, direction, and editorial.

The reported tally for López’s Nemoris pilot turns a finished 17 minutes into a useful production ledger.

• Final runtime: 17 minutes
• Production time: six months
• Generations: 7,000+
• Generated material: 12 hours of video
• Selection rate: roughly 60 generations for every 15 seconds used
• Token cost: about $20,000, excluding the creator’s time
• Tool stack: Seedance 2.0 and 2.5 for video, Nano Banana Pro and Seedream 5 for image references, routed through Magnific

Magnific’s official documentation says its Spaces workflow can generate clips from text and visual references, combine them into sequences, and enhance them afterward. López’s reported stack used that multi-model layer for the footage and reference work.

The Odyssey figures split generation spend from the people shaping the output. PJaccetturo’s Odyssey thread calls Grok Imagine fast and affordable, then says the studio usually has 10 full-time staff.

The separate tally puts the nine-day pilot at 3,627 images, 3,043 videos, and $2,677 in generations. Its workflow starts from a canvas organized by scene, then moves into daily assembly while individual shots are still being regenerated.

PJaccetturo put a separate Nexus film at $29,575 and 10 days in his budget post. The follow-up cost details locate much of that expense in people rather than model calls.

• Animation spend: $2,000 to $3,000, according to PJaccetturo’s cost reply.
• Crew: four to five animators at roughly $1,000 per day over 10 days, in another PJaccetturo reply.
• Uncounted in that external estimate: full-time internal writing, producing, look development, and other work, also specified in his breakdown.
• Look development: five full-time animators worked over the core 10 days after the team had developed the script and reference images, per PJaccetturo’s production reply.

The credited team listed a director, writers, image and animation artists, and an editor in the project thread. The generation interface sits inside a conventional production division of labor.

PJaccetturo’s Odyssey workflow thread lays out five operational moves:

• Reference exploration: make varied stills before video, changing one character, prop, location, or style variable at a time.
• Scene organization: use titled columns such as Scene 1A, 1B, and 1C, with the relevant character and location references beside each scene header.
• Short prompts: 30 to 60 words, structured around one subject, one action, and one named camera move.
• Resolution gates: explore at 480p or 720p, then pay for 1080p after the prompt is working.
• Daily edits: assemble the sequence while prompting and regenerate scenes against the emerging cut.

The reference-heavy method is one production pattern, rather than a universal requirement. Artedeingenio said a Wan 3 challenge entry was made entirely text-to-video from one detailed prompt, with no reference images.

GlennHasABeard described a different control layer: deliberately simple Blender previs. A detailed blockout can be preserved by Seedance, he wrote in his blockout note, so he uses smooth gray blobs for characters and maps each blob to a named image reference in the prompt.

The same maker said in a reply about last frames he abandoned end-frame prompting after repeated unwanted zooms, and now writes multicuts that finish within the generated sequence. MayorKingAI separately reported in a reply on long generations that 15-to-30-second clips fail more often, making selective cutting part of the workflow.

Carolletta’s sponsored Firefly demonstration separates post into four passes: silent video, effects, voice, then music. Her paid-partnership post calls the result commercially safe audio made inside Firefly, and it points readers to Adobe Firefly. Adobe’s generative-credit documentation describes credits as the currency for Firefly-powered generative features across its apps.

New platforms are also wrapping production with release. pzf_ai’s Dreamware announcement describes Dreamware as a creation, streaming, and funding platform for AI film, built around a short made in Dreamware Studio. Kling_ai profiled Diane Shorthouse, a filmmaker with 30 years in traditional film and TV, as she explores emotional AI-character performances through MINIBOTS with Kling AI in Kling_ai’s profile.