![]() Metadata XML files need to be properly formatted and checked programmatically with the right external tools. For example, review detailed information like tag formatting, locale, order of chapters, and correct time codes. itmsp package.Ĭhapter-related metadata should be reviewed thoroughly. Provide localized subtitles tags for content with burned‐in subtitles.įorced narrative tags should be reviewed and included, if they are part of the. The title should be accurate and match the movie or TV episode. For more information, see Subscription Video Asset Specification. The unique catalog and content identifiers for the item need to be included, as well as the variant identifier to distinguish between different versions of the content. They must match the tag used for Transporter. The provider tags should match the Apple-defined label for partner identification. Video assets must be encoded in ProRes 422 HQ format. If the native format isn’t available, use IVTC (Inverse Telecine) to remove pulldown patterns. Video assets with subtitles or forced narrative files should be complete, in sync, and correctly translated.Ĭurrent frame rates of video assets should match the original native format. ![]() Ghosting effects, moving image doubles, or image overlaps will be rejected. Interlacing artifacts, or “miniblinds,” must be removed. Video assets must have correct display measurements and can’t distort the aspect ratio. Videos with sequential frames that contain no distinction or movement will be rejected. Proper crop values must be specified in the XML to allow content to be presented properly across Apple devices.Įxamples are rectangular color blocks, or splits within a frame, and are reason for QC. See closed captions requirements.Ītom tags within video asset headers should be set and corrected as needed. Movies and TV episodes for other English-speaking countries or regions should also include a CC file when available. ![]() Movies and TV episodes for the United States require a closed caption (CC) file that is synchronized and complete. Video assets with errors generated by playback machines need to be fixed. Video assets must be the original aspect ratio. Once all Must Fix issues have been resolved, Apple will ingest your feed into the Universal Media Catalog. Apple’s Metadata Ops team will analyze the results of this ingestion and will provide a report categorizing any issues found as Must Fix or Should Fix. This mode will simulate mapping to our existing metadata references and will allow us to validate the quality of your metadata. Once all Must Fix issues have been resolved, Apple will ingest your feed into the Universal Media Catalog in “Isolation Mode”. Provide Apple with URLs that can be used to consume your Availability and Catalog feeds per service.Īpple will evaluate the XML structure, content, and metadata quality of your feeds for any issues not found by Media Feed Validator and provide a report with requested fixes. Ensure that your feed contains no XSD errors and no Media Feed Validator “Errors” or “Warnings.” Once achieved, be certain that your Catalog Feed complies with the UMC Standards and Style Guide to ensure your content meets Apple quality standards Use the provided XSD and Media Feed Validator to validate the structure of your XML. The Availability Feed describes when (via window definitions and restrictions) a user can access content from the Catalog Feed. The Catalog Feed includes factual information for the content available in your app (such as Title, Description, Release Date, and Artwork). Adopt the UMC Catalog Data Interface Specification (“Catalog Feed”) and the UMC Availability Data Interface Specification (“Availability Feed”).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |