Deliver component files

• Convert assets from the highest quality master possible. For example, if your program was mastered in HD you should deliver in HD. Do not convert masters for the sake of meeting this specification. First, reach out to your partner operations contact to test your existing masters.
• Content should be delivered picture-to-picture (ratings cards, FBI Logos, Piracy warnings, slates, countdowns, 2-pops, bars/tone, bumpers, and textless content should all be removed), unless specified otherwise.
• To effectively merchandize your content, a trailer should be delivered as part of the asset package.
• Trailers
  • Trailer quality should match the feature it represents.
  • HD features should be delivered with HD trailers whenever possible.
  • If an HD trailer does not exist, SD trailers for HD features are allowed.
  • If HD/SD trailer options are not available, clip previews from the feature are allowed.
  • The aspect ratio of the trailer should also match the feature.
  • 5.1 (in addition to stereo) should be delivered for trailers when available.
  • Trailers should reflect the localization of the feature. For example, if a feature is dubbed, the trailer should also be dubbed if possible.
  • We do not accept trailers with a call-to-action e.g. to click on a link.
  • Trailer must not exceed 10 minutes in length.
• Content should be localized for the area of distribution. For example, an English-language movie intended for viewing in France should have either French dubbing (preferred) or French subtitles. If you have any questions about this requirement, please reach out to your partner operations contact.
• QuickTime (.mov) files must be delivered as "self-contained" files. QuickTime Reference files that point to other media not contained within the file will be rejected.

1. Open your Aspera client.

2. Select the connection for your Google dropbox in the Connection box on the right, then click the Connect button.

   The Aspera client connects to your dropbox and displays the top-level folders.

3. Create and/or navigate to a directory named /eidr-s (if delivering with cut-level EIDR ID) or /org (if delivering with an Alt Cut ID).

4. Create a new folder for the new movie or show, using the cut-level EIDR ID or Alt Cut ID as the folder name.

   To create a folder, right-click the parent folder and select New > Folder. The name of the folder must match the value for the movie in the EIDR (CUT) column or the Alt Cut ID column in the Movie and TV Partner Portal. For example, create the folder /eidr-s/AAAA-BBBB-CCCC-DDDD-EEEE-F to deliver the movie with that EIDR ID.

5. Copy the manifest XML file into the folder.

   To copy the file into a folder, make sure the intended folder is open on the right, highlight the file in the box on the left, and click the right-facing arrow.

6. Create a resources within the EIDR (CUT) or Alt Cut folder, and copy the component files into it.

   The component files must be specified in the manifest, which specifies each file's name, language, type, and associations. The file names can contain any sequence of valid Unicode characters, of length 1-1024 bytes when UTF-8 encoded, and must not contain Carriage Return or Line Feed characters.

   

As the files are processed, their names are replaced in the dropbox with filename.processing. You can track the processing status of delivered files on the Component Delivery tab in the Movie and TV Partner Portal. 

A movie (<md:WorkType>movie</md:WorkType> in the manifest) must have values for these metadata fields:

• Title
• Summary (up to 4000 characters)
• Release Year
• Genre
• Rating
• Cast and Crew

To deliver a package that is explicitly unrated by any ratings organization, set the rating System and Value to Unrated:

       <md:RatingSet>
          <md:Rating>
            <md:Region>
             <md:country>US</md:country>
            </md:Region>
            <md:System>Unrated</md:System>
            <md:Value>Unrated</md:Value>
            <md:Description></md:Description>
          </md:Rating>
        </md:RatingSet>

For more information, see page 29 in Common Metadata Ratings Schema Definition.

These specifications are for alternative audio files that you deliver as part of a movie presentation, such as alternate language dubs. For video file encoding specifications, see Encoding.

You must provide one muxed audio track for each video file. The muxed track and all other audio tracks must appear in the inventory; each track for the same video file must have a unique language.

When delivering audio-only files, the manifest must properly specify the content type and language for each file. All audio-only files must contain just one language, and must conform to the associated video file in these ways:

• Must be left-edge aligned to the picture
• Must have a hard FX sync with a 2-frame tolerance
• Must match the duration to within 500 milliseconds

Google accepts audio files in the following three formats. Please consult your partner operations contact to determine which format is best for you, or to arrange a test delivery for audio that doesn't conform to one of these preferred specifications.

In addition to the standard encoding requirements, video files must be textless to prevent collisions with forced or normal subtitles. Each video file must also have one muxed audio track.

All subtitle files must be one of the supported formats. The manifest must specify which type of subtitles the file contains:

• Forced – Subtitles that display regardless of whether the user enables subtitles. Common examples are descriptive location identifiers or time sequences. The language of the forced subtitles must match the language of the complementary audio track.

• SDH – Subtitles for the deaf or hard-of-hearing. SDH should be used for any caption files. SDH files must include any relevant forced subtitle lines for that language.

• Normal – Subtitles used for other languages. Normal subtitle files must include any relevant forced subtitle lines for that language.

Google prefers to receive as many of the local language trailers as are available for each title. The trailer language should match the feature language where possible. For regions where no localized trailer is available, the "original version" trailer will be used if permitted in that region; otherwise, no trailer will be provided.

Google does not require you to deliver trailers in component form, although we do accept component-based trailers. You can deliver trailers in traditional muxed files. Trailers should reflect the quality of the feature it represents: HD trailers for HD features, dubbed trailers for dubbed features, and so on.