Dubbed Audio Resources

Note on Terminology 

At GEM, the terms “dubbing script” and “as-recorded dubbing script” mean the same thing. GEM only collects the as-recorded dubbing script version. Where you see “dubbing script” in any instructions, it always refers to the as-recorded dubbing script. 

What is the As-Recorded Dubbing Script (ARS)? 

The ARS is a transcription of audio and Forced Narratives (FN) in the target language of the secondary audio. 

It includes all audio and text elements needed for GEM viewers watching the dubbed version in the target language to follow the story. The ARS is a live asset, continuously updated and utilized for each secondary audio version. Delivery must always be in the TTAL format. 

Further FN requirements: 

  • See the GEM Forced Narratives Guidelines and Style Guide for Dubbing Review the GEM Forced Narratives Linguist Guide as needed 

Requirements 

  • Formatting: All dubbing scripts must be delivered in TTAL format. 
  • Timing: All events must match the dubbed video; event durations must correspond with the respective audio.

 

  • Event Coding: Each event’s in and out timecodes must align with the first and last spoken word. 
  • Pauses: For any pause in dialogue of approximately two seconds or more (including reactions/efforts), start a new event when the dialogue resumes. 
  • Voice-over and Polish Lector: Time events to the dubbed dialogue, using the Dialogue List as a reference. 
  • Transcription: Scripts must precisely match the final audio. Omit foreign language dialogue that is not meant to be understood by the audience. 
  • Spelling/Punctuation: Write all text in sentence case with proper punctuation, and avoid ALL CAPS. Typographical errors are allowed only if intentional and reflected in the audio. 
  • Acceptable Symbols: Only slashes (/, $$, circumflex (^), less-than/greater-than (<, >), and pipe (|). 
  • KNP Names: Always spell names correctly per KNP; enclose phonetic spellings in parentheses or brackets as needed. 

Titles and Tags 

  • Episode Titles: Translate according to GEM guidelines, ensuring you check approved terminology first. If there’s no approved translation, or for lip-sync needs, freely translate after viewing the episode. Flag retranslation needs to be made to the GEM representative. 
  • Main Titles: Do NOT translate freely. Only use the approved MT translation in Terminology. 
  • All relevant events involving these titles must be properly tagged in the ARS.

 

  • On-Screen Text Tags: 
  • Use when the episode title appears on screen. 
  • Use when any instance of the episode title shows up in dialogue (full title only; not partial matches). 
  • For non-English titles, ensure the English episode title also appears in corresponding PLDL events. 

Forced Narratives (FN) 

  • Tag FN events accurately and identify their on-screen positions. 
  • All FN translations should follow the GEM FN style guide as well as the respective target language FN style guide. 
  • Only include FN events that are essential or identified in project-specific instructions. 

Content Quality and Structure 

  • Redundancy: Remove empty, redundant, or unnecessary events. Each dialogue row must have text or be deleted. 
  • Reactions/Efforts: Use (), [], or {} for all included reactions/efforts. Don’t start or end events with pure reactions/efforts—base timing on spoken dialogue. 
  • Attribution: Attribute each event to one character; use NONE for on-screen text. When recreating indistinct crowd noise, use WALLA and append identifiers (e.g., WALLA – Audience). 
  • Unison Dialogue/Chanting: Duplicate events and attribute each to the relevant character(s).

 

Submission, Validation, and Updates 

  • Delivery: Submit via GEM Backlot or the GEM Script Authoring Tool in TTAL format. 
  • Timeline: Deliver the ARS three calendar days before the secondary audio. 
  • Validation: Dubbing scripts are automatically checked for format, timing, and conformity. Use the TTAL Validator for pre-checks. Correct and re-upload any files flagged for errors. 
  • Updates: Any redeliveries or corrections must always be made via the GEM Script Authoring Tool, regardless of initial creation method. 

By following these GEM standards, all dubbing operations will support premium audio localization and clear storytelling in every GEM release.