Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.

Every dubbing script task in Netflix’s Authoring tool involves an authoring pass, and one or more conformance passes. Each pass includes a translation and a proofreading step.

The below diagram shows the flow of the passes and steps as they are represented in Content Localization Portal (CLP).

 

dub_script_workflow.png

 

The Current Step and Status columns in the Dub Script tab in Content Localization Portal (CLP) indicate where the task is in the flow. The Type column shows if you’re currently working on the Pre-recorded Dubbing Script (Dub Script) or the As Recorded Dubbing Script.

Even if your translation was created elsewhere and you only want to use the Authoring tool for finishing touches or conversion to ttal, the entry point into the workflow in the Authoring tool is always the Translation Author step, as shown above.

 

Flow

  • Assignment - After the dubbing script task is created, the Current Step will be to assign the task to a translator. During this step, the status of the task will be:
    • Waiting for proxy - In this state, the task is waiting for the locked proxy and the corresponding dialogue list to be available.
    • Ready - This state indicates the task is available for translation. The proxy and the corresponding dialogue list are available for the translator. However, the task can’t start until at least one translator is assigned. The sooner a translator is assigned, the sooner the task can begin once it’s ready.
  • Translation Author - Once the assignment of the task to a translator is done, the next step is the translation (Translation Author). During this step, the task could still be Waiting for proxy, indicating that the dialogue list and locked proxy are not yet available, or it could be Ready, indicating that the translator can start working on the task. When the translator clicks “START” in the Authoring tool the task becomes editable and the status will change to
    • In Progress - to indicate the translator is working on the task.
  • Translation Proofread - When the translator finishes the work and clicks “COMPLETE,” the task will no longer be available to the translator. It will automatically move to the Translation Proofread step, and the status will be:
    • Ready - Indicates the proofer can start work right away.
    • In Progress - Indicates that proofreading is underway. The proofreader can edit the authored script and make any corrections. Proofing is always done using the same proxy used in the Translation Author step. When the proofreader clicks “COMPLETE,” the script is automatically delivered to Backlot, and the task moves to its next step.
  • Translation Conform Author -This is the conform pass, where one of the assigned translators implements the changes from the locked proxy to the final media in the dubbing script.  The changes can involve dialogue addition or removal and events timecode offsets. During this step, the status of the task can be:
    • Waiting for proxy - The final media and the updated dialogue list are still pending.
    • Ready - Final media and updated dialogue list with a change log are available. The translator responsible for implementing the dialogue and timing changes can start implementing them in the dubbing script.
  • Translation Conform Proofread - Once the translator responsible for the conform pass clicks “COMPLETE,” the dubbing script opens to the proofreader. The translator that handled the conformance will no longer have access to the task. The status of the task could be:
    • Ready - indicating the proofer can start the work right away.
    • In Progress - Proofreading is underway. The proofreader should ensure no mistakes were introduced during the conformance pass. When the proofreader clicks “COMPLETE,” the script is automatically delivered to Backlot.
  • Complete - The conformed was delivered to Backlot, and the task is over. No more steps are needed.

The flow described above assumes the work starts from the locked proxy (the most common scenario) and that only one locked proxy is used. Any intermediate locked proxies are disregarded.

 

Note: Certain projects may start the workflow using the final proxy, in which case the conformance steps are unnecessary.
Conversely, the Dubbing team may manually request the conformance of the dialogue list (or PLDL) to another locked cut, indicating that more than one conformance pass will be required.

 

When the status of the Dub Script task is In Progress and being worked on by a translator (Translation Author step) when Dubbing requests manual conformance to another locked cut, a pop-up notification in the Authoring tool will indicate to the translator that a new proxy is available. They can upgrade to the latest proxy by clicking on the Upgrade button or finish their work using the current proxy.

unnamed__6_.png

If the task is In Progress in the proofread step, it will not be upgraded to the new proxy. Proofreading is always done to the same proxy used in the authoring step. When the proofreader completes the work, the task will revert to authoring, and the conformance pass to the new proxy can start.

 

Preparing the As Recorded Dubbing Script

After the pre-recorded dubbing script conformed to final media is delivered to Backlot, the task will revert to the Ready status and Current Step to Translation Conform Author signaling that the task is available for the assigned collaborator to start implementing changes to the script as soon as the recording completes, as indicated in the diagram above.

The flow of the task follows the same steps described above and consists of one extra conform Authoring and Proofing pass.

Note that the Type column will change from Dub Script to As Recorded Dub Script to clearly indicate which source request is being fulfilled in Backlot.

 

Script_type.png

 

Revert to Authoring

Revert to authoring takes the task back from the proofreading step to the authoring step. This option is only available while the task is in proofing.
When would you need to revert to authoring?
When the translator accidentally clicks on “COMPLETE” before the task is done. Revert to authoring will re-open the task for the translators.
Select the task that is in the proofreading step (Translation Proofread or Translation Conform Proofread). It will open a contextual menu at the bottom of the screen. Click on More Options and then on Revert to Authoring. Click on SUBMIT in the window that opens to confirm.

unnamed__7_.png

 

Assigning tasks

Dub Script tasks are assigned to translators and QCers (proofers) in the Content Localization Portal (CLP).
Go to the Dub Script tab in the project you want to assign the task.
Clicking the check box next to “Title” selects all available tasks for assignment. You can also assign each task individually.

 

Note that the Current Step will say Assignment when a translator hasn’t yet been assigned to the tasks.

unnamed__8_.png
Once the task is selected, a contextual menu will appear at the bottom of the screen. Select Edit Assignment to attach a translator and proofer to the task.
The assignment panel will appear on the right side of the screen.
Select one of the translators from the dropdown menu as the Main Translator to assign the task to them. Repeat this process for the Translation Proofer field.

unnamed__9_.png

Additional translators can be added to the task by clicking on the button Add More, which will be enabled once the Main Translator is selected.

At this moment, only one proofer can be added per task.

Once the assignments are done, click Save. It will close the assignment pane, and Current Step will change to Translation Author. The translator will be able to work on the task as soon as its Status is Ready.

 

Assignment Notes

  • Translators and Proofers need to have been previously onboarded in Starship before their names appear in the dropdowns.
  • You can replace the Main Translator while the task Status is Waiting for proxy or Ready. The moment the Main Translator starts the task they can’t be replaced. Other translators can still be added during the translation steps (Translation Author, Translation Conform Author).
  • To change the main translator after the task starts, you need to stop the task using the Stop button next to the Main Translator field in the assignment window and start it over.
  • You must assign at least one translator and one proofer. Translation and proofreading are mandatory steps in the flow and the task will not move forward if no one is assigned to do it.
  • The person in the Main Translator field needs to start the task to make it available to the other collaborators. Other translators assigned to the task won’t have access to it in the Authoring tool until then.
  • The person assigned in the Main Translator field should be someone that will oversee the task throughout the entire workflow, such as a project manager. If a translator isn’t involved past the first step (Translation Author), this person should be assigned as one of the additional translators.

 

Authoring

The task doesn’t start until the START button is clicked to allow edits to be made.

During authoring, the translation is inputted into the tool by typing into each event or uploading csv files. 

When the translator is satisfied with the translation, they should click COMPLETE. You’ll see the task move to the next step in the flow in CLP.

 

Proofreading

The task doesn’t start until the START button is clicked to allow edits to be made.

Proofing is a required step that must be completed before the file can be delivered to Backlot. When the proofer clicks COMPLETE the file is delivered to Backlot and the task moves to the next step in CLP. 

The workflow will reach its final step and be considered complete after the proofing pass on the As Recorded Dub Scrip, shown in the Type column in CLP, is complete.

 

Conformance

Besides changes in the dialogue, the conformance pass may involve timecode changes in the script due to the addition or removal of footage. A  scene may have been added or removed, often production logos are not included in the locked cut and are present in the final media, requiring an offset of the events in the script.

The Dialogue List (or PLDL) will be updated and re-timed to the final proxy and the changelog in the final DL will indicate what retiming is required. The change list is part of the DL/PLDL available for download in Backlot. 

Events offset

The re-timing of events in the Authoring tool is a two-step process.

First, you need to select the events you want to offset and then indicate the offset value.

Using the change list in the DL identify the events that require offset.

Click on the three dots menu and click on Select range.

 

Range_select.png

You can select the range of events using the event’s number or the timecodes.

 

Range_select2.png

Click select to apply.

Tip: If you want to select all events in the file, the keyboard shortcut shift +A selects all events without having to go to the Select range menu option.

Now that you have the events selected, Go back to the three dots menu and select Move Events, which will be enabled.

The window will open with the timecodes for the last event in the range. Delete it to enter the offset value you want.

 

Conform.png

 

There are two offset options available:

  • Offset By
      • It offsets each event in the range by the value entered. Note that you can enter positive values to offset the events forward in the timeline or negative values to move the events backward.
  • Offset To
    • Offsets the events to the timecode supplied. The first event in the range will be placed at this timecode and subsequent events will move relative to their position in relation to the first event.


Click apply and the events will offset accordingly.

Repeat this process for each range of events that require re-timing. The range could be one event, all of them, or any number of events.

 

 

Was this article helpful?
1 out of 1 found this helpful
Powered by Zendesk