Define characters and scripts before recording
Voice mismatches, misplaced emotion and inconsistent names often call for better character briefs and recording references. Assign unique line IDs, confirm the script version and supply relationships, story context, emotion and pronunciation notes. Flag lip-sync and duration constraints before the session.
| Scope | What we check | Reference |
|---|---|---|
| Script and pronunciation | Missing words, misreads, wrong takes, names and version consistency | Approved script, line IDs, pronunciation guide |
| Character and performance | Vocal fit, emotion, emphasis and dialogue continuity | Character brief, story context, direction notes |
| Video sync & timing | Time windows, key action cues and agreed lip-sync requirements | Reference video, timecodes, recording brief |
| Audio and delivery | Truncated files, noise, loudness, format, naming and missing files | Audio specifications, manifest, version records |
| In-game playback | Missing, repeated or incorrect lines, wrong triggers and interruptions | Testable build, scene paths, line IDs |
Review content, performance and technical quality
Check missing words, misreads and wrong takes against the approved script, then review voice, emotion, emphasis and dialogue continuity. File checks cover complete beginnings and endings, noise, loudness, format, naming and missing assets. Use video references for timing and action cues, with lip sync checked to the agreed requirements.
Find the issue, fix it, and check again.
Route language, production and playback issues to the right team and track them through verification.
Agree on the review criteria
Confirm script versions, character requirements, audio specifications and game scenes in scope.
Make each issue easy to find and reproduce
Record line IDs, filenames, timestamps, and the problem. Include reproduction steps for issues that occur in the game.
Arrange the appropriate fix
Coordinate script clarification, pickups, editing or in-game configuration fixes, with version control.
Verify fixes and affected content
Recheck findings, pickup continuity, file completeness and game scenes that need regression testing.
Reproduce playback issues in the game
A complete recording can still be cut short in the game. Wrong lines, missing playback, incorrect triggers and interruptions during dialogue skipping need a build and reproduction path. Record line IDs, filenames, scene references and time positions, then revisit affected scenes after fixes.