PJ Ace says Blender references cut Seedance generation costs roughly in half

• Generation spending fell roughly in half, but the Nexus crew still spends at least $1,000 daily, according to the producer's follow-up.
• Claude operated Blender to establish shot blocking and scale, as the production walkthrough demonstrates.
• Seedance received storyboard stills instead of Blender video; the team credited that switch with more natural cuts and camera work in its raw-output post.

On Nexus, executive producer PJ Ace estimates Claude did about 80% of the Blender work. His Seedance prompt specifies 26 storyboard keyframes, eight hard cuts and handheld movement between panels.

Theo Dudley, credited with Nexus's direction, images and animation, had already made detailed airship and creature reference sheets. Those assets left too much staging open to interpretation: Ace said Seedance chose the wrong cameras, misplaced the action and changed ship sizes between shots, triggering repeated generations.

The crew had Claude run Blender to stage the film. Ace also said subsequent adjustments happened through Claude.

The infographic accompanying his earlier Blender guide described an obstacle-course demo with seven stages:

1. Stadium: A reference image became a simple greybox environment.
2. Course: Obstacles followed a specified sequence: stepping stones → buzzsaw → monkey bars → rope over fire → tower → victory button.
3. Runner: A chess pawn served as the moving stand-in.
4. Notes: Playback prompted corrections such as “the saw should barely miss him,” with saves after every change.
5. Cameras: A multicamera setup kept every camera on one side of the action.
6. Export: A fast Workbench render produced 24fps previz.
7. Generation: The video went in as @vid1, appearance references as @img1 and @img2. The video model was told to use the previz only for camera and timing.

That earlier recipe used a rendered reference video. The Nexus breakdown introduced a different handoff.

The crew found its Blender camera movement stiff, even after adding camera shake, Ace explained in a reply. They made a smart handoff: Claude captured the Blender sequences as storyboard stills, which the team attached to rewritten Seedance prompts in Dreamina.

The boards separated staging from appearance. Their footer instructed Seedance to follow each panel's composition, placement, camera angle, screen direction and action, while taking “every look” from the reference images.

For the shared sky-whale sequence, the team uploaded the storyboard images without a Blender video. The accompanying Dreamina prompt divided the work into explicit constraints:

• Panel order: Follow panels 1 through 26 in sequence, treating each as a keyframe.
• Composition: Match camera position, framing, screen direction and action.
• Movement: Use handheld motion between panels.
• Editing: Make eight hard cuts, cutting only when the storyboard's shot number changes.
• Appearance: Treat the grey previz as stand-ins; derive the finished look from the separate references and text.

Continuity instructions also kept the calf tethered at frame left, the mother above the cloud layer and the ship moving prow-first. Vosk's ceramic mask had to remain still.

The crew had been spending $2,000 a day on generations for weeks, Ace said in his opening post. His later estimate put the reduction at about half, with daily credit spending still at least $1,000.

Tweaking clips continued to cost about $10 per clip, he said in another reply.

Ace also reported that image references were cheaper than uploading reference videos in their workflow. Separately, Dreamina's October 21 pricing page lists Seedance 2.5 at 37 credits per generated second at 720p, with or without a reference, and notes that input settings and additional features can affect charges.

Lighting continuity followed a three-part chain, Ace explained in a production reply:

1. The background plate established the lighting.
2. Dudley took screenshots in two directions to distinguish front lighting from backlighting.
3. Blender reinforced that light direction across shots.

Film grain and the color grade were added in post-production.

Anthropic's Blender connector tutorial documents the local connection through Blender's Python API. It supports Claude Desktop, including Free plans; the browser version does not support this connector.

The setup has three parts:

1. Claude Desktop: Add Blender through Customize > Connectors.
2. Blender: Install the Blender MCP add-on.
3. Connection: Start the MCP server from the BlenderMCP add-on inside Blender.

Ace linked the Nexus 3D Workflow guide, but the screenshot-method update was promised for Friday. At the time of the thread, the team's Claude Blender skill was still being packaged.

Blender's MCP server documentation warns that model-generated code executes without safeguards against deleting data or sending it elsewhere.