dub'up

Français · English · Deutsch · Español · Italiano · Português

Make a scene for Dub'Up

The Dub'Up catalogue is opening up to creators. You make a scene, you submit it, we watch it; if it is selected, it joins the game with your name on it. This page says what a Dub'Up scene is, what gets one selected, how to make it step by step, and how to submit it.

  1. How it works
  2. Before you start
  3. What a Dub'Up scene is
  4. The five rules that decide
  5. The method, step by step
  6. What you submit
  7. Submitting
  8. With Claude Code: our skills
  9. What happens next

How it works

Dub'Up is a dubbing game: you pick a scene, everyone records their voice over one character, and the app puts the video together. The game is worth what its scenes are worth — and until now, they all came out of our own workshop. They are generated: characters and sets with an image generator, the video with a video generator that produces picture and voice together. That method is what we are handing over here.

What we are offering:

This page exists in every language of the app — English, French, German, Spanish, Italian and Portuguese (links at the top). It is written first in French: dubup.app/createurs. The skills further down are in French — they are our workshop's own working notes.

Before you start

What a Dub'Up scene is

A short generated film that players will dub, one character each. What we expect, in numbers:

ElementExpected
Length15 to 45 seconds. Forty-five is a ceiling, not a target. One generation runs 30 s at most: beyond that, it is two generations joined (see step 4).
Format16:9, 1280 × 720, 30 frames per second. Not vertical, not 1080p, not 4K: the game is played on a phone, held sideways.
Characters2 or 3 speaking characters (6 at most). Every part gets at least two lines and 6 seconds of speech; a part with a single line is not a part.
Lines2 to 4.5 seconds each, at a natural pace (two words per second in English). At least 40 % of the scene is speech.
VoicesThe characters speak English, at ordinary volume (see rule 5). We strip those voices before serving the scene; players never hear them.
SoundThe scene's sound effects — doors, footsteps, a glass set down — come from the generation, and they are welcome: plenty of sound, never under a line (rule 4).
EndingA silent tail of 1 to 3 seconds after the last line: the look, the reaction, the last sound. A scene that cuts on the final syllable looks truncated.
SituationA situation built to be hijacked: a turn, an incongruous object, one word too many. What the player invents on top matters more than what you wrote.

Our workshop uses GPT Image 2 for the stills and Seedance 2.5 (in Higgsfield's web interface) for the video. You may use other tools, as long as the result respects everything above — in particular lips that really articulate the lines, which only generators that produce picture and voice together know how to do.

The five rules that decide

They come from failed scenes. Any one of them, on its own, is enough to get a video declined.

1. Human behaviour. A Dub'Up scene looks like a realistic film scene, played by people — not by stage actors. No overacting, no mugging, no gesture larger than life, no face that flushes all at once. The generator amplifies everything you write it: write one notch below what you want to see.
2. Quality over length. When a length conflicts with a natural pace, a necessary silence or a believable gesture, the length gives way: fewer lines, shorter lines, a shorter scene. A take where the characters speak at double speed to fit the shot is a take to redo, never one to keep.
3. By 0:02, something has already happened. Most viewers leave at two seconds. Shot 1 opens on what is wrong, not on the situation: the gesture that goes off the rails is already under way in frame 1, and before two seconds a line has started or a clear sound has landed. No establishing shot at the top — the place reads afterwards, in the background. The test: freeze frame at 1 second, someone who knows neither the game nor the scene has to see what is odd.
4. Absolute silence under the lines, sound between them. We strip the voices with source separation, and a separator wrecks anything that shares the instants of the voice: a sound under a line comes back chewed, and the background with it — beyond repair. So under every line, nothing but a continuous bed, and no visible noisy gesture (setting an object down, slamming a door). Those gestures and sounds go in the silences between the lines, where they are very welcome.
5. English voices, and lips that move. Generate the video with audio, dialogue written in English in double quotes. It is the generated voice that moves the lips; a silent scene has frozen mouths and cannot be played. English keeps the game open: the French player does not copy, they invent. A scene in French would be declined — it would hand over the answer.

The method, step by step

1. The idea, then the breakdown — before any prompt

A scene fits in one sentence: “a birthday toast that goes off the rails”, “a police check where it is the officer who is scared”. Then lay out a table, in seconds, shot by shot:

Shotfrom → toWhat we seeWho speaksUsable silence
10 → 4wide, the knife tings on the glass at 0.2 s, the toast going wrongTom (from 0.8 s)0.8 s at the top
24 → 8close-up, she puts her fork downAnna1.5 s at the end
…
N27 → 30nobody speaks, reaction held to black—3 s

Check on this table, before spending a single credit: by 0:02 something has happened; silences long enough to carry the sound; a silent tail at the end; no noisy gesture under a line; every line between 2 and 4.5 s, and how many words it can hold — 5 words in 2 s, 7 in 3 s, 9 in 4 s, 12 in 5 s.

2. Sheets: one per character, one per place, generated once

Never count on a generator to hold a face from one shot to the next. Produce frozen sheets, which the video then takes as references:

3. The multi-shot prompt

The whole scene in one generation — never shot by shot, you would lose the continuity. The structure that works:

[Visual profile: light, contrast, focal length, grain — the same words for every shot.]

CHARACTERS: @image_1 is Tom, <visual markers>. @image_2 is Anna, <visual markers>.
  No exaggerated, theatrical or cartoonish expressions, no wide-eyed stares,
  no raised or knitted eyebrows. All expressions change gradually and
  continuously, never between one frame and the next.
SET: @image_3 is the dining room, wide view. @image_4 is the same room, reverse angle.
  The whole scene plays in this room; its geometry never changes.
ACTING: naturalistic, understated performance, as in a French realist family
  drama; the actors underplay; gestures small and economical; the voice does
  most of the work at ordinary conversational volume.
SOUND: real domestic sound, recorded in the room, at its natural loudness: no
  cinematic sound design, no added impact, no reverb. Every line is spoken at a
  slow, natural, unhurried pace, about two words per second, with real breaths;
  lines are short on purpose and must never be sped up to fit the shot.

Shot 1 (0-4 s) — wide, static. From the first frame Tom is already tapping his
  knife on a glass; three small tings at 0.2 s. From about 0.8 to 3.5 s Tom says
  "I signed my sister up for 'Roommate From Hell'." No noisy gesture during the line.
Shot 2 (4-8 s) — close on Anna. She sets her fork down at 4.3 s. From about 5 to
  7.5 s she says "You did what." No noisy gesture during the line.
…
Shot N (27-30 s) — nobody speaks, nobody makes a sound. Held reaction to black.

Spoken in English, slowly and naturally, never sped up.

4. Generating

  1. Upload the sheets in the order of the prompt: characters, then places, then any key frames.
  2. Set: the length from your table (30 s at most per generation), ratio 16:9, resolution 720p. The audio is generated with the picture — that is what we want.
  3. Run a short test first — 4 to 6 seconds, at 480p — on the one shot you are unsure about (a line, a gesture). A 30 s take is expensive, and a short test tells you straight away whether the register is right.
  4. Generate, download the mp4. Keep it as it is: that is the video with the voices, the one you will submit.

There is no seed: regenerating gives you another take, not a variant. Hence the importance of settling the breakdown and the prompt first.

Beyond 30 seconds — up to 45 — the scene is made in two generations, joined end to end. With no seed, the second take always drifts a little (faces, light); the cut only holds if it is justified by the story: a lamp going out, a door opening onto another room, a hard change of framing. Generate a key frame of that exact instant, approve the first take before launching the second, and give the second that key frame as its starting point, with the same sheets — removing any reference that contradicts the starting state (the lamp still lit). Submit both files as they are, in order: we do the joining.

5. Checking what came back

To checkIf it is wrong
Freeze frame at 1 s: the oddity or the turn is visible; by 2 s a line has started or a clear sound has landedrewrite shot 1 and regenerate — this cannot be fixed in the edit
The lips move and articulate on every lineregenerate: unplayable without it
Nobody speaks at double speed; the lines breatheshorten the lines, regenerate
Total silence under every line, no visible noisy gestureregenerate that shot; do not shift the line to compensate
The set has not moved between two shotsadd the missing location angle as a reference, regenerate
The final tail is still and silentregenerate, or accept that we trim the end
The voices really are in Englishregenerate
No overacting, no rubber faceswrite one notch below, regenerate

6. The scene sheet

A plain text that comes with the video. It lets us find who speaks when, and write the French version players will read:

Title: The Toast
Synopsis (280 characters at most): At the birthday dinner, Tom raises his glass
  and tells his sister he has signed her up for a reality show.
Characters:
  - Tom, man — the brother, thirties, creased shirt
  - Anna, woman — the sister, calm, never lets go of her fork
Lines (in order, with the approximate window):
  1. Tom, 0.8 → 3.5 s — "I signed my sister up for 'Roommate From Hell'."
     French adaptation: « J'ai inscrit ma sœur à Colocataire de l'enfer. »
     Intent: light, like good news
  2. Anna, 5 → 7.5 s — "You did what."
     French adaptation: « Tu as fait quoi. »
     Intent: without moving, the voice alone
  …
Length: 29 s. Last line finished at 26.5 s.

If you do not speak French, leave the adaptation out — write the English lines and their intent, and we will do the French.

What you submit

File
The video with the English voices (mp4, 16:9, 720p)Required. It is what we review, and what we measure the speech windows on. Do not strip the voices yourself, do not re-edit, do not re-compress. A scene in two generations: both files, in order, not an edit.
The scene sheet (text)Required. Title, synopsis, characters with their gender, English lines with their intent (and their French adaptation if you can).
The character and location sheets (images)Recommended. We use them to make each character's avatar and to judge consistency — and, if we like the scene, to prepare a follow-up in the same universe with you.
A poster (16:9, 1536 × 864)Optional: the scene's image in the catalogue. Otherwise we take a frame from the film.

No music. Each scene's music is composed on our side and mixed in the edit: do not put music in the video — it would get in the way of separating the voices. We also take care of stripping the voices, measuring the lines, encoding to the catalogue profile and setting the mix. If you already master all that (a voiceless clip, a scene manifest), send it as well, never instead of the video with the voices.

Submitting

  1. In the app — on a phone or in the browser, dubup.app/jouer, where your files are — open the Account tab: create an account if you do not have one, and verify your email address.
  2. In the Creator card, tap Submit a scene: the title, the sheet, the video (the second generation is added next to it), the images if you have them.
  3. Tick “this scene is my own creation and I allow Dub'Up to show it”, then Submit. Files go one at a time; a 45 s video takes a few dozen seconds.

The submission then appears under My submissions, with its state — pending, selected, declined — and the review note. You can withdraw it while it is pending. Any question: [email protected].

With Claude Code: our skills

Everything above is the summary of our workshop's method. The full method — with the traps met scene after scene — is written as skills for Claude Code: instruction files the assistant reads so it can write the image prompts and the video prompt for you, go over your breakdown, and draft the sheet. If you work with Claude Code, take them. They are written in French; Claude reads them in French and will answer you in your own language.

dubup-image.mdThe GPT Image 2 prompts: character sheets, location sheets, key frames, avatars, poster, and the filing convention. dubup-video.mdThe Seedance 2.5 multi-shot prompt: the rules, the breakdown, generating, checking, the scene sheet. dubup-battle.mdThe short Dub Battle variant: 12 to 18 s, one part to dub, the other actors keep their voices. manifest-checklist.mdFor those who deliver a scene manifest: the fields people get wrong.

Installing: in your project folder, create .claude/skills/dubup-image/SKILL.md, .claude/skills/dubup-video/SKILL.md and .claude/skills/dubup-battle/SKILL.md from these files (renamed SKILL.md), and .claude/skills/dubup-video/references/manifest-checklist.md for the checklist. Then, in Claude Code: “Prepare a Dub'Up scene: a birthday toast that goes off the rails, three characters” — the assistant will walk you through the steps above, in order.

These skills are written for our workshop: some steps (stripping the voices, measuring the lines, encoding, the catalogue) talk about our tools and our folders. They are not your problem — you submit the video with the voices, and we do the rest. What is yours is everything before the generation, and the checking after.

What happens next

‹ Back to the home page · Cette page en français · Privacy policy (in French)