Cross-mode - Cast Registry

Cast a character once.
Use them everywhere.

The Cast Registry is your project's memory for people: character names, descriptions, assigned voices per language, and trained voice clones. Build it in one mode, and the others already know your cast.

The ideaWhat it remembers

Each REAPER project carries one registry. For every character it stores:

The registry lives in a small JSON file in reasonate_projects/ next to your .rpp, so it travels with the project when you move or archive it.

In practiceHow modes feed and use it

Dubbing fills it automatically

Casting voices in a dubbing project writes characters, descriptions (from the glossary) and voices to the registry as you work. Nothing to manage by hand.

Repair names the speakers

When you name detected speakers in Repair or train a clone for one, the registry learns it. Select the same material tomorrow and the names are back; other items of the same recording inherit the labels too.

TTS pulls the cast in

In the dialogue sub-mode, Cast from project loads registry characters as your speaker lineup - voices, names and descriptions included (descriptions show as tooltips on the speaker chips).

Dubbing matches back

Start dubbing material whose characters the registry already knows, and a Match cast (N) button proposes voices for them. You review the suggestions in a modal - each row shows current vs registry voice, and only what you check gets applied.

Repair suggests the right voice

Editing words spoken by a character whose registry voice differs from what Repair would use? A hint appears: "Selected words are spoken by X" with a one-click Use X's voice.

New dub languages inherit

Add a new target language to a dubbing project and the cast is copied over from a configured language quietly, with a status note. You only adjust where the new language needs a different voice.

Good habitsGetting the most out of it