Handling LS to OM Migration Jobs

For non-Alula, publish using the Order ID for your client's typical Subtitle/Template Conformance Template.

IMPORTANT: For ALULA Titles...

1. Order Item Level:

Note: If this is an English file, ensure the Languages field is either "English (US)" or "English (UK)" as appropriate -- not just "English".

The Group field will automatically assume "Final". You must manually change that to match the exact Group to the file you're migrating from LS:

In the above example, the file we're migrating is the "Final" -- so, we write "Final".

2. Service Item - Additional Fields

For Conform Type, always pick "Simple Conform".

For Source Configuration, ensure your selection includes "External Source" and the configuration.

• Note: we do not yet have templates as options -- so, use the corresponding config -- e.g., pick "External Source - Full" if we're migrating a Temp-Full

Choose the Output Configuration that you're trying to create. So, if we're versioning up a Final Temp-Full to Final v2 Temp-Full, select "Full - Template".

3. Last -- for non-Alula ONLY -- go to the new Subtitle Job and open Task 2 (Ingest):

• Ensure the Remediation field says "None".
• Ensure the Task is "Workable".
• In Task Instructions, add the file path and the desired proxy asset version name -- remember, this Job will require the proxy that was used in LS ("Final", in our example).
• Assuming the above has been verified and completed, Data I/O will ingest the proxy as normal.
  • For Alula, this Task (LMR Ingest) should complete automatically -- if it doesn't, please send a support ticket

Note: If we are versioning up this subtitle in OM, Client Ops must Re-Run Job For New Proxy once Subtitling migration completes (outlined below in Migrate a Subtitle File/Template and Make OM Workable - Step 6)

Migrating a Script and Making OM Workable

Note: Everything beyond this point is NOT the responsibility of Client Ops -- however, it may be useful reference if English or Territory flag any issues.

If Client Ops followed the steps above (Publishing Scripting Jobs), we should now have two jobs in OM:

• The 'dummy' Job (representing the work that was already completed in LS).
• The Job for the script we are going to create in OM.

In the above example, we completed the "Lock v3" Dialogue List in LS. This is our 'dummy' Origination Job. We are intending to now create the "Final" Dialogue List in OM. That is the second Job - Revision.

English's Next Steps:

1. Download the DL archive from the latest Creative Letter PXM (includes the WCD version of the dialogue list). For ICS titles, also download the Language 1 DFXP from Ce5.

• Note: For ICS, if you can't find the Language 1 DFXP in the archive, you might need to reopen and export from LS.

2. Navigate to the equivalent version Job in OM (i.e., if the DL you are migrating is "Lock" or "P1", the Job you are migrating to must also be "Lock" or "P1") -- earlier in the article, this is referred to as the 'dummy' Job.

3. Open Task 3 (Ingest Conversion System Task):

• Note: this Task is un-skipped if the Job was correctly published as a "Dialogue List From External Source"

4. Under Input Requirements, find the "External Source" Asset Shell. Click Actions > Deliver > File. Select the Excel Full file. For ICS, ensure you use the "Language 2 Excel Full (English)".

5. This automation may take a few minutes. You can check if its status via Additional Details > Task Executions:

• If it fails, click Re-run Automation. Note -- this automation fails with certain file types -- notably, .doc files.

6. Once the Conversion completes, Task 4 will become workable. Assign yourself and double-check if you have download permissions. If not, immediately email Application Support with your supervisor on copy.

7. Navigate to the "Source" Asset Shell. It may read "AutoTranscription". Select Actions > Download:

8. Open CE.

9. Select Import. For ICS, ensure you import the Language 2 Excel Full (English) into the English Language track, and the Language 1 DFXP from Ce5 in the OV Transcription track.

• You'll receive a warning about adding new speakers. Select "Proceed with Selection".
• IF NOTHING HAPPENS, YOU MAY HAVE TO OPEN THE DFXP IN NOTEPAD AND FIND/REPLACE THE GENDER DENOMINATION “n/a” with “N/A” (just change to all caps).
  • Then, save and retry the import.

10. Open the Find & Replace tool. Search the Creator Notes field for "Exclude from DL". For events that show up in this search, add the "Exclude from DL" tag (shortcut: Ctrl+Alt+X). Do this for both OST and Dialogue tracks.

11. Submit.

12. Open Ce in the CQC1 Task, submit.

13. Open Ce in the Creative Reports Creation Task, submit.

14. Open Ce in the Creative Reports QC Task, submit.

• Note: We must submit these descendant Tasks to make the Job "Complete" -- otherwise, the next version Job will not become workable.
• Note: If you run into a "Job Failed" error when trying to submit on any Task, double-check that Track 1 is the dialogue track and Track 2 is the OST track. You can adjust this in Load Tracks if necessary, and click "Save". This should allow you to submit. If it does not, submit a Support ticket.

Migrating a Subtitle File/Template and Making OM Workable

Note: If we are intending to migrate a completed Subtitle Template from LS then version up in OM, Client Ops has a remaining step after publishing -- highlighted below in Step 6).

IMPORTANT: DO NOT directly import DFXPs into Ce6. Instead, follow the below steps.

First, we must find the completed file in Localization Scheduler...

1. Access the DFXP file:

• Find the relevant Job through Workflow Manager.
• Click the relevant Pixel Master ID.

• Download a DFXP from the “Latest Subtitle File Variants” list (be sure to not choose "Zero DFXP").

2. Import into Ce6: (REPLACE AND FIX THIS upload to Client Source shell in pixtt conversion task)

• Find the relevant Job in OM -- the video version will match the version from the completed LS file.
• Navigate to Task 3 (PXTT Conversion):

• Under Additional Details, find the "Client Source" Asset Shell. Click Actions > Deliver > File -- locate and select the DFXP:

• This automation may take a few minutes. You can check if its status via Additional Details > Task Executions:
• If it fails, click Re-run Automation. Note -- this automation fails with certain file types -- notably, .doc files.

• Once the Conversion completes, Task 5 (CQC1) will become workable. Assign yourself and double-check if you have download permissions. If not, email Application Support with your supervisor on copy.
• Open Ce. The Template will automatically pull into the Ce track.
• Check that the CE timecode and the burned in timecode match. See example of mismatch: 

• If there is a mismatch, flag this to a Lead editor to update for you. Be sure to provide them with an OM Job link (not CE link) and tell them what the correct timecode of the first frame of the proxy should be.)
• Check the file is in sync with the proxy, by doing a 4-point check of events 0%, 25%, 50% and 75% of the way through the file. There is a report to help us determine these points. Use Report > Configuration > Spot check.
• Double-check if Annotations have mistakenly been transferred to the Creator Notes field -- this is a bug that sometimes happens on import -- if so, follow these steps (otherwise, skip to 3A):

1. In Ce6, Export a PXTT.
2. In Notepad++:
   • Open the PXTT.
   • Find & Replace: Find "x-creator" and replace with "x-annotation".
   • Save the file.
     • Please note: all annotation brackets will also be preserved in the PXTT if they are not removed. If you need to remove them, Find + Replace them with nothing in Notepad ++ before importing into Ce6.
     • Where an event has multiple annotations, there won't be line breaks between them. You can only fix that once it has been imported back into Ce6 (step 4 below).
3. Back in Ce6, Asset > Restore snapshot.
4. Import the fixed PXTT into Ce6.
5. Note: The annotations should now appear unitalicised in the Ce. If needed, this can easily be fixed by following these steps:

3A. Prepare the file - Forced Narratives:

Note: Events tagged with #FN (and variant subtypes like #FN-MT) must be given the "Forced" tag in Ce6.

• Open up a “find” box. Event > Configuration > Find or Ctrl + F on your keyboard.
• Type #FN in the search bar, and make sure to update the “In” field from Event Text to Annotations.

• Use “Next” to jump to each event individually or open the results up in a list by choosing “Open Report”.
• For each event which contains a #FN tag, switch the event from a “Dialogue” type to an “OST” type event.

• Note: This can also be done using a customizable keyboard shortcut – default is Ctrl + K).
• Once all events are switched to “OST type,” navigate to Event > Configuration > Add Forced tag to OST events:

• All events should now contain the Forced tag:

3B. Prepare the File - Lyrics (skip if there are no Lyrics in your file):

Note: Events tagged with #LYR must be given the "Lyrics" tag in Ce6.

• Open up a “find” box. Event > Configuration > Find or Ctrl + F on your keyboard.
• Type #LYR in the search bar, and make sure to update the “In” field from Event Text to Annotations.

• Use “Next” to jump to each event individually or open the results up in a list by choosing “Open Report”.
• For each event which contains a #LYR tag, add the Lyrics tag using the tag icon (or by using a customizable keyboard shortcut, defaults shown in screenshot).

3C. Prepare the file - Other Tags:

• Find the translator credit event and add the relevant tag from the tag list or using the keyboard shortcut.

• If any archival footage is present in your file, follow the same steps as in 3B, searching for the #ARC tag, and tagging those events with the Archival Footage tag as appropriate.

4. Submit the File:

• Once ready to submit, navigate to Asset > Configuration > Submit.
• Provided the verifier does not kick out any Critical events, you can proceed with your submission. All critical events should be assessed and cleared before submission is possible.

5. Submit the CQC1 Task:

• Once the origination Task is submitted, the CQC1 task must also be completed so that the relevant “QC tag” is added to the Template asset version (translation jobs require this tag for workability). You should be assigned to a CQC1 Task for the same Job. If not, assign yourself or flag to coordination/TM/TS.
• Open Ce and navigate to Asset > Configuration > Submit. You will be asked to specify a result of the QC, choose “Pass”.

• Click Submit.
• Once submission completes, send a delivery email informing Client Ops that migration is complete.

6. IF WE ARE VERSIONING UP IN OM: Client Ops will Re-Run Job for New Proxy:

• Navigate to the last Task in the Job (Project Management / Project Confirmation / QC Report Review):

• Beneath Additional Details, click the "Re-run for New Proxy Version" button.
  • Note: DO NOT press this button on any other Task -- this can cause workability issues downstream.
• This will re-run the Ingest Task.
• After ingest and AM proxy generations, the CQC1 Task becomes workable -- this is the Task that Subtitling must work in.