Delivering, updating and removing content

Overview

All studio partners working with Google TV need to deliver their content through either Deluxe NMS or Premiere Digital. These two PPHs will get your files into the right format for Google and deliver them to us so you don't need to worry about your files conforming to Google's specifications.

Updating components

Component delivery was developed specifically so you can update certain components without having to resend the entire package.

Studio Partners: To update video or audio files, trailers, metadata, captions and subtitles and artwork, please contact your PPH and supply them with the new files.

PPHs: You will need to redeliver the relevant inventory with updated MMC via Aspera to the same ALID for each title. There is no need for a new ALID.

Metadata updates should be performed by the PPH that delivered the content originally. Delivering through Aspera, the PPH will need to send:  

1) An updated MEC (metadata file) that has been re-named from the initial delivery 
2) An updated MMC (Media Manifest) referencing the new MEC file.

The filename of the MMC however should be the same as it was when it was first delivered. 

Studios and PPHs: If you wish to update a file that has been delivered but not reviewed or approved yet by quality control, you can reach out to your Partner Operations contact

---

Removing Titles from the Store

Taking down a Title requires a new Avail submission

Movies & TV

• Fill in the EntryType column with Full Extract
• Update the End Date column to a date in the past for all corresponding line items for a title and territory combination
  • Please see the “EntryType” article for more information

TV

• When removing or blocking TV seasons from going live, be sure to also include the Season and Episode line items for a title and territory combination

FAQs

How can I update a title that's gone live with the wrong components?

The PPH will need to deliver an updated MMC XML with the replacement assets using the following steps.

Change the filename(s) of the file(s) to be redelivered, then redeliver the new file(s)
Change the <manifest:ContainerLocation> reference in the MMC XML to match the filename(s) of the redelivered file(s)
Redeliver the updated MMC XML file using the same filename. If a new MMC filename is used, it will be ignored.
It's also recommended to use the original delivery directory, if it still exists. To avoid this sub/dub issue in the future, make sure all components are delivered together in the same package.

Can ALIDs be changed?

ALIDs can be changed before the title has been delivered to Google.

In order to change an ALID after delivery, please first reach out to the Support team on [e-mail] to confirm if it will be possible for your title and for assistance with the change.

Please also note that for redeliveries, the new ALID will need to be delivered with the manifest.

Features and Bundles

ALID updates are not permitted for Features (child) that are included in a Bundle (parent) for Legacy or Next Gen titles.

If you want to update the avail metadata of a Feature inside a Bundle, you must use the ALID of the Feature that is currently in the system. This means if you want to change the start date of Title A, and Title A is part of a Bundle, you would not submit an avail with a different ALID and a new start date, you would submit an avail with the ALID that is currently in the system for Title A plus the new start date

1. If you want to change the ALID of a Feature that is currently the child of a Bundle, you must first takedown Bundle.
2. Once the Bundle is taken down, you would then need to resubmit a new avail with your new ALID for the Feature.
3. Once the updates have gone through and the new ALID is in the system for the feature, you can submit an avail for the Bundle and include the new Feature ALID in the BundleALIDs column.
4. A new delivery can be made once the avail has been processed

Should ALIDs be the same or different for dub and sub?

ALIDs should be the same regardless of the localization type. With the new component-based delivery pipeline content will be delivered as a single experience containing both dub and subs (where available). 

If the video contains burnt-in subtitles this should be reflected in the delivery XML(and not using the ALID). If a text-less asset exists (i.e. without burnt-in subs) that is going to be used for the dubbed version, then this version of the video should be delivered with a separate subtitle file (thus fulfilling both localization types). 

If you only have burnt-in sub & dubbed versions of a title, Google will use only one version. 

We shouldn't be facing instances where we have a text-less version being used for dub and a burnt in version used for sub as the text-less version covers both (with sub and dub coming in as individual components).

How long does it take for the Play Asset ID to display on the partner portal?

The Play Asset ID will be available on the partner portal after the title has had all required components approved and has published to the catalog. 

Do you accept bonus content?

We're currently not supporting extras and bonus material and there are no imminent plans to add this feature

Can we submit short TV contents?

We do not accept any content shorter than 15 mins irregardless of genre (incl. kids)