Make 500 NPC voice lines in one weekend.
A production kit in four parts for small teams. These teams use less dialogue than they want, because each new line has a cost. Vois Studio generates audio on your computer. Thus, when you change a quest, you generate the audio again, and you do not pay a new invoice.
Click the link in the first Vois email. Then we send the download link, three short follow-up emails, and Studio Notes two times each week. One click stops all of these emails.

Four files for one pipeline that you can examine.
These files are short versions of the game dialogue procedures that we publish. They are in the sequence that you use them.

Pipeline checklist
The steps in sequence are: a draft of the scene as data records, an inspection of the IDs, approval of the voices, generation, and export. It also gives the inspection points that prevent a voice change that you do not see after you change the name of a character.

Line-batch spreadsheet template
One row for each line: stable line ID, character ID, intent, spoken text, locale, scene version, and inspection status. Only the rows with the status "approved" go into the generation queue.

CLI batch procedure
The prompts for a batch that a person controls through the Vois CLI. The steps are: examine the voices before you start, make the project, generate in groups, and export. The export uses file names that do not change. It does not use the dialogue text for file names.

Localization worksheet
This is the data that a translator must have for each line. It includes the speaker, the listener, the scene, the intent, the time limit, and a pronunciation note. It also tells if you can use the line again. The worksheet also has a short voice selection guide for each locale.
Most small teams release games with text boxes that have no voice.
The cost comes from the number of lines
An RPG with voices for all characters can have hundreds of NPC lines, barks, and quest dialogue. Voice selection, direction, and new recordings for all these lines cost much. Usually, this cost is the cause when a small team keeps the characters with no voice.
Changes must be free
Game scripts change. Writers change quests, cut dialogue, and add content. When you generate audio on your computer, no price for each character controls which changes you make.
A large number of lines must have a procedure
Generation at a low cost helps only if the 50th change gives the same result as the first change. Stable character IDs, an examined voice manifest, and file names that do not change let you follow each line in a script that becomes larger.
For content production, not for the game when it operates
The CLI controls the Vois Studio desktop app on your computer. Thus, it is a part of your content production, together with your other content tools. Your pipeline makes audio files and a manifest. The released game uses that manifest to find the audio for each dialogue line. It does not make a file name from the spoken text. Exports are WAV at 24kHz mono, and you can put them directly into Unity, Unreal Engine, and Godot.
Select voices from the library of 100+ voices in 21 categories. Examples are Heroes, Villains, Companions, NPCs, Creatures, Machines, and Narrators. If the library does not have the correct voice for a character, clone a voice. Use a clear sample of 10 to 15 seconds and a written permission record. You can also use Vois Studio for a title that is not public at this time and has an NDA. The script stays on your computer during voice generation.
This is the kit.
A ZIP file with a four-page guide, the line batch CSV template, the localization worksheet, and the CLI batch procedure.


Questions from indie teams
Get the kit.
It is free, with no conditions. Start with one quest scene, not the full game. Then use that scene as the standard for the remaining scenes.
Click the link in the first Vois email. Then we send the download link, three short follow-up emails, and Studio Notes two times each week. One click stops all of these emails.