diff --git a/docs/THE ROKU CHANNEL/.gitkeep b/docs/THE ROKU CHANNEL/.gitkeep deleted file mode 100755 index e69de29b..00000000 diff --git a/docs/THE ROKU CHANNEL/_order.yaml b/docs/THE ROKU CHANNEL/_order.yaml deleted file mode 100644 index eab7d366..00000000 --- a/docs/THE ROKU CHANNEL/_order.yaml +++ /dev/null @@ -1,5 +0,0 @@ -- overview -- roku-content-partner-portal -- video-on-demand -- live-linear -- faqs diff --git a/docs/THE ROKU CHANNEL/faqs.md b/docs/THE ROKU CHANNEL/faqs.md deleted file mode 100644 index 0e079532..00000000 --- a/docs/THE ROKU CHANNEL/faqs.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: FAQs -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## Ad supported - -**When will my title(s) go live?** - -Content delivery is recommended 60 days prior to start date. All titles undergo a multi-factor QC review before publishing to ensure they meet customer quality content expectations. Any errors found during QC review can lengthen publishing timelines significantly. QC can take a minimum of 30 days and our operations team will provide feedback on content that has not passed our QC review. - -Once the QC review is complete, if there are no errors in your submission, your title will typically go live within 2-4 business days. - -**How do I find my titles on The Roku Channel?** - -You can find your content in three ways: Universal Search, The Roku Channel Search, and/or curated in The Roku Channel UI. Note The Roku Channel's UI is curated via a recommendations system. Thus, each user's UI will be different based on the content watched. - -**I would like to send additional movies and/or TV series for The Roku Channel. What is the process?** - -Please fill out the avails template (series and features/movies on separate templates) and send to [trc-avod-avails@roku.com](mailto:trc-avod-avails@roku.com). Avails template can be downloaded [here](https://devtools.web.roku.com/samples/TheRokuChannel_AvailsTemplate_v1_2.xlsx) and the avails specifications can be found [here](https://go.roku.com/rokuchannel-avails). Our programming team will review the submissions and follow up on the next steps. Please note selections can take up to 4 weeks. - -**I have a title(s) that need to be taken down from The Roku Channel.** - -If rights change from when the content was originally delivered to Roku and content needs to be removed from The Roku Channel either immediately or scheduled, the availability end date can be changed by providing a metadata update as defined in [The Roku Channel Ingest Specification](https://go.roku.com/rokuchannel-ingest-vod#metadata-updates-mdu-and-file-replacements). Explicit updates should be provided for all territories from which the content should be removed. Please be aware that end dates provided without time values specified will expire at 11:59:59pm on that date. - -Takedown notices for Feed partners should be sent via email to [avod-editorial@roku.com](mailto:avod-editorial@roku.com) & [contentoperations@roku.com](mailto:contentoperations@roku.com) and include **Name of Title** & **End Date**. Once takedown notice is confirmed from our Editorial and Operations team, partner must remove the title from the feed. - -### Roku preferred aggregators - -**I have delivered my content through one of Roku's Preferred Aggregators. When will my content go live?** - -Although we cannot speak to the Preferred Aggregator's timelines, once the Preferred Aggregator has delivered the titles, all titles undergo a multi-factor QC review before publishing to ensure they meet customer quality content expectations. Any errors found during QC review can lengthen publishing timelines significantly. QC can take a minimum of 30 days and our operations team will provide feedback on content that has not passed our QC review. - -**I would like to send additional movies and/or TV series for The Roku Channel. What is the process?** - -Please send all additional avails through your Preferred Aggregator. - -### Analytics & reporting - -**I have a channel app(s) on Roku and distribute my content on The Roku Channel. Will I receive payment for both?** - -If you have a channel app(s) on Roku, payments are sent out monthly whereas payments for The Roku Channel are sent out quarterly (Revenue Reports are sent via email 60 days' post quarter closing). Thus, you will only receive a lump sum payment for your channel app and content on The Roku Channel four times a year. Revenue reports sent via e-mail are only for content in The Roku Channel and do not apply to your channel app(s). - -**Why wasn’t I paid?** - -Roku does not verify bank account information. Our system only verifies the routing number and tax documents. If any of the bank account information you initially entered is incorrect, it will not be possible to pay you. In this case, you will receive a notification that the payment to you failed, and you will be asked to update your payment information in the Developer Dashboard. - -### Fulfillment Statuses - -**What does “Unfulfilled” mean?** - -A title is marked _Unfulfilled_ when the ordered rights and the content asset haven’t been matched yet. To advance, the rights must be linked to the asset using matching IDs. Make sure the rights ID and asset ID are the same. - -**What does “Ordered” mean?** - -_Ordered_ means the rights have been received, but the content itself hasn’t been delivered yet. - -**What does “Not Availed” mean?** - -_Not Availed_ means the content has been delivered, but the rights couldn’t be matched. This usually occurs if the Asset ID in the ingest package doesn’t align with the Partner Title ID in the rights data. - -### Need more help? - -* For all general questions including marketing, revenue reports, and analytics dashboards, please contact TRC Partner Support [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com) -* For all questions regarding partner onboarding and content delivery, please contact Content Operations [contentoperations@roku.com](mailto:contentoperations@roku.com) -* For all questions regarding content selections and editorial calendar & stunts, please contact AVOD Editorial [avod-editorial@roku.com](mailto:avod-editorial@roku.com) - -## Premium subscriptions - -**When can I expect to receive payments and revenue reports?** - -Within 30 days close of the calendar month. - -**On what cadence does the partner portal update?** - -The partner portal updates weekly on Mondays to reflect new data through the Sunday prior. - -**Why doesn’t my paid end users' number match my payout report?** - -Due to the average subscriber calculation method, the ending paid users will not match the payout report. Please use the Subscriber Audit Report under "payout_subscriber_audit" to tie the number of subscribers to your payout report. - -**What is the "payout_subscriber_audit" report?** - -This report can be used as an audit tool to tie the number of subscribers from your monthly payout report. - -## Linear - -**Where can I find my titles on The Roku Channel?** - -You can find your content a few ways: Universal Search, The Roku Channel Search, the EPG (Electronic Program Guide), the Live TV Zone, and/or curated in The Roku Channel UI. Note: The Roku Channel's UI is curated via a recommendations system. Thus, each user's UI will be different based on the content watched. - -**I am switching SSAI Providers. What is the process?** - -Roku requires 30 days notice in advance for the switchover of a SSAI Provider via e-mail to [trcliveoperations@roku.com](mailto:trcliveoperations@roku.com), [live-editorial@roku.com](mailto:live-editorial@roku.com), & [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com). Once notice is confirmed from Roku, Roku will coordinate with the new SSAI Provider to issue new ad tags and QC the channel before switching out the new channel. - -**I am rebranding my channel. What is the process?** - -Roku requires 30 days notice in advance for rebranding and/or renaming of a channel via e-mail to [trcliveoperations@roku.com](mailto:trcliveoperations@roku.com), [live-editorial@roku.com](mailto:live-editorial@roku.com), & [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com). Note: Linear channel tile and EPG logos have to be reviewed for approval beforehand. - -**How do I override my linear channel tile for promotions?** - -* Please submit any special events and artwork for your live channel via the [Airtable Form](https://airtable.com/shrbGwmr6NWkyZTBk). This is where our team will review for consideration of possible promotion. -* You can re-submit as many events as you'd like. -* The earlier the submission, the better, but if you don't have imagery yet, add a shared link to the form that can updated at a later time. -* Please feel free to give us an email shout-out in addition to the Airtable form for special & important events. - -**I would like to deprecate my channel. What is the process?** - -Roku requires 30 days notice in advance for deprecation of a channel via e-mail to [trcliveoperations@roku.com](mailto:trcliveoperations@roku.com), [live-editorial@roku.com](mailto:live-editorial@roku.com), & [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com). - -**How do I subscribe to TRC monthly editorial newsletter (which highlights upcoming linear programming priorities)?** - -Please [complete this form](https://airtable.com/shrQD1DlJIMP6Gmit). - -### Need more help? - -* For all general questions including marketing, revenue reports, and analytics dashboards, please contact TRC Partner Support [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com). -* For all questions regarding the editorial calendar, stunts, and live events, please contact Live Editorial [live-editorial@roku.com](mailto:live-editorial@roku.com). -* For all technical questions regarding channel delivery, stream issues, and EPG, please contact Live operations [trcliveoperations@roku.com](mailto:trcliveoperations@roku.com). diff --git a/docs/THE ROKU CHANNEL/live-linear/_order.yaml b/docs/THE ROKU CHANNEL/live-linear/_order.yaml deleted file mode 100644 index 4a453102..00000000 --- a/docs/THE ROKU CHANNEL/live-linear/_order.yaml +++ /dev/null @@ -1,2 +0,0 @@ -- ovp-linear-ingest-spec -- epg-on-trc diff --git a/docs/THE ROKU CHANNEL/live-linear/epg-on-trc.md b/docs/THE ROKU CHANNEL/live-linear/epg-on-trc.md deleted file mode 100644 index 0eb92712..00000000 --- a/docs/THE ROKU CHANNEL/live-linear/epg-on-trc.md +++ /dev/null @@ -1,156 +0,0 @@ ---- -title: EPG on The Roku Channel -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## Summary - -The Roku Channel employs a Programming Guide for linear channels similar to that of a traditional TV Guide. This can be accessed by launching an EPG compatible live channel and using the left arrow on the remote, or by clicking the “Live TV” bookend tile in the live channel row. - -**For the best user experience**, there are several required and highly recommended metadata guidelines which will be outlined below. - -_**Note:**_ _Some items below will require a linear partner to implement. Consult with your linear partner if you have any questions._ - -## Schedule & programming - -Any live channel to be considered for placement in the EPG is required to have a **minimum** of **seven (7) days** of scheduled programming, with at least **one (1) day** of historical data. - -* All programs must be **15 mins** or longer in duration and no more than **4 hours.** -* Partners should not make programming updates to content scheduled to air within **48 hours** of live broadcast. - -## Logos - -Each channel is required to have clearly legible logos which are displayed on the channel spine in the EPG grid as well as in the info HUD for each program. The requirements are as follows: - -* _Logos to be delivered via **zip file** to Linear Certified Partner (LCP)_ -* _No additional branding or text beyond the Channel’s title and iconography_ -* For EPG spine: 1x light logo, 1x dark logo (can be same if image reads well on both white and black backgrounds). - * Logos **must** be transparent PNGs - * Center aligned on the horizontal and vertical axis - * 3 pixel spacing from top and bottom border - * Dimensions: 114x60 pixels (width x height) - * _Note: EPG spine logos should be free of any additional parent branding, distributor branding, "presented by" and be simply the name or logo of the channel._ -* For Info HUD: 1x logo aligned to center on vertical/horizontal axis - * Logos **must** be transparent PNGs - * Logos **must** be monochromatic hex #efefef - * Dimensions: 260x147 pixels (width x height) - -roku600px - epg1 - -## Metadata by content type - -**Tip**: Including Gracenote TMS ids or IMDB ids in your program metadata generally provides all the required metadata for any content type (see [A note about deduplication of metadata](#a-note-about-deduplication-of-metadata)). TRC also supports channel level Gracenote TMS ids (aka ProgSrvIDs) but only for channels with live sports at this time. Ask your Roku rep for details. - -**Required** for all content types: - -1. Titles (35 characters max per line) - 1. No emojis - 2. Mixed case - -2. Program Art with title treatments (16x9 for all content types) - 1. Title treatment should match program title - 2. CTAs, website URLs, social media icons, etc are not permitted on program artwork. - 3. Episodes as part of a series do not require title treatments - -3. Short Description (**maximum 110 characters**) - 1. Descriptions longer than 110 characters will get truncated and cannot be expanded. - 1. Do not truncate your own descriptions or add ellipses. - 2. Do not repeat/reuse program title in the description - 3. No emojis - -4. Closed Captioning (where legally required, usually included in video stream) - -5. Closed Caption Attribute field - 1. Added to each item in schedule - 2. Denotes "CC" in info HUD for each airing of program. - -6. Program specific Content Rating - 1. [Territory specific rating systems](doc:ovp-linear-ingest-spec#accepted-parental-ratings) - 2. TVY and TVY7 are reserved for kidsDirected channels only (ask your Roku rep for details) - -7. Air dates/release dates for movies & TV episodes - -8. [Genre/s](doc:ovp-linear-ingest-spec#genres-property) - -### Series - -Additional Required Metadata: - -1. 16x9 Series art w/ title treatments - 1. Title treatment should match series title - - 2. CTAs, website URLs, social media icons, etc are not permitted on series artwork. - - 3. Episode art does not require title treatment - -2. Season/Episode numbers - 1. Do NOT include season/episode numbers in titles - 2. Do NOT use industry episode numbers (Ep 101, 201, etc) - -3. Series Title - -4. Episode Title - 1. Do NOT include Series title in Episode title - -### TV specials - -Recommended content type for one-off specials, News programs, and some sporting events. - -### Short form videos - -Catch-all for content that doesn’t fit any above content type. Useful for composite content such as blocks of short form videos, music videos, etc. - -## Additional tips - -### Sports programs - -* For most sporting events, use Series content type and **YEAR** for Season number. -* Use League or Event for name of Series -* Use team names, competitors, or specific event (in the case of when series name is Olympics, X-games, etc) in episode name. -* Additional info can be included in description. -* For one-off sporting events/coverage such as “UFC 249” or “Dew Tour 2019 Recap”, use tvSpecials content type. - -**_Feel free to ask your Roku rep if you have any questions on formatting sports programs for EPG._ - -### A note about deduplication of metadata: - -Roku augments metadata and artwork that appears in The Roku Channel on Roku devices, web browsers, mobile applications, and other off-platform players with data supplied from Gracenote’s database where available. The Gracenote data aids in a unified experience of a title across platforms as well as on the greater Roku ecosystem. Roku will attempt to match all content delivered by our Partners to a corresponding record in Gracenote’s database. At this time all metadata and artwork that appears on The Roku Channel is sourced from Gracenote if that content is found in Gracenote’s database. - -Our systems use a combination of methods to match a title its correct Gracenote record. Partners can aid in the matching to a Gracenote record by providing accurate metadata including: - -* Exact title of a series, movie, TV special, or short form video -* Release dates that are accurate to the year the title was originally released on any platform -* Accurate season and episode numbers according to the original release order -* Accurate TMS (Gracenote) IDs or IMDB IDs for each associate content type - -## Sample series in EPG - -roku600px - epg1 - -1. Series Titles -2. Episode Title -3. Rating -4. Closed Captioning Badge -5. Channel Number -6. EPG Logo -7. Description -8. Season / Episode Number -9. Program Art - -roku600px - epg1 - -1. Series Title -2. Episode Title -3. Rating -4. Closed Captioning Badge -5. Channel Number -6. HUD Logo -7. Description -8. Season / Episode Number diff --git a/docs/THE ROKU CHANNEL/live-linear/index.md b/docs/THE ROKU CHANNEL/live-linear/index.md deleted file mode 100644 index c24d769b..00000000 --- a/docs/THE ROKU CHANNEL/live-linear/index.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Linear -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## New to The Roku Channel - Getting started - -Welcome to linear channels at Roku! Here are resources to help get you started on launching live and linear content in The Roku Channel. - -## Specifications - -* [Live Linear Ingest Specification](doc:ovp-linear-ingest-spec) - -## Analytics & reporting - -### Analytics dashboard - -#### Overview - -The Roku Channel partners have access to web-based performance analytics through Roku's Content Partner Portal. This allows you to analyze the health, viewership trends, and metrics for specific titles. - -[Learn more](https://developer.roku.com/dev/docs/roku-content-partner-portal-analytics) - -### Partner payout - -#### Overview - -The Roku Channel Partners must enroll in Roku’s Partner Payouts Program, which is the vehicle through which partners receive payments for content served to Roku Users. - -#### Enrolling in Roku's Partner Payouts Program - -To sign up for Roku Partner Payouts Program: - -* Create a [Roku customer account](https://developer.roku.com/enrollment/standard) -* Enroll your [Roku account in the Developer Program](https://developer.roku.com/developer/billing) -* Enroll in the [Roku Partner Payouts Program](https://developer.roku.com/developer/billing) - -In order to enroll in the Roku Partner Payout Program, you will need to provide the following to - -* Contact information -* Bank information -* Tax forms (W9, W8-BEN, or W8-BEN-E) -* You can come back and edit this information at any time. - -#### The Roku Channel partner payouts - -Partners can select between three payout methods when enrolling in the Roku Partner Payouts Program: - -* PayPal -* Direct deposit / ACH -* Wire transfer -* **Please note that for partners outside the United States, only PayPal and wire transfers are available (direct deposit/ACH is not available).** -* For all partners, wire transfer and ACH payments are made in USD only. If there are transactions received that are non-USD, they are converted to USD using the average foreign exchange rate for the month the payment is for. -* With PayPal there is no payment fee. With wire transfers and ACH payments, your bank will charge you bank fees. diff --git a/docs/THE ROKU CHANNEL/live-linear/ovp-linear-ingest-spec.md b/docs/THE ROKU CHANNEL/live-linear/ovp-linear-ingest-spec.md deleted file mode 100644 index 503711b5..00000000 --- a/docs/THE ROKU CHANNEL/live-linear/ovp-linear-ingest-spec.md +++ /dev/null @@ -1,1635 +0,0 @@ ---- -title: The Roku Channel live linear ingest specifications (OVP) -deprecated: false -hidden: false -robots: index ---- -_Version 3.4_ - -## Overview - -This specification describes the ingest specifications and EPG requirements required for your channel's content catalog to be included in [The Roku Channel](https://www.roku.com/whats-on/the-roku-channel). A catalog is the set of movies, series, TV specials, short-form videos or linear stream your channel provides, along with the artwork that represents it in the UI. A catalog feed (JSON) or Gracenote channel ID (aka ProgSrvID) includes the metadata that describes each asset so Roku can index it, categorize it, and present it to users. **Note: Gracenote channel id support is currently limited to linear channels with live sports only.** - -The Roku Channel feed format follows the JSON-Schema Draft 4. All the properties in the schema are case sensitive. Before submitting a feed, make sure it is a valid JSON file. You can do that by using an IDE or free online tools, such as [JSON Schema Validator](https://www.jsonschemavalidator.net/) or [JSON Schema Lint](https://jsonschemalint.com/#!/version/draft-07/markup/json). - -For guidelines about presenting your channel's EPG, see [EPG on The Roku Channel](/trc-docs/live-linear/epg-on-trc.md). - -### A note about deduplication of metadata - -Roku augments metadata and artwork that appears in The Roku Channel on Roku devices, web browsers, mobile applications, and other off-platform players with data supplied from Gracenote’s database where available. The Gracenote data aids in a unified experience of a title across platforms as well as on the greater Roku ecosystem. Roku will attempt to match all content delivered by our Partners to a corresponding record in Gracenote’s database. _At this time all metadata and artwork that appears on The Roku Channel is sourced from Gracenote if that content is found in Gracenote’s database._ - -Our systems use a combination of methods to match a title its correct Gracenote record. Partners can aid in the matching to a Gracenote record by providing accurate metadata including: - -- Exact title of a series, movie, TV special, or short form video - -- Release dates that are accurate to the year the title was originally released on any platform - -- Accurate season and episode numbers according to the original release order - -- Accurate TMS (Gracenote) IDs or IMDB IDs by content type - - - Content classified as an episode with Gracenote must be delivered as an Episode to Roku - - - Content classified as a movie with Gracenote must be delivered as a movie to Roku - - - Content classified as a TV Special with Gracenote can be delivered as a movie to Roku - -## Inclusion in The Roku Channel - -In order for your content to be surfaced in The Roku Channel, you must adhere to this specification. If you already have a channel powered by Direct Publisher and you want its content to appear in The Roku Channel, you must ensure your feed meets the requirements described in this specification. Likewise, if you've built a channel using our developer program, then you must provide Roku with a separate feed adhering to this specification. The new feed must contain only assets that are available for display in The Roku Channel. - -**Note that participation in The Roku Channel is currently limited to select partners. Configuring your feed to meet this specification is a prerequisite to be reviewed for inclusion. To submit a feed for approval into The Roku Channel, contact your Roku representative.** - -All Linear Partners must utilize one of the **Linear Certified Partners** for their stream and EPG distribution: **Amagi, Wurl, Frequency, OTTera, Xumo, Akta, Zype, Evrideo, or Stenna**. Exceptions will only be considered if the partner can agree to abiding by all rules and requirements as outlined in the linear certification agreement which can be provided if such an exemption is necessary. - -### Error Reporting - -Stream and EPG issue reports go directly to the LCPs. Stream issues and high priority EPG issues are reported as needed. Comprehensive EPG issue reports go out weekly to all LCPs. - -## Roku OVP - -Roku now requires all live linear channels on TRC to run through their Online Video Platform (OVP). Below are the ingest specifications and input data template that needs to be filled out and provided to Roku Live Operations for all new live linear channels. - -### Collection of Linear Channel Input Data - -Roku Live Operations team provides templates to LCPs for channel acquisition details. - -For Live events and Special integrations, a custom ingest document will be provided. - -### **Supported Video and Audio Tech Specs** - -The following outlines what we support. A preferred video set up is outlined in the referenced column. - -{` - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- **Description** - - **Specification** - - **Preferred** -
- Delivery Method - -
    -
  • AWS Media Connect Entitlement*
    • -
  • Zixi Push*
    • -
  • SRT*
      -
    • Push IP and Port number will be provided to LCP/partner
      • -
    • -
  • RTP w/FEC Push
    • -
  • RTMP Push
      -
    • Push URL will be provided to LCP/partner
      • -
    • -
- *Support AES Decryption - 		- AWS Media Connect Entitlement -
- Container - - TS over IP - - TS over IP -
- Video Codec - - * MPEG-2 - * H.264 - * H.265 - - H.264 -
- Audio Codec - - * AAC - * MPEG Audio - * Dolby Digital (AC3 2.0 + 5.1) - * PCM - - AAC -
- Video Resolution - - * HD - 1920 x 1080 - * SD 720 x 480 - - HD - 1920 x 1080 -
- Video Frame Rate - - * 23.97 - * 24 - * 25 - * 29.97 - * 30 - * 59.94 - * 60 - - any -
- Audio Bitrate - - * 128 Kbps (min) - * 320 Kbps (max) - - within range -
- Overall Bitrate - - * HD - 12 Mbps (min) - * SD - 6 Mbps (min) - - Above 12 Mbps -
- Bitrate Mode - - CBR - - CBR -
- Video Interlacing - - Progressive Scan - - Progressive Scan -
- Audio Sampling Rate - - 48 kHz - - 48 kHz -
- Audio Channels - - Stereo - - Stereo -
- Closed Captions - - CEA 608/708 (embedded) - - CEA 608/708 (embedded) -

- Note: Beginning 25 May 2027, the CRTC requires audiovisual online streaming services operating in Canada to provide closed captions on new original programming and on programs previously broadcast on linear television with captions. See Broadcasting Regulatory Policy CRTC 2026-98 for scope and thresholds. -

-
- Aspect Ratio - - * HD - 16:9 - * SD - 4:3 - - HD - 16:9 -
- Other video details - - * Content should be free of the following technical errors: - * Windowboxing and stretching - * Excess video content such as excessive black screen and color bars - * Visible interlacing and artifacts/macroblocking - -
- Ad Insertion Points (if applicable) - - SCTE-35 Markers In Stream via any of the following: -

-
    -
  • Splice_Insertion
      -
    • Start and Duration is required
      • -
    • If scte35:SpliceInsert, outOfNetworkIndicator must be set to true
      • -
    • -
  • Time Signal
      -
    • Start and Duration is required
      • -
    • If scte35:TimeSignal, then accompany by scte35:SegmentationDescriptor scte35:SegmentationUpid with segmentationTypeId set to one of the following cue-out numbers:
        -
      • 0x22 (start break)
        • -
      • 0x30 (provider advertisement start)
        • -
      • 0x32 (distributor advertisement start)
        • -
      • 0x34 (provider placement opportunity start)
        • -
      • 0x36 (distributor placement opportunity start)
        • -
      • -
    • -
- 		- Splice_Insertion -
- Special ad support - - TripleLift DBI support* -

- *Requires Roku approval - 		-
- Ad policy - -
    -
  • Partners should not serve any ads in the channel other than the ones returned by the Roku SSAI, unless explicitly agreed in the contract.
    • -
  • Partners should adhere to the below ad length requirements:
      -
    • General Audience
        -
      • 8 minutes of ads per hour
        • -
      • Minimum 4 ads and maximum of 6 ads per pod
        • -
      • Ad pod length of 2 minutes
        • -
      • -
    • Kids
        -
      • 6 minutes of ads per hour
        • -
      • Minimum 3 ads and maximum of 6 ads per pods
        • -
      • Ad pod length of 90 seconds
        • -
      • Bumper/lead-in identifying ad break before AND after ad pods occur (6 second maximum)
          -
        • Example: "We'll be right back after this break", "Now back to the show"
          • -
        • -
      • Flexibility around the ad policy is provided during live events. Please discuss this with your Roku rep.
        • -
      • -
    • -
- **Do not include pixels, third-party tags, or Software Development Kits of any kind without express prior written approval and certification by Roku. - 		-
- Ad queue points quality - - - Avoid placing ad breaks that interrupt dialogue
- Avoid ad breaks that interrupt a major action/dramatic scene
- Ad breaks should be placed with frame accuracy in logical ad break points (ex. fades to black, scene transitions, etc) - 		-
- Blackouts and Regional restrictions - - * Roku supports regional restrictions on a channel level basis - * Currently US ZIP codes only - * SCTE 224 support for program level blackouts and restrictions (coming soon) - -
-`} - -## Live Events - -The following additional details are required for Roku discrete live events (DLEs) and insertion into Roku owned and operated linear channels. - -- All live events must have both a primary and backup source - - **SRT or Zixi Push preferred;** HLS and RTMP are not supported -- Live events intended for Roku O\&Os must include program start/stop SCTE messages - - **Splice Insert messages are preferred**; Time Signal message type must include a splice command - -### Metadata - -- Ensure all event metadata is delivered to your Roku rep for the event as early as possible - - **A Gracenote TMS ID for the event is preferred** - - Metadata fields can be found here based on event type: [https://developer.roku.com/en-gb/trc-docs/live-linear/epg-on-trc.md#metadata-by-content-type](https://developer.roku.com/en-gb/trc-docs/live-linear/epg-on-trc.md#metadata-by-content-type) - -### Recurring events - -- Roku has the ability to access third party APIs for recurring events. **Ask your Roku rep for details.** - -![roku400px - livespecs-1](https://image.roku.com/ZHZscHItMTc2/live-events-graph-1.png) - -# Direct Publisher Feed Schema - -These are the properties for the root object of your EPG feed. It contains basic information such as your company's name, when the feed was last updated, and other objects that will describe all your content in detail. The URL for your feed should have the form "https\://_[yourfeeddomain.com](http://yourfeeddomain.com/)_". - -The format of the feed is a comma-separated list with each property enclosed in double quotes. You must assign each asset (object) its own reference ID, which is a string. **Note**: The ID for an asset must not exceed 50 characters. - -**_Note:_** Partners should not make programming updates to content scheduled to air within **48 hours** of live broadcast. - -| **Field/Root Property** | **Content Type** | **Required** | **Description** | -| ----------------------- | ----------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| providerName | string | Required | The name of the feed provider. For instance, “Acme Productions” as shown in the template below. | -| lastUpdated | string | Required | The date that the feed was last modified in the [ISO 8601 ](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}T\{hh\}:\{mm\}:\{ss\}+\{TZ\}. For instance, "2015-11-11T22:21:37+00:00" as shown in the template below. | -| language | string | Required | The language the channel uses for all its information and descriptions in an ISO 639 alpha-2 or alpha-3 language code string. For instance, “en-US” as shown in the template below. | -| liveFeeds | [LiveFeed Object](#livefeed-content-type) | Required | A list of one or more live linear schedules.

**_Generally, only one liveFeed schedule per channel delivery should be present in the JSON. For bulk channel deliveries, please consult your Roku rep._** | -| movies | [Movie Object](#movie-content-type) | Required\* | A list of one or more movies. | -| series | [Series Object](#series-content-type) | Required\* | A list of one or more series. Series are episodic in nature and would include TV shows and daily or weekly ongoing shows. | -| shortFormVideos | [ShortFormVideo Object](#shortformvideo-content-type) | Required\* | A compilation of short form content with a **minimum** total duration of 15 mins. | -| tvSpecials | [TV Special Object](#tvspecial-content-type) | Required\* | A list of one or more TV specials. TV specials are one-time TV programs that are not part of a series. | - -> \*_At least one of these content types is required_ - -The Roku Channel Feed Root Object Template: - -```json -{ - "providerName": "Acme Productions", - "lastUpdated": "2015-11-11T22:21:37+00:00", - "language": "en-US", - "movies": [ ... ], - "series": [ ... ], - "shortFormVideos": [ ... ], - "tvSpecials": [ ... ], - "liveFeeds": [ ... ] - } -``` - -## Artwork for all content - -Each image must be delivered in the JPEG format (.jpg or .jpeg file extension). - -**Make sure your CDN is using the following ContentType headers** - -- image/jpeg -- image/jpg - -| **Image Type** | **Description** | **Resolution** | **Aspect Ratio** | **Required/Optional** | -| -------------- | -------------------------- | -------------- | ---------------- | ------------------------------------- | -| key art | Image with title treatment | 1920x1080 | 16:9 | Movie: Required
Series: Required | - -### Artwork content guidelines - -- Key art (graphic with the full title of the asset visible) - -- No sexually explicit or graphically violent artwork - -- Artwork should be post-theatrical and not include language such as “In Theaters Now” or “Coming Soon” - -- Artwork designed specifically for digital delivery is preferred - -- Artwork for international territories should be localized for each territory - -**For content on TRC, Roku will not accept branded artwork without prior approval for any individual video asset nor for season/series entities.** - -Object Example: - -```json -{ - "thumbnail": "http://thumbnail.jpg" -} -``` - -## Linear Channel Branding and Policies - -- Partners are permitted to have Logos, bugs and lower thirds in their channels - -#### Content Expectations - -- _Content Hours_: minimum of **150 hours of content** -- _Content per Hour:_ minimum of **50 minutes per hour** of content -- _Daily Refresh:_ **2 hours** minimum of refreshed content daily -- Content Recommendation - - _Content Loop:_ minimum of **8 hours of content before loop** - -#### Content Policy - -- Content rated R and TV-MA is allowed only **between 9pm-5am Eastern Time** -- Public policy and political issues must be presented with accuracy, honesty and fairness -- Foreign Language Programming - - _On English-language channels, subtitles _**_must_**_ be included._ - - _No foreign-language (subtitled) programming allowed on Kids & Family channels._ -- **Every program must have a rating**. - - _Note for channels in the US_: If a program has an MPAA rating, the partner must use the MPAA rating for the program. If the program does not have an MPAA rating, or is a TV edit of an MPAA film, the partner must use a TV Ratings (USA_PR) rating. See [Advisory Ratings object](#advisoryratings-property) - -#### Slate Requirements - -- Must be animated & have audio - -- Must include the linear channel logo/branding - -- Must include a countdown timer for the duration of the ad break - - _Note: Countdown timer does not satisfy the animation requirement_ - -- Must include messaging to indicate a break is in progress and programming will resume shortly - -- No CTA - -- Cannot promote a channel outside of TRC - -#### LiveFeed Promotion Guidelines - -- Partners are not allowed to promote Partner content without explicit permission from TRC. -- Calls to action (CTAs) or links to external platforms or sites (including QR codes) are not permissible and must be removed from the video prior to delivery to Roku. - -## Content types - -### LiveFeed content type - -Child object of root property liveFeeds. - -This object represents a live linear stream. Please contact your Roku representative if you want to create a channel that streams live linear content. - -| Field | Type | Required | Description | -| ------------------- | ---------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| id | string | Required | Your immutable string reference ID for the live linear stream. THIS CANNOT CHANGE. This should serve as a unique identifier for the live stream across different locales. **Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| title | string | Required | The live stream's title. Roku uses this value for matching in Roku Search. Please don’t include extra information like year, version label, etc. | -| content | [Content Object](#content-properties) | Required | Additional details about the livefeed, including the **program schedule** . | -| thumbnail | string | Required | The URL of the primary thumbnail for the live stream. This is used within your channel and in search results.

Landscape key art with the full title of the asset visible in a JPEG file. Image dimensions must be 1920x1080 (width x height, 16x9 aspect ratio)

**Make sure your CDN is using the following ContentType headers**
- image/jpeg
- image/jpg | -| shortDescription | string | Required | A live stream description that does not exceed 200 characters. The text will be clipped if longer. No emojis. | -| longDescription | string | Required | A longer live stream description that does not exceed 500 characters. The text will be clipped if longer. Must be different from shortDescription. No emojis. | -| validityPeriodStart | string | Optional | The date when the content should become available in the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}T\{hh\}:\{mm\}:\{ss\}+\{TZ\}. E.g.: 2018-11-11T22:21:37+00:00 | -| validityPeriodEnd | string | Optional | The date when the content is no longer available in the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}T\{hh\}:\{mm\}:\{ss\}+\{TZ\}. E.g.: 2018-11-11T22:21:37+00:00 (set to a perpetuity date if possible) | -| advisoryRatings | [Advisory Ratings object](#advisoryratings-property) | Required\* | An array of parental ratings for the content.
\*See [Kids-Directed content](#kids-directed-content) for rating requirements | -| genres | string | Required | Array of genre strings for the channel. Must be one or more of the values listed in [genres](#genres-property) . | -| tags | string | Optional | One or more optional tags. Each tag is a string and is limited to 20 characters.\*See [Kids-Directed content](#kids-directed-content) for tag requirements | - -Live Feed Object Example: - -``` -{ - "id":"1509428502953", - "title":"Sample Stream", - "content":{ - "..." - }, - "language":{ - "en" - }, - "thumbnail":"https://example.org/cdn/thumbnails/1509428502952/1", - "shortDescription":"A live description", - "longDescription":"A longer description of a live stream", - "advisoryRatings":[ - { - "source": "MPAA", - "value": "PG13" - }, - { - "source": "CPR", - "value": "14+" - } - ], - "genres":[ - "drama", - "comedy", - "horror" - ], - "tags":[ - "kidsdirected" - ] -} -``` - -### Movie content type - -Child object of root property `movies`. - -This object represents a movie. - -#### Movie ad policy - -- No adBreaks should be listed during the first 10 minutes of program start -- No pre-roll adBreak should be listed - 00:00:00 -- adBreak cue points should be provided at naturally occurring scene breaks and/or fades to black -- There should be no less than 10 minutes between each adBreak -- No adBreaks within 10 minutes of end credits. - -| **Field** | **Type** | **Required** | **Description** | -| ---------------- | ---------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| id | string | Required | Your immutable string reference ID for the movie. THIS CANNOT CHANGE. This should serve as a unique identifier for the movie across different locales and feeds from the same provider.
**Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| title | string | Required | Movie title. Roku uses this value for matching in Roku Search. Please use plain text and do not include extra information like year, version label, etc. No Emojis. Mixed case. | -| genres | string | Required | Array of genre strings for the movie. Must be one or more of the values listed in [genres](#genres-property) . | -| thumbnail | string | Required | The URL of the primary thumbnail for the live stream. This is used within your channel and in search results.

Landscape key art with the full title of the asset visible in a JPEG file. Image dimensions must be 1920x1080 (width x height, 16x9 aspect ratio)

**Make sure your CDN is using the following ContentType headers**
- image/jpeg
- image/jpg | -| releaseDate | string | Required | The date the movie was initially released or first aired. Used to sort programs chronologically and grouping related content in Roku Search. Conforms to the [ISO 8601 ](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}. E.g.: 2015-11-11 | -| shortDescription | string | Required | A movie description that does not exceed 110 characters. The text will be clipped if longer. No emojis. | -| credits | [Credit Object](#credit-property) | Optional | One or more credits. The cast and crew of the movie. | -| advisoryRatings | [Advisory Ratings Object](#advisoryratings-property) | Required\* | An array of parental ratings for the content.
\*See [Kids-Directed content](#kids-directed-content) for rating requirements | -| externalIds | [External IDs Object](#externalids-property) | Optional | One or more third-party metadata provider IDs. | - -Movie Object Example: - -``` -{ - "id":"1509428502953", - "title":"Sample Title", - "thumbnail":"https://example.org/cdn/thumbnails/1509428502952/1", - "shortDescription":"A movie description", - "genres":[ - "drama", - "comedy", - "horror" - ], - "releaseDate": "2016-01-01", - "advisoryRatings": [ - { - "source": "MPAA", - "value": "PG13" - }, - { - "source": "CPR", - "value": "14+" - } - ] -} - -``` - -### Series content type - -Child object of root property `series`. - -This object represents a series, such as a season of a TV show or a mini-series. - -| **Field** | **Type** | **Required** | **Description** | -| ---------------- | ---------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| id | string | Required | Your immutable string reference ID for the series. THIS CANNOT CHANGE. This should serve as a unique identifier for the movie across different locales and feeds from the same provider.
**Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| title | string | Required | The title of the series. Roku uses this field for matching in Roku Search. No Emojis. Mixed case. | -| seasons | [Season Object](#season-content-type) | Required\* | One or more seasons of the series. Seasons should be used if episodes are grouped by seasons. | -| episodes | [Episode Object](#episode-content-type) | Required\* | One or more episodes of the series. Episodes should be used if they are not grouped by seasons (e.g., a mini-series). | -| genres | string | Required | Array of genre strings for the series. Must be one or more of the values listed in [genres](#genres-property) . | -| thumbnail | string | Required | The URL of the primary thumbnail for the live stream. This is used within your channel and in search results.

Landscape key art with the full title of the asset visible in a JPEG file. Image dimensions must be 1920x1080 (width x height, 16x9 aspect ratio)

**Make sure your CDN is using the following ContentType headers**
- image/jpeg
- image/jpg | -| releaseDate | string | Required | The date the series first aired. Used to sort programs chronologically and grouping related content in Roku Search. Conforms to the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}. E.g.: 2015-11-11 | -| shortDescription | string | Required | A description of the series that does not exceed 110 characters. The text will be clipped if longer. No emojis. | -| advisoryRatings | [Advisory Ratings Object](#advisoryratings-property) | Required\* | An array of parental ratings for the content.
\*See [Kids-Directed content](#kids-directed-content) for rating requirements | -| credits | [Credit Object](#credit-property) | Optional | One or more credits. The cast and crew of the series. | -| externalIds | [External IDs Object](#externalids-property) | Optional | One or more third-party metadata provider IDs. | - - - \*Must have either `seasons` or `episodes` - - -Series Object Example (seasons): - -``` -{ - "id": "1509428502952", - "title": "The Amazing Series with Seasons!", - "seasons": [ ... ], - "genres": [ - "educational", - "science fiction", - "thriller", - ], - "thumbnail": "https://example.org/cdn/thumbnails/1509428502952/1", - "shortDescription": "Wondrous series seasons.", - "releaseDate": "2016-01-01", - "advisoryRatings": [ - { - "source": "USA_PR", - "value": "TV-14" - }, - { - "source": "CPR", - "value": "14+" - } - ] -} -``` - -Series Object Example (mini-series): - -``` -{ - "id": "1509428502952", - "title": "The Amazing Series with Episodes Only!", - "episodes": [ ... ], - "genres": [ - "fashion", - "romance", - "technology" - ], - "thumbnail": "https://example.org/cdn/thumbnails/1509428502952/1", - "shortDescription": "Unbelievables series episodes.", - "releaseDate": "2016-01-01", - "advisoryRatings": [ - { - "source": "USA_PR", - "value": "TV-14" - }, - { - "source": "CPR", - "value": "14+" - } - ] -} -``` - -### Season content type - -Child object of property `series -> seasons`. - -This object represents a single season of a series. - -| **Field** | **Type** | **Required** | **Description** | -| ------------ | --------------------------------------- | ------------ | ----------------------------------------------- | -| seasonNumber | integer | Required | Sequential season number. e.g.: 3 or 2015. | -| episodes | [Episode Object](#episode-content-type) | Required | One or more episodes of this particular season. | - -Season Object Example: - -```json -{ - "seasonNumber": 1, - "episodes": [ ... ] -} -``` - -### Episode content type - -Child object of property: - -- `series -> episodes` -- `series -> seasons -> episodes` - -This object represents a single episode in a series or a season. - -#### Episode ad policy - -Content length longer than 15 minutes: - -- No adBreaks should be listed during the first 4 mins of program start -- No pre-roll adBreak should be listed - 00:00:00 -- adBreak cue points should be provided at naturally occurring scene breaks and/or fades to black -- There should be no less than 6 mins between each adBreak -- No adBreaks within the last 4 minutes of end credits - -| **Field** | **Type** | **Required** | **Description** | -| ---------------- | ---------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| id | string | Required | Your immutable string reference ID for the episode. THIS CANNOT CHANGE. This should serve as a unique identifier for the movie across different locales and feeds from the same provider.
**Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| title | string | Required | Episode title. Roku uses this value for matching in Roku Search. Please don’t include extra information like year, version label, etc. No Emojis. Mixed case. | -| thumbnail | string | Required | The URL of the thumbnail for the episode. This is used within your channel as a backup to series artwork and in search results where applicable.

Landscape untitled key art in a JPEG file. Recommended image dimensions: 1920x1080 (width x height, 16x9 aspect ratio)

**Make sure your CDN is using the following ContentType headers**
- image/jpeg
- image/jpg | -| releaseDate | string | Required | The date the episode first aired. Used to match program data to Gracenote counterpart. Conforms to the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}. E.g.: 2015-11-11 | -| episodeNumber | integer | Required | Sequential episode number. e.g.: 3 | -| shortDescription | string | Required | An episode description that does not exceed 110 characters. The text will be clipped if longer. No emojis. | -| credits | [Credit Object](#credit-property) | Optional | One or more credits. The cast and crew of the episode. | -| advisoryRatings | [Advisory Ratings Object](#advisoryratings-property) | Required\* | An array of parental ratings for the content.
\*See [Kids-Directed content](#kids-directed-content) for rating requirements | -| externalIds | [External Property](#externalids-property) | Optional | One or more third-party metadata provider IDs. | - -Episode Object Example: - -``` -{ - "id": "1509428502952", - "title": "The Amazing First Episode Title", - "thumbnail": "https://example.org/cdn/thumbnails/1509428502952/1", - "episodeNumber": 1, - "shortDescription": "Marvelous episode description", - "releaseDate": "2016-01-01", - "advisoryRatings": [ - { - "source": "USA_PR", - "value": "TV-14" - }, - { - "source": "CPR", - "value": "14+" - } - ] -} -``` - -### ShortFormVideo content type - -Child object of root property `shortFormVideos`. - -Short-form videos are generally less than 15 minutes long, and are not TV Shows or Movies. Must be included in a composite EPG block of 15 mins or greater. - -| **Field** | **Type** | **Required** | **Description** | -| ---------------- | ---------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| id | string | Required | Your immutable string reference ID for the video. THIS CANNOT CHANGE. This should serve as a unique identifier for the movie across different locales and feeds from the same provider.
**Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| title | string | Required | Video title. Roku uses this value for matching in Roku Search. Please don’t include extra information like year, version label, etc. No Emojis. Mixed case. | -| thumbnail | string | Required | The URL of the primary thumbnail for the live stream. This is used within your channel and in search results.

Landscape key art with the full title of the asset visible in a JPEG file. Image dimensions must be 1920x1080 (width x height, 16x9 aspect ratio)

**Make sure your CDN is using the following ContentType headers**
- image/jpeg
- image/jpg | -| shortDescription | string | Required | A description of the video that does not exceed 110 characters. The text will be clipped if longer. No emojis. | -| releaseDate | string | Required | The date the video first became available. Used to sort programs chronologically and grouping related content in Roku Search.
Conforms to the [ISO 8601 ](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}. E.g.: 2015-11-11 | -| genres | string | Required | Array of genre strings for the video. Must be one or more of the values listed in [genres](#genres-property) . | -| credits | [Credit Object](#credit-property) | Optional | One or more credits. The cast and crew of the video. | -| advisoryRatings | [Advisory Ratings Object](#advisoryratings-property) | Required\* | An array of parental ratings for the content.
\*See [Kids-Directed content ](#kids-directed-content) for rating requirements | - -Short-form Video Object Example: - -``` -{ - "id": "1509428502952", - "title": "The Amazing Short-form Video", - "thumbnail": "https://example.org/cdn/thumbnails/1509428502952/1", - "shortDescription": "Astonishing short-form video", - "genres": [ - "animals", - "animated", - "fantasy", - ], - "releaseDate": "2016-01-01", - "advisoryRatings": [ - { - "source": "USA_PR", - "value": "TV-14" - }, - { - "source": "CPR", - "value": "14+" - } - ] -} -``` - -### TvSpecial content type - -Child object of root property `tvSpecials`. - -#### TvSpecial ad policy - -Content length longer than 15 minutes: - -- No adBreaks should be listed during the first 4 mins of program start -- No pre-roll adBreak should be listed - 00:00:00 -- adBreak cue points should be provided at naturally occurring scene breaks and/or fades to black -- There should be no less than 6 mins between each adBreak -- No adBreaks within the last 4 minutes of end credits - -| **Field** | **Type** | **Required** | **Description** | -| ---------------- | ---------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| id | string | Required | Your immutable string reference ID for the TV Special. THIS CANNOT CHANGE. This should serve as a unique identifier for the movie across different locales and feeds from the same provider.
**Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| title | string | Required | Episode title. Roku uses this value for matching in Roku Search. Please don’t include extra information like year, version label, etc. No Emojis. Mixed case. | -| thumbnail | string | Required | The URL of the primary thumbnail for the live stream. This is used within your channel and in search results.

Landscape key art with the full title of the asset visible in a JPEG file. Image dimensions must be 1920x1080 (width x height, 16x9 aspect ratio)

**Make sure your CDN is using the following ContentType headers**
- image/jpeg
- image/jpg | -| genres | string | Required | Array of genre strings for the special. Must be one or more of the values listed in [genres](#genres-property) . | -| releaseDate | string | Required | The date the TV Special first aired. Used to sort programs chronologically and grouping related content in Roku Search. Conforms to the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}. E.g.: 2015-11-11 | -| shortDescription | string | Required | A description of the special that does not exceed 110 characters. The text will be clipped if longer. No emojis. | -| credits | [Credit Object](#credit-property) | Optional | One or more credits. The cast and crew of the TV special. | -| advisoryRatings | [Advisory Ratings Object](#advisoryratings-property) | Required\* | An array of parental ratings for the content.
\*See [Kids-Directed content ](#kids-directed-content) for rating requirements | -| externalIds | [External IDs Property](#externalids-property) | Optional | One or more third-party metadata provider IDs. | - -TV Special Object Example: - -``` -{ - "id": "1509428502952", - "title": "The Amazing First Episode Title", - "genres": [ - "animals", - "animated", - "fantasy", - ], - "thumbnail": "https://example.org/cdn/thumbnails/1509428502952/1", - "shortDescription": "Unusual episode description", - "releaseDate": "2016-01-01", - "advisoryRatings": [ - { - "source": "USA_PR", - "value": "TV-14" - }, - { - "source": "CPR", - "value": "14+" - } - ] -} -``` - -### **Schedule object** - -All linear feeds require a schedule as part of the livefeed content object. - -| Field | Type | Required | Description | -| ----------------- | ------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| id | string | Required | Your immutable string reference ID to the program's content ID from its respective content type section. THIS CANNOT CHANGE. This should serve as a unique identifier for the live stream across different locales. **Note** : The ID for an asset must not exceed 50 characters and must be alphanumeric. | -| durationInSeconds | integer | Required | the duration in seconds that the program will run. | -| isLive | boolean | Required | true OR false - Identifies a program as a true live event. | -| date | string | Required | Scheduled date for program to play. All times are UTC. Format: \{YYYY\}-\{MM\}-\{DD\} | -| times | string | Required | An array of start times in the particular day the program will start \[ "HH:MM:SS" ] | -| attributes | enum | Recommended | May denote a number of badges to appear in the EPG UI next to a program's title. Currently, only "CC" for Closed Captions is supported. | - -Schedule object example - -```json -{ - "id": "programId", - "isLive": false, - "date": "2020-01-13", - "times": [ - "21:30:00" - ], - "durationInSeconds": 2760, - "attributes": [ - "CC" - ] -} -``` - -### EPG - -EPG Requirement - -8 days of full data (1 week forward and 24 Hours back) to populate the EPG - -15-minute minimum duration for content block - -For full details and guidance on constructing your EPG, please refer this this guide. - -[https://developer.roku.com/en-ot/trc-docs/live-linear/epg-on-trc.md](https://developer.roku.com/en-ot/trc-docs/live-linear/epg-on-trc.md) - -Notes: - -- Please include the liveFeed as the first item in a feed. -- Only a title or a **TMS** ExternalID is required for programs referenced in a schedule. We will reject anything that's not a **valid** ExternalID. -- When referencing an episode, the parent items must also be in included ([series](/docs/specs/direct-publisher-feed-specs/json-dp-spec.md#series) and [season](/docs/specs/direct-publisher-feed-specs/json-dp-spec.md#season) when applicable). These parent items must be fully populated with required fields as specified in the [Roku Direct Publisher feed specification](/docs/specs/direct-publisher-feed-specs/json-dp-spec.md) or the series item must contain a valid External **TMS** id. - - Episodes using TMS External IDs must also include the Series TMS ID on the parent. - -![roku400px - feedspecs-1](https://image.roku.com/ZHZscHItMTc2/feed-specs-1-v2.jpg) - -#### EPG logos - -**To be provided via .zip file to Roku** - -| Logo | Required | Resolution | Notes | -| ---------------------------------------- | -------- | ---------------------------------------- | ---------------------------------------- | -| Program Guide channel Identifier (light) | Required | 114x60 pixels | Needs to read well on a black background | -| Program Guide channel Identifier (dark) | Required | 114x60 pixels | Needs to read well on a white background | -| Info HUD channel Identifier | Required | 260x147 (**MUST** be hex color #efefef ) | | - -For EPG Spine - -- 1 logo for white background, 1 for black background (can be the same image if reads well on both backgrounds). -- Logos need to be transparent PNGs -- 114 pixels wide x 60 pixels tall -- Center aligned on the horizontal & vertical axis -- 3 pixel top and bottom border - -For Info HUD - -- Logos need to be transparent PNGs -- Logos need to be monochromatic hex #efefef -- 260 pixels wide x 147 pixels tall -- 1x logo center aligned - -Feed Example: - -```json -{ - "liveFeeds": [ - { - "id": "providerx-live", - "title": "Provider X Live", - "content": { - "dateAdded": "2019-06-01", - "language": "en", - "schedule": [ - { - "id": "movie-id-1", - "durationInSeconds": 7200, - "isLive": false, - "date": "2018-04-05", - "times": [ - "10:00:00" - ] - }, - { - "id": "episode-id-1", - "durationInSeconds": 7200, - "isLive": false, - "date": "2018-04-05", - "times": [ - "12:00:00", - "16:00:00" - ] - }, - { - "id": "shortformvideo-id-1", - "durationInSeconds": 7200, - "isLive": false, - "date": "2018-04-05", - "times": [ - "14:00:00" - ] - }, - { - "id": "tvspecial-id-1", - "durationInSeconds": 7200, - "isLive": true, - "date": "2018-04-05", - "times": [ - "18:00:00" - ] - }, - { - "id": "movie-id-2", - "durationInSeconds": 3600, - "isLive": false, - "date": "2018-04-05", - "times": [ - "20:00:00" - ] - }, - { - "id": "movie-id-3", - "durationInSeconds": 7200, - "isLive": false, - "date": "2018-04-05", - "times": [ - "21:00:00" - ] - } - ] - }, - "thumbnail": "https://.jpg", - "shortDescription": "Live business and national news, with top executives interviews and coverage of the technologies transforming our lives and economy.", - "longDescription": "Live business and national news, with top executives interviews and coverage of the technologies transforming our lives and economy." - } - ], - "movies": [ - { - "id": "movie-id-1", - "title": "Between Worlds", - "externalIds": [ - { - "id": "MV015001100000", - "idType": "TMS" - } - ] - }, - { - "id": "movie-id-2", - "title": "Between Worlds 2", - "thumbnail": "https://.jpg", - "shortDescription": "A truck driver whose life spirals out of control after the spirit of his deceased wife comes to life.", - "releaseDate": "1999-02-13", - "advisoryRatings": [ - { - "source": "MPAA", - "value": "R" - }, - { - "source": "CPR", - "value": "14+" - } - ], - "genres": [ - "animals", - "animated", - "fantasy" - ] - } - ], - "series": [ - { - "id": "series-id-1", - "title": "series1", - "seasons": [ - { - "seasonNumber": 6, - "episodes": [ - { - "id": "episode-id-1", - "title": "episode1", - "episodeNumber": 59 - } - ] - } - ] - } - ], - "tvSpecials": [ - { - "id": "tvspecial-id-1", - "title": "tvspecial1" - } - ], - "shortFormVideos": [ - { - "id": "shortformvideo-id-1", - "title": "shortformvideo1" - } - ] -} -``` - -## Kids-directed content - -“**Kids-Directed Content**” means content that either: (i) is directed to children as defined by the applicable law of the jurisdiction in which the content is shown (e.g., The Children's Online Privacy Protection Act); or (ii) was made for viewing primarily by children within the jurisdiction in which the content is shown. - -You may NOT submit or distribute Kids-Directed Content unless you have Roku’s express written approval. - -The following additional obligations apply to all Kids-Directed Content: - -| **Field** | **Type** | **Required** | **Description** | -| --------------- | ---------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| tags | string | Required | Include a "kidsdirected" tag into the tags string \* _all lowercase_
- This is how you flag to Roku that the content is Kids-Directed Content
- Do not include this tag in non-Kids-Directed Content | -| advisoryRatings | [Advisory Ratings Object](#advisoryratings-property) | Required | A parental rating for the content. (MPAA or TV Rating).
- 'Unrated' and "Not Rated" are not accepted ratings for Kids-Directed Content | - -The following additional obligations apply to all live linear streams that include Kids-Directed Content: - -- You will only include Kids-Directed Content in a live linear stream if that live linear stream is (and will always be) comprised exclusively of Kids-Directed Content. Do not mingle Kids-Directed Content and non-Kids-Directed Content in a live linear feed. -- You will provide a single TV content rating in the Rating Object reflecting the most restrictive rating of all Kids-Directed Content that will be available on the live linear feed. - -### Additional kidsdirected guidelines - -A `kidsdirected` tag should be inserted for any channel that is directed to children, based on a variety of factors, including the following: - -- Ratings which designate the content as designed to be appropriate for children - - Allowable ratings: Rating = TVPG, PG, TVY, TVY7, TVG, G - - TVY and TVY7 are reserved for kidsDirected channels only -- Content subject matter (e.g., teaching the alphabet) -- Visual content (e.g., unicorns) -- Use of animated characters (e.g., My Little Pony) -- Child-oriented activities and incentives -- Music or other audio content designed for children (e.g., nursery rhymes) -- Young age of models (e.g., toddlers) -- Presence of child celebrities or celebrities who appeal to children -- Language or other characteristics of the content that target children -- Whether advertising appearing with the content is directed to children -- Whether your intended audience for the content is children -- Whether you have competent and reliable empirical evidence that your audience composes primarily of children - -## Content properties - -### content Property - -Child object of property: - -- `liveFeed` - -This object represents the details about the liveFeed - -| **Field** | **Type** | **Required** | **Description** | -| ------------------- | ----------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| dateAdded | string | Required | The date the liveFeed was added to the library in the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}T\{hh\}:\{mm\}:\{ss\}+\{TZ\}. E.g.: 2015-11-11T22:21:37+00:00 This information is used to generate the “Recently Added” category. | -| language | string | Required | The language in which the feed is intended (e.g., “en”, “en-US”, “es”, etc). ISO 639 alpha-2 or alpha-3 language code string. | -| validityPeriodStart | string | Optional | The date when the content should become available in the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}T\{hh\}:\{mm\}:\{ss\}+\{TZ\}. E.g.: 2015-11-11T22:21:37+00:00 | -| validityPeriodEnd | string | Optional | The date when the content is no longer available in the [ISO 8601](http://www.iso.org/iso/home/standards/iso8601.htm) format: \{YYYY\}-\{MM\}-\{DD\}T\{hh\}:\{mm\}:\{ss\}+\{TZ\}. E.g.: 2015-11-11T22:21:37+00:00 | -| schedule | [Schedule Object](#schedule-object) | Required | A chronological listing of program start times and durations referencing objects in other content type sections (movies, series, shortFormVideos, tvSpecials) | - -Content Object Example: - -```json -{ - "dateAdded": "2015-11-11T22:21:37+00:00", - "language": "es", - "schedule": [...], - "validityPeriodStart": "2020-03-13", - "validityPeriodEnd": "2100-03-12" -} -``` - -### Genres property - -The following genres are supported: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 1. - - 2. - - 3. - - 4. - - 5. - - 6. -
- - action - - action sports - - adventure - - aerobics - - agriculture - - animals - - animated - - anime - - anthology - - archery - - arm wrestling - - art - - arts/crafts - - artistic gymnastics - - artistic swimming - - athletics - - auction - - auto - - auto racing - - aviation - - awards - - badminton - - ballet - - baseball - - basketball - - 3x3 basketball - - beach soccer - - beach volleyball - - biathlon - - bicycle - - bicycle racing - - billiards - - biography - - blackjack - - bmx racing - - boat - - boat racing - - - bobsled - - bodybuilding - - bowling - - boxing - - bullfighting - - bus./financial - - canoe - - card games - - ceremony - - cheerleading - - children - - children-music - - children-special - - children-talk - - collectibles - - comedy - - comedy drama - - community - - computers - - canoe/kayak - - consumer - - cooking - - cricket - - crime - - crime drama - - curling - - cycling - - dance - - dark comedy - - darts - - debate - - diving - - docudrama - - documentary - - dog racing - - dog show - - dog sled - - drag racing - - drama - - - educational - - entertainment - - environment - - equestrian - - erotic - - event - - exercise - - fantasy - - faith - - fashion - - fencing - - field hockey - - figure skating - - fishing - - football - - food - - fundraiser - - gaelic football - - game show - - gaming - - gay/lesbian - - golf - - gymnastics - - handball - - health - - historical drama - - history - - hockey - - holiday - - holiday music - - holiday music special - - holiday special - - holiday-children - - holiday-children special - - home improvement - - horror - - horse - - - house/garden - - how-to - - hunting - - hurling - - hydroplane racing - - indoor soccer - - interview - - intl soccer - - judo - - karate - - kayaking - - lacrosse - - law - - live - - luge - - martial arts - - medical - - military - - miniseries - - mixed martial arts - - modern pentathlon - - motorcycle - - motorcycle racing - - motorsports - - mountain biking - - music - - music special - - music talk - - musical - - musical comedy - - mystery - - nature - - news - - newsmagazine - - olympics - - opera - - outdoors - - parade - - - paranormal - - parenting - - performing arts - - playoff sports - - poker - - politics - - polo - - pool - - pro wrestling - - public affairs - - racquet - - reality - - religious - - ringuette - - road cycling - - rodeo - - roller derby - - romance - - romantic comedy - - rowing - - rugby - - running - - rhythmic gymnastics - - sailing - - science - - science fiction - - self improvement - - shooting - - shopping - - sitcom - - skateboarding - - skating - - skeleton - - skiing - - snooker - - snowboarding - - snowmobile - - soap - - - soap special - - soap talk - - * soccer - * softball - * special - * speed skating - * sport climbing - * sports - * sports talk - * squash - * standup - * sumo wrestling - * surfing - * suspense - * swimming - * table tennis - * taekwondo - * talk - * technology - * tennis - * theater - * thriller - * track/field - * track cycling - * travel - * trampoline - * triathlon - * variety - * volleyball - * war - * water polo - * water skiing - * watersports - * weather - * weightlifting - * western - * wrestling - * yacht racing -
- -### ExternalIds property - -Child object of property: - -- `movie` -- `series` -- `series -> episodes -> episode` -- `series -> seasons -> episodes -> episode` -- `shortFormVideo` -- `tvSpecial` - -This object represents a third-party metadata provider ID (such as TMS, Rovi, IMDB, EIDR) that can provide more information about a specific video content. This metadata optimizes the opportunity for your content to be discovered by Roku search and to provide more details to users. - -| **Field** | **Type** | **Required** | **Description** | -| --------- | -------- | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| id | string | Required | The third-party metadata provider ID for your video content. For example, in the case of IMDB you would use the last part of the URL of a movie such as "[http://www.imdb.com/title/tt0371724](http://www.imdb.com/title/tt0371724)". | -| idType | enum | Required | Must be one of the following:
- TMS – A Tribune Metadata Service ID for the content. Roku recommends using TMS and will associate these IDs for you.
- ROVI - A Rovi ID for the content
- IMDB – An Internet Movie Database ID
- EIDR – An Entertainment Identifier Registry ID | - -External IDs Object Example: - -``` -{ "id": "123456789", "idType": "TMS" }, - -{ "id": "tt0371724", "idType": "IMDB" }, - -{ "id": "10.5240/48A5-E3C5-6B11-D874-FD2B-V", "idType": "EIDR" } -``` - -### AdvisoryRatings property - -Child object of property: - -- `movie` -- `series -> episodes -> episode` -- `shortFormVideo` -- `tvSpecial` -- `livefeed` - -This object represents the ratings across multiple territories for the video content. You can define the parental rating, as well as the source (USA Parental Rating, UK Content Provider, etc). See Parental Ratings and Rating Sources for acceptable values. - -| Field | Type | Required | Description | -| ------ | ---- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| value | enum | Required | Must be a value listed in [Parental Ratings](#accepted-parental-ratings) .
Do not include any content targeted specifically to children. | -| source | enum | Required | Must be one or more of the following:
- BBFC\*\*
- CHVRS
- CPR
- MPAA
- USA_PR
- RTC
- ACB
- CLASSIND | - -UK content - rating is required\*\*. If there is no BBFC rating, please note a content rating of 'NR' - -Rating Object Example: - -``` -"advisoryRatings": [ - { - "source": "MPAA", - "value": "PG13" - }, - { - "source": "CPR", - "value": "14+" - } - ], -``` - -### Accepted parental ratings - -The following parental ratings can be used to better help your viewers find age-appropriate content. - -Note: No content can be targeted specifically to children. No pornographic or porn industry-related content is allowed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Source - - USA_PR (USA Parental Rating) - - MPAA (Motion Picture Association of America) - - CHVRS (Canadian Home Video Rating System) - - CPR (Canadian Parental Rating) -
- Rating - - - TV-Y
- TVY
- TV-Y7
- TVY7
- TV-G
- TVG
- TV-PG
- TVPG
- TV-14
- TV14
- TV-MA
- TVMA - 		- - G
- PG
- PG13
- PG-13
- R
- NC-17
- NC17
- UR - 		- - G
- PG
- 14A
- 14-A
- 18A
- 18-A
- R
- E - 		- - 14+
- 18+
- C
- C8
- C-8
- G
- PG
- E -
- **Source** - - **RTC (General Directorate of Radio Television and Cinematography) - Mexico** - - **BBFC (British Board of Film Classification)** - - **ACB (Australian Classification Board)** - - **CLASSIND (Classificação Indicativa) - Brazil** -
- Rating - - - AA
- A
- B
- B-15
- B15
- C
- D - 		- - U
- PG
- 12A
- 12-A
- 12
- 15
- 18
- R18
- R-18 - 		- - E
- G
- PG
- M
- MA 15+
- R 18+
- X 18+
- AV 15+
- C
- NC
- RC - 		- - L
- 10
- 12
- 14
- 16
- 18
- AL
- A10
- A12
- A14
- A16
- A18 -
- -### Rating source property - -These are the accepted values for the `ratingSource` property: - -- BBFC - British Board of Film Classification -- CHVRS - Canadian Home Video Rating System -- CPR - Canadian Parental Rating -- MPAA - Motion Picture Association of America -- USA_PR - USA Parental Rating -- RTC - General Directorate of Radio Television and Cinematography - Mexico -- ACB - Australian Classification Board -- CLASSIND - Classificação Indicativa - Brazil - -### Credit property - -Child object of property: - -- `movie` -- `series` -- `series -> episodes -> episode` -- `shortFormVideo` -- `tvSpecial` - -This object represents a single person in the credits of a video content. - -| Field | Type | Required | Description | -| ----- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| name | string | Required | name of the person | -| role | enum | Required | role of the person - must be one of the following values:
- actor
- anchor
- host
- narrator
- voice
- director
- producer
- screenwriter | - -Credit Object Example: - -``` -{ - "name": "Douglas N. Adams", - "role": "screenwriter", - "birthDate": "1952-03-11" -} -``` diff --git a/docs/THE ROKU CHANNEL/overview.md b/docs/THE ROKU CHANNEL/overview.md deleted file mode 100644 index ad3fe560..00000000 --- a/docs/THE ROKU CHANNEL/overview.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: The Roku Channel overview -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -At Roku, we believe that all TV will be streamed. Everything we do is rooted in this vision to ultimately make TV better for everyone. New shows, additional kinds of content, better product offerings, and smarter algorithms have attracted enthusiastic fans who are tuning into The Roku Channel more and more each month. - -Our goal is to encourage the success of partners on The Roku Channel with massive reach and viewership, free and subscription services that continue to drive growth, and solutions for publishers to drive monetization across TV streaming and linear TV. - -If you’re interested in becoming a Roku Channel partner, please complete our [distribution inquiries](https://airtable.com/shrlPRfkLW3UWDGo1) form. - -**Scale and distribution** - -* The Roku Channel now reaches ~145 million streamers in U.S. households (2025) -* Roku is rapidly expanding across the globe -* \#1 DTC app distributor - -**Growth** - -* Expand reach via The Roku Channel, a top 5 AVOD channel with linear and premium subscription models -* Constantly evolving UI experience drives content discovery -* Full-funnel marketing, automation, and advanced measurement tools to boost audience growth - -**Monetization** - -* Maximize ad supply and grow revenue through OneView, Dynamic Linear Ads, audience insights, and more -* Best in-class payments system that leverages Roku Pay to drive acquisition and reduce churn diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/_order.yaml b/docs/THE ROKU CHANNEL/roku-content-partner-portal/_order.yaml deleted file mode 100644 index 723a5642..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/_order.yaml +++ /dev/null @@ -1,3 +0,0 @@ -- roku-content-partner-portal-dashboard -- roku-content-partner-portal-analytics -- roku-content-partner-portal-key-features diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/index.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/index.md deleted file mode 100644 index d9a1c671..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/index.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: Roku Content Partner Portal -excerpt: Overview -deprecated: false -hidden: false -metadata: - robots: index -next: - description: Begin your experience from the Roku Content Partner Portal dashboard - pages: - - slug: roku-content-partner-portal-dashboard - title: Dashboard - type: basic ---- -The Roku Content Partner Portal is a self-service platform designed to give you greater visibility, control, and efficiency in managing your content lifecycle on The Roku Channel. It serves as a centralized destination where you can track the status of titles, monitor key milestones, access analytics to understand performance and engagement, and manage storefront and creatives marketing for Premium Subscriptions—all without relying on manual support or back-and-forth communication. - -
- - - -
- -# What the portal enables - -At its core, the Roku Content Partner Portal is built to simplify how you interact with Roku’s content operations, and marketing. Instead of operating through fragmented tools or delayed updates, you can: - -* **Track title status in real time** across the full lifecycle, from ingestion through availability and expiration -* **Understand processing outcomes** with clear, actionable status indicators -* **Identify issues early** such as failed or unfulfilled deliveries -* **Monitor rights windows and availability** across territories -* **Access a consolidated view** of all titles in one place -* **Manage storefront and creative marketing** to control how content appears and is promoted for your Premium Subscriptions on The Roku Channel -* **Access analytics** to gain insights on content performance, viewership trends, and engagement - -This transparency reduces uncertainty and empowers your teams to take action faster. - -
- -# Why it matters - -Historically, you have depended on manual workflows, support tickets, or internal contacts to understand what is happening with your content. This slows down decision-making and creates unnecessary operational overhead. - -The Roku Content Partner Portal shifts that model by: - -* Reducing dependency on support teams -* Improving turnaround time for issue resolution -* Providing consistent and reliable data -* Enabling you to self-serve critical insights - -The result is a more scalable and efficient partnership model. - -
- -# Who this is for - -The portal is designed for business, operation, and marketing stakeholders within your organizations who need visibility into content performance, delivery, and marketing status. This includes teams responsible for: - -* Content and operations teams -* Business and strategy teams -* Marketing and merchandising teams -* Partner account management - -To get started, users must have the appropriate access role, typically **business manager**, **operations manager**, **marketing manager**, or **analytics** — assigned by one of your company’s account administrators. - -
- -# Portal layout - - - -
- -| Key | Page component | -| ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **A** | **Documentation and help guides:** Access the Content Partner documentation space, including feature guides and help topics. | -| **B** | **Contact us _(partner support)_:** Opens support options for reaching out to Roku for assistance. | -| **C** | **Dashboard navigation _(top nav)_:** Navigates to the main Dashboard view from the top navigation bar. | -| **D** | **Profile** – Provides access to user profile settings and account-related options. | -| **E** | **Licensor switcher _(if applicable)_:** Allows users to switch between licensors within the same organization to view associated titles. | -| **F** | **Dashboard navigation _(left nav)_:** Navigates to the Dashboard using the left-hand navigation panel. | -| **G** | **Switch accounts:** Allows you to switch between different accounts you may have access to. | -| **H** | **Partner guide:** Access the Content Partner documentation space, including feature guides and help topics. | -| **I** | **Feature pages:** The main application workspace where selected features are displayed and interacted with. This area updates based on navigation and is where you view and manage feature-specific data, such as Title Status, Storefront, Creatives, and more. | -| **J** | **Collapse left navigation** Toggles the visibility of the left-hand navigation panel to expand workspace. | - -
- -# Getting started - -Access to the portal requires a Roku account. You can sign in or create an account at: [https://my.roku.com/signin](https://my.roku.com/signin) - -Once signed in, you can access the [Roku Launchpad](https://developer.roku.com/dev/landing) to explore available tools. Access to the portal itself must be granted before you see it in the Roku Launchpad. - -* Ask your company's administrator to grant access based on your responsibilities. - Contact your internal team if you are not sure who your administrator is. - -
- -The Roku Content Partner Portal represents a shift toward greater transparency and operational independence, giving you the tools you need to manage your content with confidence and speed. diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-analytics.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-analytics.md deleted file mode 100644 index 98e294a6..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-analytics.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -title: Analytics -excerpt: Overview -deprecated: false -hidden: false -metadata: - robots: index -next: - description: Explore key features available in the Roku Content Partner Portal - pages: - - slug: roku-content-partner-portal-key-features - title: Key features - type: basic ---- -The analytics section provides insights into how your content and storefront experiences are performing on The Roku Channel. It helps you understand audience engagement, measure the impact of merchandising decisions, and identify opportunities to optimize your catalog and promotions. - -
- -# Who this is for - - - ## Access and availability - - Analytics reports and metrics vary based on your partner type and subscription level. Not all data is available to all partners. - - For example, merchandising and storefront performance insights are only available to Premium Subscription partners, since these features are tied to storefront and promotional capabilities that are exclusive to that tier. - - If you do not see certain reports or metrics in your analytics view, it is likely due to your current access level or report eligibility. - - -The analytics section is designed for stakeholders who need visibility into content performance and audience behavior, including: - -* Business and strategy teams -* Content and operations teams -* Marketing and merchandising teams - -
- -# What you can do - -Use analytics to: - -* **Monitor performance trends:** Track how your titles and storefront are performing over time. -* **Measure audience engagement:** Understand how users are interacting with your content, including viewing behavior and discovery patterns. -* **Evaluate merchandising impact:** Assess how featured placements, pinned titles, and promotional assets influence performance. -* **Identify optimization opportunities:** Spot underperforming titles or campaigns and take action to improve results. - -
- -# How it works - -Analytics data is organized into dashboards and visualizations designed to give you both a high-level overview and deeper insights. - -Depending on your access level, you may be able to: - -1. **View summary metrics:** Get a snapshot of overall performance across your catalog. -2. **Filter and segment data:** Refine insights by territory, time range, or specific titles. -3. **Drill into detailed views:** Explore performance at the title or campaign level. -4. **Track changes over time:** Compare performance before and after merchandising or content updates. - -
- -# Key metrics you may see - -Analytics includes a range of reports that surface performance across different business models, including AVOD, SVOD, Live, and FAST. The specific reports and metrics available to you will depend on your partner type, subscription tier, and report eligibility. - -Below is an overview of the types of insights available: - -* **Streaming activity:** How much content is being watched (streaming hours, stream starts). -* **Audience engagement:** How consumers interact with content (starts, completion rates, session duration). -* **Content performance:** Which titles, episodes, or channels are driving viewership and retention. -* **Platform and distribution:** Where and how consumers are watching (device, platform, channel, or storefront). -* **Subscriber behavior:** How consumers convert, retain, and churn across subscription offerings _(Premium Subscriptions only)_. - -
- -# Getting access - -To use this feature, get the appropriate role assigned to your account. - -1. Request **analytics** access from your company’s account administrator. -2. Ask your administrator to grant access based on your responsibilities, such as understanding performance of your content. -3. Contact your internal team if you are not sure who your administrator is. - -
- -# Tips for getting the most value - -* Regularly review performance trends to stay ahead of changes in audience behavior -* Use filters to isolate what is driving performance in specific territories or time periods -* Pair analytics insights with storefront updates to continuously improve engagement -* Focus on a small set of key metrics to guide decisions rather than tracking everything at once \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-dashboard.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-dashboard.md deleted file mode 100644 index a0320737..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-dashboard.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Dashboard -excerpt: Overview -deprecated: false -hidden: false -metadata: - robots: index -next: - description: Explore key features available in the Roku Content Partner Portal - pages: - - slug: roku-content-partner-portal-key-features - title: Key features - type: basic ---- -The dashboard is your starting point in the Roku Content Partner Portal. It introduces the platform and provides quick access to key features based on your account permissions. - -![Dashboard](https://files.readme.io/b3632282cab88d72778dd09fb8a0fc358816ea0f8670be69a8cbd2ffba838d0e-image.png) - -
- -# The Roku Channel content partner program - -The Roku Content Partner Portal supports The Roku Channel content partner program, which provides tools to directly manage your content on The Roku Channel. This includes managing your brand presence, promotional assets, and subscription offerings. - -
- -# Navigate with feature cards - -Depending on your role and access level, the dashboard displays feature cards that link directly to available areas of the portal. - -Use these cards to quickly: - -* Access specific features -* Jump into workflows relevant to your role -* Navigate the portal efficiently without needing to browse through menus - - - If you do not see a feature card, your account may not have access. Contact your company administrator to request additional permissions. - - -
\ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/_order.yaml b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/_order.yaml deleted file mode 100644 index b82e127d..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/_order.yaml +++ /dev/null @@ -1,3 +0,0 @@ -- roku-content-partner-portal-title-tracking-status -- roku-content-partner-portal-storefront -- roku-content-partner-portal-creatives diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/index.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/index.md deleted file mode 100644 index 8184d2c8..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/index.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Key features -excerpt: Explore available features in the Roku Content Partner Portal -deprecated: false -hidden: false -metadata: - robots: index -next: - description: Explore the features that are relevant to you. ---- -The Roku Content Partner Portal brings together the core tools you need to manage, monitor, and promote your content on The Roku Channel. Each feature is designed to give you greater visibility, control, and flexibility across your content lifecycle. - -
- - - -
- -# Title tracking status - -Track the progress of your content from delivery through publication. Title tracking status provides clear visibility into where each title is in the Roku content pipeline, helping you quickly identify delays, resolve issues, and stay aligned with launch timelines. - -Want to learn more, check out [Title tracking status](doc:roku-content-partner-portal-title-tracking-status). - -# Storefront - -Manage how your content is presented to consumers. The storefront feature allows you to curate featured titles, pin content for promotion, and influence merchandising within your channel experience to drive engagement. - - - Available only to eligible Premium Subscription partners. - - -Want to learn more, check out [Storefront](doc:roku-content-partner-portal-storefront). - -# Creatives - -Upload and manage the assets that represent your content. Creatives allows you to upload and manage brand assets such as tiles, banners, and call-to-action (CTA) images, as well as manage subscription offer creatives like side cards to support merchandising and promotion. - - - Available only to eligible Premium Subscription partners. - - -Want to learn more, check out [Creatives](doc:roku-content-partner-portal-creatives). - -
- -Together, these features provide a centralized, self-service experience that helps you operate more efficiently and maximize the impact of your content on The Roku Channel. - -
diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-creatives.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-creatives.md deleted file mode 100644 index 176caab0..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-creatives.md +++ /dev/null @@ -1,126 +0,0 @@ ---- -title: Creatives -excerpt: Overview -deprecated: false -hidden: false -metadata: - robots: index ---- -The creatives section is where you manage a limited set of publisher-level visual assets used across The Roku Channel subscription experience. - - - Available only to eligible Premium Subscription partners. - - -These assets are not title specific. Instead, they represent your service branding and are displayed in key consumer journeys such as subscription entry points and publisher collection pages. - -At this stage, creative control is intentionally scoped to a small number of high-impact assets to ensure consistency across the platform. - -
- - - -
- -# Who this is for - -Creatives is available to eligible content partners who manage **Premium Subscription** storefronts on The Roku Channel. - -This feature is intended for users responsible for maintaining brand consistency and subscription presentation, including: - -* Marketing teams managing service-level branding -* Merchandising teams optimizing subscription entry points -* Business stakeholders responsible for subscription performance - -
- -# What you can manage - -Currently, the creatives section supports management of the following assets: - -## CTA banner - -A large banner displayed within the publisher collection home that promotes your service and encourages users to take action. - -* Used for subscription discovery and engagement -* Supports high-visibility promotional messaging -* One asset per service and territory - -Specifications: - -* Size: 1538 × 424 -* Format: JPEG - -## Partner tile (4:3) - -A core brand tile used across multiple surfaces, including subscription and trial initiation screens, as well as grid placements. - -* Represents your service in UI surfaces -* Must be clear and recognizable at smaller sizes -* One asset per service and territory - -Specifications: - -* Size: 540 × 405 -* Format: JPEG - -
- -# How it works - -1. **Select Context:** Choose the **Service** and **Territory** to manage creatives for that specific configuration. -2. **View Current Assets:** Review the currently published images for each creative type. -3. **Upload New Assets:** Drag and drop or browse to upload a replacement image. -4. **Update:** Apply changes to replace the existing creative. - -
- -# Important limitations - -Creative management is currently limited to: - -* One CTA banner per service and territory -* One partner tile per service and territory -* No support for multiple variants, A/B testing, or scheduling - -This means updates will immediately replace the existing asset and apply universally within that context. - -
- -# Creative guidelines - -All assets must meet Roku’s branding and technical requirements. For full specifications, safe zones, and design recommendations, refer to the official documentation: - -* CTA Banner Guidelines -* Partner Tile (4:3) Guidelines - -Failure to meet these requirements may result in assets being rejected or rendered incorrectly in the UI. - -
- -# Why it matters - -These creatives directly impact how consumers perceive your service and whether they choose to subscribe. Strong, clear visuals: - -* Improve brand recognition -* Increase click-through rates on subscription entry points -* Drive higher conversion - -
- -# Best practices - -* Keep branding simple and legible, especially for smaller tile formats -* Avoid cluttered layouts or excessive text -* Ensure key messaging is centered and within safe zones -* Regularly refresh creatives to align with campaigns or seasonal promotions - -
- -# Getting access - -To use this feature, get the appropriate role assigned to your account. - -1. Request **marketing manager** access from your company’s account administrator. -2. Ask your administrator to grant access based on your responsibilities, such as storefront and creative management. -3. Contact your internal team if you are not sure who your administrator is. diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-storefront.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-storefront.md deleted file mode 100644 index d0a2eb2c..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-storefront.md +++ /dev/null @@ -1,194 +0,0 @@ ---- -title: Storefront -excerpt: Overview -deprecated: false -hidden: false -metadata: - robots: index -next: - description: Interested in managing your creatives? We have that too! - pages: - - slug: roku-content-partner-portal-creatives - title: Creatives - type: basic ---- -Storefront allows you to manage the featured row on your channel storefront directly within the Roku Content Partner Portal. - - - Available only to eligible Premium Subscription partners. - - -By default, the featured row is populated by Roku’s recommendation system to deliver personalized content to viewers. With Storefront, you can pin titles to specific positions for a defined period of time, ensuring key content is prominently displayed. - -Pinned titles appear alongside Roku recommendations, giving you a balance of control and automated optimization to keep your storefront engaging and relevant. - - - **Tip:** The featured row works best when used sparingly. Pin a small number of high-impact titles for short durations to maximize visibility and engagement. - - -
- - - -
- -# Who this is for - -Storefront is available to eligible content partners who manage **Premium Subscription** storefronts on The Roku Channel. - -This feature is designed for teams responsible for marketing, merchandising, and audience growth, enabling them to control how titles are promoted within their Premium Subscription pages. - -If your organization has a Premium Subscription storefront but does not yet have access to this feature, reach out to your Partner Support team to express interest. - -
- -# Getting access - -To use this feature, get the appropriate role assigned to your account. - -1. Request **marketing manager** access from your company’s account administrator. -2. Ask your administrator to grant access based on your responsibilities, such as storefront and creative management. -3. Contact your internal team if you are not sure who your administrator is. - -
- -# Key concepts - -## Featured row - -The top row on your channel storefront. This row is fixed in position and highlights promoted content. - -## Pinned titles - -Titles you assign to specific positions in the Featured row. These override recommendation-driven placements. - -## Scheduled pins - -Titles configured to appear during a defined start and end time. - -## Recommendation-filled positions - -Any positions not pinned are automatically filled by Roku’s recommendation system to ensure a complete row. - -## Eligible titles - -Only titles that are production-ready, have valid availability dates, and include required metadata and artwork can be pinned. - -
- -# Page layout - -The storefront interface is designed to help you quickly view, manage, and update your Featured row. - - - -
- -| Key | Page component | -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **A** | **Feature navigation:** Displays the available features within the portal and allows users to switch between them. Organizes functionality into sections so users can quickly access different areas such as Title Tracking, Storefront, Creatives, and more. | -| **B** | **Service field:** Select the Premium Subscription service you want to manage. If you only have access to one service, it is automatically selected. | -| **C** | **Territory field:** Choose the territory (channel store) you want to view or edit. Each territory has its own independent Featured row configuration. | -| **D** | **Feature description:** Displays a brief description of the feature, explaining its purpose, how it should be used, the actions available, and any guidance to help you get the most value from it. | -| **E** | **Date range filter:** Filter the Featured row to view which titles are active or scheduled within a selected date or date range. | -| **F** | **Today:** Quickly return to the current date view to see which titles are pinned today. | -| **G** | **Date navigation cards:** Browse Featured row configurations across different dates. Each card represents a specific date or time period, showing the titles pinned during that window. | -| **H** | **Pinned titles search field:** Enables searching for titles by name. | -| **I** | **Pinned titles filter panel:** Provides filtering options to refine the pinned title list based on selected criteria. | -| **J** | **Pin title control:** Add a title to the Featured row by selecting its position and, if needed, defining when it should be active. | -| **K** | **Collapse left navigation:** Toggles the visibility of the left-hand navigation panel to expand workspace. | -| **L** | **Pinned titles table:** Displays detailed information for each pinned title, including status, position, availability dates, actions, and more. | -| **M** | **Pinned title action control:** Manage an existing pinned title by editing its position or schedule, or removing it from the Featured row. | - -
- -# What you can do - -## Manage the featured row - -View and edit all titles currently pinned in your Featured row, including their positions and metadata. - - - -## Filter pinned titles - -Filter pinned titles by content type, status, and position. - - - -## Pin titles to specific positions - -Assign titles to fixed positions (for example, position #1 or #5) to control layout and visibility. - -![](https://files.readme.io/5faab399ba9ffdbd22fb86b5e556fa0103a163e0e86ec39937d0281a7873c8b3-image.png) - -## Schedule featured titles - -Plan ahead by scheduling titles to go live or expire at specific dates and times. You can also view which titles will be active on any future date or date range. - -## Customize by territory - -Configure different featured rows per territory (channel store). Changes made in one territory do not affect others. - -## Search and select eligible titles - -Search for titles that are eligible to be featured, including movies, TV series, TV specials, sports events, and linear channels. - - - -## Recommendation-filled positions - -Any positions not pinned are automatically filled by Roku’s recommendation system to ensure a complete and personalized row. - -## Track changes and ownership - -See who created or last modified each pinned title, providing visibility across your team. - -
- -# How it works - -1. Select a Premium Subscription service (if applicable) - 1. If you manage multiple services, choose which storefront you want to manage - 2. If you only have one service, it is automatically selected -2. Select a territory (if applicable) - 1. Choose the territory you want to manage (for example, US, UK, etc.) -3. View current pinned titles in the Featured row -4. Search and select eligible titles -5. Pin titles to positions or schedule them for future dates -6. Preview your changes -7. Publish updates (changes take effect immediately) - -
- -# System rules and limits - -To maintain a consistent storefront experience, the following rules apply: - -* A Featured row contains up to 40 titles -* Duplicate titles are not allowed -* Only eligible titles can be pinned -* Conflicting pins (same position or overlapping schedules) must be resolved before publishing -* Scheduled pins cannot exceed the 40-title limit at any given time - -If these conditions are not met, the system will block publishing until issues are resolved. - - - - - -
- -
- -# Best practices - -* Focus on a small number of high-impact titles rather than filling the entire row -* Pin no more than 5 titles at a time to maintain effectiveness -* Limit pin duration to no more than 3 days to keep content fresh -* Align pinned titles with key moments such as launches, promotions, or live events -* Use scheduling to plan ahead rather than making last-minute changes -* Preview changes before publishing to avoid conflicts -* Regularly refresh your Featured row to maintain engagement - -
diff --git a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-title-tracking-status.md b/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-title-tracking-status.md deleted file mode 100644 index 6f9301e4..00000000 --- a/docs/THE ROKU CHANNEL/roku-content-partner-portal/roku-content-partner-portal-key-features/roku-content-partner-portal-title-tracking-status.md +++ /dev/null @@ -1,555 +0,0 @@ ---- -title: Title tracking status -excerpt: Overview -deprecated: false -hidden: false -metadata: - robots: index -next: - description: >- - Title tracking issues for detailed diagnostics and resolution paths, coming - soon! ---- -Monitor where your titles are in The Roku Channel publishing pipeline and identify which titles need action. - -
- - - -
- -# Who this is for - -Use the **Title status** view if you are responsible for delivering or managing Video on Demand (VOD) content on **The Roku Channel**. - -This view is most useful for: - -## Operations managers (asset delivery) - -Use this view to: - -* Track asset delivery and processing progress -* Identify ingestion or processing failures -* Monitor titles blocked by asset-related issues - -Focus on these statuses: - -* **Unfulfilled**: Missing or unmatched assets -* **Failed**: Processing or QC issues -* **Processing**: Assets are actively being prepared - -## Business managers (rights delivery) - -Use this view to: - -* Track rights submission and approval status -* Monitor availability windows across territories -* Identify titles blocked by rights issues - -Focus on these statuses: - -* **Unfulfilled**: Missing or unmatched rights -* **Rights under review**: Pending approval -* **Expired**: Rights windows need updating - -
- -# Getting access - -To use this feature, get the appropriate role assigned to your account. - -1. Request **business manager** or **operations manager** access from one of your company’s account administrators. -2. Ask your administrator to grant access based on your responsibilities, such as rights management or asset delivery. -3. Contact your internal team if you are not sure who your administrator is. - -
- -# Page layout - - - -| Key | Page component | -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **A** | **Feature navigation:** Displays the available features within the portal and allows users to switch between them. Organizes functionality into sections so users can quickly access different areas such as Title Tracking, Storefront, Creatives, and more. | -| **B** | **Page header and feature description:** Displays the current page title and a brief description of the feature. Provides context on what the page is used for and what actions users can take. | -| **C** | **Title status cards:** Displays a summary of titles by status and acts as a primary filter for the table below. | -| **D** | **Title status table:** Displays detailed information for each title, including status, territories, availability dates, and more. | -| **E** | **Title status search field:** Enables searching for titles by name, series, or title ID. | -| **F** | **Title status filter panel:** Provides filtering options to refine the title list based on selected criteria. | -| **G** | **Collapse left navigation:** Toggles the visibility of the left-hand navigation panel to expand workspace. | - -
- -## How to use this page - -### 1. Select a licensor (if applicable) - -If your organization includes multiple licensors, use the dropdown in the top-left to switch views. - -* Only titles for the selected licensor are displayed. -* If you have a single licensor, this control is hidden. - -### 2. Use status cards as a primary filter - -At the top of the page, status cards let you quickly filter and assess your catalog. - -Available cards: - -* All titles -* Unfulfilled -* Failed -* Rights under review -* Processing -* Scheduled -* Live -* Expired - -Click any card to filter the table. - -
- - - -
- - - -
- -# How status is determined - -## How the **'All titles'** card works - -The **All titles** card shows every title in your catalog. - -For each title, the **Status** column reflects the **most restrictive condition** across all territories and components. - -This means: - -* A single blocking issue, such as **Failed** or **Unfulfilled**, overrides all other states. -* The status shown here represents the overall health of the title. - -### Status priority - -From most restrictive to least restrictive: - -1. Failed -2. Unfulfilled -3. Rights under review -4. Processing -5. Scheduled -6. Live -7. Expired - -**Examples** - -| Scenario | Result | -| --------------------------------------- | ----------- | -| Some territories Live, some Failed | Failed | -| Some territories Live, some Unfulfilled | Unfulfilled | -| Some territories Live, some Expired | Live | -| All territories Expired | Expired | - -### Why a title may show a restrictive status - -Even if most of a title is **Live**, a single **Failed** or **Unfulfilled** component overrides the overall status. - -Use the **Territories** panel to identify where the issue exists. - -
- -## How the other status cards work - -Each status-specific card, such as **Failed** or **Expired**, highlights titles that are actively in that state. - -A title appears in a status card if: - -* At least one territory matches that status, or -* At least one component matches that status - -**Example** - -* The **Expired** card shows any title that has at least one territory where availability has expired. -* The **Live** card shows any title that is live in at least one territory. - -
- - - A single title can appear in multiple status cards because status is evaluated at the territory level. Use **All titles** to see the rolled-up overall status. - - -Because status is evaluated at the territory level, a single title can appear under multiple cards. - -**Example** - -* **US** → Live -* **CA** → Scheduled -* **MX** → Expired - -This title appears in: - -* Live -* Scheduled -* Expired - -But in the **All titles** view, the **Status** column shows the most restrictive status. In this case, that status is **Scheduled**. - -
- -## Why this matters - -* Use **All titles** to understand overall readiness. -* Use individual status cards to find and act on specific conditions. -* Do not assume a title belongs to only one status. -* Expand the title to see where issues exist. - -
- -# What requires your attention - - - -## Unfulfilled - -> Waiting for ordered rights, assets, or a match between the two. Requires your attention. - -This means required inputs are missing or not linked by the same **Title ID**. - -**Action:** - -* Deliver rights and assets. -* Make sure the **Rights ID** and **Asset ID** match the same **Title ID**. - -## Failed - -> One or more issues occurred while processing your files and are preventing this title from going live. Requires your attention. - -This means blocking errors occurred during processing. - -**Action:** - -* Resolve the errors before the title can proceed. - -
- -# Understanding the title status table - -Each row represents a single title and its current status across territories. - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Column - - Description -
- **Title** - - Displays the title name. Includes your **Title ID**, which can be copied on click. Use the Title ID for support, troubleshooting, and internal tracking. -
- **Content type** - - Indicates the type of content. Each title has one type: -

-
    -
  • Movie
    • -
  • Short-form clip
    • -
  • TV episode
    • -
  • TV season
    • -
  • TV series
    • -
- - TV episodes are the actual playable titles. TV seasons and TV series are organizational levels used to group and structure episodes. Status, Territories, Expected start date, and Expected end date for seasons and series are rolled up from their underlying episodes. - -
- **License types** - - A title may have one or more license types, including **Ad-supported**, **Linear O&O FAST**, and **Premium subscription**. -
- **Services** - - A service represents how your content is distributed and monetized on The Roku Channel. Examples include **TRC AVOD**, **TRC O&O FAST**, or one of your own or participating Premium subscriptions such as **Howdy**. A single title may appear under multiple services depending on its rights. -
- **Status** - - Displays the overall status of the title, such as: -

-
-
Unfulfilled
-
Waiting for ordered rights, assets, or a match between the two. Requires your attention.
-
Failed
-
One or more issues occurred while processing your files and are preventing this title from going live. Requires your attention.
-
Rights under review
-
Rights are being reviewed for approval by the Roku team. Turnaround time may vary based on catalog volume.
-
Processing
-
The Roku pipeline is preparing your assets for publishing.
-
Scheduled
-
Ready for go-live as scheduled.
-
Live
-
The title is available to viewers.
-
Expired
-
Update windows to reactivate.
-
- - For multi-territory titles, you may see values like 1 of 3 unfulfilled, which means only some territories are impacted. - -
- **Territories** - - Displays the countries where the title is available or targeted. Territories appear as country flags and codes, such as **US**, **CA**, and **MX**. A title may be available in multiple territories, and status may vary by territory. -
- **Expected start date** - - Shows when the title is expected to become available. It reflects the next upcoming start date across all territories. If all start dates are in the past, it shows the most recent start date. Dates are based on your local timezone. -
- **Expected end date** - - Shows when the title is expected to expire. It reflects the next upcoming expiration date. If all dates are in the past, it shows the most recent expiration date. Dates are based on your local timezone. -
- -
- -## How to read a row - -![](https://files.readme.io/188a32cc62ee6f082b97470205b4753dae747e59eaac7bf0966cf4441df8d2c0-image.png) - -When reviewing a title: - -1. Start with **License types** by identifying how the title is licensed: - - * Ad-supported - * Linear O&O FAST - * Premium subscription - - This tells you what types of distribution the title is eligible for. -2. Next, review **Services** where the title will appear: - - * TRC AVOD - * TRC O&O FAST - * Premium Subscription services - - A title may be associated with multiple services depending on its rights. - - This helps you understand how and where the title will be surfaced to viewers. -3. Check the overall **Status** to understand overall readiness. -4. Review **Territories** to understand rights coverage. - - If the status shows something like “1 of 3 unfulfilled,” expand the row to identify which territories are impacted. -5. Finally, check the **Expected** timing: - - * **Expected start date** → When the title will become available - * **Expected end date** → When availability will expire - - These dates reflect: - - * The next upcoming change across all territories - * Your local time zone - - For TV content: - - * Expected start and end dates for a TV series (and seasons) are derived by rolling up dates from all associated TV episodes. - * This means the dates represent the earliest upcoming availability or expiration across all episodes. - - - A title can appear ready in one territory but blocked in another. The **Status** column shows the most restrictive condition across all territories. - To investigate territory-level differences, expand the row. - - -
- -## Default sorting - -By default, titles are sorted by the date they were added, with the most recently added titles shown first. - -For TV content, additional sorting rules apply: - -* TV seasons are ordered by **season number**. -* TV episodes are ordered by **episode number** within each season. - -This ensures that: - -* Episodes appear in the correct chronological sequence - -* Seasons and episodes display in a logical viewing order - - - -
- -## Using search and filters - -Use search and filtering to limit results and improve your focus. - - - -
- -### Use search to find a specific title - -* **Title name** -* **Series name** -* **Title ID** - -
- -### Use filters to narrow results - -* **Content type** -* **License type** -* **Service** -* **Territory** -* **Expected start period** - - This filter shows titles whose **Expected start date** falls within a selected timeframe. - - Available options: - - * Tomorrow - * This week - * This month - * Next week - * Next month - - Use this filter to: - - * Identify titles launching soon - * Prepare for upcoming releases - * Monitor near-term availability -* **Expected end period** - - This filter shows titles whose **Expected end date** falls within a selected timeframe. - - Available options: - - * Tomorrow - * This week - * This month - * Next week - * Next month - - Use this filter to: - - * Identify titles that are expiring soon - * Take action to extend availability - * Monitor upcoming expirations across your catalog - - - -These filters use the rolled-up **Expected start** and **Expected end** dates shown in the table. - - - * Filters apply to the full title list and update results immediately. - * A title appears if its date falls within the selected period. - - -
- -## Viewing status by territory - -Some titles have different statuses across channel store locations. - -To view details: - -1. Select the expand arrow next to a title. -2. The **Territories** panel appears. - -![](https://files.readme.io/2e946945e0dda50df1ef2efa2f1ed3e25349a976d13bdbcf4e60ea1e3f976d8e-image.png) - -### How to read the territories panel - -Each card shows: - -* Territory -* Status -* License type -* Availability window - -### Understanding mixed status - -**Example** - -**1 of 3 unfulfilled** - -This means: - -* Some territories are ready or live -* Others require action - -Use the panel to: - -* Identify affected territories -* Focus only where action is needed - -
- -# Common scenarios - -## Which titles need attention? - -Select **Unfulfilled** or **Failed**. - -Prioritize titles with **Errors**. - -## Why isn’t my title live? - -Check the status: - -* **Unfulfilled:** Missing or unmatched inputs -* **Failed:** Blocking errors -* **Processing** or **Rights under review:** Still in progress - - - If rights are missing, fields such as license types, services, territories, or expected dates may display as blank or `'-'`. This is expected until the required data is provided and matched. - - -
- -# Some final callouts - -* This view provides summary-level visibility only. -* Issue details are not shown here. -* A dedicated **Title tracking issues** view will be provided in the future for detailed diagnostics and resolution paths. -* Some fields may display `'-'` when data is unavailable. diff --git a/docs/THE ROKU CHANNEL/video-on-demand/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/_order.yaml deleted file mode 100644 index 38e89e2f..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/_order.yaml +++ /dev/null @@ -1,7 +0,0 @@ -- assets_and_branding -- copy-of-premium-subscriptions -- roku-originals -- delivery -- title-avail-specifications -- recs -- content-tags-metadata diff --git a/docs/THE ROKU CHANNEL/video-on-demand/assets_and_branding.md b/docs/THE ROKU CHANNEL/video-on-demand/assets_and_branding.md deleted file mode 100644 index 7a3766ba..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/assets_and_branding.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Premium Subscriptions -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## Premium Subscriptions on The Roku Channel - -## Assets & branding overview - -This document provides an overview of how your brand with appear within The Roku Channel and on the Roku Platform, assets needed for content merchandising and best practices to promote your content experience: - -[Premium Subscriptions on The Roku Channel - Partner Handbook Glow Up Edition](https://image.roku.com/ZHZscHItMTc2/PremiumSubscriptionPartnerGuide2026GlowUp.pdf) diff --git a/docs/THE ROKU CHANNEL/video-on-demand/content-tags-and-metadata.md b/docs/THE ROKU CHANNEL/video-on-demand/content-tags-and-metadata.md deleted file mode 100644 index 53430516..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/content-tags-and-metadata.md +++ /dev/null @@ -1,182 +0,0 @@ ---- -title: Content tags and metadata ---- -_The following document outlines best practices for using content tags and metadata for media ingest. Please see [ingest specifications](/trc-docs/video-on-demand/ingest-specifications.md#metadata-updates-mdu-and-file-replacements) for more._ - -We are often asked - how does the content appear on the Roku platform? The answer is almost always with metadata. - -BETTER is MORE - MORE isn't necessarily BETTER - -Due to Roku's propriety machine learning, we have enhanced personalization of all content offerings in the user interface. Different customers see different content categories based on their viewing behaviors and browse history. Utilizing standard Roku-provided tags will enable content to surface in more places across discovery products on the Roku platform and The Roku Channel. Without tags, limited visibility is likely - relegating content to fewer places. - -Quality tagging will help boost the right content to the right people and in more places. Our studies have shown that irrelevant (aka 'bad') tags decrease content performance because of mismatches and machine learning. (For example, Schindler's List is tagged with 'comedy' and surfaces in a comedy row. Assuming comedy seekers will not want such a title, that movie will likely underperform because the algorithm will 'learn' it is not a high engagement comedy title and will be deprioritized). - -## Roku recommendation: - -Include **at least 2 relevant Roku Provided Tags** from the menu below on _every_ piece of content delivered to Roku (i.e., Episodes, Movies, Series..). - -* You are welcome to add additional relevant or brand specific tags (not on the list) along with the aforementioned Roku required tags. (e.g., LGBTQ, classic, biography) -* For time-boxed, seasonal, or thematic collections, the Roku team will continue to create bespoke categories as requested in the monthly content refresh. (e.g., Halloween, Back to School, Mother's Day) -* Roku reserves the right to make changes to metadata if/when content is miscategorized. - -Examples: - -| Title | Baseline
(2 Roku tags)
Preferred | Rich Tags
(2 Roku Tags +)
Preferred | | Mismatched Tags -
Not Preferred | -| :--------------: | :----------------------------------------: | :----------------------------------------------------: | :-: | :----------------------------------: | -| Mean Girls | comedy
coming of age | comedy, coming of age, romantic comedy, leading ladies | | action, documentary | -| Schindler's List | drama
world war 2 | drama, world war 2, war, history, biography | | comedy, romance, action | -| Hoarders | reality tv
documentary | reality tv, documentary, bingeworthy | | romance, ensemble tv shows, cooking | - -Choose from the list of Roku tags: - -### **Core Tags** - -These are high (level 1) genres. - -* action -* adventure -* biography -* comedy -* crime -* documentary -* drama -* history -* horror -* mystery -* romance -* romantic -* comedy -* science fiction -* suspense -* thriller -* british tv -* classic tv -* comedies tv -* drama tv -* ensemble tv shows -* favorite tv dads -* favorite tv moms -* police tv -* reality tv -* tv - -### **Niche/Specific Tags** - -These are level 2 tags. Used to add an additional layer of description not covered from a Core Genre Tag. Needs to be at least 80 % of the content to be applicable. - -Examples: - -| Title | Core Tag | Niche Tag | -| ------------- | -------- | ------------- | -| Terminator | action | cyborgs | -| Downton Abbey | drama | period pieces | - -* aliens -* animals -* anime -* anthology -* apocalypse -* art -* autos -* baking -* baseball -* based on books -* basketball -* biopic -* bus financial -* collectibles -* comedy drama -* coming of age -* concerts -* cooking -* courtroom -* crime drama -* crime fighters -* cyborgs -* dance -* dark comedy -* diy -* docudrama -* drama movies -* dystopian -* entertainment -* environment -* espionage -* exercise -* faith and spirituality -* family dynamics -* fantasy -* fashion -* female directors -* film noir -* game show -* games -* gay lesbian -* health -* heartfelt -* historical drama -* home -* diy -* home / house / garden -* home improvement -* horses -* indies -* inspired by true events -* interview -* jazz -* korean war -* law -* leading ladies -* leading men -* lifestyle -* martial arts -* medical -* medical drama -* military -* miniseries -* music -* music docs bios -* musical -* musical comedy -* nature -* news -* outdoors -* paranormal -* period pieces -* police movies -* politics -* psychological thriller -* revenge -* science -* sitcom -* sketch comedy -* slashers -* sorcery -* space exploration -* sports -* sports talk -* standup -* supernatural -* survival -* talk -* technology -* thought provoking -* travel -* true crime -* mystery -* vampires -* vietnam war -* war -* werewolves -* western -* world war 1 -* world war 2 -* zombies - -Per the Ingest Spec: kidsdirected tag is REQUIRED for all kids directed movies and episodes - -### Examples of how Categories surface in the Roku user interface - -![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/MDU-Photo2.png) - -If you have any questions please reach out to [editorial@roku.com](mailto:editorial@roku.com) or [svod-editorial@roku.com](mailto:svod-editorial@roku.com) diff --git a/docs/THE ROKU CHANNEL/video-on-demand/copy-of-premium-subscriptions.md b/docs/THE ROKU CHANNEL/video-on-demand/copy-of-premium-subscriptions.md deleted file mode 100644 index 01457c1c..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/copy-of-premium-subscriptions.md +++ /dev/null @@ -1,361 +0,0 @@ ---- -title: Legacy Premium Subscriptions Page -deprecated: false -hidden: true -metadata: - robots: index ---- - -## Premium Subscriptions on The Roku Channel - -## Assets & branding overview - -This page provides an overview of how your brand with appear within The Roku Channel and on the Roku Platform, assets needed for content merchandising and best practices to promote your content experience. - -## Partner assets/deliverables - -There are a total of **15 assets** we will need from you: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DeliverablesExamples
Partner Tileroku400px - premium-asset-1
Logo (2 colors)roku400px - premium-asset-2 roku400px - premium-asset-3
CTA (Call to Action) Bannerroku400px - premium-asset-4
Side Card (2 sizes)roku400px - premium-asset-5
Shortcut Tile (2 sizes)roku400px - premium-asset-6
On-Device Bannerroku400px - premium-asset-7
On-Device Screensaver (2 sizes)roku400px - premium-asset-9

roku400px - premium-asset-8
:30 Promo Videoroku400px - premium-asset-10
Subscriptions Details Copyroku600px - premium-asset-11
Back of Back Copyroku600px - premium-asset-12
- - -## Asset details - -Below is a list of details, best practices, and dimensions sizes for each partner asset/deliverable that are required for content distribution. - -### Partner tile (4:3) - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DetailsExamples
Subscription Initiation

The partner tile is utilized in multiple locations within the app.

In this example, your brand will appear on a subscription/trial initiation and confirmation page.

This page provides subscription details and initiates the service.		roku400px - premium-asset-13

roku400px - premium-asset-14
Grid

The partner tile also appears within a grid.

It represents your brand within a row and is also a gateway to access more content from your service.		roku400px - premium-asset-15

roku400px - premium-asset-16
Dimensions and Best Practices

Deliverable size:
  • 540 x 405px
  • Jpg


Logo should be centered within the guidelines - padding is 87px on all sides.

*Refer to Photoshop PSD file for more details		roku400px - premium-asset-17
roku400px - premium-asset-18
Examples of potential treatments:roku400px - premium-asset-19

roku400px - premium-asset-20

roku400px - premium-asset-21
- - - -### Logo - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DetailsExamples
Subscription Confirmation

Your brand’s logo is displayed when the user is engaging with your service and/or content from your library.

This screen is displayed after the user has successfully subscribed or started a free trial.		roku400px - premium-asset-22

roku400px - premium-asset-23
Content details screen

Your logo is displayed on content detail screens and is scaled down to fit within the focus button.		roku400px - premium-asset-24

roku400px - premium-asset-25
Grid BoB (Back of Box)

Your logo is also visible within the Grid BoB (Back of Box) and used to identify content from your library.		roku26 - premium-asset-26

roku400px - premium-asset-27
Website (Billboard)

Your logo is also displayed on The Roku Channel website on all content details pages.		roku400px - premium-asset-28

roku400 - premium-asset-29
Excess Space

After re-sizing your logo, please crop the logo so there is no margin between your logo and the edge of canvas.

This means for horizontal logos, removing excess height. Vertical logos will remove excess width.

Logos that are wider than they are tall (1:1 or wider) are preferred for legibility here.

PSD Files: White Logo | Black Logo		In this example, the delivered logo files would be 195 x 55 px
roku400px - premium-asset-32

In this example, the delivered logo files would be 85 x 111 px
roku400 - premium-asset-33
Dimensions

We require your logo to be delivered to us in two variants: a black transparent PNG and a light(#EFEFEF) transparent PNG, sized no taller or wider than 195 x 111 px.		roku400px - premium-asset-3roku400px - premium-asset-2roku400px - premium-asset-30
roku400px - premium-asset-31
- - -### CTA (call to action) banner - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DetailsExamples
Publisher home (Grid)

The CTA banner is a large tile/banner located within publisher's collection home. The banner contains enticing imagery of content available through the publisher, and the publisher's brand/logo along with subscription/trial start details. The background can be recolored to match the publisher’s brand.		roku400px - premium-asset-34

400px - premium-asset-35
Dimensions

Link to system font
Link to PSD source file		roku400px - premium-asset-36

roku400px - premium-asset-37
roku400px - premium-asset-38
Best Practices Asset Elements 1

Your delivered asset should only include:
  • Logo (required)
  • Description (required)
  • Background imagery (required)
  • Content Title (optional)
Your delivered asset
roku400px - premium-asset-39
Best Practices Asset Elements 2

Any additional text and CTA will be overlaid programmatically onto the tile image.

Don’t include this text as part of your banner image.		Banner shown on device (no offer)
roku400px - premium-asset-43
Banner shown on device (with offer)
roku400px - premium-asset-44
Best Practices Logo

Your logo should be bottom left aligned with a max height of 80px.

We recommend using a white, horizontal logo to improve legibility.		roku400px - premium-asset-40
Best Practices Content Image

Use a solid color or subtle background pattern behind the left half of the banner to ensure the logo, description, programmatic text and CTA are legible. Where transitioning from the offer area to the content imagery area, our preference is to utilize the included curved shape mask instead of using gradients or fades, to keep artwork looking crisp. Refrain from showcasing cast or characters in this area of your imagery.

We recommend limiting the number of subjects or faces shown in a single image. The fewer objects, the more focus that can be given.

Make sure PSD layer “BOTTOM OVERLAY” is left on when exporting. This ensures programmatic text and CTA will be legible.		Refrain from using content imagery that includes title artwork, so that it does not compete with the logo, description, programmatic text, and CTA on the left.

DO use imagery without title artwork
roku400px - premium-asset-41

DON’T use imagery with title artwork included
roku400px - premium-asset-42
Best Practices Content Title

If your imagery features 1 or 2 pieces of content, include the Content Titles in the bottom right.

If your imagery features 3 or more pieces of content, do not include the Content Titles.		Up to 2 titles
roku400px - premium-asset-45

3+ titles
roku400px - premium-asset-46
Best Practices Creative Examples

Here are a few examples to demonstrate some creative ways to display content imagery paired with legible backgrounds.		roku400px - premium-asset-47

roku400px - premium-asset-48
- - - -### Side card - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DetailsExamples
Roku Pay Screen

The side card is located on the Roku Pay screen when a user starts a free trial or subscription.

Side card images should match the corresponding banner call to action to ensure there is continuity between the marketing and purchase flow.		roku400px - premium-asset-53

roku400px - premium-asset-54
Dimensions

Both sizes required.
Link to PSD Source File: download here		roku400px - premium-asset-55

roku400px - premium-asset-56
roku400px - premium-asset-57
Best practices Overlay Area

Use a solid color or subtle background pattern behind the bottom half of the banner to ensure the programmatic text is legible. When transitioning from the offer area to the content imagery area, our preference is to utilize the included curved shape mask instead of using gradients or fades, to keep artwork looking crisp.

Do not alter position.

Ensure that the Top and Bottom Left corners ONLY are rounded and transparent. Template includes masking.

Best practices File format

Export as transparent PNG.		roku400px - premium-asset-60
Best Practices Template Usage

Offer language is added to this asset programmatically. Do not include any copy in the overlay area – it must remain blank.

Best practices Logo

We recommend using a white, horizontal logo to improve legibility.

Best practices Content image

Select show or character artwork that does not include title treatment. Use clean, engaging imagery that showcases your brand logo well. Do not include any marketing copy.

Do not alter position or size of content image area.		roku400px - premium-asset-58
Best practices Proper Usage Example

Character-focused, clean, and clear branding.
Dark/Bold colors allow for maximum legibility
Limit characters		roku400px - premium-asset-61
Best practices Improper Usage Example

Omit title treatments
Keep logo within guides
Do not include any copy
Do not place artwork out of bounds
Do not reposition logo		roku400px - premium-asset-62
- - -### Channel tile - - - - - - - - - - - - - - - - - - - -
DetailsExamples
Co-Branded Channel Tile

When a user starts a free trial or subscription, a dedicated channel tile will appear on the Roku home screen. The channel tile features your logo and “on The Roku Channel” branding.

The shortcut tile is a gateway to access a dedicated content experience from your brand.		roku400px - premium-asset-49
Dimensions

Depending on the design of your brand’s logo, scale it to fit the canvas provided.

After re-sizing your logo, please crop the logo so there is no margin between your logo and the edge of canvas.

Link to PSD source files:
Large | Small		roku400px - premium-asset-50

roku400px - premium-asset-51
roku400px - premium-asset-52
Both sizes required.
- - -### On-device banner + screensaver - - - - - - - - - - - - - - - - - - - - - - - -
DetailsExamples
Roku Home Screen

The screensaver ad appears when a user’s UI is in screensaver mode.
The native banner ad appears on the Roku home screen.
When a user clicks on the banner or screensaver, they will be taken to the movie or series details page.

On-device banner and screensaver creative should match the banner call to action and side card mentioned in the previous slide.		roku400px - premium-asset-63

roku400px - premium-asset-64

roku400px - premium-asset-65
Best Practices Single Title On Device Ads

Content image:
Use show or character artwork that is clean and engaging. No more than 20% text on image. All ads must align to Roku’s advertising guidelines. See full policy here.
Deliverables:
  • File Format: JPG
  • File Size: >150kb


Do not alter curve position, pattern, colors, or fonts.

PSD Source Files:
Banner
Portrait Screensaver
Landscape Screensaver		Native Display Banner Ad

roku400px - premium-asset-66

Screensaver ads
(portrait and landscape)

roku400px - premium-asset-67

roku400px - premium-asset-68
Best Practices Multi-Title On Device Ads

Select show or character artwork that does not include title treatment.
Content title is written out in top right corner.
We do not recommend including title in screensaver ads, due to legibility concerns at size.

Use clean, engaging imagery that showcases your brand logo well.

PSD Source Files:
Banner
Portrait Screensaver
Landscape Screensaver		Native Display Banner Ad
roku400px - premium-asset-69

Screensaver ads
(portrait and landscape)
roku400px - premium-asset-70

roku400px - premium-asset-71
- - - -### :30 promotional video - - - - - - - - - - - - - - - -
DetailsExample
Pre-roll + AVOD Mid-roll

The :30 promotional video will be served as a pre-roll ad prior to unlocked content playback and can also be used in mid-roll ads that appear on The Roku Channel.

All :30 promotional videos will include \{Partner logo\} on The Roku Channel end card.		roku400px - premium-asset-10
- - -### Subscriptions details copy - - - - - - - - - - - - - - - -
DetailsExample
Subscriptions Details Copy

The subscriptions details copy provides an overview of your subscription service.

It can be accessed by clicking * on the Roku remote when a user is on the banner call to action.

215-characters (including spaces)		roku400px - premium-asset-11
- - -### Back-of-box copy - -| Details | Example | -| ------------------------------------------------------------ | ------------------------------------------------------------ | -| **Back-of-Box (BoB) Copy**: 30 characters (including spaces) | ![roku400px - premium-asset-72](https://image.roku.com/ZHZscHItMTc2/premium-asset-72-v2.jpg) | - -## Delivery of assets & copy - -Send assets and copies to [svod-editorial@roku.com](mailto:svod-editorial@roku.com) or use the Box folder provided by Roku. - -If you would like to change any asset, we require at least 72 hours notice to push a change through. - -## Editorial mapping - -Email [svod-editorial@roku.com](mailto:svod-editorial@roku.com) with your editorial mapping for your page on Roku. - -- You can update as often as you like. -- It may take up to 72 hours for the change to happen. - -Follow the template – download [HERE](https://devtools.web.roku.com/samples/Editorial%20Recommendations%20Template.xlsx). - -- 12 titles are optimal for your featured row. -- 15 rows are optimal for your dynamic rows. - -## Planners - -We will need updates to your title trackers (planners) by the first of the month, for the following month (i.e. Jan 1, we would like to see your February title trackers). On-time updates allow us to incorporate these updates into The Roku Channel, Premium Subscriptions editorial, and marketing plans. - -Email [svod-editorial@roku.com](mailto:svod-editorial@roku.com) with a spreadsheet listing all titles and availability windows. - -Follow the template – found [HERE](https://devtools.web.roku.com/samples/SVOD%20Planner%20Template.xlsx) - -Your spreadsheet should highlight any “high value” content.  Originals, featured titles, etc. will be ushered through the process. - -This is not the place to communicate takedowns or changed availability dates (MDUs). This is **for reference only**. Updates to your metadata should go through our [Content Operations](mailto:contentoperations@roku.com) team. - -## Background art - -Background art for publisher pages - found [HERE](https://devtools.web.roku.com/samples/Partner_BG_Template.png) \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/delivery/_order.yaml deleted file mode 100644 index 2bbad3ba..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/_order.yaml +++ /dev/null @@ -1,10 +0,0 @@ -- ingest-specifications-spanish -- video-requirements -- audio-requirements -- closed-captions-and-subtitles -- artwork-requirements -- trailer-delivery -- delivery-methods -- file-delivery -- metadata -- resources diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/artwork-requirements.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/artwork-requirements.md deleted file mode 100644 index e22ce3ac..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/artwork-requirements.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -title: Artwork -excerpt: Required image types, resolutions, and aspect ratios by content type. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -Roku supports **six image types**, each used in a different location within Roku Channel. Roku **prefers** to receive all applicable image types whenever possible. - -**All image types share the following delivery requirements**, regardless of type: - -- **Format:** JPEG or PNG -- **Color space:** RGB -- **Resolution (density):** 72ppi -- **File extension:** `.jpg`, `.jpeg`, or `.png` - -Beyond these shared rules: - -- Images **must** meet or exceed the **minimum** resolution defined for their image type. -- Images **must** be delivered in the **exact** aspect ratio defined for their image type — no cropping tolerance. -- Deliver at Roku's **preferred** resolution where possible, to avoid delays in publishing. - -*** - -## Image Types - -| Image Type | Aspect Ratio | Preferred Resolution | Min Resolution | Max Resolution | Metadata Field | -| ------------------ | ------------ | ---------------------- | -------------- | -------------- | -------------- | -| Key Art | 16:9 | 1920×1080 or 3840×2160 | 1920×1080 | 3840×2160 | `keyart` | -| Box Cover (Series) | 4:3 | 2560×1920 | 1600×1200 | 2560×1920 | `boxcover` | -| Box Cover (Movies) | 3:4 | 1920×2560 | 1200×1600 | 1920×2560 | `boxcover` | -| Poster Art | 2:3 | 2000×3000 | 1000×1500 | 2000×3000 | `poster` | -| Background Art | 16:9 | 1920×1080 or 3840×2160 | 1920×1080 | 3840×2160 | `background` | -| Episode Art | 16:9 | 1920×1080 or 3840×2160 | 1920×1080 | 3840×2160 | `thumbnail` | - -_The Metadata Field column reflects the field name used to tag each image type in delivery metadata — not a separate description._ - -### Key Art - -16:9 artwork that appears when browsing Roku Channel. **Must** include the title treatment (a graphic showing the full title of the asset) and the title treatment text **must** be visible on the image. - -### Box Cover (Series) - -4:3 artwork for future Roku Channel browsing and/or third-party platforms. **Not currently required** for distribution to Roku Channel. Must include the title treatment. Used for **series only**. - -### Box Cover (Movies) - -3:4 artwork for future Roku Channel browsing and/or third-party platforms. **Not currently required** for distribution to Roku Channel. Must include the title treatment. Used for **movies only**. - -### Poster Art - -2:3 artwork that can appear when searching on Roku or Roku Channel. Must include the title treatment. - -### Background Art - -16:9 artwork used as the background of the details page for a series or movie. **Must NOT** contain any text. - -### Episode Art - -16:9 artwork representing an episode without spoilers — typically a still from the episode. **Must NOT** contain any text. - -*** - -## Minimum Art Requirements by Content Type - -| Image Type | Clip | Movie | Series | Episode | -| ---------------------------- | ------------ | ------------ | ------------ | ------------ | -| 16:9 Key Art | **Required** | **Required** | **Required** | — | -| 2:3 Poster Art | — | **Required** | **Required** | — | -| 3:4 Box Cover | — | **Required** | — | — | -| 4:3 Box Cover | — | — | **Required** | — | -| 16:9 Background Art | — | **Required** | **Required** | **Required** | -| 16:9 Episode Art (thumbnail) | — | — | — | **Required** | - -### Episode-Specific Notes - -For Episode content, delivered Background Art: - -- **May** be letterboxed or pillarboxed depending on the source video's aspect ratio. -- **Must NOT** be windowboxed — windowboxed images will be rejected. -- **Should** be unique per episode and representative of that episode's actual content. - -*** - -## Artwork Content Guidelines - -- **No** sexually explicit or graphically violent artwork. -- Artwork **should** be post-theatrical — do not include language such as _"In Theaters Now"_ or _"Coming Soon."_ -- Artwork designed specifically for digital delivery is **preferred**. -- Artwork for international territories **should** be localized for each territory. -- Roku will **not** accept branded artwork without prior approval — this applies to individual video assets as well as season/series-level entities. -- Calls to action (CTAs) or links to external platforms/sites are **not permissible** and **must** be removed from the image file prior to delivery. - -*** - -## Artwork Placement Examples - -**Movie artwork — browse experience** -16:9 texted image with title treatment, as shown when browsing. - -![Movie browse example](https://image.roku.com/ZHZscHItMTc2/movieBrowse.jpg) - -**Movie artwork — details experience** -16:9 textless image, as shown on the movie details page. - -![Movie details example](https://image.roku.com/ZHZscHItMTc2/movieDetail.jpg) - -**Series artwork — browse experience** -16:9 texted series image with title treatment, as shown when browsing. - -![Series browse example](https://image.roku.com/ZHZscHItMTc2/seriesBrowse.jpg) - -**Series artwork — details experience** -16:9 textless series image, as shown on the series details page. - -![Series details example](https://image.roku.com/ZHZscHItMTc2/seriesDetails.jpg) - -**Episode artwork — episode picker experience** -16:9 textless episode images, as shown in the episode picker. - -![Episode picker example](https://image.roku.com/ZHZscHItMTc2/episodePicker.jpg) - -**Episode artwork — episode details experience** -16:9 textless episode image, as shown on the episode details page. - -![Episode details example](https://image.roku.com/ZHZscHItMTc2/episodeDetail.jpg) - -**Clip artwork — browse experience** -16:9 texted image with title treatment, as shown when browsing. - -![Clip browse example](https://image.roku.com/ZHZscHItMTc2/clipBrowse.jpg) - -**Poster artwork — search experience** -2:3 texted image with title treatment, as shown in the search experience. 2:3 images are **preferred** for series and movie content types. - -![Poster search example](https://image.roku.com/ZHZscHItMTc2/posterSearch.jpg) - -*** - -## Glossary - -| Term | Definition | -| ------------------- | ----------------------------------------------------------------------------------------------------------------- | -| **Title treatment** | A stylized graphic rendering of a title's name, designed to appear directly on key art/poster/box cover images. | -| **Texted image** | An image that includes text (typically the title treatment). | -| **Textless image** | An image with no text or title treatment overlaid. | -| **Letterboxed** | Black bars added above and below the image to fit a wider source into a taller frame. | -| **Pillarboxed** | Black bars added to the left and right of the image to fit a narrower source into a wider frame. | -| **Windowboxed** | Black bars on all four sides of an image — combining letterboxing and pillarboxing. Not accepted for Episode Art. | diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/audio-requirements.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/audio-requirements.md deleted file mode 100644 index 717190ab..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/audio-requirements.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: Audio -excerpt: >- - Audio codec, channel configuration, and sidecar dub/descriptive audio - requirements. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Scope - -The audio requirements in this document — including channel configuration, channel labeling, and language/locale matching — apply **regardless of delivery method**: - -- Audio **multiplexed (muxed) into the video file** container, and -- Audio delivered as a **sidecar file** separate from the video - -Both delivery paths **must** conform to the same channel configuration and labeling rules described below. - -*** - -## Audio Codec & Sample Rate - -- **PCM 16-Bit or 24-Bit, 48kHz** audio at the highest available bitrate is **preferred**. -- **Dolby AC3** audio is supported. - -Roku **prefers to receive 5.1 Surround and Stereo audio whenever possible.** - -*** - -## Channel Configuration & Labeling - -All channels **must** be clearly labeled for position and language (label format depends on file format). This applies to both muxed and sidecar audio — see [Scope](#scope). - -### 5.1 Surround + 2.0 Stereo (preferred) - -| Channel | Label | -| --------- | ------------------- | -| Channel 1 | Left Front (L) | -| Channel 2 | Right Front (R) | -| Channel 3 | Center (C) | -| Channel 4 | LFE (Lfe) | -| Channel 5 | Left Surround (Ls) | -| Channel 6 | Right Surround (Rs) | -| Channel 7 | Stereo Left (SL) | -| Channel 8 | Stereo Right (SR) | - -### 5.1 Surround only - -_Acceptable if 5.1 + Stereo is not available._ - -| Channel | Label | -| --------- | ------------------- | -| Channel 1 | Left Front (L) | -| Channel 2 | Right Front (R) | -| Channel 3 | Center (C) | -| Channel 4 | LFE (Lfe) | -| Channel 5 | Left Surround (Ls) | -| Channel 6 | Right Surround (Rs) | - -### 2.0 Stereo only - -_Acceptable if 5.1 + Stereo and 5.1 Surround only are not available._ - -| Channel | Label | -| --------- | ----------------- | -| Channel 1 | Stereo Left (SL) | -| Channel 2 | Stereo Right (SR) | - -*** - -## Sidecar Audio Deliverables - -Content delivered with an audio language that is **not primary to the territory of distribution** must be delivered with an audio dub and/or subtitle file translating the content into that territory's primary language. - -- Localized audio tracks **may** be multiplexed into the video file, or delivered as a single interleaved sidecar audio file. -- Regardless of delivery method, all localized audio tracks **must** be delivered as a **full audio mix**. Roku does **not** support dialogue-only dub tracks. -- Sidecar audio **must** be delivered as a **single interleaved file**. Roku does **not** support discrete single-channel files. -- Sidecar audio **must** sync to the video source file delivered to Roku. -- Roku supports **one sidecar audio dub file per language**. -- Sidecar audio **must** follow the same channel configuration and labeling rules defined in [Channel Configuration & Labeling](#channel-configuration--labeling) above. - -Deliver sidecar audio at the highest bitrate and sampling rate available. - -### Supported Sidecar Audio Formats - -| Container | Codecs | Extension | -| -------------------------------------------------- | -------------------------- | --------- | -| WAV _(preferred)_ | PCM
GSM | .wav | -| MOV
(must not include a video track) | AAC
MP3
PCM | .mov | -| MP4 (MPEG-4)
(must not include a video track) | AAC
FLAC | .mp4 | -| MPEG-1 Layer 3 | MP3 | .mp3 | -| OGA | FLAC
Opus
Vorbis | .ogg | - -*** - -## Descriptive Audio - -Descriptive audio is an alternative audio track for the visually impaired, per [FCC Audio Description requirements](https://www.fcc.gov/audio-description). - -- Roku **strongly prefers** to receive descriptive audio tracks wherever available. -- Descriptive audio deliveries **must** follow the same requirements outlined in [Sidecar Audio Deliverables](#sidecar-audio-deliverables) above. -- Descriptive audio **must** be provided in the same language and locale as its companion standard (non-descriptive) audio track for that language. -- **The audio language code of the descriptive audio track must exactly match the audio language code of its companion standard audio track.** For example, a descriptive track paired with a standard track coded `en-US` must also be coded `en-US` — not `en`, `en-GB`, or any other variant. - -*** - -## Audio Channel Layout Hints - -If video files cannot be created with proper audio channel labels embedded, an **audio layout hint must be provided in the metadata** for the delivered video file. This applies to muxed audio only where in-file labeling is not possible; it does not replace the labeling requirement for sidecar files. - -| Descriptor | Definition | -| -------------------- | ------------------------------------------------------------------------------------------- | -| `stereoOnly` | 2-channel stereo audio only. May be delivered on a single track or 2 discrete tracks. | -| `surroundOnly` | 6-channel 5.1 surround audio only. May be delivered on a single track or 6 discrete tracks. | -| `stereoPlusSurround` | 8-channel audio with stereo on channels 1–2, followed by 5.1 surround on channels 3–8. | -| `surroundPlusStereo` | 8-channel audio with 5.1 surround on channels 1–6, followed by stereo on channels 7–8. | - -*** - -## Glossary - -| Term | Definition | -| ----------------------- | ---------------------------------------------------------------------------------------------------------- | -| **Muxed / Multiplexed** | Audio combined into the same file container as the video, rather than delivered separately. | -| **Sidecar file** | An audio or subtitle file delivered alongside (not embedded in) the video file, mapped to it via metadata. | -| **Interleaved** | Multiple audio channels combined into a single file, as opposed to separate discrete files per channel. | -| **Discrete channel** | An individual audio channel delivered as its own separate file/track rather than combined with others. | -| **LFE** | Low-Frequency Effects channel — the ".1" in 5.1 surround, typically routed to a subwoofer. | -| **Full audio mix** | A complete mixed audio track (dialogue, music, effects), as opposed to a dialogue-only or partial track. | -| **Language code** | A standardized code identifying language and, optionally, regional locale (e.g., `en-US`, `es-MX`). | - -{/* Example Usage */} - - diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/closed-captions-and-subtitles.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/closed-captions-and-subtitles.md deleted file mode 100644 index bb090405..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/closed-captions-and-subtitles.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: Closed captions and subtitles -excerpt: >- - Requirements for Closed Captions/SDH, Full Subtitles, and Forced Narrative - Subtitles. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -Roku supports three distinct text-track types: **Closed Captions/SDH**, **Full Subtitles**, and **Forced Narrative Subtitles**. Though visually similar to a viewer, they serve different purposes and follow different rules. - -**Critical constraint:** the Roku player displays **only one text track at a time**. This has two direct consequences that shape the rest of this document: - -- Any CC/SDH or Full Subtitle track **must** contain a complete transcription/translation of all narratively important dialogue and on-screen text. A viewer will never see two tracks layered together. -- Forced Narrative content **must also be duplicated inside** any CC/SDH or Full Subtitle track, because enabling one of those tracks will suppress the Forced Narrative track entirely. - -*** - -## Track Types Compared - -| | Closed Captions / SDH | Full Subtitles | Forced Narrative Subtitles | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -| **Purpose** | Accessibility for deaf/hard-of-hearing viewers | Localization — translates dialogue/text for viewers who don't understand the audio language | Localization for specific moments unintelligible to the viewer (foreign-language snippets, unreadable on-screen text, inaudible audio) | -| **Viewer toggle** | Can be turned on/off | Can be turned on/off | **Cannot** be turned on/off — displays automatically | -| **Language/audio pairing** | Must match the language and locale of its companion audio track; unavailable if no matching-language audio track is delivered | Available regardless of which audio track(s) are delivered | Tied to whichever audio track the viewer has selected; automatically displays when that track includes unintelligible content | -| **Content included** | Full transcription of dialogue + sound effects/music cues/lyrics + all forced narrative content | Full translation of narratively important dialogue/text; does not describe sound effects or music cues (song lyrics translated only if narratively important) | Only the specific unintelligible moments — not a full transcription | -| **Regulatory** | May be required by regulatory agencies in certain territories | — | — | - -*** - -## Forced Narrative Subtitles - -Forced narratives translate or convey information the viewer would otherwise miss, including: - -- Spoken dialogue in a language different from the viewer's selected audio track -- On-screen text in a language different from the viewer's selected audio track -- Inaudible or difficult-to-hear audio (e.g., noisy scenes, poor-quality recordings) - -**Important:** the forced narrative _track_ travels with whichever audio track the viewer selects — it is not a separate audio-language option in its own right. Its _content_, however, specifically covers the moments within that audio track where dialogue or text appears in a different language, or is otherwise unintelligible. - -Because the Roku player shows only one text track at a time, enabling a CC/SDH or Full Subtitle track will suppress the Forced Narrative track. For this reason, **CC/SDH and Full Subtitle tracks must include all forced narrative content** so the viewer never loses that information by enabling captions or subtitles. - -*** - -## Closed Captions / SDH - -_Also known as: subtitles for the deaf or hard of hearing (SDH), subtitles for the deaf and hard of hearing._ - -Roku **prefers** to receive closed captions/SDH for all content. - -### Regulatory Requirements (US) - -For content intended for the US, Roku adheres to **FCC closed captioning rules for Internet Video Programming**: [https://www.fcc.gov/consumers/guides/captioning-internet-video-programming](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming) - -- Content **required** by the FCC to carry closed captions **must** be delivered with CC/SDH, conformed and synced to the program. -- Content **exempt** from the requirement **must** include a valid exemption code number in the metadata. - -**Exemption codes:** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -For content intended for territories outside the US, Roku adheres to the requirements of that territory. - -### Delivery Method - -Captions/SDH **may** be provided as: - -- **EIA-608/CEA-708** embedded in-stream in the video file, or -- A **sidecar** caption/SDH file - -Roku **prefers** a human-readable sidecar file (`.ttml`, `.dfxp`, `.vtt`, or `.srt`). - -### Delivery Rules - -- Sidecar captions/SDH **must** be timed to timecode hour `00:00:00:00` — the Roku encoder does **not** honor timecode embedded in the video file. -- Do **not** provide an empty file (a file with no text) as a sidecar caption/SDH deliverable. -- TTML and WebVTT positional data **is** supported and will be honored as defined in the file. -- QuickTime video files **must** be accompanied by a sidecar closed caption file — Roku does **not** support the QuickTime text track. -- Text styling support is limited to: bold (``) and italic (``) tags, text color, and text positioning. _(This applies identically to Full Subtitles — see [Text Styling Support](#text-styling-support).)_ - -### Supported Formats - -| Format Name | Positional Data | Style Data | Extension | Encoding | Delivery Type | Languages | -| ------------------------------------------- | --------------- | ---------- | ------------------- | -------- | ----------------------- | ------------------------------------------------ | -| Timed Text Markup Language (TTML) | Y | Y | `.ttml` | UTF-8 | Sidecar | Follows audio language of video file or dub file | -| Web Video Text Track (WebVTT) | Y | Y | `.vtt` or `.webvtt` | UTF-8 | Sidecar | Follows audio language of video file or dub file | -| Distribution Format Exchange Profile (DFXP) | N | N | `.dfxp` | UTF-8 | Sidecar | Follows audio language of video file or dub file | -| EBU Subtitle Data Exchange Format (STL) | N | N | `.stl` | UTF-8 | Sidecar | Follows audio language of video file or dub file | -| SubRip Text (SRT) | N | N | `.srt` | UTF-8 | Sidecar | Follows audio language of video file or dub file | -| EIA-608/CEA-708 | N | N | n/a | n/a | Embedded in MPEG stream | Embedded in video file | - -> **Note on CC/SDH language:** because CC/SDH is an accessibility companion to a _specific_ audio track, its language simply follows whichever audio track (main or dub) it accompanies — it does not require an independent language-code declaration the way Full Subtitles do (see below). - -#### Legacy Format (supported, not preferred) - -| Format Name | Positional Data | Style Data | Extension | Encoding | Delivery Type | Languages | -| ----------------------------------------------------- | --------------- | ---------- | --------- | -------- | ------------- | ------------------------------------------------ | -| ~~SCC~~ _(legacy — use a format above when possible)_ | N | N | `.scc` | ASCII | Sidecar | Follows audio language of video file or dub file | - -*** - -## Full Subtitles - -Content delivered with an audio language that is not primary to the territory of distribution **must** be delivered with an audio dub and/or a subtitle file translating the content into that territory's primary language. (This is the same underlying concept described in [Track Types Compared](#track-types-compared) above.) - -### Delivery Rules - -- Subtitles **must NOT** be burned into (hardcoded onto) the video. -- Roku **prefers** a human-readable sidecar file (`.ttml`, `.dfxp`, `.vtt`, or `.srt`). -- Sidecar subtitles **must** be timed to timecode hour `00:00:00:00` — the Roku encoder does **not** honor timecode embedded in the video file. -- Do **not** provide an empty file (a file with no text) as a sidecar subtitle deliverable. -- TTML and WebVTT positional data **is** supported and will be honored as defined in the file. - -### Text Styling Support - -Both Closed Captions/SDH and Full Subtitles are limited to the same styling support: - -- Bold (``) and italic (``) tags -- Text color -- Text positioning - -### Supported Formats - -| Format Name | Positional Data | Style Data | Extension | Encoding | Delivery Type | Languages | -| ------------------------------------------- | --------------- | ---------- | ------------------- | -------- | ------------- | ------------------------------------------------------------------------------------------------ | -| Timed Text Markup Language (TTML) | Y | Y | `.ttml` | UTF-8 | Sidecar | Must conform to a supported [language code](#language-codes); include region code where possible | -| Web Video Text Track (WebVTT) | Y | Y | `.vtt` or `.webvtt` | UTF-8 | Sidecar | Must conform to a supported [language code](#language-codes); include region code where possible | -| Distribution Format Exchange Profile (DFXP) | N | N | `.dfxp` | UTF-8 | Sidecar | Must conform to a supported [language code](#language-codes); include region code where possible | -| EBU Subtitle Data Exchange Format (STL) | N | N | `.stl` | UTF-8 | Sidecar | Must conform to a supported [language code](#language-codes); include region code where possible | -| SubRip Text (SRT) | N | N | `.srt` | UTF-8 | Sidecar | Must conform to a supported [language code](#language-codes); include region code where possible | - -> **Note on Subtitle language:** unlike CC/SDH (which simply follows its companion audio track), Full Subtitles are independently language-tagged, since a single title may carry subtitle tracks in many languages regardless of which audio tracks are delivered. - -*** - -## Glossary - -| Term | Definition | -| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **SDH** | Subtitles for the Deaf or Hard of hearing — functionally identical to closed captions in this spec. | -| **EIA-608/CEA-708** | Broadcast caption standards embedded directly in the video stream (in-stream), as opposed to a sidecar file. | -| **Forced narrative** | A non-toggleable text track that displays only for specific unintelligible moments (foreign dialogue, unreadable text, inaudible audio) within the viewer's selected audio track. | -| **Burned-in / hardcoded subtitles** | Subtitle text permanently rendered into the video image itself, rather than delivered as a separate, toggleable track. Not permitted for Full Subtitles. | -| **Conformed and synced** | Captions that have been time-aligned and verified to match the final program cut exactly. | -| **Positional data** | Information within a caption/subtitle file specifying where on screen the text should appear, rather than defaulting to a fixed position. | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/delivery-methods.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/delivery-methods.md deleted file mode 100644 index 7e470f00..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/delivery-methods.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: Delivery methods -excerpt: 'Supported transfer methods: Aspera (Shares/P2P) and direct S3 connection.' -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -Roku supports two primary content delivery methods: - -1. **Aspera**: via Aspera Shares (desktop app) or Aspera Enterprise/P2P (SSH-key authenticated) -2. **Direct S3 connection:** cross-account S3-to-S3 transfer - -Roku will confirm which delivery method applies to a given partner during onboarding. Alternate file transfer or physical delivery methods **may** be evaluated on a case-by-case basis, but **must** be approved by Roku in advance. **If approved, any physical media/hard drives provided to Roku will not be returned.** - -*** - -## Aspera - -Roku accepts content via Aspera, configured as either: - -- **Aspera Shares** (using the IBM Aspera for Desktop application), or -- **Aspera Enterprise/P2P** (using Aspera Client or Console) - -**Choosing between them:** Aspera Shares is a simpler, desktop-app-based option well suited to occasional or smaller-scale transfers. Aspera Enterprise/P2P uses SSH-key authentication and is typically used for larger-volume or more frequent automated transfers. Roku will confirm which applies to your onboarding. - -### Aspera Shares Delivery - -Provide the name(s) and email address(es) of users who will be transmitting content to Roku for Roku Channel. - -- **Roku's Aspera Shares URL:** [https://aspera.sr.roku.com](https://aspera.sr.roku.com) -- **Required application:** [IBM Aspera for Desktop](https://ibmaspera.com/help/downloads/desktop) — installation is required to upload content via Aspera Shares. - -> **Invitation emails:** account invitations to Aspera Shares are sent from Roku's Aspera Shares server. These automated emails are commonly flagged as spam/junk, or blocked by an organization's email filtering or firewall. If you don't see the invitation, **check your spam/junk folder** and move it out before attempting to use the link. - -### Aspera Enterprise/P2P/HSTS Delivery - -Roku authenticates via **RSA public/private key exchange**. To complete configuration, provide a **public RSA-SSH key**. - -- Steps to create SSH keys: [Aspera's official documentation](https://download.asperasoft.com/download/docs/ascp/3.5.2/html/dita/creating_public_key.html) -- Roku will provide **host and username information** during onboarding. -- **Required application:** [Aspera Client](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software\&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all) - -#### Transfer Bandwidth - -Roku applies a **global bandwidth cap of 300 Mbps**. Roku recommends verifying or updating your Aspera Client's global and user preferences to align with your preferred upload bandwidth. - -![Aspera preferences example](https://image.roku.com/ZHZscHItMTc2/asperaPreferences.jpg) - -Where you configure transfer speed depends on which client/connection type you're using: - -| Connection Type | Where to Configure | Reference | -| ------------------------------------ | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Desktop Client GUI (global settings) | Global bandwidth preferences | [IBM docs: global bandwidth settings](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-global-bandwidth-settings) | -| Desktop Client GUI (per-connection) | "Speed" setting when adding/editing a connection | [IBM docs: adding/editing connections](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-adding-editing-connections) | -| Command line | `-l` switch on the transfer command, e.g. `ascp -l 100m ...` sets a 100 Mbps transfer rate | — | -| Aspera Shares (web interface) | System-wide or per-user target rate | [Configuring transfer settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=options-configuring-transfer-settings) / [Configure user settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=accounts-configure-user-settings) | - -> Pick the row matching your connection type — these are alternative configuration paths, not sequential steps. - -*** - -## Direct S3 Connection - -Roku supports direct S3-to-S3 transfer for content delivery. The Roku delivery bucket for S3 direct connect uses a **customer-managed KMS key**. Because this is a cross-account transfer, a KMS key and policy granting the partner's account permission is required. - -### What Roku Needs From Partners - -The partner's **IAM role ARN**, used (assumed) for multipart upload/S3 copy. Once received, Roku adds it to the KMS/policy allow list. - -Typical ARN format: - -``` -arn:aws:iam:::role/ -``` - -The IAM policy below is presented in the source spec as the required permission set for the partner's assumed role: - -```json -{ -"Version": "2012-10-17", -"Statement": [ - { - "Effect": "Allow", - "Action": [ - "kms:\*", - "s3:\*" - ], - "Resource": "\*" - } -] -} -``` - -### What Partners Need From Roku - -1. **Roku's production environment bucket name** for direct ingest: - - ``` - ingest-direct1-886239521314 - ``` - -2. **Partner-specific prefix** within the bucket, supplied by Roku during onboarding, following this convention: - - **Convention:** - - ``` - ingest//prod/ - ``` - - **Full bucket path example:** - - ``` - ingest-direct1-886239521314/ingest//prod/ - ``` - -### Best Practices / Optimization - -Roku's S3 bucket is located in the **us-east-1** region — cross-region transfers are expected to be slower. Transfers can be optimized via multipart upload/copy settings: - -``` -aws configure set default.s3.multipart_chunksize 128MB -aws configure set default.s3.max_concurrent_requests 30 -``` - -### Testing - -To validate configuration, perform the following: - -1. Test uploading a file to the Roku S3 bucket, into the designated partner prefix. -2. Test copying a file from the partner's S3 bucket to the Roku S3 bucket, into the designated partner prefix. - -*** - -## Glossary - -| Term | Definition | -| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Aspera Shares** | A browser/desktop-app-based Aspera delivery method using user invitations rather than SSH-key authentication. | -| **Aspera Enterprise/P2P/HSTS** | An SSH-key-authenticated Aspera delivery method, typically used for larger or automated transfers. _(HSTS here refers to Aspera's "High-Speed Transfer Server")_ | -| **KMS key** | AWS Key Management Service key — used here to encrypt/decrypt content in Roku's S3 delivery bucket. | -| **IAM role ARN** | Amazon Resource Name identifying an AWS IAM role — the identity a partner's system assumes to perform the transfer. | -| **Multipart upload** | An S3 upload method that splits a large file into parts uploaded in parallel, improving transfer speed and reliability. | -| **Cross-account transfer** | A transfer between two separate AWS accounts (the partner's and Roku's), requiring explicit permission grants on both sides. | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/file-delivery.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/file-delivery.md deleted file mode 100644 index fc2f9bd5..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/file-delivery.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -title: File delivery -excerpt: Folder structure, retention windows, and file-naming rules. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Delivery Sequence - -Video, closed caption, and artwork files **must** be **completely delivered prior to** the delivery of metadata. Metadata references these files by name, so delivering metadata first (or before the referenced files finish transferring) can cause processing failures. - -*** - -## Folder Structure - -- Production files **MUST** be delivered to the `/prod` folder. Automation depends on proper file delivery location. Failure to deliver to the correct folder will result in processing delays, or content not processing at all. -- Test files **may** be delivered to the `/testing` folder. - -### Subfolders - -Content **should not** be delivered into subfolders. Deliver directly to `/prod` (or `/testing`) whenever possible. **If subfolders are necessary**, follow these guidelines: - -- Subfolder names **must not** begin with an underscore. Roku's system will **ignore** any subfolder beginning with an underscore. _(Note: this is a separate rule from the file-naming underscore rule below. It applies to the folder name itself, not the files inside it.)_ -- Do **not** separate files into subfolders by file type (e.g., don't put all video in one subfolder and all artwork in another). -- All media files for a single title (episode, movie, or short-form) **must** be delivered to the **same** directory. -- Metadata **must** be delivered to the **same** directory as the media files it references — the ingest platform assumes referenced media files are located alongside the metadata file. -- When replacing a file delivered via subfolder, the replacement file **and** its associated metadata **must** be delivered to a folder named **identically** to the original delivery folder. - -## Delivery Notifications - -Delivery notifications can be sent to: [deliverynotifications@roku.com](mailto:deliverynotifications@roku.com) - -*** - -## File Retention - -The delivery location is a **temporary** staging area for partners to upload files for ingestion into the Roku Channel content library. - -- Upon successful ingest, automation moves files from the delivery location to an archive location, where they are stored **indefinitely**. -- Files uploaded to the delivery location are expected to be ingested within a **reasonable timeframe, not to exceed 30 days**. -- Valid and complete metadata **must** be delivered shortly after files are delivered, to ensure timely ingest. -- Files remaining in the delivery location **after 30 days without ingesting are subject to deletion.** - -> **Exception:** files in the `/testing` folder may be exempted from the file retention policy. - -*** - -## File Naming - -Source video, closed caption, and artwork files delivered for ingest **must** adhere to the following: - -- File names **must not** exceed **125 characters** in length. -- File names **must** match the file name referenced in the metadata supplied for the title. -- File names are **case-sensitive**. -- File names **must** end with a proper file extension, and extensions **must** be **lowercase**. -- File names **must not** begin with an underscore. Roku's system will **ignore** any file beginning with an underscore. _(This is a separate rule from the subfolder-naming rule above. It applies to individual file names, not folder names.)_ -- Whitespace and special characters **must not** be included in any file name — this restriction applies to video, subtitle, closed caption, sidecar audio, and metadata files alike. See the forbidden character table below for the complete list with character names. -- Reusing the same image across every episode of a series is **discouraged.** A unique per-episode image is preferred. **If** the same image is reused, it **must** still be delivered as a separate, uniquely-named file for each episode (e.g., `episode.jpg` delivered as `episode_01.jpg`, `episode_02.jpg`, etc.) Identical image content does not exempt a file from unique naming. - -### Characters Allowed in File Names - -| Character Set | -| ------------- | -| `0-9` | -| `a-z` | -| `A-Z` | - -| Character Name | Character | -| -------------- | --------- | -| Hyphen | `-` | -| Period | `.` | -| Underscore | `_` | - -### Characters Forbidden in File Names - -| Character Name | Character | Character Name | Character | -| ----------------- | --------- | ---------------------------- | --------- | -| "At" symbol | `@` | Left square bracket | `[` | -| Ampersand | `&` | Less than | `<` | -| Asterisk | `*` | Percent | `%` | -| Backslash | `\` | Plus | `+` | -| Caret | `^` | Pound/hashtag | `#` | -| Colon | `:` | Question mark | `?` | -| Comma | `,` | Quotation marks/double quote | `"` | -| Dollar | `$` | Right curly brace | `}` | -| Equals | `=` | Right square bracket | `]` | -| Exclamation point | `!` | Semicolon | `;` | -| Forward slash | `/` | Single quote/apostrophe | `'` | -| Grave accent | `` ` `` | Space | ` ` | -| Greater than | `>` | Tilde | `~` | -| Left curly brace | `{` | Vertical pipe | `\|` | -| Left parenthesis | `(` | Right parenthesis | `)` | - -*** - -## Partner Responsibility - -> Correct file delivery location, proper file delivery cadence, and proper file naming are the responsibility of Roku's partners, as the partner is the expert in their own content — Roku does not always have insight into individual partner delivery schedules. - -*** - -## Glossary - -| Term | Definition | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Ingest** | The automated process by which Roku pulls delivered files and metadata into the Roku Channel content library. | -| **Delivery location** | The temporary staging folder(s) (`/prod`, `/testing`) partners upload to; distinct from the permanent archive location files move to after successful ingest. | -| **Sidecar file** | A subtitle, caption, or audio file delivered alongside (not embedded in) the video file, referenced by the metadata. | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/index.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/index.md deleted file mode 100644 index 4c16dcd0..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/index.md +++ /dev/null @@ -1,4056 +0,0 @@ ---- -title: Content delivery -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## Ingest specifications - -Below is a comprehensive list of formatting requirements for partner media assets and metadata, including file templates and delivery guidelines. Roku's ingest platform is fully automated and full compliance with this specification will ensure timely and error-free processing of content for distribution to Roku Channel. Should any changes need to be made to the workflow established during onboarding, please inform a Roku representative as early as possible to arrange for any new testing or configuration. Roku expects content and metadata to be delivered in a manner that was agreed upon during the onboarding and testing phase. Please ensure delivery knowledge is transferred to new personnel in the event that teams are updated or changed. - -### MovieLabs - -As an alternative to this specification, Roku Channel supports content delivery via MovieLabs specification. - -- **MMC and MEC** - Roku Channel MovieLabs service was built on MEC v2.9 and MMC v1.10 as defined on MovieLabs’ site: [https://www.movielabs.com/md/](https://www.movielabs.com/md/) -- **EMA avails** - Roku Channel supports the latest version of the [EMA specification](https://movielabs.com/md/avails/) via the xlsx deliverable - -Roku prefers MovieLabs deliverables from all Premium Subscription (SVOD) Partners. Please see additional Roku Channel-specific MovieLabs delivery details [here](#movielabs-content-delivery) - -## Roku content policies - -### Ad policy - -Roku will serve up to 8 minutes of advertisements per viewing hour. Roku’s ad policy is subject to change. - -#### Ad-supported content on Roku Channel - -Roku Channel is looking for ad-supported content that is appropriate for our users and advertisers – for example, Roku Channel does not want ad-supported content that contains excessive nudity or extreme/graphic violence.Please use your best judgement when sharing content. If an asset is questionable, please find an alternative to share. We reserve the right to remove or reject any content that we deem inappropriate. - -#### Ad breaks - -Ad break timecodes shall be delivered according to the Roku Ad Policy in the adBreak nodes of the movie/episode/clip metadata to trigger ad breaks during playback on the platform. adBreaks should be accurately provided to the millisecond. Please convert any frame rate value to a millisecond equivalent. Providing adBreaks in the ingest metadata is highly recommended and will speed up the QC process. All adBreak data must be supplied as HH:MM:SS.sss (e.g., 01:23:45.678) - -##### Movie ad policy - -- No adBreaks should be listed during the first 10 minutes of playback -- No pre-roll adBreak should be listed – 00:00:00.000 -- adBreak cue points should be provided at naturally occurring scene breaks and/or fades to black -- There should be no less than 10 minutes between each adBreak -- No adBreaks within 10 minutes of end credits - -##### Series episode ad policy - -Content length longer than 15 minutes: - -- No adBreaks should be listed during the first 5 mins of playback -- No pre-roll adBreak should be listed - 00:00:00 -- adBreak cue points should be provided at naturally occurring scene breaks and/or fades to black -- There should be no less than 7 mins between each adBreak -- No adBreaks within the last 5 minutes of end credits - -### Kids directed content policy - -“Kids-Directed Content” is content that either: (i) is directed to children as defined by the applicable law of the jurisdiction in which the content is shown (e.g., [The Children's Online Privacy Protection Act](https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa)); or (ii) was made for viewing primarily by children within the jurisdiction in which the content is shown. - -- Roku must be made aware of the intent to submit or distribute content that is directed at children -- DO NOT submit or distribute kids directed content without Roku’s express written approval -- When given approval by Roku to submit or distribute content directed at children, all content metadata must include the following: -- For Movie content: -- The `` “kidsdirected” (all lowercase) must be included as one of the tags for every movie -- A valid MPAA, USA_PR, or TV parental [rating](#rating-values-by-rating-system-and-country) must be included. “UNRATED” and “Not Rated” are not acceptable ratings for kids directed content -- For Episodic Series content: -- The `` “kidsdirected” (all lowercase) must be included as one of the series and episodic tags for every series and episode -- A valid TV parental [rating](#rating-values-by-rating-system-and-country) must be included. “UNRATED” and “Not Rated” are not acceptable ratings for kids directed content - -Please see [here](https://docs.roku.com/published/madeforkids) for more information and guidance on content "made for kids" - -### External branding and calls to action (CTAs) - -Roku Channel does not allow branding or external URL links/calls to action on key art or within the video and closed captioning. Calls to action are creatives and/or content segments that direct users outside of the Roku Channel ecosystem to consume content on external services. Video must be edited to remove links or directions for users to visit external sites. This includes: - -- Brand logos -- Web urls -- QR codes -- Verbally or textually calling viewers to "click", "subscribe", "buy now", "go to", etc - -Please contact your Roku representative for more details. - -### Music cue sheets - -Music cue sheets may be submitted to Roku for content distributed to Roku Channel via the below link: - -[https://go.roku.com/music-cue-sheet-submission](https://go.roku.com/music-cue-sheet-submission) - -Please do not submit music cue sheets with the video package deliverables via Aspera. Cue sheets delivered with the video package will be subject to deletion. - -## User experience on Roku Channel - -Roku augments metadata and artwork that appears in Roku Channel on Roku devices, web browsers, mobile applications, and other off-platform players with data supplied from Gracenote’s database where available. The Gracenote data aids in a unified experience of a title across platforms as well as on the greater Roku ecosystem. Roku will attempt to match all content delivered by our Partners to a corresponding record in Gracenote’s database. _At this time all metadata and artwork that appears on Roku Channel is sourced from Gracenote if that content is found in Gracenote’s database._ - -Gracenote leverages "Artwork Personalization" where they supply alternate imagery to diversify title artwork for different users based on several factors (demographics, popularity, etc.); which has led to an increase in user engagement. Gracenote does accept official key art from Partners, but not all users will see official art unless the algorithm serves it to them. Gracenote supplies \~3 unique images, and create alternative versions of artwork sourced from a variety of places (ex. original broadcaster, production studio, creative agency). Gracenote has stated to Roku that all images are under a fair use license, and they apply the same quality standards to Personalized Images as they do to partner supplied Key Art, e.g., no major spoilers, no dark/blurry/grainy images, no violent/suggestive imagery, avoidance of smoking. - -Our systems use a combination of methods to match a title its correct Gracenote record. Partners can aid in the matching to a Gracenote record by providing accurate metadata including: - -- Exact title of a series, movie, TV special, or short form video -- Release dates that are accurate to the year the title was originally released on any platform -- Accurate season and episode numbers according to the original release order -- Accurate TMS (Gracenote) IDs by content type -- Content classified as an episode with Gracenote must be delivered as an Episode to Roku -- Content classified as a movie with Gracenote must be delivered as a movie to Roku -- Content classified as a TV Special with Gracenote can be delivered as a movie to Roku - -Partners can aid in the curation of their content on Roku Channel by providing Tags with each movie, episode, or clip. Roku Channel editorial team and recommendations engine will utilize the provided Tags and Genres to help surface content on Roku Channel Platform UI. The more tags that are included, the more ways the content can be curated/surfaced to the end user. Please see [Best practices: content tags and metadata](doc:content-tags-and-metadata) for more details. - -## Media asset guidelines - -### Video requirements - -- All video content must be **full program only**: - - no bars/tone or slates at program start - - no textless video after program end - - no more than 2 seconds of black at program start - - no more than 2 seconds of black after program end - -- Video files should be semi-textless (also known as "texted with no subtitles" or "textless with main, ends, and graphic text"). Video can include opening and end credit text but all subtitles for foreign dialogue must be removed. - -- Do not include advertisements within the video. All ad insertion points for ad supported content will be provided in the metadata file based on the [Roku Ad Policy guidelines](#ad-policy) - -- Commercial blacks may be included within the video so long as they are no longer than 2 seconds - -- Commercial blacks are acceptable for episodic TV content but not expected for movie content - -- Video files must be delivered as a single, seamless video file - -- Do not deliver hard parted (broken into segments at the ad break points) video files - -- Calls to action (CTAs) or links to external platforms or sites are not permissible and must be removed from the video prior to delivery to Roku - -- HD video content must be delivered in a 16:9 container - -- Full-Frame presentation (1.78 aspect ratio) is preferred whenever available - -- Letterboxed 16:9 is allowed but should be minimized - -- SD 16:9 content must not be delivered in a 4:3 container with letterboxing - -- High-quality mezzanine level files are preferred with the highest bitrate and highest resolution possible. - -#### Video frame rate - -Roku supports a variety of frame rates and scan types. All video files should be delivered in their original native frame rate and scan type - -#### Video resolution - -| Type | Width | Height | Pixel Aspect Ratio | -| ------- | ----- | ------ | ------------------------------- | -| SD | 720 | 480 | 4:3 or 16:9 (anamorphic pixels) | -| SD | 640 | 480 | 1:1 (square pixels) | -| SD | 853 | 480 | 1:1 (square pixels) | -| SD | 720 | 576 | 4:3 or 16:9 (anamorphic pixels) | -| SD | 768 | 576 | 1:1 (square pixels) | -| SD | 1024 | 576 | 1:1 (square pixels) | -| HD | 1280 | 720 | 1:1 (square pixels) | -| FHD | 1920 | 1080 | 1:1 (square pixels) | -| UHD\*\* | 3840 | 2160 | 1:1 (square pixels) | - -_\*\*UHD is supported as an input resolution only. Roku does not currently encode to or display 4K UHD video on Roku Channel_ - -#### Video formats - -| Name | Codecs | Extension | Bitrate | -| :------------ | :--------------------------------------------------------------------------------------- | :------------ | :----------------------------------------------------- | -| Apple® ProRes | ProRes 444 (all profiles)
ProRes 4444 (all profiles)
ProRes 422 (all profiles) | .mov | 50 Mbps or greater | -| XDCam | | .mxf | 50 Mbps or greater | -| MPEG-2 | | .ts
.mpg | HD - 15 Mbps or greater
SD - 3.75 Mbps or greater | -| MPEG-4 | H.264 | .mp4 | 5 Mbps or greater | - -### Audio requirements - -_Files must have industry standard audio configurations with all channels clearly labeled for position and language_ (depending on file format) - -- PCM 16-Bit or 24-Bit 48kHz audio at highest bitrate preferred -- Dolby AC3 Audio is supported - -**Roku prefers to receive 5.1 and Stereo audio whenever possible** - -| 5.1 Surround + 2.0 Stereo | Channel Label | -| ------------------------- | ------------------- | -| Channel 1 | Left Front (L) | -| Channel 2 | Right Front (R) | -| Channel 3 | Center (C) | -| Channel 4 | LFE (Lfe) | -| Channel 5 | Left Surround (Ls) | -| Channel 6 | Right Surround (Rs) | -| Channel 7 | Stereo Left (SL) | -| Channel 8 | Stereo Right (SR) | - -**5.1 Surround only is acceptable if 5.1 + Stereo is not available** - -| 5.1 Surround Only | Channel Label | -| ----------------- | ------------------- | -| Channel 1 | Left Front (L) | -| Channel 2 | Right Front (R) | -| Channel 3 | Center (C) | -| Channel 4 | LFE (Lfe) | -| Channel 5 | Left Surround (Ls) | -| Channel 6 | Right Surround (Rs) | - -**Stereo only is acceptable if 5.1 + Stereo and 5.1 Surround only are not available** - -| 2.0 Stereo | Channel Label | -| ---------- | ----------------- | -| Channel 1 | Stereo Left (SL) | -| Channel 2 | Stereo Right (SR) | - -### Secondary audio deliverables - -Content delivered with an audio language that is not primary to the territory of distribution must be delivered with an audio dub and/or subtitle file translating the content into that territory’s primary language. Secondary audio tracks may be multiplexed in with the video file deliverable or delivered in a single interleaved sidecar audio file. All secondary audio tracks, whether multiplexed in the video or delivered as an interleaved sidecar file, must be delivered as a full audio mix. Roku does not support dialogue only dub tracks. - -#### Sidecar secondary audio - -- Sidecar audio must be delivered as a single interleaved file. Roku does not support discrete single-channel files -- Sidecar audio must sync to the video source file delivered to Roku -- Roku supports one sidecar audio dub file per language - -Below are the supported sidecar audio formats. Deliver sidecar audio with highest bitrate and sampling rate available. - -| Container | Codecs | Extension | -| --------------- | ------------ | --------- | -| WAV (preferred) | PCM | .wav | -| MPEG-1 Layer 3 | MP3 | .mp3 | -| OGA | Opus, Vorbis | .ogg | - -#### Descriptive audio - -Descriptive audio is an alternate audio track for the visually impaired. The official FCC Audio Description documentation can be found at the below link: - -[https://www.fcc.gov/audio-description](https://www.fcc.gov/audio-description) - -Roku strongly prefers to receive descriptive audio tracks wherever available. Descriptive audio deliveries will follow the deliverables outlined in the [Secondary Audio Deliverables](#secondary-audio-deliverables) section above - -#### Audio channel layout hints - -In the event video files cannot be created to include proper audio channel labels, an audio layout hint must be provided in the metadata for the video files that are delivered. The available hints are defined below. - -##### Audio layout hints - -| Descriptor | Definition | -| ------------------ | ------------------------------------------------------------------------------------------------ | -| stereoOnly | 2 channel stereo audio only. Can be delivered on a single track or on 2 discrete tracks | -| surroundOnly | 6 channel 5.1 surround audio only. Can be delivered on a single track or on 6 discrete tracks | -| stereoPlusSurround | 8 channel audio with stereo on channels 1 and 2 followed by 5.1 surround on channels 3 through 8 | -| surroundPlusStereo | 8 channel audio with 5.1 on channels 1 through 6 followed by stereo on channels 7 and 8 | - -### Closed captions and subtitles - -Closed captions (also known as subtitles for the deaf or hard of hearing or SDH subtitles) and subtitles, while similar, serve separate distinct functions: - -**Closed captions/SDH subtitles/subtitles for the deaf or hard of hearing** - -- Transcribes the spoken dialogue and the sounds heard in an audio track -- Intended as an accessibility device for the deaf or hard of hearing -- Can be enabled/disabled (toggled on/off) by the viewer during playback -- Includes text that describes sound effects and/or music cues and lyrics -- Must include a full transcription of all spoken dialogue and narrative text that needs to be understood by the viewer, including forced narratives as the Roku player will only display a single text track at a time -- Are companions to an audio track and must be provided in the same language and locale as that audio track -- Will not be made available to the viewer if a companion audio track in the same language is not provided -- May be required per regulatory agencies in certain territories - -**Full subtitles** - -- Translates all narratively important spoken dialogue and on-screen text from one language to another -- Intended as a localization device when an audio track is in a language that the viewer does not understand -- Must include a full translation of all spoken dialogue and narrative text that needs to be understood by the viewer, including forced narratives as the Roku player will only display a single text track at a time -- Can be enabled/disabled (toggled on/off) by the viewer during playback -- Does not include text that describes sound effects or music cues, but may translate song lyrics if narratively important to the viewer or as a creative choice -- Can be made available to the viewer regardless of the audio track language(s) delivered - -**Forced narrative subtitles** - -- Translates narratively important spoken dialogue and/or on-screen text for the purpose of conveying information that may not be understood by the viewer. This information could include: - - Spoken dialogue in a language different from the audio track language selected by the viewer - - On-screen text in a language different from the audio track selected by the viewer - - Inaudible or difficult to hear audio (such as an overly noisy scene or poor-quality audio recordings) -- Intended as a localization device when a portion of a program is presented in a language different from the main audio track language selected by the viewer or is otherwise unintelligible -- Can NOT be enabled/disabled (toggled on/off) by the viewer during playback - - _Forced narrative playback WILL be disabled when the viewer enables a CC/SDH/Subtitle track as the Roku player will only display a single text track at a time. For this reason, it is required that CC/SDH and full subtitles contain all forced narrative elements_ -- Are companions to an audio track and must be provided in the same language and locale as that audio track -- Will automatically display based on the audio language track selected by the viewer - -### Closed captions - -Roku prefers to receive closed captioning for all content to provide the best user experience possible. - -For content intended for the US, Roku adheres to FCC closed captioning rules regarding Internet Video Programming. Those rules can be found at the below link: - -[https://www.fcc.gov/consumers/guides/captioning-internet-video-programming](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming) - -All content required by the FCC to have closed captioning must be delivered to Roku with closed captions and those captions must be conformed and synced to program. For content that is exempt from the closed caption requirement per FCC rules, a valid exemption code number must be included in the metadata. Allowable exemption code numbers and their definitions: - -1 - The content has never aired on television in the United States.
2 - The content has only aired on television in the United States without captions.
3 - The content has not aired on television in the United States with captions since September 30, 2012.
4 - The content does not consist of full-length video programming.
5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)).
6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. - -For content intended for territories outside of the US, Roku will adhere to the requirements in that territory. - -Captions may be provided in one of two ways: - -- EIA-608/CEA-708 embedded in-stream in the video file -- Sidecar caption file -- Roku prefers a human-readable sidecar subtitle file such as .ttml, .dfxp, .vtt, or .srt -- See below for a full listing of supported sidecar caption files -- Sidecar captions must begin at timecode hour 00:00:00:00 as the Roku encoder does not honor the timecode embedded in the video file -- Do not provide an empty file (a file without text) for sidecar captions -- TTML and WebVTT positional data supported -- Positional data provided in TTML and WebVTT captions will be honored as defined in the file provided - -_Closed caption text styling support is limited to:_ - -- _bold \ and italic \ tags_ -- _text color_ -- _text positioning_ - -_Quicktime video files must be accompanied by a sidecar closed caption file. Roku does not support the Quicktime text track._ - -| **Format Name** | Supports Positional Data | **File Extension** | Encoding | **Delivery Type** | **Languages** | -| ------------------------------------------- | ------------------------ | ------------------ | -------- | ----------------------- | ------------------------------------------------------- | -| Timed Text Markup Language (TTML) | Y | .ttml | UTF-8 | sidecar | follows audio language of either video file or dub file | -| Web Video Text Track (WebVTT) | Y | .vtt or .webvtt | UTF-8 | sidecar | follows audio language of either video file or dub file | -| Distribution Format Exchange Profile (DFXP) | N | .dfxp | UTF-8 | sidecar | follows audio language of either video file or dub file | -| EBU Subtitle Data Exchange Format (STL) | N | .stl | UTF-8 | sidecar | follows audio language of either video file or dub file | -| SubRip Text (SRT) | N | .srt | UTF-8 | sidecar | follows audio language of either video file or dub file | -| EIA-608/CEA-708 | N | n/a | n/a | Embedded in MPEG stream | embedded in video file | -| SCC | N | .scc | ASCII | sidecar | follows audio language of either video file or dub file | - -### Subtitles - -Content delivered with an audio language that is not primary to the territory of distribution must be delivered with an audio dub and/or subtitle file translating the content into that territory’s primary language. - -- Full subtitles must NOT be burned into the video -- Roku prefers a human-readable sidecar subtitle file such as .ttml, .dfxp, .vtt, or .srt -- See below for a full listing of supported sidecar subtitle files -- Sidecar subtitles must begin at timecode hour 00:00:00:00 as the Roku encoder does not honor the timecode embedded in the video file -- Do not provide an empty file (a file without text) for sidecar subtitles -- TTML and WebVTT positional data supported -- Positional data provided in TTML and WebVTT captions will be honored as defined in the file provided - -_Subtitle text styling support is limited to:_ - -- _bold \ and italic \ tags_ -- _text color_ -- _text positioning_ - -| **Format Name** | Supports Positional Data | **File Extension** | Encoding | **Delivery Type** | **Languages** | -| ------------------------------------------- | ------------------------ | ------------------ | -------- | ----------------- | ------------------------------------------------------------------------------------------------------------ | -| Timed Text Markup Language (TTML) | Y | .ttml | UTF-8 | sidecar | must conform to a supported [language code](#language-codes). Please also include region code where possible | -| Web Video Text Track (WebVTT) | Y | .vtt or .webvtt | UTF-8 | sidecar | must conform to a supported [language code](#language-codes). Please also include region code where possible | -| Distribution Format Exchange Profile (DFXP) | N | .dfxp | UTF-8 | sidecar | must conform to a supported [language code](#language-codes). Please also include region code where possible | -| EBU Subtitle Data Exchange Format (STL) | N | .stl | UTF-8 | sidecar | must conform to a supported [language code](#language-codes). Please also include region code where possible | -| SubRip Text (SRT) | N | .srt | UTF-8 | sidecar | must conform to a supported [language code](#language-codes). Please also include region code where possible | - -### Artwork - -Roku supports three image types for each piece of content. Each image type will be used in a different location within Roku Channel. Roku prefers to receive all three art sizes whenever possible. Each image must be delivered in JPEG or PNG format. Please provide images in Roku's preferred image resolution to avoid delays in publishing. Images _must_ meet or exceed the minimum resolution and _must_ be delivered in the _exact_ aspect ratio defined for each image type. - -#### Image type definitions - -| Format | Extensions | Image Type | Aspect
Ratio | Minimum
Resolution | Preferred
Resolution | -| :------------------------------- | :------------------------ | :----------------------------------------------------------- | :---------------- | :---------------------- | :------------------------ | -| JPEG or PNG
RGB
72 ppi | .jpg
.jpeg
.png | Texted key art image with title treatment | 16:9 | 800x450 | 1920x1080 | -| JPEG or PNG
RGB
72 ppi | .jpg
.jpeg
.png | Textless background image used in background of program page | 16:9 | 800x450 | 1920x1080 | -| JPEG or PNG
RGB
72 ppi | .jpg
.jpeg
.png | Texted vertical poster image with title treatment | 2:3 | 534x801 | 2000x3000 | - -#### Minimum art requirements by content type - -##### Clip content type art requirements - -| Art | Required/Preferred | Notes | -| ------------ | ------------------ | ------------------------------------------------ | -| 16:9 Key Art | Required | Only the 16:9 texted image is required for Clips | - -##### Movie content type art requirements - -| Art | Required/Preferred | Notes | -| --------------- | ------------------ | ---------------------------------------------------------------------------------------------- | -| 16:9 Key Art | Required | At a minimum, Roku requires the 16:9 Key Art for all Movie assets. All 3 images are preferred. | -| 2:3 Box Cover | Preferred | At a minimum, Roku requires the 16:9 Key Art for all Movie assets. All 3 images are preferred. | -| 16:9 Background | Preferred | At a minimum, Roku requires the 16:9 Key Art for all Movie assets. All 3 images are preferred. | - -##### TV content type art requirements - -###### Series content type - -| Art | Required/Preferred | Notes | -| --------------- | ------------------ | ----------------------------------------------------------------------------------------------- | -| 16:9 Key Art | Required | At a minimum, Roku requires the 16:9 Key Art for all Series assets. All 3 images are preferred. | -| 2:3 Box Cover | Preferred | At a minimum, Roku requires the 16:9 Key Art for all Series assets. All 3 images are preferred. | -| 16:9 Background | Preferred | At a minimum, Roku requires the 16:9 Key Art for all Series assets. All 3 images are preferred. | - -###### Episode content type - -| Art | Required/Preferred | Notes | -| --------------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 16:9 Background | Required | Episodic image may be letterboxed or pillarboxed depending upon the source video. Windowboxed images will be rejected. Episodic images should be unique for each episode and represent the content of the episode | - -#### Artwork content guidelines - -- Key Art (graphic with the full title of the asset visible) -- No sexually explicit or graphically violent artwork -- Artwork should be post-theatrical and not include language such as _In Theaters Now_ or _Coming Soon_ -- Artwork designed specifically for digital delivery is preferred -- Artwork for international territories should be localized for each territory -- For content on Roku Channel, Roku will not accept branded artwork without prior approval for any individual video asset nor for season/series entities. -- Calls to action (CTAs) or links to external platforms or sites are not permissible and must be removed from the image file prior to delivery to Roku - -#### Artwork placement on platform examples - -**Movie artwork -browse experience** - -Highlighted example of the 16:9 texted image with title treatment - -![roku400px - movieGrid](https://image.roku.com/ZHZscHItMTc2/movieBrowse.jpg) - -**Movie artwork -details experience** - -Highlighted example of the 16:9 textless image - -![roku400px - movieDetails](https://image.roku.com/ZHZscHItMTc2/movieDetail.jpg) - -**Series artwork - browse experience** - -Highlighted example of the 16:9 texted series image with title treatment - -![roku400px - seriesGrid](https://image.roku.com/ZHZscHItMTc2/seriesBrowse.jpg) - -**Series artwork - details experience** - -Highlighted example of the 16:9 textless series image - -![roku400px - seriesDetail](https://image.roku.com/ZHZscHItMTc2/seriesDetails.jpg) - -**Episode artwork - episode picker experience** - -Highlighted example of the 16:9 textless episode images - -![roku400px - episodePicker](https://image.roku.com/ZHZscHItMTc2/episodePicker.jpg) - -**Episode artwork - episode details experience** - -Highlighted example of the 16:9 textless episode image - -![roku400px - episodeDetail](https://image.roku.com/ZHZscHItMTc2/episodeDetail.jpg) - -**Clip artwork - browse experience** - -Highlighted example of the 16:9 texted image with title treatment - -![roku400px - clipGrid](https://image.roku.com/ZHZscHItMTc2/clipBrowse.jpg) - -**Poster artwork - search experience** - -Highlighted example of the 2:3 texted image with title treatment from the Search experience. 2:3 images are preferred for series and movie content types - -![posterSearch](https://image.roku.com/ZHZscHItMTc2/posterSearch.jpg) - -## Delivery guidelines - -Roku accepts content via Aspera which can be configured as either an Aspera Shares (using the Aspera Connect Browser plugin) or as an Aspera P2P/Enterprise connection (using Aspera Client or Console). - -Alternate file transfer or physical delivery methods may be evaluated on a case-by-case basis and must be approved by Roku. Any physical media/hard drives Roku may accept will not be returned. - -### Aspera shares delivery - -Provide the name(s) and email address(es) for users that will be transmitting content to Roku for Roku Channel. - -Roku’s Aspera Shares URL: [https://aspera.sr.roku.com](https://aspera.sr.roku.com) - -You will need to install the Aspera Connect browser plugin to upload content via Aspera Shares. - -Invitations to create an Aspera Shares account will come from Roku’s Aspera Shares server. These automated invitation emails can be flagged as spam or junk emails or can be blocked by an organization’s email filtering system or firewall. Please check the spam/junk folder for the invitation and move it from the spam/junk folder before trying to access the link provided. - -### Aspera enterprise/P2P/HSTS delivery - -Roku authenticates through RSA Public/Private key exchange. To complete this configuration, please provide a Public RSA-SSH key. - -Steps to create SSH keys can be found in [Aspera’s official documentation](https://download.asperasoft.com/download/docs/ascp/3.5.2/html/dita/creating_public_key.html) - -Roku will provide host and username information during onboarding. - -**Aspera Client** - -[Aspera Client Download](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software\&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all) - -#### Transfer Bandwidth - -Roku recommends verifying or updating the global and user preferences of the Aspera Client to align with your preferred upload bandwidth. Please note Roku applies a global bandwidth cap of 300Mbps. - -![asperaPreferences](https://image.roku.com/ZHZscHItMTc2/asperaPreferences.jpg) - -Depending on what client is being used, there are different settings that can affect transfer speeds. - -- If using the Desktop Client GUI, global settings can be set [https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-global-bandwidth-settings](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-global-bandwidth-settings) -- Transfer speeds can also be set on a per-Connection level (the "Speed" setting in step 7): [https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-adding-editing-connections](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-adding-editing-connections) -- If connecting via command line, there is a specific switch: `-l 100m` would set the transfer rate at 100Mbps -- If connecting via Aspera Shares, target rates can be set both system-wide or per-user in the Shares web interface [https://www.ibm.com/docs/en/aspera-shares/1.10?topic=options-configuring-transfer-settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=options-configuring-transfer-settings) [https://www.ibm.com/docs/en/aspera-shares/1.10?topic=accounts-configure-user-settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=accounts-configure-user-settings) - -### File delivery - -- Video, closed captions, and artwork files must be _completely delivered prior to the delivery of metadata_ -- Production files MUST be delivered to the `/prod` folder. Automation is dependent on proper file delivery location. Failure to deliver files to the correct folder will result in processing delays or content not processing at all -- Test files may be delivered to the `/testing` folder -- It is preferred that content not be delivered to subfolders. If subfolders are necessary, follow the below guidelines: -- Subfolders must **not** begin with an underscore -- Do **not** separate files into subfolders by file type -- All media files for a single title (episode, movie, or shortForm) must be delivered to the same directory -- The ingest platform assumes media files referenced in the metadata are in the same directory as the metadata file. As such, metadata must be delivered to the same directory as the media files contained within the metadata -- Delivery notifications can be sent to [deliverynotifications@roku.com](mailto:deliverynotifications@roku.com) - -#### File retention - -The delivery location is a temporary location for our Partners to upload files for ingestion into Roku Channel content library. Automation will move files from the delivery location upon successful ingest to an archive location to be stored indefinitely. All files uploaded to the delivery location are expected to be ingested within a reasonable time frame not to exceed 30 days. Valid and complete metadata must be delivered shortly after files are delivered to ensure timely ingest. Files in the delivery location that have not ingested after 30 days are subject to deletion. - -_Exceptions to the file retention policy may be made to files in the _`/testing`_ folder_ - -#### File naming - -Source video, closed captions, and artwork files delivered for ingest must adhere to the following guidelines: - -- File names must not exceed 125 characters in length -- File names must match the reference to the file name in the metadata supplied for the title delivered -- File names are case-sensitive -- File names must end with a proper file extension. File extensions are expected to be lowercase -- Whitespace and special characters `!@#$%^&*()\{}|[];:\’\”?/>,\<` must not be included in any file name -- The same image can be used for every episode of a series, but it is not ideal. If the same image is used for every episode, that image must be delivered multiple times and uniquely named for each episode. For example, “episode.jpg” should be delivered as “episode_01.jpg”, “episode_02.jpg”, etc.… - -
- -##### Characters allowed in file names - - - - - - - - - - - - - -
- Character sets -
- - 0-9 - - a-z - - A-Z -
- -
- -| Character name | Character | -| -------------- | --------- | -| Hyphen | - | -| Period | . | -| Underscore | \_ | - -##### Characters forbidden in file na - -| Character Name | Character | -| :--------------------------- | :-------- | -| "At" symbol | @ | -| Ampersand | & | -| Asterisk | \* | -| Backslash | \\ | -| Caret | ^ | -| Colon | : | -| Comma | , | -| Dollar | $ | -| Equals | = | -| Forward slash | / | -| Grave accent | \` | -| Greater than | > | -| Left curly brace | \{ | -| Left square bracket | \[ | -| Less than | \< | -| Percent | % | -| Plus | + | -| Pound/hashtag | # | -| Question mark | ? | -| Quotation marks/double quote | " | -| Right curly brace | \} | -| Right square bracket | ] | -| Semicolon | ; | -| Space | ` ` | -| Tilde | \~ | -| Vertical pipe | \| | - -
- -## MovieLabs content delivery - -Order of delivery is important. The Roku MovieLabs service will require that the MMC XML file be delivered after all media files referenced within have completed delivery. Roku cannot process content without successful delivery of both the MMC and MEC XMLs. Please see examples below: - -- For each MMC, all files referenced in the MMC should be delivered prior to the delivery of the MMC XML to be considered a successful delivery -- For each MEC, all files referenced in the MEC should be delivered prior to the delivery of the MEC XML to be considered a successful delivery -- Movies, Series, Seasons, and Episodes require successful delivery of both MMC and MEC to ingest -- Episodes cannot ingest without successful delivery and ingest of MMC and MEC of the Season to which the Episode belongs -- Seasons cannot ingest without successful delivery and ingest of MMC and MEC of the Series to which the Season belongs -- Episodes processed by Roku’s system before the Series and/or Season to which the Episode belongs will be held in an uningested state until the Series and/or Season has been successfully delivered -- Seasons processed by Roku’s system before the Series to which the Season belongs and/or an Episode belonging to that Season will be held in an uningested state until the Series and/or an Episode has been successfully delivered -- Series processed by Roku’s system before a Season and an Episode belonging to that Series will be held in an uningested state until a Season and Episode has been successfully delivered - -### Roku specific metadata and media files - -[Video files](#video-requirements), [audio files](#audio-requirements), [closed caption files](#closed-captions), [subtitle files](#subtitles), [image files](#artwork), [minimum metadata requirements](#minimum-required-metadata-by-content-type), [genres](#genres), and [ratings and rating sources](#rating-values-by-rating-system-and-country), must adhere to the supported formats and requirements defined in this specification - -#### Tags - -Tags for merchandising/curation can be delivered via the Keyword node supported in the MovieLabs MEC XML. Please see the [MovieLabs MEC Schema](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link116) for proper placement of the Keyword node - -Example: - -```xml - - Great Title of My Show - Short summary of my show. - Longer summary of my show. - - keyword - -``` - -#### TMS IDs - -Gracenote TMS IDs can be delivered via the MovieLabs MEC XML as an Identifier with Namespace TMSID in the AltIdentifier node. Please see the [MovieLabs MEC Schema](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link121) for proper structure of the AltIdentifier node - -Example: - -```xml - - TMSID - EP012345678910 - -``` - -#### MMC XML ad breaks and cue points - -Ad break, intro credit, and end credit cue points can be supplied in the MovieLabs MMC XML in the Markers node. Please see the [MovieLabs MMC Schema](https://movielabs.com/md/manifest/v1.10/manifest-v1.10/manifest-v1.10.html#Link184) for proper structure of the Markers node - -Example: - -```xml - - - - - 155.071 - FIRST_FRAME_EPISODE_INTRO - FFEI - - - 200.867 - LAST_FRAME_EPISODE_INTRO - LFEI - - - - - - 3669.207 - FIRST_FRAME_UP_NEXT - FFUN - - - 3812.517 - LAST_FRAME_UP_NEXT - LFUN - - - - - - 737.111 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 1361.276 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 1948.821 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 2841.421 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 3270.100 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - -``` - -### MovieLabs schema validation - -Roku is using Apache [xmlbeans](https://xmlbeans.apache.org/download/index.html) for parsing & validating the MEC MMC XML files. You can use the command line tool provided in xmlbeans to validate. - -1. Download & extract xmlbeans to local -2. From command line, cd to the xmlbeans bin directory -3. Inside bin directory you will find the validate tool -4. Also download the official MovieLab schema xsd files to local ( [https://movielabs.com/schema/manifest/v1.10/manifest-v1.10.xsd](https://movielabs.com/schema/manifest/v1.10/manifest-v1.10.xsd) [https://movielabs.com/schema/mdmec/v2.9/mdmec-v2.9.xsd](https://movielabs.com/schema/mdmec/v2.9/mdmec-v2.9.xsd) ) -5. Usage: validate schema.xsd instance.xml ( be sure to point schema.xsd to mdmec-v2.9.xsd for MEC, and manifest-v1.10.xsd for MMC ) -6. From the command line output you can tell if the given xml is valid or not - -**Example usage** - -```bash -./validate ~/dev/movielabsSpec/schema/mdmec-v2.9.xsd /path/to/file/directory/MEC_SAMPLE_123456789.xml -``` - -**Example response** - -```text -XMLBEANS_LIB=./../lib -ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... -/path/to/file/directory /MEC_SAMPLE_123456789.xml valid -``` - -## Metadata requirements - -Roku utilizes a transform engine that can “normalize” different metadata formats to fit Roku’s ingestion needs. Exact element or field names are not as important as consistent delivery of agreed upon element or field names. The data within any field must conform to Roku Channel Ingest Specification regardless of element or field name. If you use an XML format for delivery of your content to other platforms, you may be able to repurpose this for delivery to Roku. You may provide a sample of this existing metadata format during onboarding for Roku to evaluate validity for ingest into Roku Channel. Regardless of the format delivered, all required elements/fields must be provided in the metadata deliverable. - -### Minimum required metadata by content type - -
- - - - - - - - - - - - - - - - - - - - - - - -
- Film/Clip Requirements - - TV Requirements -
- - provider - - content type - - asset_id - - title - - release_date - - runtime - - genres - - rating - - rating_system - - short_synopsis - - video_file_name - - captions file_name (if captions are required) - - key art file_name - - - provider - - - content type - - - asset_id - - - episode_title - - - episode_number - - - episode_release_date - - - runtime - - - rating - - - rating_system - - - episode_short_synopsis - - - series_id - - - series_title - - - series_release_date - - - series_genres - - - series_short_synopsis - - - season_id - - - season_number - - - video_file_name - - - captions file_name (if captions are required) - - - key art file_name -
- - - -
- -### Content type definitions - -Roku Channel supports 3 content types: tv, film, and clip. All content must be delivered as one of these 3 content types. Titles must be delivered to Roku Channel in the same content type the program was originally available in. The below definitions can help guide how to classify content that is intended for Roku Channel. - -**TV** - -Episodic content that is structured in a series --> season --> episode hierarchy should be delivered to the TV specification. - -**Film** - -Full length, long form, stand-alone titles should be delivered to the Film specification. Any program that is not intended to be nested in a series/season/episode hierarchy and exceeds roughly 15 minutes run time should be considered a film. This includes stand-alone TV Specials. - -**Clip** - -Short form, stand-alone titles that do not exceed roughly 15 minutes run time should be delivered to the Clip specification. - -### ID requirements and expectations - -Roku does not supply IDs for content. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. Every clip and movie must be delivered with an asset_id. Every episode must be delivered with 3 IDs: an asset_id, a series_id, and a season_id. IDs need to be meaningful to your team as they are how we positively identify a title in our system. The asset ID in the ingest metadata should match the Title ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. Any updates to the title once it has been ingested into our system MUST be accompanied by the asset ID. Guidelines and definitions of IDs are below: - -| **ID** | Definitions | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| asset_id | Immutable, unique identifier for a clip, episode, or movie. Required for all content. 50 characters maximum. Alphanumeric characters, hyphens, and underscores only – **SPACES OR SPECIAL CHARACTERS IN ANY ID WILL FAIL INGESTION** | -| series_id | Immutable, unique identifier for a series. Cannot be the same as the season or unique episode ID. Must be delivered with all episodes of a series and must be consistent for all episodes of a series. Required for TV content. 50 characters maximum. Alphanumeric characters, hyphens, and underscores only – **SPACES OR SPECIAL CHARACTERS IN ANY ID WILL FAIL INGESTION** | -| season_id | Immutable, unique identifier for a season. Cannot be the same as the series or unique episode ID. Must be delivered with all episodes of a season of a series and must be consistent for all episodes within that season. Required for TV content. 50 characters maximum. Alphanumeric characters, hyphens, and underscores only – **SPACES OR SPECIAL CHARACTERS IN ANY ID WILL FAIL INGESTION** | - -### Availability sheets/planners - -Roku requests an initial launch list of titles/episodes/clips in current library that are available to Roku at the time of onboarding and a schedule when the content will be refreshed. For ongoing production, Roku requests that Avails be provided 60 days prior to licensing window start and the content be delivered at least 30 days before curation onto the channel. This will allow ample time for processing and QC of the content before it goes live on Roku Channel. Delivery capacity to be coordinated after signing - -| Documents | | -| ------------------- | ---------------------------------------------------------------------------------- | -| Roku Avail Spec | Check out the avail specifications page [here](https://go.roku.com/trc-avail-spec) | -| Roku Avail Template | Download Roku's avail template [here](https://go.roku.com/trc-avail-template) | - -### Availability windows - -Roku has the ability for content to display on-device and for user playback at a specific starting time. By default, content will go into window at 12:00 am (midnight) and expire at 11:59:59 pm in the users’ time zone. - -If content is to go live at a time other than midnight or expire at a time other than 11:59:59 pm, the license window start or end values in the inbound metadata must include the desired times. - -There are two types of specific time designations – relative and absolute. - -- Relative Time – a Saturday night premiere of a movie goes into window at 9pm local time for all users. A user in the Eastern Time Zone watches at 9pm but a user in the Pacific Time Zone, at the exact same moment (6pm PT), cannot watch that content. -- Absolute Time – a new episode of a series goes into window at 9pm Eastern and becomes immediately available across all time zones. A user in the Pacific Time Zone can watch the content at 6 pm local time. - -While time settings are dictated by the content owner, Roku will need the metadata as follows: - -- If the content has a relative start time, that time must be indicated in the ingest metadata and formatted as “yyyy-mm-ddThh:mm:ss” (2019-11-01T21:00:00) -- If the content has an absolute start time, that time must be indicated in the ingest metadata. The time must be presented as UTC time and formatted as “yyyy-mm-ddThh:mm:ssZ” (2019-11-02T01:00:00Z). -- In this example, 9 pm Eastern Time on November 1 is 1 am UTC ([https://www.thetimezoneconverter.com](https://www.thetimezoneconverter.com)) -- If the ingest metadata arrives without a time, Roku will assume a relative start time of midnight and a relative end time of 11:59:59 pm - -### Special characters - -Roku utilizes CDATA sections to allow special characters (e.g. `!@#$%^&*()\{}|[];:\’\”?/>\<`, as well as foreign character sets) within certain node values of the ingest XML. Roku highly recommends wrapping data in CDATA sections to ensure proper ingest of content. The below nodes are the _only_ nodes that support CDATA sections: - -- title -- long_synopsis -- short_synopsis -- display_name - -Certain characters in an XML will render the document unreadable by the Roku ingest platform unless handled (escaped) properly. The below characters must be provided in their Escaped Form for all node values that do not support CDATA sections: - -| Character Name | Character | Escaped Form | -| -------------- | --------- | ------------ | -| Ampersand | & | `&` | -| Less-than | \< | `<` | -| Greater-than | > | `>` | -| Quotes | " | `"` | -| Apostrophe | ' | `'` | - -Special characters should never be used in file names or file name references within the XML or Excel metadata. [See File Naming Guidelines](#file-naming) for more on this. - -### Supported metadata formats - -XML format preferred. One complete XML shall be delivered for each movie, clip, or TV episode video file delivered. Metadata shall be delivered via Aspera to the same folder location as the video, captions, and artwork files. - -**Supported metadata formats** - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Format Name - - Format Extension - - Encoding - - Package Version -
- XML
(preferred) - 		- .xml - - UTF-8 - - clip1.0
film5.0
tv1.0
Cablelabs ADI 1.1
MEC 2.9
MMC 1.10 - - Additional schemas supported on a case-by-case basis -
- Excel - - .xlsx - - See below for [Roku Excel Metadata Templates](#roku-excel-metadata-guildelines) and [Excel Metadata Guidelines](#roku-excel-metadata-guidelines-and-templates) - - -
- -### Metadata updates (MDU) and file replacements - -Updates are automated and can be sent if there is a need to change metadata or asset files for any program that has previously been delivered to Roku Channel. All metadata and/or file replacement updates must include **Provider**, **Asset ID**, and **Content Type** of the program as it was originally delivered to Roku for the update to succeed. Version control will be handled by Roku's system, there is no need to provide versioning information in the metadata. - -Roku currently supports updating the below metadata fields via automated MDU: - -- TMS ID -- EIDR ID -- Titles (primary and localized) -- Short Descriptions (primary and localized) -- Long Descriptions (primary and localized) -- Release Date -- Series Titles -- Season Number -- Episode Number -- Language (and localized languages) -- Availability Windows -- License Types -- Countries -- Genres -- Provider Tags -- Content Ratings (system & rating) -- Credits -- Ad Breaks -- Cue Points - -**Metadata update (MDU)** - -Metadata updates (MDUs) are automated and will be processed in the same manner as content that needs to be ingested into Roku Channel's content library. Please follow the procedure outlined below to update metadata only. - -Metadata updates must be delivered in the same format as the ingest metadata - -Metadata updates must include **the exact same asset ID** that was included when the content was originally ingested - -_Please reach out to [contentoperations@roku.com](mailto:contentoperations@roku.com) if you need a complete listing of asset IDs as they exist in Roku Channel's system_ - -All file name references must be removed from a metadata only update. This includes: - -- source video file name -- closed captions file name -- subtitle file name -- audio dub file name -- key, background, and/or poster art file names - -Some fields need to be updated in "groups". All required fields in a group must be provided for the update to process successfully. Below are the current groups: - -- Metadata group (all of the required fields must be present in order to update one of these) - -- Language (required) - -- Title (required) - -- Short description (required) - -- Long description (optional) - -- Availability group (all of the required fields must be present in order to update one of these) - -- License Type (required) - -- Country (required) - -- Start Date (required) - -- End Date (required) - -Upload the metadata update to the "prod" folder in Aspera - -_If you do not see the update reflected on Roku Channel within 24 hours, please reach out to [contentoperations@roku.com](mailto:contentoperations@roku.com)_ - -**File replacements and additions** - -File replacements and additions are automated and will be processed in the same manner as content that needs to be ingested into Roku Channel's content library. A file replacement will replace a file that currently exists in Roku Channel's library. A file addition will add a new file to an existing record in Roku Channel's library. A file addition would be used to add localized subtitles or dubs to an existing record. Please follow the procedure outlined below to replace one or more files. - -1. File replacements and additions must be delivered in the same format as the ingest metadata -2. File replacements and additions must include **the exact same asset ID** that was included when the content was originally ingested - -- _Please reach out to [contentoperations@roku.com](mailto:contentoperations@roku.com) if you need a complete listing of asset IDs as they exist in Roku Channel's system_ - -3. Only the file name references of the files that are being replaced or added should be included in the metadata file. Any file that is not being replaced or added should not be delivered or referenced in the metadata file. -4. If the source video file is being replaced and there is a change in the duration of the source, any related files (captions, subtitles, audio dubs) should also be replaced. -5. File replacements require language values in order to update properly -6. Upload the file replacement or addition metadata to the "prod" folder in Aspera - -\_As a best practice, please provide replacement files with a unique name both in the metadata and on the file itself. Simply adding a versionnumber (\_v2, _v3, etc.) would suffice. For example:_ `movie_title_v2.mov` - -**Content takedown** - -If rights change from when the content was originally delivered to Roku and content needs to be removed from Roku Channel either immediately or scheduled, the availability end date can be changed by providing ametadata update as defined [below](#metadata-updates-mdu-and-file-replacements). Explicit updates should be provided for all territories from which thecontent should be removed. Please be aware that end dates providedwithout time values specified will expire at 11:59:59pm on that date. - -### Roku XML metadata requirements, samples, and schemas - -| Roku XML Schema | Download Link | -| --------------------------------- | --------------------------------------------------------- | -| Film XML Schema | [Download here](https://go.roku.com/film-xml-schema) | -| TV XML Schema | [Download here](https://go.roku.com/tv-xml-schema) | -| Clip XML Schema | [Download here](https://go.roku.com/clip-xml-schema) | -| **Roku XML Samples** | **Download Link** | -| Annotated Roku Film XML | [Download here](https://go.roku.com/film-xml-example) | -| Annotated Roku TV XML | [Download here](https://go.roku.com/tv-xml-example) | -| Annotated Roku Clip XML | [Download here](https://go.roku.com/clip-xml-example) | -| **Sample Cablelabs ADI Metadata** | **Download Link** | -| Cablelabs Film ADI XML Example | [Download here](https://go.roku.com/film-adi-xml-example) | -| Cablelabs TV ADI XML Example | [Download here](https://go.roku.com/tv-adi-xml-example) | -| Cablelabs Clip ADI XML Example | [Download here](https://go.roku.com/clip-adi-xml-example) | - -**NOTE:** Cablelabs ADI samples are intended for illustrative purposes and not necessarily as templates. The required data must be supplied in a static node in each XML. - -*** - -### XML - film metadata fields - -**package** - -Defines the package version type - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/@version` | film5.0 | Required | - -Example: - -```xml - -``` - -**provider** - -Name of content owner/studio/network - -| XML XPath | Example | Required | -| ------------------- | -------------- | -------- | -| `/package/provider` | Roku Originals | Required | - -Example: - -```xml -Roku Originals -``` - -**language** - -Primary language of the package metadata. At a minimum, the value must conform to a supported [language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------- | -------- | -| `/package/language` | Valid [language value](#language-codes) (en, es, etc.)May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml -en -``` - -**type** - -Defines the content type of the package - -| XML XPath | Accepted Values | Required | -| --------------------- | --------------- | -------- | -| `/package/video/type` | film | Required | - -Example: - -```xml -film -``` - -**asset_id** - -Immutable, unique identifier for a movie. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit - -| XML XPath | Accepted Values | Required | -| ------------------------- | ----------------------------------------------------------------------------- | -------- | -| `/package/video/asset_id` | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | Required | - -Example: - -```xml -movieAssetIdHere -``` - -**eidr** - -EIDR ID if one exists - -| XML XPath | Accepted Values | Required | -| --------------------- | ----------------- | -------- | -| `/package/video/eidr` | Any valid EIDR ID | Optional | - -Example: - -```xml - -``` - -**tmsId** - -Gracenote ID if one exists - -| XML XPath | Accepted Values | Required | -| ---------------------- | ---------------- | -------- | -| `/package/video/tmsId` | Any valid TMS ID | Optional | - -Example: - -```xml - -``` - -**title** - -Title of movie. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) - -| XML XPath | Example | Required | -| ---------------------- | ----------- | -------- | -| `/package/video/title` | Movie Title | Required | - -Example: - -```xml -<![CDATA[Movie Title. Required.]]> -``` - -**short_synopsis** - -A short synopsis of the content. CDATA section supported. 250-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------- | ---------------------- | -------- | -| `/package/video/short_synopsis` | 250-character synopsis | Required | - -Example: - -```xml - -``` - -**long_synopsis** - -A long synopsis of the content. CDATA section supported. 500-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | ---------------------- | -------- | -| `/package/video/long_synopsis` | 500-character synopsis | Required | - -Example: - -```xml - -``` - -**original_spoken_language** - -Defines the original production language of the title being delivered. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/original_spoken_language` | Valid [language value](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml -en -``` - -**country_of_origin** - -Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. - -| XML XPath | Accepted Values | Required | -| ---------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `/package/video/country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -Example: - -```xml -en -``` - -**closedCaptions** - -Indicates whether the title delivered contains closed captions. Accepted values are Y or N. This field is required for all content intended for Roku Channel in the US - -| XML XPath | Accepted Values | Required | -| ------------------------------- | --------------- | ------------------------------ | -| `/package/video/closedCaptions` | Y or N | Required for content in the US | -| | | | - -Example: - -```xml -Y -``` - -**closedCaptionsExemption** - -FCC exemption code for closed caption requirement. This node is required if the `closedCaptions` value = “N” - -Allowable value and their definitions: 1 - The content has never aired on television in the United States. 2 - The content has only aired on television in the United States without captions. 3 - The content has not aired on television in the United States with captions since September 30, 2012. 4 - The content does not consist of full-length video programming. 5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)). 6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------- | ------------------------------ | -| `/package/video/closedCaptionsExemption` | 1, 2, 3, 4, 5, 6 | Required if closedCaptions = N | - -Example: - -```xml -1 -``` - -**release_date** - -Original date content was first made available in any presentation. Must include accurate year of release at a minimum - -| XML XPath | Accepted Values | Required | -| ----------------------------- | --------------------------------------- | -------- | -| `/package/video/release_date` | Conforms to ISO 8601 format: YYYY-MM-DD | Required | - -Example: - -```xml -YYYY-MM-DD -``` - -**runtime** - -Total run time of content in whole minutes - -| XML XPath | Accepted Values | Required | -| ------------------------ | --------------- | -------- | -| `/package/video/runtime` | Integers only | Required | - -Example: - -```xml -120 -``` - -**genre** - -Genre classification of the content. Roku requires each movie to be delivered with at least one supported genre. Please see [enumerated list](#genres) of genres that Roku supports. - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/genres/genre` | See [enumerated list](#genres) below. No more than 10 genres may be submitted for a single title | Required | -| Example: | | | - -```xml - - drama - -  - -``` - -**rating** - -Parental or content advisory rating for the movie by a rating source. A valid movie or TV rating from the rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. If the title has not been rated by that Territory’s official rating authority, please include a valid rating from the USA_PR ratingSystem. There is no official body that assigns ratings for the USA_PR ratingSystem. Please use the guidelines listed at [http://tvguidelines.org/](http://tvguidelines.org/) to assign the appropriate rating. Multiple rating value - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/ratings/rating` `must include the system attribute` | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system.
Multiple rating/rating system pairs are allowed | Required | -| Example: | | | - -```xml - - PG-13 - -  12A -  14A - -``` - -**tag** - -Tag is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. - -| XML XPath | Accepted Values | Required | -| ------------------------- | ---------------------------------------- | -------------------------------- | -| `/package/video/tags/tag` | any string under 50 characters in length | Optional, but HIGHLY recommended | -| Example: | | | - -```xml - - energy - -  dance -  - -``` - -**adBreak** **start_time** - -Used to determine[ Ad Breaks for Ad Supported Content](#ad-breaks). adBreak values must be accurate to the millisecond. If the video provided includes commercial blacks, please provide the timecode equal to the midpoint of the commercial black. While not required for SVOD content, frame accurate adBreak data can be ingested if available. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------- | --------------- | -------------------------- | -| `/package/video/adBreaks/adBreak/start_time` | HH:MM:SS.sss | Preferred for AVOD content | - -Example: - -```xml - -  -    00:03:15.000 -  -  -    00:07:45.425 -  - - -``` - -**cuePoint start_time and end_time** - -Used to identify the in and out points of opening credits, content recaps, end credits, and behind the scenes footage. cuePoint tags must include the type attribute cuePoint start_time and end_time values must be accurate to the millisecond. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | --------------- | --------- | -| `/package/video/cuePoints/cuePoint/start_time` | HH:MM:SS.sss | Preferred | -| `/package/video/cuePoints/cuePoint/end_time` | HH:MM:SS.sss | Preferred | - -Example: - -```xml - - - 00:09:10.456 - 00:09:12.678 - - - 00:07:08.123 - 00:07:59.123 - - - 00:01:08.123 - 00:01:59.123 - - - 00:21:08.123 - 00:21:59.123 - - - 00:41:08.123 - 00:41:59.123 - - - -``` - -**cuePoint type attribute** - -Defines the cuePoint type of the cuePoint provided within the cuePoints block. The cuePoint tag's attribute must be type and the value provided must be one of the below: - -| Type Value | Description | -| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ad overlay` | Identifies the cuePoint as the point within the video for in-program product placement advertisements. If providing, start_time and end time required | -| `behind the scenes` | Identifies the cuePoint as behind the scenes footage typically at the tail of a video. If providing, start_time and end_time required | -| `intro` | Identifies the cuePoint as the opening credits of the program. If providing, start_time and end_time required | -| `recap` | Identifies the cuePoint as a recap of previous content typically for episodic television. If providing, start_time and end_time required | -| `end` | Identifies the cuePoint as the end credits of the program. If providing, start_time and end_time is required | - -| XML XPath | Accepted Values | Required | -| ----------------------------------- | ---------------------------------------------- | ------------------------------- | -| `/package/video/cuePoints/cuePoint` | One of the values in the enumerated list above | Required if providing cuePoints | - -Example: - -```xml - -``` - -**cast display_name** - -Name of cast member\*\*.\*\* CDATA section supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | -------- | -| `/package/video/cast/cast_member/display_name` | Firstname Lastname | Optional | -| Example: | | | - -```xml - - -  -    -  - - -``` - -**crew display_name** - -Name of crew member. CDATA section supported. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | --------------------------------- | -| `/package/video/crew/crew_member/display_name` | Firstname Lastname | Required if providing crew_member | - -Example: - -```xml - -``` - -**role** - -Role of the crew member listed in the display_name. Roku requires each crew member included in the metadata to also include that crew member’s role. Please see the [enumerated list](#crew-roles) of crew roles that Roku supports. Roles are case sensitive. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| -------------------------------------- | ---------------------------------------- | --------------------------------- | -| `/package/video/crew/crew_member/role` | See [enumerated list](#crew-roles) below | Required if providing crew_member | - -Example: - -```xml -director -``` - -**localizations** - -Begins the asset block that provides localized metadata for multi-language packages. localizations define the language and provide the translated title, short_synopsis, and long_synopsis of the package. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/localizations` | | Required | - -Example: - -```xml - -``` - -**localization name attribute** - -Defines the language of the localized title, short_synopsis, and long_synopsis provided within the localization block. The localization tag's attribute must be name and the value provided in the name must at a minimum conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/localizations/localization` | Valid [language code](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml - -``` - -**localized title** - -Localized title of movie in the language specified in the localization tag’s name attribute. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD). Localized `title` must be accompanied by a localized `short_synopsis` and localized `long_synopsis` - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | --------------------- | -------- | -| `/package/video/localizations/localization/title` | Localized Movie Title | Required | - -Example: - -```xml -<![CDATA[Localized Movie Title. Required.]]> -``` - -**localized short_synopsis** - -A localized short synopsis of the content in the language specified in the localization tag’s name attribute. CDATA section supported. 250-character limit. Localized `short_synopsis` must be accompanied by a localized `title` and localized `long_synopsis` - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/short_synopsis` | 250 characters | Required | - -Example: - -```xml - -``` - -**localized long_synopsis** - -A localized long synopsis of the content in the language specified in the localization tag’s name attribute. CDATA section supported. 500-character limit. Localized `long_synopsis` must be accompanied by a localized `title` and localized `short_synopsis` - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/long_synopsis` | 500 characters | Required | - -Example: - -```xml - -``` - -**playOptions** - -Begins the asset block that provides the availability information of the package. playOptions consist of the country/territory availability, monetization type, availability start, and availability end dates of the title in the package. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | --------------- | -------- | -| `/package/video/playOptions` | | Required | - -Example: - -```xml - -``` - -**country** - -Country code of the territory in which the content is available. Multiple country nodes can be provided assuming vodType, licensePeriodStart, and licensePeriodEnd dates are identical across countries. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | -------------------------- | --------- | -| `/package/video/playOptions/playOption/country` | US
CA
GB
MX | Preferred | -| Example: | | | - -```xml - - US - -  - -``` - -**vodType** - -Monetization Type of the movie. Multiple vodType nodes can be provided assuming country, licensePeriodStart, and licensePeriodEnd dates are identical across vodType. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | --------------- | --------- | -| `/package/video/playOptions/playOption/vodType` | AVOD
SVOD | Preferred | -| Example: | | | - -```xml - - AVOD - -  - -``` - -**licensePeriodStart** - -Start date of content availability to users on Roku Channel. One licensePeriodStart date is allowed per playOption. licensePeriodStart dates must be chronologically before licensePeriodEnd dates. licensePeriodStart and licensePeriodEnd must not be identical - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | ------------------------------------------------ | -------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | Optional | -| Example: | | | - -```xml - - YYYY-MM-DDTHH:MM:SS - - -``` - -**licensePeriodEnd** - -End date of content availability to users on Roku Channel. One licensePeriodEnd date allowed per playOption. licensePeriodEnd dates must be chronologically after licensePeriodStart dates. licensePeriodStart and licensePeriodEnd must not be identical - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | ------------------------------------------------ | -------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | Optional | -| Example: | | | - -```xml - -  YYYY-MM-DDTHH:MM:SS - -``` - -**assets** - -Begins the asset block that references the files delivered in the package - -| XML XPath | Accepted Values | Required | -| ----------------------- | ------------------ | -------- | -| `/package/video/assets` | media_type="video" | Required | - -Example: - -```xml - -``` - -**data_file** - -**full source** - -The block that describes the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="source". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | -------------------------------------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="source"` | Required | -| Example: | | | - -```xml - - - -``` - -**full captions** - -The block that describes the closed captions for the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="captions". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | -------------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="captions"` | Required in US | -| Example: | | | - -```xml - - - -``` - -**full audio** - -The block that describes sidecar audio for the source video file. The audio file will either be a full audio dub for language translation purposes or a descriptive audio track for the accessibility purposes. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="audio" for translation dubs or role=”audio.descriptive” for accessibility purposes. The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="audio"`
`data_file role="audio.descriptive"` | Optional\*
audio.descriptive is strongly preferred | - -\*_sidecar audio may be required if localized assets are needed when the original audio of the source file is not native to the territory of distribution or when complying with FCC regulations_ Example: - -```xml - - - -``` - -**full subtitles** - -The block that describes sidecar subtitles for the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="subtitles". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------------------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="subtitles"` | Optional\* | - -\*_sidecar subtitles may be required if localized assets are needed when the original audio of the source file is not native to the territory of distribution._ Example: - -```xml - - - -``` - -**artwork** - -The block that describes the artwork file(s). The asset tag's attribute must be type="artwork". The `` and `` nodes are also required. Please see [Artwork](#artwork) for full image delivery specifications. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="artwork"` | Required | - -Example: - -```xml - - - - -  - - -  -``` - -**locale** - -Identifies the language of the data_file. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -Applicable to data_file roles: source, captions, audio, subtitles, and asset type: artwork. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/locale` | [Supported language code](#language-codes) | Required | - -Example: - -```xml - -``` - -**file_name** - -Filename of the asset indicated in the data_file role or type attribute. All file_name values are case-sensitive and must contain the proper file extension. - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | ------------------------------------------------------ | --------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | See guidelines below for asset delivery specifications | Required for each asset delivered | -| `/package/video/assets/asset/data_file/file_name` | | Required | -| `/package/video/assets/asset/data_file/file_name` | Attribute values:
`type="background_image"` | Preferred | -| `/package/video/assets/asset/data_file/file_name` | Attribute values:
`type="thumbnail_boxcover"` | Preferred | - -Example: - -```xml -VideoFilename.mxf -``` - -**audio** - -[Audio Layout Descriptor](#descriptive-audio) for the video file delivered. See guidelines below - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file/audio` | Allowed values:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo | Optional | - -Example: - -```xml - -``` - -*** - -### XML - episodic TV metadata fields - -**package** - -Defines the package version type - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/@version` | tv1.0 | Required | - -Example: - -```xml - -``` - -**provider** - -Name of content owner/studio/network - -| XML XPath | Example | Required | -| ------------------- | -------------- | -------- | -| `/package/provider` | Roku Originals | Required | - -Example: - -```xml -Roku Originals -``` - -**language** - -Primary language of the package metadata. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------- | -------------------------------------- | -------- | -| `/package/language` | [Valid language code](#language-codes) | Required | - -Example: - -```xml -en -``` - -**type** - -Defines the content type of the package - -| XML XPath | Accepted Values | Required | -| --------------------- | --------------- | -------- | -| `/package/video/type` | tv | Required | - -Example: - -```xml -tv -``` - -**asset_id** - -Immutable, unique identifier for an episode. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit - -| XML XPath | Accepted Values | Required | -| ------------------------- | ----------------------------------------------------------------------------- | -------- | -| `/package/video/asset_id` | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | Required | - -Example: - -```xml -episodeAssetIdHere -``` - -**eidr** - -EIDR ID if one exists - -| XML XPath | Accepted Values | Required | -| --------------------- | ----------------- | -------- | -| `/package/video/eidr` | Any valid EIDR ID | Optional | - -Example: - -```xml - -``` - -**tmsId** - -Gracenote ID if one exists - -| XML XPath | Accepted Values | Required | -| ---------------------- | ---------------- | -------- | -| `/package/video/tmsId` | Any valid TMS ID | Optional | - -Example: - -```xml - -``` - -**title** - -Title of episode. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) - -| XML XPath | Example | Required | -| ---------------------- | ------------- | -------- | -| `/package/video/title` | Episode Title | Required | - -Example: - -```xml -<![CDATA[Episode Title. Required.]]> -``` - -**episodeNumber** - -Numerical position of the episode within a season of a series. This value will determine the order in which the episodes will be viewed on platform. episodeNumber values must be delivered as they were originally broadcast or exhibited on any platform. Production numbers must not be provided. Only numerical (integer) values are allowed. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/episodeNumber` | Integers only | Required | - -Example: - -```xml -2 -``` - -**short_synopsis** - -A short synopsis of the episode. CDATA section supported. 250-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------- | ---------------------- | -------- | -| `/package/video/short_synopsis` | 250-character synopsis | Required | - -Example: - -```xml - -``` - -**long_synopsis** - -A long synopsis of the episode. CDATA section supported. 500-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | ---------------------- | -------- | -| `/package/video/long_synopsis` | 500-character synopsis | Required | - -Example: - -```xml - -``` - -**closedCaptions** - -Indicates whether the episode delivered contains closed captions. Accepted values are Y or N. This field is required for all content intended for Roku Channel in the US - -| XML XPath | Accepted Values | Required | -| ------------------------------- | --------------- | ------------------------------ | -| `/package/video/closedCaptions` | Y or N | Required for content in the US | - -Example: - -```xml -Y -``` - -**closedCaptionsExemption** - -FCC exemption code for closed caption requirement. This node is required if the `closedCaptions` value = “N” - -Allowable value and their definitions: - -1 - The content has never aired on television in the United States. 2 - The content has only aired on television in the United States without captions. 3 - The content has not aired on television in the United States with captions since September 30, 2012. 4 - The content does not consist of full-length video programming. 5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)). 6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------- | ------------------------------ | -| `/package/video/closedCaptionsExemption` | 1, 2, 3, 4, 5, 6 | Required if closedCaptions = N | - -Example: - -```xml -1 -``` - -**release_date** - -Original date the episode was first made available in any presentation. Must include accurate year of release at a minimum - -| XML XPath | Accepted Values | Required | -| ----------------------------- | --------------------------------------- | -------- | -| `/package/video/release_date` | Conforms to ISO 8601 format: YYYY-MM-DD | Required | - -Example: - -```xml -YYYY-MM-DD -``` - -**runtime** - -Total run time of content in whole minutes - -| XML XPath | Accepted Values | Required | -| ------------------------ | --------------- | -------- | -| `/package/video/runtime` | Integers only | Required | - -Example: - -```xml -120 -``` - -**rating** - -Parental or content advisory rating for the episode by a rating source. A valid TV rating from the rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each episode. If the title has not been rated by that Territory’s official rating authority, please include a valid rating from the USA_PR ratingSystem. There is no official body that assigns ratings for the USA_PR ratingSystem. Please use the guidelines listed at [http://tvguidelines.org/](http://tvguidelines.org/) to assign the appropriate rating. Multiple rating value - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/ratings/rating` `must include the system attribute` | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. Multiple rating/rating system pairs are allowed | Required | - -Example: - -```xml - -PG-13 -12A -14A - -``` - -**tag** - -Tag is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. - -| XML XPath | Accepted Values | Required | -| ------------------------- | ---------------------------------------- | -------------------------------- | -| `/package/video/tags/tag` | any string under 50 characters in length | Optional, but HIGHLY recommended | - -Example: - -```xml - - energy - dance - - -``` - -**adBreak start_time** - -Used to determine[ Ad Breaks for Ad Supported Content](#ad-breaks). adBreak values must be accurate to the millisecond. If the video provided includes commercial blacks, please provide the timecode equal to the midpoint of the commercial black. While not required for SVOD content, frame accurate adBreak data can be ingested if available. - -| XML XPath | Accepted Values | Required | -| --------------------------------- | --------------- | -------------------------- | -| `/package/video/adBreaks/adBreak` | HH:MM:SS.sss | Preferred for AVOD content | -| Example: | | | - -```xml - - - 00:03:15.000 - - - - 00:07:45.425 - - - -``` - -**cuePoint start_time and end_time** - -Used to identify the in and out points of opening credits, content recaps, end credits, and behind the scenes footage. cuePoint tags must include the type attribute cuePoint start_time and end_time values must be accurate to the millisecond. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | --------------- | --------- | -| `/package/video/cuePoints/cuePoint/start_time` | HH:MM:SS.sss | Preferred | -| `/package/video/cuePoints/cuePoint/end_time` | HH:MM:SS.sss | Preferred | - -Example: - -```xml - - - 00:09:10.456 - 00:09:12.678 - - - 00:07:08.123 - 00:07:59.123 - - - 00:01:08.123 - 00:01:59.123 - - - 00:21:08.123 - 00:21:59.123 - - - 00:41:08.123 - 00:41:59.123 - - - -``` - -**cuePoint type attribute** - -Defines the cuePoint type of the cuePoint provided within the cuePoints block. The cuePoint tag's attribute must be type and the value provided must be one of the below: - -| Type Value | Description | -| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ad overlay` | Identifies the cuePoint as the point within the video for in-program product placement advertisements. If providing, start_time and end time required | -| `behind the scenes` | Identifies the cuePoint as behinds the scenes footage typically at the tail of a video. If providing, start_time and end_time required | -| `intro` | Identifies the cuePoint as the opening credits of the program. If providing, start_time and end_time required | -| `recap` | Identifies the cuePoint as a recap of previous content typically for episodic television. If providing, start_time and end_time required | -| `end` | Identifies the cuePoint as the end credits of the program. If providing, start_time and end_time is required | - -| XML XPath | Accepted Values | Required | -| ----------------------------------- | ---------------------------------------------- | ------------------------------- | -| `/package/video/cuePoints/cuePoint` | One of the values in the enumerated list above | Required if providing cuePoints | - -Example: - -```xml - -``` - -**cast display_name** - -Name of cast member for the episode\*\*.\*\* CDATA section supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ----------------------- | -------- | -| `/package/video/cast/cast_member/display_name` | Firstname
Lastname | Optional | -| Example: | | | - -```xml - - - - - - - -``` - -**crew display_name** - -Name of crew member for the episode. CDATA section supported. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ----------------------- | --------------------------------- | -| `/package/video/crew/crew_member/display_name` | Firstname
Lastname | Required if providing crew_member | - -Example: - -```xml - -``` - -**role** - -Role of the crew member listed in the display_name. Roku requires each crew member included in the metadata to also include that crew member’s role. Please see the [enumerated list](#crew-roles) of crew roles that Roku supports. Roles are case sensitive. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| -------------------------------------- | ---------------------------------------- | --------------------------------- | -| `/package/video/crew/crew_member/role` | See [enumerated list](#crew-roles) below | Required if providing crew_member | - -Example: - -```xml -director -``` - -**localizations** - -Begins the asset block that provides localized metadata of the episode for multi-language packages. localizations define the language and provide the translated title, short_synopsis, and long_synopsis of the package. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/localizations` | | Required | - -Example: - -```xml - -``` - -**localization name attribute** - -Defines the language of the localized title, short_synopsis, and long_synopsis provided within the localization block. The localization tag's attribute must be name and the value provided in the name must at a minimum conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/localizations/localization` | Valid [language code](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml - -``` - -**localized title** - -Localized title of episode in the language specified in the localization tag’s name attribute. Include only the name of the episode as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD). Localized `title` must be accompanied by a localized `short_synopsis` and localized `long_synopsis` - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | ----------------------- | -------- | -| `/package/video/localizations/localization/title` | Localized Episode Title | Required | - -Example: - -```xml -<![CDATA[Localized Episode Title. Required.]]> -``` - -**localized short_synopsis** - -A localized short synopsis of the episode in the language specified in the localization tag’s name attribute. CDATA section supported. 250-character limit. Localized `short_synopsis` must be accompanied by a localized `title` and localized `long_synopsis` - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/short_synopsis` | 250 characters | Required | - -Example: - -```xml - -``` - -**localized long_synopsis** - -A localized long synopsis of the episode in the language specified in the localization tag’s name attribute. CDATA section supported. 500-character limit. Localized `long_synopsis` must be accompanied by a localized `title` and localized `short_synopsis` - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/long_synopsis` | 500 characters | Required | - -Example: - -```xml - -``` - -**series** - -Begins the series block that references the metadata for the show to which the episode belongs. Roku follows the US definition of a series. Episodes are nested within a season of a series following the hierarchy: series -> season -> episode - -| XML XPath | Example | Required | -| ----------------------- | ------- | -------- | -| `/package/video/series` | | Required | - -Example: - -```xml - -``` - -**series_id** - -Immutable, unique identifier for a series. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit - -| XML XPath | Accepted Values | Required | -| --------------------------------- | ----------------------------------------------------------------------------- | -------- | -| `/package/video/series/series_id` | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | Required | - -Example: - -```xml -seriesIdHere -``` - -**title** - -Title of series. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) - -| XML XPath | Example | Required | -| ----------------------------- | ------------- | -------- | -| `/package/video/series/title` | Episode Title | Required | - -Example: - -```xml -<![CDATA[Episode Title. Required.]]> -``` - -**short_synopsis** - -A short synopsis of the series. CDATA section supported. 250-character limit. - -| XML XPath | Accepted Values | Required | -| -------------------------------------- | ---------------------- | -------- | -| `/package/video/series/short_synopsis` | 250-character synopsis | Required | - -Example: - -```xml - -``` - -**long_synopsis** - -A long synopsis of the series. CDATA section supported. 500-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------------- | ---------------------- | -------- | -| `/package/video/series/long_synopsis` | 500-character synopsis | Required | - -Example: - -```xml - -``` - -**original_spoken_language** - -Defines the original production language of the episode being delivered. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/series/original_spoken_language` | Valid [language code](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml -en -``` - -**country_of_origin** - -Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `/package/video/series/country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -Example: - -```xml -US -``` - -**release_date** - -Original date the series was first made available in any presentation. This is typically the same date as the first episode of the series. Must include accurate year of release at a minimum - -| XML XPath | Accepted Values | Required | -| ------------------------------------ | --------------------------------------- | -------- | -| `/package/video/series/release_date` | Conforms to ISO 8601 format: YYYY-MM-DD | Required | - -Example: - -```xml -YYYY-MM-DD -``` - -**genre** - -Genre classification of the content. Roku requires each episode to be delivered with at least one supported genre. Please see [enumerated list](#genres) of genres that Roku supports. - -| XML XPath | Accepted Values | Required | -| ------------------------------------ | ----------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/series/genres/genre` | See [enumerated list](#genres) below.
No more than 10 genres may be submitted for a single title | Required | - -Example: - -```xml - - drama - - -``` - -**tag** - -Tag is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. - -| XML XPath | Accepted Values | Required | -| -------------------------------- | ---------------------------------------- | -------------------------------- | -| `/package/video/series/tags/tag` | any string under 50 characters in length | Optional, but HIGHLY recommended | - -Example: - -```xml - - energy - dance - - -``` - -**cast display_name** - -Name of cast member of the series\*\*.\*\* CDATA section supported. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------------- | ----------------------- | -------- | -| `/package/video/series/cast/cast_member/display_name` | Firstname
Lastname | Optional | - -Example: - -```xml - - - - - - -``` - -**crew display_name** - -Name of crew member of the series. CDATA section supported. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------------- | ----------------------- | --------------------------------- | -| `/package/video/series/crew/crew_member/display_name` | Firstname
Lastname | Required if providing crew_member | - -Example: - -```xml - -``` - -**role** - -Role of the crew member listed in the display_name. Roku requires each crew member included in the metadata to also include that crew member’s role. Please see the [enumerated list](#crew-roles) of crew roles that Roku supports. Roles are case sensitive. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ---------------------------------------- | --------------------------------- | -| `/package/video/series/crew/crew_member/role` | See [enumerated list](#crew-roles) below | Required if providing crew_member | - -Example: - -```xml -director -``` - -**localizations** - -Begins the asset block that provides localized metadata for the series in multi-language packages. localizations define the language and provide the translated title, short_synopsis, and long_synopsis of the package. - -| XML XPath | Accepted Values | Required | -| ------------------------------------- | --------------- | -------- | -| `/package/video/series/localizations` | | Required | - -Example: - -```xml - -``` - -**localization name attribute** - -Defines the language of the localized title, short_synopsis, and long_synopsis provided within the localization block. The localization tag's attribute must be name and the value provided in the name must at a minimum conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/series/localizations/localization` | Valid [language code](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml - -``` - -**localized title** - -Localized title of the series in the language specified in the localization tag’s name attribute. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD). Localized `title` must be accompanied by a localized `short_synopsis` and localized `long_synopsis` - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | ----------------------- | -------- | -| `/package/video/series/localizations/localization/title` | Localized Episode Title | Required | - -Example: - -```xml -<![CDATA[Localized Episode Title. Required.]]> -``` - -**localized short_synopsis** - -A localized short synopsis of the series in the language specified in the localization tag’s name attribute. CDATA section supported. 250-character limit. Localized `short_synopsis` must be accompanied by a localized `title` and localized `long_synopsis` - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------------------------- | --------------- | -------- | -| `/package/video/series/localizations/localization/short_synopsis` | 250 characters | Required | - -Example: - -```xml - -``` - -**localized long_synopsis** - -A localized long synopsis of the series in the language specified in the localization tag’s name attribute. CDATA section supported. 500-character limit. Localized `long_synopsis` must be accompanied by a localized `title` and localized `short_synopsis` - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------------- | --------------- | -------- | -| `/package/video/series/localizations/localization/long_synopsis` | 500 characters | Required | - -Example: - -```xml - -``` - -**season** - -Begins the season block that references the metadata for the season of the series to which the episode belongs. Roku follows the US definition of a series. Episodes are nested within a season of a series following the hierarchy: series -> season -> episode - -Example: - -| XML XPath | Example | Required | -| ----------------------- | ------- | -------- | -| `/package/video/season` | | Required | - -```xml - -``` - -**season_id** - -Immutable, unique identifier for a season. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit - -| XML XPath | Accepted Values | Required | -| --------------------------------- | ----------------------------------------------------------------------------- | -------- | -| `/package/video/season/season_id` | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | Required | - -Example: - -```xml -seasonIdHere -``` - -**seasonNumber** - -Numerical position of the season within a series. This value will determine the order in which the underlying episodes will be viewed on platform. seasonNumber values must be delivered as they were originally broadcast or exhibited on any platform. Only numerical (integer) values are allowed. - -| XML XPath | Accepted Values | Required | -| ------------------------------------ | --------------- | -------- | -| `/package/video/season/seasonNumber` | Integers only | Required | - -Example: - -```xml -2 -``` - -**playOptions** - -Begins the asset block that provides the availability information of the package. playOptions consist of the country/territory availability, monetization type, availability start, and availability end dates of the title in the package. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | --------------- | -------- | -| `/package/video/playOptions` | | Required | - -Example: - -```xml - -``` - -**country** - -Country code of the territory in which the content is available. Multiple country nodes can be provided assuming vodType, licensePeriodStart, and licensePeriodEnd dates are identical across countries. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | -------------------------- | --------- | -| `/package/video/playOptions/playOption/country` | US
CA
GB
MX | Preferred | - -Example: - -```xml - - US - - -``` - -**vodType** - -Monetization Type of the episode. Multiple vodType nodes can be provided assuming country, licensePeriodStart, and licensePeriodEnd dates are identical across vodType. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | --------------- | --------- | -| `/package/video/playOptions/playOption/vodType` | AVOD
SVOD | Preferred | - -Example: - -```xml - - AVOD - - -``` - -**licensePeriodStart** - -Start date of content availability to users on Roku Channel. One licensePeriodStart date is allowed per playOption. licensePeriodStart dates must be chronologically before licensePeriodEnd dates. licensePeriodStart and licensePeriodEnd must not be identical - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | ------------------------------------------------ | -------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | Optional | - -Example: - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -**licensePeriodEnd** - -End date of content availability to users on Roku Channel. One licensePeriodEnd date allowed per playOption. licensePeriodEnd dates must be chronologically after licensePeriodStart dates. licensePeriodStart and licensePeriodEnd must not be identical - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | ------------------------------------------------ | -------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | Optional | -| Example: | | | - -```xml - - YYYY-MM-DDTHH:MM:SS - - -``` - -**assets** - -Begins the asset block that references the files delivered in the package - -| XML XPath | Accepted Values | Required | -| ----------------------- | ------------------ | -------- | -| `/package/video/assets` | media_type="video" | Required | - -Example: - -```xml - -``` - -**data_file** - -**full source** - -The block that describes the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="source". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="source"` | Required | -| Example: | | | - -```xml - - - -``` - -**full captions** - -The block that describes the closed captions for the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="captions". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | -------------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="captions"` | Required in US | - -Example: - -```xml - - -``` - -**full audio** - -The block that describes sidecar audio for the source video file. The audio file will either be a full audio dub for language translation purposes or a descriptive audio track for the accessibility purposes. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="audio" for translation dubs or role=”audio.descriptive” for accessibility purposes. The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="audio"`
`data_file role="audio.descriptive"` | Optional
\*audio.descriptive is strongly preferred | - -\*_sidecar audio may be required if localized assets are needed when the original audio of the source file is not native to the territory of distribution or when complying with FCC regulations_ - -Example: - -```xml - - -``` - -**full subtitles** - -The block that describes sidecar subtitles for the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="subtitles". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full`
`data_file role="subtitles"` | Optional\* | - -\*_sidecar subtitles may be required if localized assets are needed when the original audio of the source file is not native to the territory of distribution._ - -Example: - -```xml - - -``` - -**artwork** - -The block that describes the artwork file(s). The asset tag's attribute must be type="artwork". The data_file tag's attribute can either be type="episode" for episode level image delivery, or type="series" for series level image delivery. The `` and `` nodes are also required. Please see [Artwork](#artwork) for full image delivery specifications. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ----------------------------------------------------------------------------- | --------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="artwork"`
`data_file type="episode"` | Preferred | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="artwork"`
`data_file type="series"` | Preferred | -| Example: | | | - -```xml - - - -``` - -```xml - - -``` - -**locale** - -Identifies the language of the data_file. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -Applicable to data_file roles: source, captions, audio, subtitles, and asset type: artwork. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/locale` | [Supported language code](#language-codes) | Required | - -Example: - -```xml - -``` - -**file_name** - -Filename of the asset indicated in the data_file role or type attribute. All file_name values are case-sensitive and must contain the proper file extension. - -For artwork files the file_name tag's attribute can either be omitted (to indicate key art), type="background_image", or type="thumbnail_boxcover". - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | ------------------------------------------------------ | --------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | See guidelines below for asset delivery specifications | Required for each asset delivered | -| `/package/video/assets/asset/data_file/file_name` | | Required | -| `/package/video/assets/asset/data_file/file_name` | Attribute values:
`type="background_image"` | Preferred | -| `/package/video/assets/asset/data_file/file_name` | Attribute values:
`type="thumbnail_boxcover"` | Preferred | - -Example: - -```xml -VideoFilename.mxf -``` - -**audio** - -[Audio Layout Descriptor](#descriptive-audio) for the video file delivered. See guidelines below - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file/audio` | Allowed values:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo | Optional | - -Example: - -```xml - -``` - -*** - -### XML - shortForm clip metadata fields - -**package** - -Defines the package version type - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/@version` | clip1.0 | Required | - -Example: - -```xml - -``` - -**provider** - -Name of content owner/studio/network - -| XML XPath | Accepted Values | Required | -| ------------------- | ---------------------- | -------- | -| `/package/provider` | Example:Roku Originals | Required | - -Example: - -```xml -Roku Originals -``` - -**language** - -Primary language of the package metadata. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------- | -------------------------------------- | -------- | -| `/package/language` | [Valid language code](#language-codes) | Required | - -Example: - -```xml -en -``` - -**type** - -Defines the content type of the package - -| XML XPath | Accepted Values | Required | -| --------------------- | --------------- | -------- | -| `/package/video/type` | clip | Required | - -Example: - -```xml -clip -``` - -**subType** - -Defines the content subType of the package. Roku does not currently support parent/child connections natively. Ancillary or related content can be delivered and identified using one of the below subTypes. _There is no link between the parent and child asset_ - -| XML XPath | Accepted Values | Required | -| ------------------------ | ---------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/subType` | trailer
highlight
making_of
behind_scenes
interview
related
recap
extra | Optional | - -Example: - -```xml -trailer -``` - -**asset_id** - -Immutable, unique identifier for a shortForm clip. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit - -| XML XPath | Accepted Values | Required | -| ------------------------- | ----------------------------------------------------------------------------- | -------- | -| `/package/video/asset_id` | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | Required | - -Example: - -```xml -clipAssetIdHere -``` - -**eidr** - -EIDR ID if one exists - -| XML XPath | Accepted Values | Required | -| --------------------- | ----------------- | -------- | -| `/package/video/eidr` | Any valid EIDR ID | Optional | - -Example: - -```xml - -``` - -**tmsId** - -Gracenote ID if one exists - -| XML XPath | Accepted Values | Required | -| ---------------------- | ---------------- | -------- | -| `/package/video/tmsId` | Any valid TMS ID | Optional | - -Example: - -```xml - -``` - -**title** - -Title of shortForm clip. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) - -| XML XPath | Example | Required | -| ---------------------- | ---------- | -------- | -| `/package/video/title` | Clip Title | Required | - -Example: - -```xml -<![CDATA[Clip Title. Required.]]> -``` - -**short_synopsis** - -A short synopsis of the content. CDATA section supported. 250-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------- | ---------------------- | -------- | -| `/package/video/short_synopsis` | 250-character synopsis | Required | - -Example: - -```xml - -``` - -**long_synopsis** - -A long synopsis of the content. CDATA section supported. 500-character limit. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | ---------------------- | -------- | -| `/package/video/long_synopsis` | 500-character synopsis | Required | - -Example: - -```xml - -``` - -**original_spoken_language** - -Defines the original production language of the title being delivered. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/original_spoken_language` | Valid [language code](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml -en -``` - -**country_of_origin** - -Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. - -| XML XPath | Accepted Values | Required | -| ---------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `/package/video/country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -Example: - -```xml -en -``` - -**closedCaptions** - -Indicates whether the title delivered contains closed captions. Accepted values are Y or N. This field is required for all content intended for Roku Channel in the US - -| XML XPath | Accepted Values | Required | -| ------------------------------- | --------------- | ------------------------------ | -| `/package/video/closedCaptions` | Y or N | Required for content in the US | - -Example: - -```xml -Y -``` - -**closedCaptionsExemption** - -FCC exemption code for closed caption requirement. This node is required if the `closedCaptions` value = “N” - -Allowable value and their definitions: - -1 - The content has never aired on television in the United States. 2 - The content has only aired on television in the United States without captions. 3 - The content has not aired on television in the United States with captions since September 30, 2012. 4 - The content does not consist of full-length video programming. 5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)). 6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------- | ------------------------------ | -| `/package/video/closedCaptionsExemption` | 1, 2, 3, 4, 5, 6 | Required if closedCaptions = N | - -Example: - -```xml -1 -``` - -**release_date** - -Original date content was first made available in any presentation. Must include accurate year of release at a minimum - -| XML XPath | Accepted Values | Required | -| ----------------------------- | --------------------------------------- | -------- | -| `/package/video/release_date` | Conforms to ISO 8601 format: YYYY-MM-DD | Required | - -Example: - -```xml -YYYY-MM-DD -``` - -**runtime** - -Total run time of content in whole minutes - -| XML XPath | Accepted Values | Required | -| ------------------------ | --------------- | -------- | -| `/package/video/runtime` | Integers only | Required | - -Example: - -```xml -120 -``` - -**genre** - -Genre classification of the content. Roku requires each shortForm clip to be delivered with at least one supported genre. Please see [enumerated list](#genres) of genres that Roku supports. - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/genres/genre` | See [enumerated list](#genres) below. No more than 10 genres may be submitted for a single title | Required | - -Example: - -```xml - - drama - - -``` - -**rating** - -Parental or content advisory rating for the shortForm clip by a rating source. A valid movie or TV rating from the rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each shortForm clip. If the title has not been rated by that Territory’s official rating authority, please include a valid rating from the USA_PR ratingSystem. There is no official body that assigns ratings for the USA_PR ratingSystem. Please use the guidelines listed at [http://tvguidelines.org/](http://tvguidelines.org/) to assign the appropriate rating. Multiple rating value - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/ratings/rating` `must include the system attribute` | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system.
Multiple rating/rating system pairs are allowed | Required | - -Example: - -```xml - - PG-13 - 12A - 14A - -``` - -**tag** - -Tag is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. - -| XML XPath | Accepted Values | Required | -| ------------------------- | ---------------------------------------- | -------------------------------- | -| `/package/video/tags/tag` | any string under 50 characters in length | Optional, but HIGHLY recommended | - -Example: - -```xml - - energy - dance - - -``` - -**cast display_name** - -Name of cast member\*\*.\*\* CDATA section supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ----------------------- | -------- | -| `/package/video/cast/cast_member/display_name` | Firstname
Lastname | Optional | - -Example: - -```xml - - - - - - -``` - -**crew display_name** - -Name of crew member. CDATA section supported. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ----------------------- | --------------------------------- | -| `/package/video/crew/crew_member/display_name` | Firstname
Lastname | Required if providing crew_member | - -Example: - -```xml - -``` - -**role** - -Role of the crew member listed in the display_name. Roku requires each crew member included in the metadata to also include that crew member’s role. Please see the [enumerated list](#crew-roles) of crew roles that Roku supports. Roles are case sensitive. - -\*NOTE: Director is the only crew_member supported for Excel ingest at this time - -| XML XPath | Accepted Values | Required | -| -------------------------------------- | ---------------------------------------- | --------------------------------- | -| `/package/video/crew/crew_member/role` | See [enumerated list](#crew-roles) below | Required if providing crew_member | - -Example: - -```xml -director -``` - -**localizations** - -Begins the asset block that provides localized metadata for multi-language packages. localizations define the language and provide the translated title, short_synopsis, and long_synopsis of the package. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/localizations` | | Required | - -Example: - -```xml - -``` - -**localization name attribute** - -Defines the language of the localized title, short_synopsis, and long_synopsis provided within the localization block. The localization tag's attribute must be name and the value provided in the name must at a minimum conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/localizations/localization` | Valid [language code](#language-codes) (en, es, etc.)
May also include region codes (en-US, es-MX, etc.) | Required | - -Example: - -```xml - -``` - -**localized title** - -Localized title of shortForm clip in the language specified in the localization tag’s name attribute. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) - -| XML XPath | Example | Required | -| ------------------------------------------------- | -------------------- | -------- | -| `/package/video/localizations/localization/title` | Localized Clip Title | Required | - -Example: - -```xml -<![CDATA[Localized Clip Title. Required.]]> -``` - -**localized short_synopsis** - -A localized short synopsis of the content in the language specified in the localization tag’s name attribute. CDATA section supported. 250-character limit. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/short_synopsis` | 250 characters | Required | - -Example: - -```xml - -``` - -**localized long_synopsis** - -A localized long synopsis of the content in the language specified in the localization tag’s name attribute. CDATA section supported. 500-character limit. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/long_synopsis` | 500 characters | Required | - -Example: - -```xml - -``` - -**playOptions** - -Begins the asset block that provides the availability information of the package. playOptions consist of the country/territory availability, monetization type, availability start, and availability end dates of the title in the package. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | --------------- | -------- | -| `/package/video/playOptions` | | Required | - -Example: - -```xml - -``` - -**country** - -Country code of the territory in which the content is available. Multiple country nodes can be provided assuming vodType, licensePeriodStart, and licensePeriodEnd dates are identical across countries. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | -------------------------- | --------- | -| `/package/video/playOptions/playOption/country` | US
CA
GB
MX | Preferred | - -Example: - -```xml - - US - - -``` - -**vodType** - -Monetization Type of the shortForm clip. Multiple vodType nodes can be provided assuming country, licensePeriodStart, and licensePeriodEnd dates are identical across vodType. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | --------------- | --------- | -| `/package/video/playOptions/playOption/vodType` | AVOD
SVOD | Preferred | - -Example: - -```xml - - AVOD - - -``` - -**licensePeriodStart** - -Start date of content availability to users on Roku Channel. One `licensePeriodStart` date is allowed per playOption. licensePeriodStart dates must be chronologically before licensePeriodEnd dates. licensePeriodStart and licensePeriodEnd must not be identical - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | ------------------------------------------------ | -------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | Optional | - -Example: - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -**licensePeriodEnd** - -End date of content availability to users on Roku Channel. One `licensePeriodEnd` date allowed per playOption. licensePeriodEnd dates must be chronologically after licensePeriodStart dates. licensePeriodStart and licensePeriodEnd must not be identical - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | ------------------------------------------------ | -------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | Optional | - -Example: - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -**assets** - -Begins the asset block that references the files delivered in the package - -| XML XPath | Accepted Values | Required | -| ----------------------- | ------------------ | -------- | -| `/package/video/assets` | media_type="video" | Required | - -Example: - -```xml - -``` - -**data_file** - -**full source** - -The block that describes the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="source". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="source"` | Required | - -Example: - -```xml - - -``` - -**full captions** - -The block that describes the closed captions for the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="captions". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | -------------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="captions"` | Required in US | - -Example: - -```xml - - -``` - -**full audio** - -The block that describes sidecar audio for the source video file. The audio file will either be a full audio dub for language translation purposes or a descriptive audio track for the accessibility purposes. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="audio" for translation dubs or role=”audio.descriptive” for accessibility purposes. The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="audio"`
`data_file role="audio.descriptive"` | Optional
\*audio.descriptive is strongly preferred | - -\*_sidecar audio may be required if localized assets are needed when the original audio of the source file is not native to the territory of distribution or when complying with FCC regulations_ - -Example: - -```xml - - -``` - -**full subtitles** - -The block that describes sidecar subtitles for the source video file. The asset tag's attribute must be type="full" and the data_file tag's attribute must be role="subtitles". The `` and `` nodes are also required - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------------------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="full"`
`data_file role="subtitles"` | Optional\* | - -\*_sidecar subtitles may be required if localized assets are needed when the original audio of the source file is not native to the territory of distribution._ - -Example: - -```xml - - -``` - -**artwork** - -The block that describes the artwork file(s). The asset tag's attribute must be type="artwork". The `` and `` nodes are also required. Please see [Artwork](#artwork) for full image delivery specifications. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | Attribute values:
`asset type="artwork"` | Required | - -Example: - -```xml - - -``` - -**locale** - -Identifies the language of the data_file. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). - -Applicable to data_file roles: source, captions, audio, and subtitles and asset type: artwork. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/locale` | [Supported language code](#language-codes) | Required | - -Example: - -```xml - -``` - -**file_name** - -Filename of the asset indicated in the data_file role or type attribute. All file_name values are case-sensitive and must contain the proper file extension. - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | ------------------------------------------------------ | --------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | See guidelines below for asset delivery specifications | Required for each asset delivered | - -Example: - -```xml -VideoFilename.mxf -``` - -**audio** - -[Audio Layout Descriptor](#descriptive-audio) for the video file delivered. See guidelines below - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file/audio` | Allowed values:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo | Optional | - -Example: - -```xml - -``` - -**parentInfo** - -Begins the asset block that provides the parent information of the package. parentInfo consists of the parent content's contentType, episode/movie title, episode/movie runtime, releaseDate, TMS ID, seriesTitle, seasonNumber, and episodeNumber. Used in combination with a valid subType - -| XML XPath | Accepted Values | Required | -| --------------------------- | --------------- | -------- | -| `/package/video/parentInfo` | | Optional | - -Example: - -```xml - -``` - -**contentType** - -Content Type of the parent the clip is derived from or describes - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------ | -------- | -| `/package/video/parentInfo/contentType` | episode
movie
series | Optional | -| Example: | | | - -```xml - - episode - - -``` - -**title** - -Title of the parent program if the parent is a movie or episode - -| XML XPath | Accepted Values | Required | -| --------------------------------- | ------------------------------- | -------- | -| `/package/video/parentInfo/title` | Title of Parent Movie or Series | Optional | -| Example: | | | - -```xml - - Title of Parent Movie or Series - - -``` - -**runtime** - -Runtime of the parent program if the parent is a movie or episode - -| XML XPath | Accepted Values | Required | -| ----------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/runtime` | Integer | Optional | -| Example: | | | - -```xml - - 45 - - -``` - -**releaseDate** - -Release date of the parent movie, episode, or series - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------- | -------- | -| `/package/video/parentInfo/releaseDate` | Conforms to ISO 8601 format: YYYY-MM-DD | Optional | -| Example: | | | - -```xml - - YYYY-MM-DD - - -``` - -**tmsId** - -TMS ID of the parent movie, episode, or series - -| XML XPath | Accepted Values | Required | -| --------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/tmsId` | Valid TMS ID | Optional | -| Example: | | | - -```xml - - TMSID - - -``` - -**seriesTitle** - -Series Title of the parent program if the parent is an episode - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------- | -------- | -| `/package/video/parentInfo/seriesTitle` | Parent Series Title | Optional | -| Example: | | | - -```xml - - Parent Series Title - - -``` - -**seasonNumber** - -Season number of the parent program if the parent is an episode - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/seasonNumber` | Integer | Optional | -| Example: | | | - -```xml - - 2 - - -``` - -**episodeNumber** - -Episode number of the parent program if the parent is an episode - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/episodeNumber` | Integer | Optional | -| Example: | | | - -```xml - - 14 - - -``` - -**sportType** - -Name of the sport featured in the clip/highlight - -| XML XPath | Accepted Values | Required | -| -------------------------- | ----------------- | ------------------------------ | -| `/package/video/sportType` | Name of the sport | Required for
sports clips | - -Example: - -```xml -Baseball -``` - -**sportLeague** - -Name of the sport league featured in the clip/highlight - -| XML XPath | Accepted Values | Required | -| ---------------------------- | ------------------------ | ------------------------------ | -| `/package/video/sportLeague` | Name of the sport league | Required for
sports clips | - -Example: - -```xml -MLB -``` - -**teams** - -Teams featured in the sport clip/highlight. Home and Away teams to be defined in the Location attribute - -_At this time Roku only supports team-based participant metadata. Individual sports will be supported at a later date_ - -| XML XPath | Accepted Values | Required | -| --------------------------- | ------------------------------------------------------------------------- | ------------------------------ | -| `/package/video/teams/team` | Attribute values:
`team location="away"`
`team location="home"` | Required for
sports clips | - -Example: - -```xml - - Chicago Cubs - St. Louis Cardinals - -``` - -*** - -### Roku Excel metadata guidelines and templates - -Excel metadata can only be accepted if delivered in the ROKU approved formats below: - -| Excel Metadata | Download Link | -| ---------------------------- | -------------------------------------------------------- | -| Film Metadata Excel Template | [Download here](https://go.roku.com/film-excel-template) | -| TV Metadata Excel Template | [Download here](https://go.roku.com/tv-excel-template) | -| Clip Metadata Excel Template | [Download here](https://go.roku.com/clip-excel-template) | - -The Roku Excel metadata template must be submitted with all required fields populated. Roku has provided hints on row 2 of each metadata template to highlight the required cells and any special formatting needed for each cell. Please refer to these hints when filling out the Excel metadata template. Other considerations when filling out a template include: - -- Dates must be provided in YYYY-MM-DD format (change the cell formatting to “Text” if necessary) -- File names must not contain [special characters or spaces](#special-characters) -- Any formulas used must be converted to text prior to submission. Inclusion of a formula will result in rejected deliveries and will cause content processing delays/failures -- Do not link to external data or Excel workbooks. All data must be self contained within the Excel workbook delivered to Roku -- Do not add additional sheets to the workbook -- Do not add additional columns to the workbook -- Do not delete the legend/hint row (row 2) -- Do not supply a value of “N/A” or “n/a”. Required cells should contain valid data and optional cells may be left blank -- Multiple movies, clips, and multiple episodes may be supplied in a single Excel workbook - - Each row is considered a unique language experience of an episode/movie/clip - - Do not leave a blank row between entries in a worksheet. The system will terminate processing at the first empty row. - - Do not include more than 900 rows in a single sheet -- Excel metadata must be saved with .xlsx extension and be exported from Microsoft Excel. If using a different program, please export as CSV - -### Excel - film metadata fields - -| Field | Description | Accepted Values | Required | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| provider | Name of content owner/studio/network | Example:
Roku Originals | required | -| contentType | Defines the content type of the package | film | required | -| language | Language of the title, synopses, video, captions, subtitles, audio dubs, and/or artwork listed on the row. The value must conform to a supported [language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). Only one language is allowed | Valid [language value](#language-codes) | required | -| original_spoken_language | Defines the original production language of the title being delivered. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). | Valid [language value](#language-codes) | required | -| country_of_origin | Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. | Valid 2-character country code per [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) | preferred | -| asset_id | Immutable, unique identifier for a movie. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the Title ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | required | -| title | Title of movie in the language defined in the language column. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) | Example:
Movie Title | required | -| genres | Genre classification of the content. Roku requires each movie to be delivered with at least one supported genre. Please see [enumerated list](#genres) of genres that Roku supports. | See [enumerated list](#genres) below. No more than 10 genres may be submitted for a single title | required | -| tags | Tags is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. | any string under 50 characters in length | HIGHLY recommended | -| runtime | Total run time of content in whole minutes | Integers only.
Example: 90 | required | -| release_date | Original date content was first made available in any presentation. Must include accurate year of release at a minimum | Conforms to ISO 8601 format: YYYY-MM-DD | required | -| adBreaks | Used to determine[ Ad Breaks for Ad Supported Content](#ad-breaks). adBreak values must be accurate to the millisecond. If the video provided includes commercial blacks, please provide the timecode equal to the midpoint of the commercial black. While not required for SVOD content, frame accurate adBreak data can be ingested if available. | HH:MM:SS.sss | preferred | -| cuePoints | Used to identify start and end times of opening credits, content recaps, end credits, and behind the scenes footage. cuePoint start and end time values must be accurate to the millisecond. comma separated list constructed using the following format:
`type`=`startTime`>`endTime`

Example:
intro=00:05:10.253>00:07:15:123,
recap=00:01:12.456>00:03:12.052 | Format:
type=HH:MM:SS.sss>
HH:MM:SS.sss
Allowable type values:
`ad overlay`

`behind the scenes`
`intro`
`recap`
`end` | optional | -| ratingSystem | The rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. | required | -| ratings | Parental or content advisory rating for the movie by a rating source. A valid movie or TV rating from the rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. If the title has not been rated by that Territory’s official rating authority, please include a valid rating from the USA_PR ratingSystem. There is no official body that assigns ratings for the USA_PR ratingSystem. Please use the guidelines listed at [http://tvguidelines.org/](http://tvguidelines.org/) to assign the appropriate rating. | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. | required | -| cast | Names of cast members | Comma separated list of Firstname Lastname | preferred | -| director | Name(s) of the director of the movie. Director is the only crew member role currently supported in Excel metadata ingest | Comma separated list of Firstname Lastname | preferred | -| short_synopsis | A short synopsis of the content in the language defined in the language column. 250-character limit. | 250-character synopsis | required | -| long_synopsis | A long synopsis of the content in the language defined in the language column. 500-character limit. | 500-character synopsis | optional | -| eidr | EIDR ID if one exists | Any valid EIDR ID | optional | -| tms_id | Gracenote ID if one exists | Any valid TMS ID | optional | -| closed_captions | Indicates whether the title delivered contains closed captions. Accepted values are Y or N. This field is required for all content intended for Roku Channel in the US | Y or N | required | -| closed_captions_exemption | FCC exemption code for closed caption requirement. This node is required if the `closedCaptions` value = “N”
1 - The content has never aired on television in the United States.
2 - The content has only aired on television in the United States without captions.
3 - The content has not aired on television in the United States with captions since September 30, 2012.
4 - The content does not consist of full-length video programming.
5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)).
6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | | required in US
if closed_captions = N | -| video_file_name | The file name of the video in the language defined in the language column that was delivered via Aspera. Only 1 video is allowed per asset_id. The video_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieVideoFile.mov | required | -| audio_layout | [Audio Layout Descriptor](#descriptive-audio) for the video file delivered. | Allowed values:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo | optional | -| sidecar_audio_file_name | The file name of the sidecar audio file in the language defined in the language column that was delivered via Aspera. The sidecar_audio_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieDubFile.wav | optional
For delivery of sidecar audio file for translation or accessibility purposes | -| sidecar_audio_label | For use only with audio description files. Leave this column blank for audio dubs. | Allowed value:
audio description | required for descriptive audio files | -| caption_file_name | The file name of the closed caption in the language defined in the language column that was delivered via Aspera. The caption_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieCaptions.srt | required | -| subtitle_file_name | The file name of the full subtitle in the language defined in the language column that was delivered via Aspera. The localized_subtitle_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example: movieSubtitle.srt | required when providing localized metadata and/or localized assets | -| keyart_file_name | The file name of the texted key art image in the language defined in the language column that was delivered via Aspera. The keyart_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieKeyArt.jpg | required | -| background_file_name | The file name of the textless background image that was delivered via Aspera. The background_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieBGimage.jpg | preferred | -| boxcover_file_name | The file name of the texted boxcover image in the language defined in the language column that was delivered via Aspera. The boxcover_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieBoxArt.jpg | preferred | -| territory | Country code(s) of the territory in which the content is available. Multiple comma separated country nodes can be provided assuming vodType, licensePeriodStart, and licensePeriodEnd dates are identical across countries. | Allowed values:
US
CA
GB
MX | preferred | -| vodType | Monetization Type of the movie. Multiple comma separated vodType nodes can be provided assuming country, licensePeriodStart, and licensePeriodEnd dates are identical across vodType. | Example:
avod
svod
avod,svod | preferred | -| license_start_date | Start date of content availability to users on Roku Channel. license_start_date must be chronologically before license_end_date. license_start_date and license_end_date must not be identical | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | preferred | -| license_end_date | End date of content availability to users on Roku Channel. license_end_date must be chronologically after license_start_date. license_start_date and license_end_date must not be identical | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | preferred | - -*** - -### Excel - episodic TV metadata fields - -| Field | Description | Accepted Values | Required | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| provider | Name of content owner/studio/network | Example:
Roku Originals | required | -| contentType | Defines the content type of the package | episode | required | -| Language | Language of the title, synopses, video, captions, subtitles, audio dubs, and/or artwork listed on the row. The value must conform to a supported [language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). Only one language is allowed | One valid [language value](#language-codes) | required | -| original_spoken_language | Defines the original production language of the title being delivered. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). | One valid [language value](#language-codes) | required | -| country_of_origin | Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. | One valid 2-character country code per [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) | preferred | -| series_id | Immutable, unique identifier for a series. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the Series ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit | alphanumeric characters, hyphens, and underscores only. 50 character maximum | required | -| series_title | Title of the series in the language defined in the language column. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) | Example:
Series Title | required | -| series_tmsId | Gracenote ID if one exists | Any valid Show TMS ID | optional | -| series_release_date | Original date series was first made available in any presentation. Must include accurate year of release at a minimum | Conforms to ISO 8601 format: YYYY-MM-DD | required | -| series_genres | Genre classification of the content. Roku requires each movie to be delivered with at least one supported genre. Please see [enumerated list](#genres) of genres that Roku supports. | See [enumerated list](#genres) below. No more than 10 genres may be submitted for a single title | required | -| series_tags | Tags is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. | any string under 50 characters in length | HIGHLY recommended | -| series_cast | Names of series cast members | Comma separated list of Firstname Lastname | preferred | -| series_directors | Name(s) of the director of the series. Director is the only crew member role currently supported in Excel metadata ingest | Comma separated list of Firstname Lastname | preferred | -| series_short_synopsis | A short synopsis of the series in the language defined in the language column. 250-character limit. | 250-character synopsis | required | -| series_long_synopsis | A long synopsis of the series in the language defined in the language column. 500-character limit. | 500-character synopsis | Optional | -| season_id | Immutable, unique identifier for a season. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. 50 character limit | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | required | -| season_number | Numerical position of the season within a series. This value will determine the order in which the underlying episodes will be viewed on platform. seasonNumber values must be delivered as they were originally broadcast or exhibited on any platform. Only numerical (integer) values are allowed. | Integers only | required | -| season_tmsId | Gracenote ID if one exists | Any valid season TMS ID | optiona | -| asset_id | Immutable, unique identifier for an episode. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the Title ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | required | -| episode_title | Title of episode in the language defined in the language column. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) | Example:
Movie Title | required | -| episode_number | Numerical position of the episode within a season of a series. This value will determine the order in which the episodes will be viewed on platform. episodeNumber values must be delivered as they were originally broadcast or exhibited on any platform. Production numbers must not be provided. Only numerical (integer) values are allowed. | Integers only | required | -| episode_release_date | Original date content was first made available in any presentation. Must include accurate year of release at a minimum | Conforms to ISO 8601 format: YYYY-MM-DD | required | -| episode_runtime | Total run time of content in whole minutes | Integers only.
Example: 22 | required | -| episode_adBreaks | Used to determine[ Ad Breaks for Ad Supported Content](#ad-breaks). adBreak values must be accurate to the millisecond. If the video provided includes commercial blacks, please provide the timecode equal to the midpoint of the commercial black. While not required for SVOD content, frame accurate adBreak data can be ingested if available. | HH:MM:SS.sss | preferred | -| episode_cuePoints | Used to identify start and end times of opening credits, content recaps, end credits, and behind the scenes footage. cuePoint start and end time values must be accurate to the millisecond. comma separated list constructed using the following format:
`type`=`startTime`>`endTime`

Example:
intro=00:05:10.253>00:07:15:123,
recap=00:01:12.456>00:03:12.052 | Format:
type=HH:MM:SS.sss>
HH:MM:SS.sss
Allowable type values:
`ad overlay`

`behind the scenes`
`intro`
`recap`
`end` | optional | -| ratingSystem | The rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. | Required | -| episode_ratings | Parental or content advisory rating for the content by a rating source. A valid movie or TV rating from the rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. If the title has not been rated by that Territory’s official rating authority, please include a valid rating from the USA_PR ratingSystem. There is no official body that assigns ratings for the USA_PR ratingSystem. Please use the guidelines listed at [http://tvguidelines.org/](http://tvguidelines.org/) to assign the appropriate rating. | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. | required | -| episode_tags | Tags is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. | any string under 50 characters in length | HIGHLY recommended | -| episode_cast | Names of cast members | Comma separated list of Firstname Lastname | preferred | -| episode_director | Name(s) of the director of the episode. Director is the only crew member role currently supported in Excel metadata ingest | Comma separated list of Firstname Lastname | preferred | -| episode_short_synopsis | A short synopsis of the episode in the language defined in the language column. 250-character limit. | 250-character synopsis | required | -| episode_long_synopsis | A long synopsis of the episode in the language defined in the language column. 500-character limit. | 500-character synopsis | optional | -| episode_eidr | EIDR ID if one exists | Any valid episodic EIDR ID | optional | -| episode_tmsId | Gracenote ID if one exists | Any valid episodic TMS ID | optiona | -| closed_captions | ndicates whether the title delivered contains closed captions. Accepted values are Y or N. This field is required for all content intended for Roku Channel in the US | Y or N | required | -| closed_captions_exemption | FCC exemption code for closed caption requirement. This node is required if the `closedCaptions` value = “N”
1 - The content has never aired on television in the United States.
2 - The content has only aired on television in the United States without captions.
3 - The content has not aired on television in the United States with captions since September 30, 2012.
4 - The content does not consist of full-length video programming.
5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)).
6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | | required in US
if closed_captions = N | -| video_file_name | The file name of the video in the language defined in the language column that was delivered via Aspera. Only 1 video is allowed per asset_id. The video_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
episodeVideoFile.mov | required | -| audio_layout | [Audio Layout Descriptor](#descriptive-audio) for the video file delivered. | Allowed values:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo | optional | -| sidecar_audio_file_name | The file name of the sidecar audio file in the language defined in the language column that was delivered via Aspera. The sidecar_audio_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieDubFile.wav | optional
For delivery of sidecar audio file for translation or accessibility purposes | -| sidecar_audio_label | For use only with audio description files. Leave this column blank for audio dubs. | Allowed value:
audio description | required for descriptive audio files | -| closed_caption_file_name | The file name of the closed caption in the language defined in the language column that was delivered via Aspera. The caption_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
episodeCaptions.srt | required | -| series_keyart_file_name | The file name of the texted key art image in the language defined in the language column that was delivered via Aspera. The keyart_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
episodeKeyArt.jpg | required | -| series_boxcover_file_name | The file name of the texted boxcover image in the language defined in the language column that was delivered via Aspera. The boxcover_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
episodeBoxArt.jpg | preferred | -| series_background_file_name | The file name of the textless background image that was delivered via Aspera. The background_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
episodeBGimage.jpg | preferred | -| episode_background_file_name | The file name of the textless background image that was delivered via Aspera. The background_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
episodeBGimage.jpg | preferred | -| vodType | Monetization Type of the movie. Multiple comma separated vodType nodes can be provided assuming country, licensePeriodStart, and licensePeriodEnd dates are identical across vodType. | Example:
avod
svod
avod,svod | preferred | -| territory | Country code(s) of the territory in which the content is available. Multiple comma separated country nodes can be provided assuming vodType, licensePeriodStart, and licensePeriodEnd dates are identical across countries. | Allowed values:
US
CA
GB
MX | preferred | -| episode_startDate | Start date of content availability to users on Roku Channel. episode_startDate must be chronologically before episode_endDate. episode_startDate and episode_endDate must not be identical | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | preferred | -| episode_endDate | End date of content availability to users on Roku Channel. episode_endDate must be chronologically after episode_startDate. episode_startDate and episode_endDate must not be identical | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | preferred | - -*** - -### Excel - shortForm clip metadata fields - -| Field | Description | Accepted Values | Required | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| provider | Name of content owner/studio/network | Example:
Roku Originals | required | -| contentType | Defines the content type of the package | clip | required | -| subType | Defines the content subType of the package. Roku does not currently support parent/child connections natively. Ancillary or related content can be delivered and identified using one of the below subTypes. _There is no link between the parent and child asset_
Supported subTypes:
trailer
highlight
making_of
behind_scenes
interview
related
recap
extra | Allowed values:
trailer
highlight
making_of
behind_scenes
interview
related
recap
extra | optional | -| language | Language of the title, synopses, video, captions, subtitles, audio dubs, and/or artwork listed on the row. The value must conform to a supported [language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). Only one language is allowed | Valid [language value](#language-codes) | required | -| original_spoken_language | Defines the original production language of the title being delivered. At a minimum, the value must conform to a [supported language code](#language-codes). As a best practice when providing language, please also include a region code to convey helpful information such as the distinction between Spanish spoken in Mexico (es-MX) and Spanish spoken in Spain (es-ES). | Valid [language value](#language-codes) | required | -| country_of_origin | Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. | Valid 2-character country code per [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) | preferred | -| asset_id | Immutable, unique identifier for a movie. IDs are to be generated and supplied by the Partner for content that is delivered to Roku. The ID in the ingest metadata should match the Title ID provided in the avail document. This will aid in tracking the content throughout Roku’s pipeline from Avails submission through publication on Roku Channel. 50 character limit | alphanumeric characters, hyphens, and underscores only. 50 characters maximum | required | -| title | Title of clip in the language defined in the language column. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format, for example: (Classic), (1987), (Season 1), or (HD) | Example:
Movie Title | required | -| genres | Genre classification of the content. Roku requires each movie to be delivered with at least one supported genre. Please see [enumerated list](#genres) of genres that Roku supports. | See [enumerated list](#genres) below. No more than 10 genres may be submitted for a single title | required | -| tags | Tags is a freeform field that can be used to further categorize content aside from the limited number of supported Genre values. Roku Channel editorial team and recommendations engine will utilize the provided Tags to help surface content on Roku Channel Platform UI. The more tags that are included to a clip, episode, or movie, the more ways the content can be curated/surfaced to the end user. There is no limit to the number of tags that can be delivered with a title and there is no defined set of Tags. Tags are case sensitive. For example, a Tags “Rom-Com” and “rom-com” would be considered two unique tags. Please ensure Tags are all delivered consistently. | any string under 50 characters in length | HIGHLY recommended | -| runtime | Total run time of content in whole minutes | Integers only.
Example: 90 | required | -| release_date | Original date content was first made available in any presentation. Must include accurate year of release at a minimum | Conforms to ISO 8601 format: YYYY-MM-DD | required | -| adBreaks | Used to determine[ Ad Breaks for Ad Supported Content](#ad-breaks). adBreak values must be accurate to the millisecond. While not required for SVOD content, frame accurate adBreak data can be ingested if available. | HH:MM:SS.sss | preferred | -| cuePoints | | | optional | -| ratingSystem | The rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. | required | -| ratings | Parental or content advisory rating for the movie by a rating source. A valid movie or TV rating from the rating authority (ratingSystem) of the Territory the content will be available in shall be provided for each movie. If the title has not been rated by that Territory’s official rating authority, please include a valid rating from the USA_PR ratingSystem. There is no official body that assigns ratings for the USA_PR ratingSystem. Please use the guidelines listed at [http://tvguidelines.org/](http://tvguidelines.org/) to assign the appropriate rating. | See [below](#rating-values-by-rating-system-and-country) for allowable ratings by rating system. | required | -| cast | Names of cast members | Comma separated list of Firstname Lastname | preferred | -| director | Name(s) of the director of the movie. Director is the only crew member role currently supported in Excel metadata ingest | Comma separated list of Firstname Lastname | preferred | -| short_synopsis | A short synopsis of the content in the language defined in the language column. 250-character limit. | 250-character synopsis | required | -| long_synopsis | A long synopsis of the content in the language defined in the language column. 500-character limit. | 500-character synopsis | required | -| eidr | EIDR ID if one exists | Any valid EIDR ID | optional | -| tms_id | Gracenote ID if one exists | Any valid TMS ID | optional | -| closed_captions | Indicates whether the title delivered contains closed captions. Accepted values are Y or N. This field is required for all content intended for Roku Channel in the US | Y or N | required | -| closed_captions_exemption | FCC exemption code for closed caption requirement. This node is required if the `closedCaptions` value = “N”
1 - The content has never aired on television in the United States.
2 - The content has only aired on television in the United States without captions.
3 - The content has not aired on television in the United States with captions since September 30, 2012.
4 - The content does not consist of full-length video programming.
5 - The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)).
6 - The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | | required in US
if closed_captions = N | -| video_file_name | The file name of the video in the language defined in the language column that was delivered via Aspera. Only 1 video is allowed per asset_id. The video_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieVideoFile.mov | required | -| audio_layout | [Audio Layout Descriptor](#descriptive-audio) for the video file delivered. | Allowed values:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo | optional | -| sidecar_audio_file_name | The file name of the sidecar audio file in the language defined in the language column that was delivered via Aspera. The sidecar_audio_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieDubFile.wav | optional
For delivery of sidecar audio file for translation or accessibility purposes | -| sidecar_audio_label | For use only with audio description files. Leave this column blank for audio dubs. | Allowed value:
audio description | required for descriptive audio files | -| caption_file_name | The file name of the closed caption in the language defined in the language column that was delivered via Aspera. The caption_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieCaptions.srt | required | -| keyart_file_name | The file name of the texted key art image in the language defined in the language column that was delivered via Aspera. The keyart_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieKeyArt.jpg | required | -| background_file_name | The file name of the textless background image that was delivered via Aspera. The background_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieBGimage.jpg | preferred | -| boxcover_file_name | The file name of the texted boxcover image in the language defined in the language column that was delivered via Aspera. The boxcover_file_name must exactly match the file delivered. File names are case sensitive and must not contain whitespace or special characters | Example:
movieBoxArt.jpg | preferred | -| territory | Country code(s) of the territory in which the content is available. Multiple comma separated country nodes can be provided assuming vodType, licensePeriodStart, and licensePeriodEnd dates are identical across countries. | Allowed values:
US
CA
GB
MX | preferred | -| vodType | Monetization Type of the movie. Multiple comma separated vodType nodes can be provided assuming country, licensePeriodStart, and licensePeriodEnd dates are identical across vodType. | Example:
avod
svod
avod,svod | preferred | -| license_start_date | Start date of content availability to users on Roku Channel. license_start_date must be chronologically before license_end_date. license_start_date and license_end_date must not be identical | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | preferred | -| license_end_date | End date of content availability to users on Roku Channel. license_end_date must be chronologically after license_start_date. license_start_date and license_end_date must not be identical | Conforms to ISO 8601 format: YYYY-MM-DDTHH:MM:SS | preferred | -| parent_type | Content Type of the parent the clip is derived from or describes | Allowed values:
episode
movie
series | optional | -| parent_title | Title of the parent program if the parent content | Example:
Title of Parent Movie or Series | optional | -| parent_runtime | Runtime of the parent program if the parent is a movie or episode | Integer | optional | -| parent_release_date | Release date of the parent movie, episode, or series | Conforms to ISO 8601 format:
YYYY-MM-DD | optional | -| parent_tms_id | TMS ID of the parent movie, episode, or series | Any valid TMS ID | optional | -| parent_series | Series Title of the parent program if the parent is an episode | Example:
Parent Series Title | optional | -| parent_season | Season number of the parent program if the parent is an episode | Integer | optional | -| parent_episode | Episode number of the parent program if the parent is an episode | Integer | optional | -| sport_type | Name of the sport featured in the clip/highlight | Sport name | required for
sports clips | -| sport_league | Name of the sport league featured in the clip/highlight | Sport league name | required for
sports clips | -| sport_teams | Teams featured in the sport clip/highlight. Multiple comma separated teams may be provided.
_At this time Roku only supports team-based participant metadata. Individual sports will be supported at a later date_ | Comma separated list. Example:
Chicago Cubs,St. Louis Cardinals | required for
sports clip= | - -
- -*** - -## Roku supported values - -### Crew roles - -- Actor -- Anchor -- Host -- Narrator -- Voice -- Director -- Producer -- Screenwriter - -### Genres - -| | | | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 3x3 basketball
action
action sports
adventure
aerobics
agriculture
animals
animated
anime
anthology
archery
arm wrestling
art
artistic gymnastics
artistic swimming
arts/crafts
athletics
auction
auto
auto racing
aviation
awards
badminton
ballet
baseball
basketball
beach soccer
beach volleyball
biathlon
bicycle
bicycle racing
billiards
biography
blackjack
bmx racing
boat
boat racing
bobsled
bodybuilding
bowling
boxing
bullfighting
bus./financial
canoe
canoe/kayak
card games
ceremony
cheerleading
children
children-music
children-special
children-talk
collectibles
comedy
comedy drama
community
computers
consumer
cooking
cricket
crime
crime drama
curling
cycling
dance
dark comedy
darts
debate
diving
docudrama
documentary
dog racing
dog show
dog sled
drag racing
drama | educational
entertainment
environment
equestrian
erotic
event
exercise
faith
fantasy
fashion
fencing
field hockey
figure skating
fishing
food
football
fundraiser
gaelic football
game show
gaming
gay/lesbian
golf
gymnastics
handball
health
historical drama
history
hockey
holiday
holiday music
holiday music special
holiday special
holiday-children
holiday-children special
home improvement
horror
horse
house/garden
how-to
hunting
hurling
hydroplane racing
indoor soccer
interview
intl soccer
judo
karate
kayaking
lacrosse
law
live
luge
martial arts
medical
military
miniseries
mixed martial arts
modern pentathlon
motorcycle
motorcycle racing
motorsports
mountain biking
music
music special
music talk
musical
musical comedy
mystery
nature
news
newsmagazine
olympics
opera
outdoors
parade
paranormal | parenting
performing arts
playoff sports
poker
politics
polo
pool
pro wrestling
public affairs
racquet
reality
religious
rhythmic gymnastics
ringuette
road cycling
rodeo
roller derby
romance
romantic comedy
rowing
rugby
running
sailing
science
science fiction
self improvement
shooting
shopping
sitcom
skateboarding
skating
skeleton
skiing
snooker
snowboarding
snowmobile
soap
soap special
soap talk
soccer
softball
special
speed skating
sport climbing
sports
sports talk
squash
standup
sumo wrestling
surfing
suspense
swimming
table tennis
taekwondo
talk
technology
tennis
theater
thriller
track cycling
track/field
trampoline
travel
triathlon
variety
volleyball
war
water polo
water skiing
watersports
weather
weightlifting
western
wrestling
yacht racing | - -### Rating values by rating system and country - -A valid film or TV rating from the rating authority (Rating Source) of the Territory the title will be available in shall be provided for each movie, episode, or shortForm video. If the title has not been rated by that Territory’s official rating authority, a rating of NR (Not Rated) may be provided, however please note that Roku strongly prefers an actual rating on all content. Titles with a rating of NR (Not Rated) will be subject to manual verification which can delay the selection process and publishing to Roku Channel. Discoverability on Roku Channel may also be impacted for titles with the NR (Not Rated) rating and placement within the Kids & Family experience will be prohibited. In lieu of the NR (Not Rated) rating, the title should be self rated using the USA_PR rating system. Guidelines pertaining to the USA_PR ratings can be found [here](http://tvguidelines.org/) - -| **Ratings Authority and Territory** | **Country** | **ratingSystem** | **Rating Value** | -| ------------------------------------------------------------------- | ----------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| British Board of Film Classification
United Kingdom | GB | BBFC | U
PG
12A
12-A
12
15
18
NR
R18
R-1 | -| Canadian Home Video Rating System
Canada | CA | CHVRS | G
PG
14A
14-A
18A
18-A
NR
R
E | -| Motion Picture Associate of America
United States | US | MPAA | G
PG
PG13
PG-13
R
NC-17
NC17
NR | -| Canadian Parental Rating
Canada | CA | CPR | 14+
18+
C
C8
C-8
G
NR
PG
E | -| Dirección General de Radio, Televisión y Cinematografía
Mexico | MX | RTC | AA
A
B
B-15
B15
C
DD
D
NR | -| USA Parental Rating (V-Chip)
United States | US | USA_PR | TV-Y
TVY
TV-Y7
TVY7
TV-G
TVG
TV-PG
TVPG
TV-14
TV14
TV-MA
TVMA
NR | - -### Language codes - -The below list is the full set of language codes Roku currently supports for content ingest. This list is a simplified version of the [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646) specification. - -| Language Code | Language | Language Code | Language | -| ------------- | ------------------------ | ------------- | ------------------------------ | -| af | Afrikaans | km | Khmer | -| sq | Albanian | rw | Kinyarwanda | -| am | Amharic | ko | Korean | -| ar | Arabic | ko-kr | Korean (Korea) | -| ar-dz | Arabic (Algeria) | ku | Kurdish | -| ar-bh | Arabic (Bahrain) | ky | Kyrgyz | -| ar-eg | Arabic (Egypt) | lo | Lao | -| ar-iq | Arabic (Iraq) | la | Latin | -| ar-jo | Arabic (Jordan) | lv | Latvian | -| ar-kw | Arabic (Kuwait) | lt | Lithuanian | -| ar-lb | Arabic (Lebanon) | mk | Macedonian | -| ar-ly | Arabic (Libya) | mg | Malagasy | -| ar-ma | Arabic (Morocco) | ms | Malay | -| ar-om | Arabic (Oman) | ms-my | Malay (Malaysia) | -| ar-qa | Arabic (Qatar) | ml | Malayalam | -| ar-sa | Arabic (Saudi Arabia) | mt | Maltese | -| ar-sy | Arabic (Syria) | mr | Marathi | -| ar-tn | Arabic (Tunisia) | mn | Mongolian | -| ar-ae | Arabic (U.A.E.) | nd | Ndebele | -| ar-ye | Arabic (Yemen) | ne | Nepali | -| hy | Armenian | no | Norwegian | -| as | Assamese | no-no | Norwegian (Norway) | -| az | Azerbaijani | or | Oriya | -| eu | Basque | om | Oromo | -| be | Belarusian | ps | Pashto | -| bn | Bengali | fa | Persian (Farsi) | -| bh | Bihari | pl | Polish | -| bs | Bosnian | pl-pl | Polish (Poland) | -| bg | Bulgarian | pt | Portuguese | -| bg-bg | Bulgarian (Bulgary) | pt-br | Portuguese (Brazil) | -| my | Burmese | pt-pt | Portuguese (Portugal) | -| ca | Catalan | pa | Punjabi | -| zh | Chinese | qu | Quechua | -| zh-hk | Chinese (Hong Kong) | rm | Rhaeto-Romanic | -| zh-cn | Chinese (PRC) | ro | Romanian | -| zh-sg | Chinese (Singapore) | ro-md | Romanian (Republic of Moldova) | -| zh-tw | Chinese (Taiwan) | ro-ro | Romanian (Romania) | -| zh-hans | Chinese (Simplified) | rn | Rundi | -| zh-hant | Chinese (Traditional) | ru | Russian | -| hr | Croatian | ru-md | Russian (Republic of Moldova) | -| hr-hr | Croatian (Croatia) | ru-ru | Russian (Russia) | -| cs | Czech | se | Sami | -| cs-cz | Czech (Czech Republic) | sa | Sanskrit | -| da | Danish | gd | Scottish (Gaelic) | -| da-dk | Danish (Denmark) | sr | Serbian | -| dv | Divehi | sn | Shona | -| nl | Dutch | ii | Sichuan Yi | -| nl-be | Dutch (Belgium) | sd | Sindhi | -| nl-nl | Dutch (Netherlands) | si | Sinhalese | -| dz | Dzongkha | sk | Slovak | -| en | English | sl | Slovenian | -| en-au | English (Australia) | sl-si | Slovenian (Slovenia) | -| en-bz | English (Belize) | so | Somali | -| en-ca | English (Canada) | st | Sotho | -| en-ie | English (Ireland) | es | Spanish | -| en-jm | English (Jamaica) | es-ar | Spanish (Argentina) | -| en-nz | English (New Zealand) | es-bo | Spanish (Bolivia) | -| en-za | English (South Africa) | es-cl | Spanish (Chile) | -| en-tt | English (Trinidad) | es-co | Spanish (Colombia) | -| en-gb | English (United Kingdom) | es-cr | Spanish (Costa Rica) | -| en-us | English (United States) | es-do | Spanish (Dominican Republic) | -| et | Estonian | es-ec | Spanish (Ecuador) | -| fo | Faeroese | es-sv | Spanish (El Salvador) | -| fi | Finnish | es-gt | Spanish (Guatemala) | -| fr | French | es-hn | Spanish (Honduras) | -| fr-be | French (Belgium) | es-mx | Spanish (Mexico) | -| fr-ca | French (Canada) | es-ni | Spanish (Nicaragua) | -| fr-lu | French (Luxembourg) | es-pa | Spanish (Panama) | -| fr-ch | French (Switzerland) | es-py | Spanish (Paraguay) | -| fy | Frisian | es-pe | Spanish (Peru) | -| ff | Fulfulde (Fulah) | es-pr | Spanish (Puerto Rico) | -| gl | Galician | es-es | Spanish (Spain) | -| ka | Georgian | es-uy | Spanish (Uruguay) | -| de | German | es-ve | Spanish (Venezuela) | -| de-at | German (Austria) | sw | Swahili | -| de-de | German (Germany) | sv | Swedish | -| de-li | German (Liechtenstein) | sv-fi | Swedish (Finland) | -| de-lu | German (Luxembourg) | sv-se | Swedish (Sweden) | -| de-ch | German (Switzerland) | tl | Tagalog | -| el | Greek | ty | Tahitian | -| el-gr | Greek (Greece) | tg | Tajik | -| gn | Guarani | ta | Tamil | -| gu | Gujarati | tt | Tatar | -| ht | Haitian (Creole) | te | Telugu | -| ha | Hausa | th | Thai | -| he | Hebrew | th-th | Thai (Thailand) | -| hi | Hindi | bo | Tibetan | -| hu | Hungarian | ti | Tigrigna | -| hu-hu | Hungarian (Hungary) | ts | Tsonga | -| is | Icelandic | tn | Tswana | -| ig | Igbo | tr | Turkish | -| id | Indonesian | tr-tr | Turkish (Turkey) | -| iu | Inuktitut | tk | Turkmen | -| ik | Inupiaq | uk | Ukrainian | -| ga | Irish | ur | Urdu | -| it | Italian | uz | Uzbek | -| it-it | Italian (Italy) | ve | Venda | -| it-ch | Italian (Switzerland) | vi | Vietnamese | -| ja | Japanese | vi-vn | Vietnamese (Vietnam) | -| ja-jp | Japanese (Japan) | cy | Welsh | -| kn | Kannada | xh | Xhosa | -| kr | Kanuri | yi | Yiddish | -| ks | Kashmiri | yo | Yoruba | -| kk | Kazakh | zu | Zulu | - -## Glossary - -| Term | Definition | -| ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Package/
Full Package/
Asset Package/
Full Asset Package | Complete delivery of a movie, episode, or shortForm video. A package consists of:
video, closed caption (where available), artwork, and metadata.

When delivering multi-language titles, a package can also consist of the above as well as:
audio dub, subtitle, localized artwork, and localized metadata | -| MDU | [Metadata update](#metadata-updates-mdu-and-file-replacements) | - -*** - -## Resources - -| Resource | Link | -| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Film Metadata Excel Template | [https://go.roku.com/film-excel-template](https://go.roku.com/film-excel-template) | -| TV Metadata Excel Template | [https://go.roku.com/tv-excel-template](https://go.roku.com/tv-excel-template) | -| Clip Metadata Excel Template | [https://go.roku.com/clip-excel-template](https://go.roku.com/clip-excel-template) | -| Film XML Schema | [https://go.roku.com/film-xml-schema](https://go.roku.com/film-xml-schema) | -| TV XML Schema | [https://go.roku.com/tv-xml-schema](https://go.roku.com/tv-xml-schema) | -| Clip XML Schema | [https://go.roku.com/clip-xml-schema](https://go.roku.com/clip-xml-schema) | -| Annotated Film XML | [https://go.roku.com/film-xml-example](https://go.roku.com/film-xml-example) | -| Annotated TV XML | [https://go.roku.com/tv-xml-example](https://go.roku.com/tv-xml-example) | -| Annotated Clip XML | [https://go.roku.com/clip-xml-example](https://go.roku.com/clip-xml-example) | -| Film ADI XML Example | [https://go.roku.com/film-adi-xml-example](https://go.roku.com/film-adi-xml-example) | -| TV ADI XML Example | [https://go.roku.com/tv-adi-xml-example](https://go.roku.com/tv-adi-xml-example) | -| Clip ADI XML Example | [https://go.roku.com/clip-adi-xml-example](https://go.roku.com/clip-adi-xml-example) | -| All Metadata Templates/Examples/Schemas | [https://go.roku.com/metadata-docs](https://go.roku.com/metadata-docs) | -| Best practices: content tags and metadata | [https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md](https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md) | -| Music cue sheet submission | [https://go.roku.com/music-cue-sheet-submission](https://go.roku.com/music-cue-sheet-submission) | -| Aspera Client | [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm\~Other%20software∏uct=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software\&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all) | -| US MPAA Ratings | [https://www.filmratings.com/](https://www.filmratings.com/) | -| US TV Ratings | [http://tvguidelines.org/](http://tvguidelines.org/) | -| UK BBFC Ratings | [https://bbfc.co.uk/](https://bbfc.co.uk/) | -| Canadian Film Ratings | [https://www.mpa-canada.org/film-ratings/](https://www.mpa-canada.org/film-ratings/) | -| Canadian TV Ratings | [https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/](https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/) | - -## Change Log - -**v2.3 - 2025-02-18** - -- Updated all references to The Roku Channel to Roku Channel -- Added MovieLabs and EMA support -- Added description of Gracenote's Artwork Personalization employed by Roku Channel -- Added expectations post-onboarding -- Added ad-supported content policy -- Added definition and examples of calls to action -- Added submission link for music cue sheets -- Updated video requirements to require semi-textless video -- Updated Roku's preferred sidecar caption/subtitle files -- Identified which sidecar captions/subtitles support positional data -- Updated ratings requirements and preferences discouraging NR and removing support for UR -- Updated minimum 2:3 image resolution to align dimensions to exactly 2:3 -- Updated image examples on platform -- Added some guidance on providing images -- Noted that episodic images should be unique for each episode -- Noted that sidecar subtitles and captions must not be empty files -- Added a link to Roku's "made for kids" page -- Fixed typo in Xpath sample for content type from "episode" to "tv" -- Noted that Excel documents should not link to external data -- Clarified that start dates need to be chronologically before end dates -- Clarified that start dates and end dates cannot be identical -- Updated ingest templates to add additional hints -- Added sports metadata nodes to the clip specifications and templates -- Removed link to file update template -- Updated XSD documents to account for above changes - -**v2.2 - 2023-05-18** - -- Removed support for legacy MDU -- Removed requirement for long_synopsis -- Refreshed the language for automated MDU and file replacements -- Added a 30 day retention policy for files in delivery location -- Added list of allowable and forbidden characters for file names -- Added link to Best practices: content tags and metadata page -- Added end_time as a requirement for credit cuePoint -- Added support for ad overlay cuePoints -- Added language prohibiting delivery of hard parted video segments -- Added language allowing letterboxed/pillarboxed episodic thumbnails -- Added link for a .zip file of all sample docs -- Addressed typographical errors - -**v2.1 - 2022-10-28** - -- Updated MDU documentation adding support for automated MDUs and renaming legacy method -- Separated Excel metadata fields descriptions from XML metadata fields descriptions -- Reformatted XML metadata fields descriptions for increased legibility -- Clarified audio channel labelling -- Clarified sidecar audio requirements -- Clarified sidecar subtitle requirements -- Updated the list of supported language codes -- Added support for ingest of credit cuePoints -- Added Mexico content ratings and rating system (RTC) - -**v2.0 - 2022-04-25** - -- Identified .srt as preferred side car caption input -- Clarified episode number requirements -- Reorganized document to end with metadata -- Reformat metadata node definitions to show xpath and Excel column names -- Hardened and clarified video requirements -- Added acceptable amount of black video at head/tail -- Updated Film requirements to allow release_date rather than theatrical_release_date -- Added support for differing availability information between licenseTypes and/or territories -- Added support for multiple language deliverables including - - Language - - Original Spoken Language - - Country of Origin - - Localized metadata - - Sidecar audio - - Sidecar subtitles - - Localized artwork -- Added listing of supported subtitle files -- Added listing of supported sidecar audio files -- Added listing of supported language codes -- Added support for delivery of descriptive audio -- Clarified language code requirements for localized metadata/assets -- Updated XML samples to include multi-language support -- Updated XSD to validate multi-language XMLs -- Updated Excel samples to include multi-language support -- Added glossary of terminology -- Added external link to FTC page describing COPPA compliance -- Updated the name of the audio layout descriptors to audio layout hints to avoid confusion with descriptive audio -- Updated adBreak policy per latest Roku Ad Policy \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/ingest-specifications-spanish.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/ingest-specifications-spanish.md deleted file mode 100644 index cb6d512c..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/ingest-specifications-spanish.md +++ /dev/null @@ -1,5897 +0,0 @@ ---- -title: Especificaciones para la ingesta -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -A continuación, encontrarás una lista completa de los requisitos de formato para los activos multimedia y metadatos de las empresas socias, incluidas las plantillas de archivo y las pautas de entrega. La plataforma de ingesta de Roku está totalmente automatizada y el pleno cumplimiento de esta especificación garantizará el procesamiento puntual y sin errores del contenido para su distribución en Roku Channel. Si fuera necesario realizar algún cambio en el flujo de trabajo establecido durante la incorporación, avisa a un representante de Roku lo antes posible para organizar cualquier prueba o configuración nueva. Roku espera que el contenido y los metadatos se entreguen de la manera acordada durante la fase de incorporación y prueba. Asegúrate de que el conocimiento sobre las entregas se transfiera al nuevo personal en caso de que se actualicen o cambien los equipos. - -### MovieLabs - -Como alternativa a esta especificación, Roku Channel admite la entrega de contenido a través de la especificación de MovieLabs. - -* **MMC y MEC:** el servicio MovieLabs de Roku Channel se desarrolló con la versión 2.9 de MEC y la versión 1.10 de MMC, tal y como se define en el sitio web de MovieLabs: [https://www.movielabs.com/md/](https://www.movielabs.com/md/) -* **EMA Avails:** Roku Channel admite la última versión de la [especificación de EMA](https://movielabs.com/md/avails/) a través del archivo entregable en formato xlsx - -Roku prefiere los entregables de MovieLabs de todas las empresas socias de suscripción prémium (SVOD). Consulta los detalles adicionales de entrega de MovieLabs específicos para Roku Channel [aquí](#entrega-de-contenido-de-movielabs) - -## Políticas de contenido de Roku - -### Política de anuncios - -Roku mostrará hasta 8 minutos de anuncios por hora de visualización. La política de anuncios de Roku está sujeta a cambios. - -#### Contenido financiado con anuncios en Roku Channel - -Roku Channel busca contenido financiado con anuncios que sea adecuado para nuestras personas usuarias y anunciantes; por ejemplo, Roku Channel no quiere contenido financiado con anuncios con desnudez excesiva o violencia extrema o gráfica. Utiliza el sentido común a la hora de compartir contenido. Si un activo te genera dudas, busca alguna opción alternativa para compartir. Nos reservamos el derecho a eliminar o rechazar cualquier contenido que consideremos inadecuado. - -#### Cortes publicitarios - -Los códigos de tiempo de los cortes publicitarios se deben entregar en conformidad con la Política de anuncios de Roku en los nodos adBreak de los metadatos de la película, el episodio o el clip para activar los cortes publicitarios durante la reproducción en la plataforma. Los adBreaks deben proporcionarse con una precisión de milisegundos. Convierte cualquier valor de velocidad de fotogramas a su equivalente en milisegundos. Recomendamos incluir los adBreaks en los metadatos de ingesta, ya que así se acelerará el proceso de control de calidad. Todos los datos de adBreak deben suministrarse como HH:MM:SS.sss (por ejemplo, 01:23:45.678). - -##### Política de anuncios en películas - -* No se deben incluir adBreaks durante los 10 primeros minutos de reproducción. -* No se debe incluir ningún adBreak previo al video: 00:00:00.000. -* Los puntos de referencia del adBreak deben proporcionarse en las pausas naturales de la escena o en las transiciones a negro. -* No debe haber menos de 10 minutos entre cada adBreak. -* No se admiten adBreaks a menos de 10 minutos de los créditos finales. - -##### Política de anuncios en episodios de series - -Contenido con una duración mayor a 15 minutos: - -* No se deben incluir adBreaks durante los primeros 5 minutos de reproducción. -* No se debe incluir ningún adBreak previo al video: 00:00:00.000. -* Los puntos de referencia del adBreak deben proporcionarse en las pausas naturales de la escena o en las transiciones a negro. -* No debe haber menos de 7 minutos entre cada adBreak. -* No se admiten adBreaks a menos de 5 minutos de los créditos finales. - -### Política de contenido dirigido a niños - -El “contenido dirigido a niños” es contenido que: (i) está dirigido a niños según la definición de la legislación aplicable de la jurisdicción en la que se muestra el contenido (por ejemplo, [La Ley de Protección de la Privacidad Infantil en Internet](https://www.ftc.gov/legal-library/browse/rules/childrens-online-privacy-protection-rule-coppa)); o (ii) se creó para ser visto principalmente por niños dentro de la jurisdicción en la que se muestra el contenido. - -* Debe informarse a Roku de la intención de enviar o distribuir contenido dirigido a niños. -* SE PROHÍBE el envío o la distribución de contenido dirigido a niños sin la aprobación expresa por escrito de Roku. -* Cuando Roku aprueba el envío o la distribución de contenido dirigido a niños, todos los metadatos del contenido deben incluir lo que se detalla a continuación: - * Para contenido de películas: - * La leyenda `` “kidsdirected” (todo en minúscula) debe incluirse como una de las etiquetas para cada película - * Debe incluirse una [clasificación](#valores-de-clasificación-por-sistema-de-clasificación-y-país) por edades válida de MPAA, USA_PR o TV. Las clasificaciones “UNRATED” y “Not Rated” no son aceptables para el contenido dirigido a niños. - - * Para contenido de series por episodios: - * La leyenda `` “kidsdirected” (todo en minúscula) debe incluirse como una de las etiquetas de la serie y los episodios para cada serie y episodio - * Debe incluirse una [clasificación](#valores-de-clasificación-por-sistema-de-clasificación-y-país) por edades de TV válida. Las clasificaciones “UNRATED” y “Not Rated” no son aceptables para el contenido dirigido a niños. - -Consulta [aquí](https://docs.roku.com/published/madeforkids) para obtener más información y asesoramiento sobre contenido “creado para niños” - -### Marcas y llamadas a la acción (CTA) externas - -Roku Channel no permite marcas o enlaces a URL o llamadas a la acción externas en el arte clave o dentro del video y los subtítulos descriptivos. Las llamadas a la acción son recursos creativos o segmentos de contenido que dirigen a las personas usuarias fuera del ecosistema de Roku Channel para consumir contenido en servicios externos. Deben editarse los videos y eliminar los enlaces o las indicaciones que dirigen a las personas usuarias a visitar sitios externos. Esto incluye: - -* logotipos de marca -* URL de sitios web -* códigos QR -* invitación verbal o textual a la audiencia a “hacer clic”, “suscribirse”, “comprar ahora”, “ir a”, etc. - -Comunícate con tu representante de Roku para obtener más información. - -### Hojas de referencia musical - -Las hojas de referencia musical pueden enviarse a Roku para contenido distribuido en Roku Channel a través del siguiente enlace: - -[https://go.roku.com/music-cue-sheet-submission](https://go.roku.com/music-cue-sheet-submission) - -No envíes hojas de referencia musical con los entregables del paquete de video a través de Aspera. Las hojas de referencia que se entreguen con el paquete de video estarán sujetas a eliminación. - -## Experiencia de uso en Roku Channel - -Roku aumenta los metadatos y las ilustraciones que aparecen en Roku Channel en los dispositivos Roku, navegadores web, apps móviles y otros reproductores fuera de la plataforma con datos suministrados por la base de datos de Gracenote, siempre que estén disponibles. Los datos de Gracenote contribuyen a una experiencia unificada de un mismo título en todas las plataformas y en todo el ecosistema de Roku. Roku intentará que todo el contenido entregado por nuestras empresas socias coincida con el registro correspondiente en la base de datos de Gracenote. _En este momento, todos los metadatos e ilustraciones que aparecen en Roku Channel provienen de Gracenote, si dicho contenido se encuentra en su base de datos._ - -Gracenote utiliza la “personalización de las ilustraciones”, mediante la cual proporciona imágenes alternativas para diversificar las ilustraciones de los títulos para distintas personas usuarias en función de varios factores (demografía, popularidad, etc.). Este cambio ha aumentado la participación de los usuarios en nuestra plataforma. Gracenote acepta el arte clave oficial de las empresas socias, sin embargo, no todas las personas usuarias verán el arte oficial, a menos que el algoritmo lo muestre. Gracenote suministra ~3 imágenes únicas y crea versiones alternativas de ilustraciones procedentes de diversos lugares (por ej., emisora original, estudio de producción, agencia creativa). Gracenote le informó a Roku que todas las imágenes están sujetas a una licencia de uso justo y que aplica los mismos estándares de calidad tanto a las imágenes personalizadas como al arte clave suministrado por las empresas socias, por ejemplo, sin grandes revelaciones de la trama, sin imágenes oscuras, borrosas o granuladas, sin imágenes violentas o sugestivas y sin referencias al tabaquismo. - -Nuestros sistemas utilizan varios métodos para hacer coincidir un título con su registro de Gracenote correcto. Las empresas socias pueden facilitar la correspondencia con un registro de Gracenote al brindar metadatos precisos, entre los que se incluyen: - -* El título exacto de una serie, película, especial de TV o video de formato corto. -* Las fechas de lanzamiento que correspondan al año de lanzamiento original del título en cualquier plataforma. -* La numeración exacta de las temporadas y los episodios según el orden de lanzamiento original. -* Los ID de TMS (Gracenote) precisos según el tipo de contenido. - * El contenido clasificado como un episodio en Gracenote debe entregarse a Roku como un episodio. - * El contenido clasificado como una película en Gracenote debe entregarse a Roku como una película. - * El contenido clasificado como un especial de TV en Gracenote debe entregarse a Roku como un especial de TV. - -Las empresas socias pueden ayudar en la selección de su contenido en Roku Channel al brindar etiquetas con cada película, episodio o clip. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas y los géneros proporcionados para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan, más formas habrá de seleccionar y presentar el contenido a la persona usuaria final. Consulta [Prácticas recomendadas: etiquetas y metadatos del contenido](https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md) para obtener más información. - -## Pautas de activos multimedia - -### Requisitos de video - -* Todo el contenido de video debe ser **solo el programa completo** : - - * sin barras ni tonos ni pizarras al inicio del programa - * sin video sin texto tras la finalización del programa - * no más de 2 segundos de negro al inicio del programa - * no más de 2 segundos de negro tras la finalización del programa - -* Los archivos de video deben tener muy poco texto (lo que también se conoce como “con texto sin subtítulos” o “sin texto con texto principal, final y gráfico”). El video puede incluir los crédito iniciales y finales, pero deben eliminarse todos los subtítulos de los diálogos en idioma extranjero. - -* No deben incluirse anuncios en el video. Todos los puntos de inserción de anuncios para el contenido financiado con anuncios se proporcionarán en el archivo de metadatos según las [pautas de la Política de anuncios de Roku.](#política-de-anuncios) - -* Pueden incluirse fotogramas en negro para comerciales en el video siempre que no duren más de 2 segundos. - -* Pueden incluirse fotogramas en negro para comerciales en el contenido de TV por episodios, pero no en el contenido de películas. - -* Los archivos de video deben entregarse como un único archivo de video sin interrupciones. - -* No deben entregarse archivos de video fragmentados (divididos en segmentos en los puntos de corte publicitario). - -* No se permiten las llamadas a la acción (CTA) ni los enlaces a plataformas o sitios externos, y deben eliminarse del video antes de entregarlo a Roku. - -* El contenido de video HD debe entregarse en un contenedor 16:9. - -* Se prefiere la presentación de cuadro completo (relación de aspecto de 1.78), siempre que esté disponible. - -* Se permite el uso del formato letterboxed en 16:9, pero debe reducirse al mínimo. - -* No debe entregarse contenido SD en 16:9 en un contenedor 4:3 con letterboxing. - -* Se prefieren archivos de nivel intermedio de alta calidad con la mayor tasa de bits y la mayor resolución posible. - -#### Velocidad de fotogramas del video - -Roku admite una gran variedad de velocidades de fotogramas y tipos de escaneo. Todos los archivos de video deben entregarse con su velocidad de fotogramas y tipo de escaneo originales. - -#### Resolución de video - -| Tipo | Ancho | Alto | Relación de aspecto de pixeles | -| ----- | ----- | ---- | -------------------------------- | -| SD | 720 | 480 | 4:3 o 16:9 (pixeles anamórficos) | -| SD | 640 | 480 | 1:1 (pixeles cuadrados) | -| SD | 853 | 480 | 1:1 (pixeles cuadrados) | -| SD | 720 | 576 | 4:3 o 16:9 (pixeles anamórficos) | -| SD | 768 | 576 | 1:1 (pixeles cuadrados) | -| SD | 1024 | 576 | 1:1 (pixeles cuadrados) | -| HD | 1280 | 720 | 1:1 (pixeles cuadrados) | -| FHD | 1920 | 1080 | 1:1 (pixeles cuadrados) | -| UHD** | 3840 | 2160 | 1:1 (pixeles cuadrados) | - -_**La resolución UHD solo se admite como resolución de entrada. Actualmente, Roku no codifica ni muestra video en formato 4K UHD en Roku Channel._ - -#### Formatos de video - -| Nombre | Códecs | Extensión | Tasa de bits | -| ------------- | ---------------------------------------------------------------------------------------------------------- | --------- | -------------------------------------- | -| Apple® ProRes | ProRes 444 (todos los perfiles)
ProRes 4444 (todos los perfiles)
ProRes 422 (todos los perfiles) | .mov | 50 Mbps o más | -| XDCam | | .mxf | 50 Mbps o más | -| MPEG-2 | | .ts.mpg | HD = 15 Mbps o más SD= 3.75 Mbps o más | -| MPEG-4 | H.264 | .mp4 | 5 Mbps o más | - -### Requisitos de audio - -_La configuración de audio de los archivos debe ser la estándar de la industria, con todos los canales claramente etiquetados por posición e idioma_ (según el formato del archivo) - -* Es preferible el audio PCM de 16 bits o 24 bits a 48 kHz con la tasa de bits más alta. -* El audio Dolby AC3 es compatible. - -**Roku prefiere recibir audio 5.1 y estéreo siempre que sea posible.** - -| Sonido envolvente 5.1 y sonido estéreo 2.0 | Etiqueta del canal | -| ------------------------------------------ | ------------------------- | -| Canal 1 | Frontal izquierdo (L) | -| Canal 2 | Frontal derecho (R) | -| Canal 3 | Central (C) | -| Canal 4 | LFE (Lfe) | -| Canal 5 | Envolvente izquierdo (Ls) | -| Canal 6 | Envolvente derecho (Rs) | -| Canal 7 | Estéreo izquierdo (SL) | -| Canal 8 | Estéreo derecho (SR) | - -**Solo se acepta sonido envolvente 5.1 si no se dispone de 5.1 y estéreo** - -| Solo sonido envolvente 5.1 | Etiqueta del canal | -| -------------------------- | ------------------------- | -| Canal 1 | Frontal izquierdo (L) | -| Canal 2 | Frontal derecho (R) | -| Canal 3 | Central (C) | -| Canal 4 | LFE (Lfe) | -| Canal 5 | Envolvente izquierdo (Ls) | -| Canal 6 | Envolvente derecho (Rs) | - -**Solo se acepta sonido estéreo si no se dispone de 5.1 y estéreo o sonido envolvente 5.1 solo.** - -| Estéreo 2.0 | Etiqueta del canal | -| ----------- | ---------------------- | -| Canal 1 | Estéreo izquierdo (SL) | -| Canal 2 | Estéreo derecho (SR) | - -### Entregables de audio secundario - -El contenido que se entregue con audio en un idioma que no sea el principal del territorio de distribución debe entregarse con un archivo de doblaje de audio o subtítulos que traduzcan el contenido al idioma principal de ese territorio. Las pistas de audio secundarias pueden multiplexarse con el archivo de video entregable o entregarse en un único archivo de audio sidecar entrelazado. Todas las pistas de audio secundarias, ya sea que estén multiplexadas en el video o entregadas como un archivo sidecar entrelazado, deben entregarse como una mezcla de audio completa. Roku no admite pistas de doblaje que solo contengan diálogo. - -#### Audio secundario sidecar - -* El audio sidecar debe entregarse como un único archivo entrelazado. Roku no admite archivos discretos de un solo canal. -* El audio sidecar debe sincronizarse con el archivo fuente de video que se entregó a Roku. -* Roku admite un archivo de doblaje de audio sidecar por idioma. - -A continuación, se enumeran los formatos de audio sidecar compatibles. Entrega audio sidecar con la mayor tasa de bits y frecuencia de muestreo disponibles. - -| Contenedor | Códecs | Extensión | -| --------------- | ------------ | --------- | -| WAV (preferido) | PCM | .wav | -| MPEG-1 Layer 3 | MP3 | .mp3 | -| OGA | Opus, Vorbis | .ogg | - -#### Audio descriptivo - -El audio descriptivo es una pista de audio alternativa para las personas con discapacidad visual. Puedes consultar la documentación oficial de la FCC sobre descripción de audio en el siguiente enlace: - -[https://www.fcc.gov/audio-description](https://www.fcc.gov/audio-description) - -Roku prefiere recibir pistas de audio descriptivo siempre que sea posible. El material de audio descriptivo debe entregarse de acuerdo con las pautas indicadas en la sección anterior de [Entregables de audio secundario](#entregables-de-audio-secundario) - -#### Consejos para el diseño de los canales de audio - -En caso de que los archivos de video no puedan crearse para incluir etiquetas de canal de audio adecuadas, se debe proporcionar un consejo de diseño de audio en los metadatos para los archivos de video que se entreguen. A continuación, se definen los consejos disponibles. - -##### Consejos de diseño de audio - -| Descriptor | Definición | -| ------------------ | ----------------------------------------------------------------------------------------------------------------- | -| stereoOnly | Solo audio en estéreo de 2 canales. Puede entregarse en una sola pista o en 2 pistas discretas. | -| surroundOnly | Solo audio envolvente 5.1 de 6 canales. Puede entregarse en una sola pista o en 6 pistas discretas. | -| stereoPlusSurround | Audio de 8 canales con sonido estéreo en los canales 1 y 2 seguido de sonido envolvente 5.1 en los canales 3 al 8 | -| surroundPlusStereo | Audio de 8 canales con 5.1 del canal 1 al 6 seguido de sonido estéreo en los canales 7 y 8 | - -### Subtítulos descriptivos - -Roku prefiere recibir los subtítulos descriptivos de todo el contenido para brindar la mejor experiencia de uso posible. - -Para el contenido destinado a los EE. UU., Roku se adhiere a las normas de subtitulado descriptivo de la FCC en lo que respecta a la programación de video por internet. Puedes encontrar dichas normas en el siguiente enlace: - -[https://www.fcc.gov/consumers/guides/captioning-internet-video-programming](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming) - -Todo el contenido que, según la FCC, debe tener subtítulos descriptivos, debe entregarse a Roku con subtítulos descriptivos, los cuales deben estar ajustados y sincronizados con el programa. En el caso del contenido que está exento del requisito de subtítulos descriptivos de acuerdo con las normas de la FCC, debe incluirse un número de código de exención válido en los metadatos. Números de código de exención permitidos y sus definiciones: - -1 - El contenido nunca se emitió por televisión en Estados Unidos. -2 - El contenido solo se emitió por televisión en Estados Unidos sin subtítulos descriptivos. -3 - El contenido no se emite por televisión en Estados Unidos con subtítulos descriptivos desde el 30 de septiembre de 2012. -4 - El contenido no consiste en programación de video de larga duración. -5 - El contenido no pertenece a una categoría de programación en línea que requiera subtítulos descriptivos según la normativa de la FCC (49 C.F.R. § 79.4(b)). -6 - La FCC o el Congreso de EE. UU. concedieron una exención de los requisitos de subtítulos descriptivos para este contenido. - -Para el contenido destinado a territorios fuera de EE. UU., Roku cumplirá con los requisitos de cada territorio. - -Los subtítulos descriptivos pueden proporcionarse en una de las dos siguientes formas: - -* EIA-608 o CEA-708 incrustados en el flujo de video del archivo de video -* Archivo de subtítulos descriptivos sidecar -* Roku prefiere un archivo de subtítulos sidecar legible por humanos como .ttml, .dfxp, .vtt o .srt. -* Más adelante, puedes ver una lista de todos los archivos de subtítulos descriptivos sidecar compatibles. -* Los subtítulos descriptivos sidecar deben comenzar en la hora de código de tiempo 00:00:00:00, ya que el codificador de Roku no respeta el código de tiempo incrustado en el archivo de video. -* No se debe proporcionar un archivo vacío (un archivo sin texto) para los subtítulos descriptivos sidecar. -* Se admiten datos de posición TTML y WebVTT. -* Los datos de posición proporcionados en los subtítulos descriptivos TTML y WebVTT se respetarán tal y como se definen en el archivo proporcionado. - -_Solo se admiten los siguientes estilos de texto para los subtítulos descriptivos:_ - -* _etiquetas en negrita \ y cursiva \_ -* _color del texto_ -* _posicionamiento del texto_ - -_Los archivos de video de Quicktime deben ir acompañados de un archivo de subtítulos descriptivos sidecar. Roku no admite la pista de texto de Quicktime._ - -| **Nombre del formato**- | Admite datos de posición | **Extensión del archivo** | Codificación | **Tipo de entrega**- | **Idiomas**- | -| ------------------------------------------- | ------------------------ | ------------------------- | ------------- | --------------------------- | ---------------------------------------------------------------------- | -| Timed Text Markup Language (TTML) | SÍ | .ttml | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| Web Video Text Track (WebVTT) | SÍ | .vtt o .webvtt | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| Distribution Format Exchange Profile (DFXP) | NO | .dfxp | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| EBU Subtitle Data Exchange Format (STL) | NO | .stl | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| SubRip Text (SRT) | NO | .srt | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| EIA-608 o CEA-708 | NO | no disponible | no disponible | Incrustado en el flujo MPEG | incrustado en el archivo de video | -| SCC | NO | .scc | ASCII | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | - -### Subtítulos - -El contenido que se entregue con audio en un idioma que no sea el principal del territorio de distribución debe entregarse con un archivo de doblaje de audio o subtítulos que traduzcan el contenido al idioma principal de ese territorio. - -* Los subtítulos completos NO deben grabarse en el video. -* Roku prefiere un archivo de subtítulos sidecar legible por humanos como .ttml, .dfxp, .vtt o .srt. -* Más adelante, puedes ver una lista de todos los archivos de subtítulos sidecar compatibles. -* Los subtítulos sidecar deben comenzar en la hora de código de tiempo 00:00:00:00, ya que el codificador de Roku no respeta el código de tiempo incrustado en el archivo de video. -* No se debe proporcionar un archivo vacío (un archivo sin texto) para los subtítulos sidecar. -* Se admiten datos de posición TTML y WebVTT. -* Los datos de posición proporcionados en los subtítulos descriptivos TTML y WebVTT se respetarán tal y como se definen en el archivo proporcionado. - -_Solo se admiten los siguientes estilos de texto para los subtítulos:_ - -* _etiquetas en negrita \ y cursiva \_ -* _color del texto_ -* _posicionamiento del texto_ - -| **Nombre del formato** | Admite datos de posición | **Extensión delarchivo** | Codificación | **Tipo de entrega** | **Idiomas** | -| ------------------------------------------- | ------------------------ | ------------------------ | ------------ | ------------------- | ---------------------------------------------------------------------- | -| Timed Text Markup Language (TTML) | SÍ | .ttml | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| Web Video Text Track (WebVTT) | SÍ | .vtt o .webvtt | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| Distribution Format Exchange Profile (DFXP) | NO | .dfxp | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| EBU Subtitle Data Exchange Format (STL) | NO | .stl | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | -| SubRip Text (SRT) | NO | .srt | UTF-8 | sidecar | sigue el idioma de audio del archivo de video o del archivo de doblaje | - -### Ilustraciones - -Roku admite tres tipos de imagen para cada contenido. Cada tipo de imagen se utilizará en una ubicación diferente dentro de Roku Channel. Roku prefiere recibir los tres tamaños de la ilustración, siempre que sea posible. Cada imagen debe entregarse en formato JPEG o PNG. Proporciona las imágenes en la resolución de imagen preferida de Roku para evitar retrasos en la publicación. Las imágenes _deben_ tener al menos la resolución mínima y _entregarse_ en la relación de aspecto _exacta_ definida para cada tipo de imagen. - -#### Definiciones de tipo de imagen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Formato - - Extensión - - Tipo de imagen - - Resolución mínima - - Resolución preferida - - Relación de aspecto -
- * JPEG o PNG - * RGB - * 72 ppp - - .jpg
.jpeg
.png - 		- Arte clave Imagen con tratamiento de título - - 800x450 - - 1920x1080 - - 16:9 -
- * JPEG o PNG - * RGB - * 72 ppp - - .jpg
.jpeg
.png - 		- Fondo Imagen sin texto utilizada en el fondo de la página del programa - - 800x450 - - 1920x1080 - - 16:9 -
- * JPEG o PNG - * RGB - * 72 ppp - - .jpg
.jpeg
.png - 		- Portada Imagen de póster vertical con tratamiento del título - - 534x801 - - 2000x3000 - - 2:3 -
- -#### Requisitos de ilustración mínimos por tipo de contenido - -**Requisitos de ilustración para contenido de clips** - -| Ilustración | Obligatorio o preferido | Notas | -| ------------------ | ----------------------- | ----------------------------------------------------------- | -| Arte clave en 16:9 | Obligatorio | Solo se necesita la imagen con texto en 16:9 para los clips | - -**Requisitos de ilustración para contenido de películas** - -| Ilustración | Obligatorio o preferido | Notas | -| :----------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -| Arte clave en 16:9 | Obligatorio | Como mínimo, Roku requiere el arte clave en 16:9 para todos los activos de una película. Se prefieren los 3 tipos de imágenes. | -| Portada en 2:3 | Preferido | Como mínimo, Roku requiere el arte clave en 16:9 para todos los activos de una película. Se prefieren los 3 tipos de imágenes. | -| Fondo en 16:9 | Preferido | Como mínimo, Roku requiere el arte clave en 16:9 para todos los activos de una película. Se prefieren los 3 tipos de imágenes. | - -**Requisitos de ilustración para contenido de TV** - -| _**Tipo de contenido de series**_ | | | -| ------------------------------------ | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Ilustración** | **Obligatorio o preferido** | **Notas** | -| Arte clave en 16:9 | Obligatorio | Como mínimo, Roku requiere el arte clave en 16:9 para todos los activos de una serie. Se prefieren los 3 tipos de imágenes. | -| Portada en 2:3 | Preferido | Como mínimo, Roku requiere el arte clave en 16:9 para todos los activos de una serie. Se prefieren los 3 tipos de imágenes. | -| Fondo en 16:9 | Preferido | Como mínimo, Roku requiere el arte clave en 16:9 para todos los activos de una serie. Se prefieren los 3 tipos de imágenes. | -| _**Tipo de contenido de episodios**_ | | | -| **Ilustración** | **Obligatorio o preferido** | **Notas** | -| Fondo en 16:9 | Obligatorio | La imagen de los episodios puede estar en formato letterbox o pillarbox según el video fuente. Las imágenes en formato windowbox serán rechazadas. Las imágenes de los episodios deben ser únicas para cada episodio y representar el contenido de este. | - -#### Pautas de las ilustraciones de contenido - -* Arte clave (gráfico con el título completo del activo visible). -* Sin ilustraciones explícitas ni violencia gráfica. -* Las ilustraciones deben ser posteriores a la fecha de estreno y no incluir expresiones como _En cartelera_ o _Próximamente_ . -* Se prefieren las ilustraciones diseñadas específicamente para la entrega digital. -* Las ilustraciones para territorios internacionales deben localizarse para cada territorio. -* Para el contenido de Roku Channel, Roku no aceptará ilustraciones de marca sin aprobación previa para ningún activo de video individual ni para entidades de temporadas o series. -* No se permiten las llamadas a la acción (CTA) ni los enlaces a plataformas o sitios externos, y deben eliminarse del archivo de imagen antes de entregarlo a Roku. - -#### Ejemplo de ubicaciones de las ilustraciones en la plataforma - -**Ilustraciones de películas: experiencia de navegación** - -Ejemplo resaltado de la imagen en 16:9 con texto y tratamiento de título - -roku400px - movieGrid - -**Ilustraciones de películas: experiencia de los detalles** - -Ejemplo resaltado de la imagen en 16:9 sin texto - -roku400px - movieDetails - -**Ilustraciones de series: experiencia de navegación** - -Ejemplo resaltado de la imagen de la serie en 16:9 con texto y tratamiento de título - -roku400px - seriesGrid - -**Ilustraciones de series: experiencia de los detalles** - -Ejemplo resaltado de la imagen de la serie en 16:9 sin texto - -roku400px - seriesDetail - -**Ilustraciones de episodios: experiencia del selector de episodios** - -Ejemplo resaltado de las imágenes de los episodios en 16:9 sin texto - -roku400px - episodePicker - -**Ilustraciones de episodios: experiencia de los detalles de episodios** - -Ejemplo resaltado de la imagen del episodio en 16:9 sin texto - -roku400px - episodeDetail - -**Ilustraciones de clips: experiencia de navegación** - -Ejemplo resaltado de la imagen en 16:9 con texto y tratamiento de título - -roku400px - clipGrid - -**Ilustraciones de póster: experiencia de búsqueda** - -Ejemplo resaltado de la imagen en 2:3 con texto y tratamiento de título de la experiencia de búsqueda. Se prefieren las imágenes en 2:3 para los tipos de contenido de series y películas - -posterSearch - -## Pautas para la entrega - -Roku acepta contenido a través de Aspera, que puede configurarse como Aspera Shares (con el complemento de Aspera Connect Browser) o como una conexión de Aspera P2P o Enterprise (con Aspera Client o Console). - -Los métodos alternativos de transferencia de archivos o entrega física pueden evaluarse caso por caso y Roku debe aprobarlos. No se devolverá ninguna unidad de disco duro o medio físico que Roku acepte. - -### Entrega a través de Aspera Shares - -Deberás proporcionar los nombres y las direcciones de correo electrónico de las personas usuarias que transmitirán contenido a Roku para Roku Channel. - -URL de Aspera Shares de Roku: [https://aspera.sr.roku.com](https://aspera.sr.roku.com) - -Deberás instalar el complemento del navegador Aspera Connect para cargar contenido a través de Aspera Shares. - -Las invitaciones para crear una cuenta de Aspera Shares se enviarán desde el servidor de Aspera Shares de Roku. Es posible que estos correos electrónicos de invitación automáticos se marquen como correo no deseado, o que el sistema de filtrado de correo electrónico o el cortafuegos de una organización los bloquee. Comprueba si la invitación está en la carpeta de correo no deseado y cambia su ubicación antes de acceder al enlace proporcionado. - -### Entrega a través de Aspera Enterprise, P2P o HSTS - -Roku realiza la autenticación mediante el intercambio de claves RSA públicas o privadas. Para completar esta configuración, proporciona una clave pública RSA-SSH. - -Puedes consultar los pasos para crear claves SSH en la [documentación oficial de Aspera](https://download.asperasoft.com/download/docs/ascp/3.5.2/html/dita/creating_public_key.html) - -Roku proporcionará información sobre el host y el nombre de persona usuaria durante la incorporación. - -**Aspera Client** -[Descarga de Aspera Client](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software\&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all) - -#### Ancho de banda de transferencia - -Roku recomienda verificar o actualizar las preferencias globales y de uso de Aspera Client para que se ajusten a tu ancho de banda de carga preferido. Ten en cuenta que Roku aplica un límite global de ancho de banda de 300 Mbps. - -asperaPreferences - -Según el cliente que se utilice, hay diferentes configuraciones que pueden afectar la velocidad de transferencia. - -* Si se utiliza la interfaz gráfica de uso para clientes de escritorio, se puede establecer una configuración global [https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-global-bandwidth-settings](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-global-bandwidth-settings) -* La velocidad de transferencia también puede configurarse por nivel de conexión (la configuración de “Velocidad” en el paso 7): [https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-adding-editing-connections](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-adding-editing-connections) -* Si se realiza la conexión mediante la línea de comandos, hay un conmutador específico: `-l 100m` establecería la velocidad de transferencia en 100 Mbps -* Si se realiza la conexión mediante Aspera Shares, las velocidades deseadas pueden establecerse para todo el sistema o para cada persona usuaria en la interfaz web de Shares - [https://www.ibm.com/docs/en/aspera-shares/1.10?topic=options-configuring-transfer-settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=options-configuring-transfer-settings) - [https://www.ibm.com/docs/en/aspera-shares/1.10?topic=accounts-configure-user-settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=accounts-configure-user-settings) - -### Entrega de archivos - -* Todos los archivos de video, subtítulos descriptivos e ilustraciones deben _entregarse antes de entregar los metadatos._ -* Los archivos de producción DEBEN entregarse en la carpeta **`/prod`** . La automatización depende de la entrega de archivos en la ubicación correcta. Si no se entregan los archivos en la carpeta correcta, se producirán retrasos en el procesamiento o el contenido no se procesará en absoluto. -* Los archivos de prueba pueden entregarse en la carpeta **`/testing`** . -* Se prefiere que el contenido no se entregue en subcarpetas. En caso de que sea necesario crear subcarpetas, sigue las siguientes pautas: - * Las subcarpetas **no** deben comenzar con un guion bajo. - * **No** separes los archivos en subcarpetas por tipo de archivo. - * Todos los archivos multimedia de un mismo título (episodio, película o formato corto) deben entregarse en el mismo directorio. - * La plataforma de ingesta asume que los archivos multimedia a los que se hace referencia en los metadatos se encuentran en el mismo directorio que el archivo de metadatos. Por lo tanto, los metadatos deben entregarse en el mismo directorio que los archivos multimedia que contienen. -* Las notificaciones de entrega pueden enviarse a [deliverynotifications@roku.com](mailto:deliverynotifications@roku.com) - -#### Conservación de archivos - -La ubicación de entrega es una ubicación temporal para que nuestras empresas socias carguen archivos para la ingesta en la biblioteca de contenido de Roku Channel. Tras completar la ingesta, la automatización moverá los archivos desde la ubicación de entrega hasta una ubicación de archivo en la que se almacenarán por tiempo indefinido. Se espera que todos los archivos cargados en la ubicación de entrega se ingieran en un plazo razonable que no supere los 30 días. Los metadatos válidos y completos deben entregarse poco después de la entrega de los archivos para garantizar la ingesta oportuna. Los archivos en la ubicación de entrega que no se hayan ingerido al cabo de 30 días están sujetos a eliminación. - -_Es posible hacer excepciones a la política de conservación de archivos para los archivos de la carpeta **`/testing`**_ - -#### Denominación de archivos - -Los archivos de video fuente, subtítulos descriptivos e ilustraciones entregados para su ingesta deben cumplir las siguientes pautas: - -* Los nombres de los archivos no deben tener más de 125 caracteres. -* Los nombres de los archivos deben coincidir con la referencia al nombre del archivo en los metadatos suministrados para el título entregado. -* Los nombres de archivo distinguen entre mayúsculas y minúsculas. -* Los nombres de los archivos deben terminar con la extensión adecuada. Las extensiones de los archivos deben estar en minúsculas. -* No deben incluirse espacios en blanco ni caracteres especiales como `!@#$%^&*(){}|[]\;:’”?/><,` en ningún nombre de archivo. -* Puede utilizarse la misma imagen para cada episodio de una serie, pero no es lo ideal. Si se utiliza la misma imagen para cada episodio, esa imagen debe entregarse varias veces y con un nombre único para cada episodio. Por ejemplo, “episode.jpg” debe entregarse como “episode_01.jpg”, “episode_02.jpg”, etc. - -##### Caracteres permitidos en los nombres de archivo - - - - - - - - - - - - -
- Conjuntos de caracteres -
- * 0-9 - * a-z - * A-Z -
- -| Nombre del carácter | Carácter | -| ------------------- | -------- | -| Guion | - | -| Punto | . | -| Guion bajo | _ | - -##### Caracteres prohibidos en los nombres de archivo - -| Nombre del carácter | Carácter | Nombre del carácter | Carácter | -| ------------------- | -------- | -------------------------- | -------- | -| Símbolo arroba | @ | Corchete izquierdo | [ | -| Ampersand | & | Menos de | \< | -| Asterisco | * | Porcentaje | % | -| Barra inversa | \ | Más | + | -| Caret | ^ | Numeral o etiqueta | # | -| Dos puntos | : | Signo de interrogación | ? | -| Coma | , | Comillas o comillas dobles | " | -| Dólar | $ | Llave derecha | } | -| Igual a | = | Corchete derecho | ] | -| Barra | / | Punto y coma | ; | -| Acento grave | ` | Espacio | | -| Mayor de | > | Tilde | ~ | -| Llave izquierda | \{ | Barra vertical | \| | - -_Tanto la ubicación correcta como la cadencia adecuada al momento de la entrega de los archivos, así como la denominación adecuada de estos, es responsabilidad de nuestras empresas socias, ya que estas son las expertas en su propio contenido y no siempre tenemos conocimiento de los plazos de entrega de cada empresa socia particular._ - -## Entrega de contenido de MovieLabs - -El orden de entrega es importante. El servicio MovieLabs de Roku requerirá que el archivo MMC XML se entregue después de completarse la entrega de todos los archivos multimedia a los que se hace referencia en él. Roku no puede procesar el contenido si no se entregaron correctamente los archivos MMC y MEC XML. Consulta los ejemplos a continuación: - -* Para cada archivo MMC, todos los archivos a los que se hace referencia en él deben entregarse antes del archivo MMC XML para considerarse una entrega correcta. -* Para cada archivo MEC, todos los archivos a los que se hace referencia en él deben entregarse antes del archivo MEC XML para considerarse una entrega correcta. -* Las películas, las series, las temporadas y los episodios requieren la entrega correcta tanto del archivo MMC como del MEC para su ingesta. -* No es posible realizar la ingesta de los episodios sin la entrega e ingesta correctas de los archivos MMC y MEC de la temporada a la que pertenece el episodio. -* No es posible realizar la ingesta de las temporadas sin la entrega e ingesta correctas de los archivos MMC y MEC de la serie a la que pertenece la temporada. -* Los episodios procesados por el sistema de Roku antes que la serie o temporada a la que pertenece el episodio se mantendrán en estado de ingesta pendiente hasta que la serie o temporada se hayan entregado correctamente. -* Las temporadas procesadas por el sistema de Roku antes que la serie a la que pertenece la temporada o un episodio perteneciente a esa temporada se mantendrán en un estado de ingesta pendiente hasta que la serie o el episodio se hayan entregado correctamente. -* Las series procesadas por el sistema de Roku antes que una temporada y un episodio perteneciente a esa serie se mantendrán en un estado de ingesta pendiente hasta que una temporada y un episodio se hayan entregado correctamente. - -### Metadatos y archivos multimedia específicos de Roku - -[Los archivos de video](#requisitos-de-video), [archivos de audio](#requisitos-de-audio), [archivos de subtítulos descriptivos](#subtítulos-descriptivos), [archivos de subtítulos](#subtítulos), [archivos de imágenes](#ilustraciones), [requisitos mínimos de metadatos](#metadatos-mínimos-requeridos-por-tipo-de-contenido), [géneros](#géneros) y [clasificaciones y fuentes de clasificación](#valores-de-clasificación-por-sistema-de-clasificación-y-país) deben adherirse a los formatos y requisitos compatibles definidos en esta especificación - -#### Tags - -Las etiquetas para merchandising/curación se pueden enviar a través del nodo de palabras clave compatible con el XML de MovieLabs MEC. Consulte [el esquema MEC de MovieLabs](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link116) para la correcta colocación del nodo de palabra clave. - -*Ejemplo:* - -```xml - - Gran título de mi programa - Resumen breve de mi programa. - Resumen más extenso de mi programa. - - palabra clave - -``` - -#### IDs TMS - -Los TMS IDs de Gracenote se pueden enviar a través del XML de MovieLabs MEC como un identificador con el Namespace TMSID en el nodo AltIdentifier. Consulte [el esquema MEC de MovieLabs](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link121) para conocer la estructura adecuada del nodo AltIdentifier - -Ejemplo: - -```xml - - TMSID - EP012345678910 - -``` - -#### Entrega MMC XML adBreak and cuePoint - -adBreak, intro credit, and end credit cuePoints pueden ser entregado en MovieLabs MMC XML in el nodo marcado, Por favor revise la siguiente información [MovieLabs MMC Schema](https://movielabs.com/md/manifest/v1.10/manifest-v1.10/manifest-v1.10.html#Link184) para una apropiada estructura de los nodos de Markeres -Ejemplo: - -```xml - - - - - 155.071 - FIRST_FRAME_EPISODE_INTRO - FFEI - - - 200.867 - LAST_FRAME_EPISODE_INTRO - LFEI - - - - - - 3669.207 - FIRST_FRAME_UP_NEXT - FFUN - - - 3812.517 - LAST_FRAME_UP_NEXT - LFUN - - - - - - 737.111 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 1361.276 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 1948.821 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 2841.421 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 3270.100 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - -``` - -### Validación del esquema de MovieLabs - -Roku utiliza Apache [xmlbeans](https://xmlbeans.apache.org/download/index.html) para analizar y validar los archivos MEC y MMC XML. Puedes utilizar la herramienta de línea de comandos proporcionada en xmlbeans para llevar a cabo la validación. - -1. Descarga y extrae xmlbeans a tu equipo. -2. Desde la línea de comandos, ve al directorio bin de xmlbeans. -3. Dentro del directorio bin, encontrarás la herramienta de validación. -4. Descarga también los archivos xsd del esquema oficial de MovieLab en tu equipo ( [https://movielabs.com/schema/manifest/v1.10/manifest-v1.10.xsd](https://movielabs.com/schema/manifest/v1.10/manifest-v1.10.xsd) [https://movielabs.com/schema/mdmec/v2.9/mdmec-v2.9.xsd](https://movielabs.com/schema/mdmec/v2.9/mdmec-v2.9.xsd) ) -5. Uso: valida schema.xsd instance.xml (asegúrate de apuntar schema.xsd a mdmec-v2.9.xsd para MEC, y manifest-v1.10.xsd para MMC) -6. A partir del resultado de la línea de comandos, puedes saber si ese xml es válido o no. - -**Uso de ejemplo** - -```bash -./validate ~/dev/movielabsSpec/schema/mdmec-v2.9.xsd /path/to/file/directory/MEC_SAMPLE_123456789.xml -``` - -**Respuesta de ejemplo** - -```bash -XMLBEANS_LIB=./../lib -ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... -/path/to/file/directory /MEC_SAMPLE_123456789.xml valid -``` - -## Requisitos de metadatos - -Roku utiliza un motor de transformación que puede “normalizar” diferentes formatos de metadatos para adaptarlos a las necesidades de ingesta de Roku. Los nombres exactos de los elementos o campos no son tan importantes como la entrega consistente de los nombres acordados de los elementos o campos. Los datos dentro de cualquier campo deben ajustarse a la Especificación de ingesta de Roku Channel, independientemente del nombre del elemento o del campo. Si utilizas un formato XML para entregar tu contenido a otras plataformas, puedes reutilizarlo para entregarlo a Roku. Puedes proporcionar una muestra de este formato de metadatos existente durante la incorporación para que Roku evalúe su validez para la ingesta en Roku Channel. Independientemente del formato utilizado, el entregable de metadatos debe incluir todos los elementos y campos obligatorios. - -### Metadatos mínimos requeridos por tipo de contenido - - - - - - - - - - - - - - -
- Requisitos de películas y clips - - Requisitos de TV -
- * provider - * content type - * asset_id - * title - * release_date - * runtime - * genres - * rating - * rating system - * short_synopsis - * video file_name - * captions file_name (si se requieren subtítulos descriptivos) - * key art file_name - - * provider - * content type - * asset_id - * episode title - * episodeNumber - * episode release_date - * runtime - * rating - * rating system - * episode short_synopsis - * series_id - * series title - * series release_date - * series genres - * series short_synopsis - * season_id - * seasonNumber - * video file_name - * captions file_name (si se requieren subtítulos descriptivos) - * episode thumbnail file_name - * series key art file_name -
- -### Definiciones del tipo de contenido - -Roku Channel admite 3 tipos de contenido: tv, películas y clips. Todo el contenido debe entregarse como uno de estos 3 tipos. Los títulos deben entregarse a Roku Channel en el mismo tipo de contenido en el que el programa estaba disponible originalmente. Las siguientes definiciones pueden ser útiles para clasificar el contenido destinado a Roku Channel. - -**TV** - -El contenido por episodios que se estructura en una jerarquía de serie --> temporada --> episodio debe entregarse según las especificaciones de TV. - -**Película** - -Los títulos completos, de formato largo e independientes deben entregarse según las especificaciones de las películas. Cualquier programa que no está destinado a anidarse en una jerarquía de serie, temporada y episodio y dura más de 15 minutos debe considerarse una película. Esto incluye los especiales de TV independientes. - -**Clip** - -Los títulos de formato corto independientes que duran menos de 15 minutos deben entregarse según las especificaciones de clips. - -### Requisitos y expectativas para los ID - -Roku no proporciona ID para el contenido. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. Todos los clips y películas deben entregarse con un asset_id. Todos los episodios deben entregarse con 3 ID: un asset_id, un series_id y un season_id. Los ID deben ser significativos para tu equipo, ya que son la forma en que identificamos positivamente un título en nuestro sistema. El asset id en los metadatos de ingesta debe coincidir con el title id proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Cualquier actualización del título una vez introducido en nuestro sistema DEBE ir acompañada del asset id. A continuación, figuran las pautas y definiciones de los ID: - -| **ID ** | Definiciones | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| asset_id | Identificador único e inalterable de un clip, un episodio o una película. Obligatorio para todo el contenido. 50 caracteres como máximo. Solo caracteres alfanuméricos, guiones y guiones bajos: **LOS ESPACIOS O CARACTERES ESPECIALES EN CUALQUIER ID PROVOCARÁN UN ERROR EN LA INGESTA** | -| series_id | Identificador único e inalterable de una serie. No puede ser igual al ID de temporada o episodio único. Debe entregarse con todos los episodios de una serie y debe ser consistente para todos los episodios de una serie. Obligatorio para el contenido de TV. 50 caracteres como máximo. Solo caracteres alfanuméricos, guiones y guiones bajos: **LOS ESPACIOS O CARACTERES ESPECIALES EN CUALQUIER ID PROVOCARÁN UN ERROR EN LA INGESTA** | -| season_id | Identificador único e inalterable de una temporada. No puede ser igual al ID de serie o episodio único. Debe entregarse con todos los episodios de una temporada de una serie y debe ser consistente para todos los episodios de una temporada. Obligatorio para el contenido de TV. 50 caracteres como máximo. Solo caracteres alfanuméricos, guiones y guiones bajos: **LOS ESPACIOS O CARACTERES ESPECIALES EN CUALQUIER ID PROVOCARÁN UN ERROR EN LA INGESTA** | - -### Hojas y planificadores de disponibilidad - -Roku solicita una lista de lanzamiento inicial de títulos, episodios o clips de la biblioteca actual que estén disponibles para Roku al momento de la incorporación y un calendario al momento de actualización del contenido. Para una producción en curso, Roku solicita que la información de Avails se proporcione 60 días antes del inicio del período de licencias y que el contenido se entregue al menos 30 días antes de su inclusión en el canal. De este modo, habrá tiempo suficiente para procesar y controlar la calidad del contenido antes de que se publique en Roku Channel. La capacidad de entrega se coordinará después de la firma - -| Documentos | | -| ---------------------------------- | ----------------------------------------------------------------------------------------------- | -| Especificaciones de avails de Roku | Consulta la página de las especificaciones de avails [aquí](https://go.roku.com/trc-avail-spec) | -| Plantilla de avails de Roku | Descarga la plantilla de avails de Roku [aquí](https://go.roku.com/trc-avail-template) | - -### Períodos de disponibilidad - -Roku permite que el contenido se muestre en el dispositivo y que la persona usuaria lo reproduzca a una hora de inicio determinada. De forma predeterminada, el contenido pasará a estar disponible a las 12:00 a. m. (medianoche) y caducará a las 11:59:59 p. m. en la zona horaria de la persona usuaria. - -Si el contenido debe publicarse a una hora que no sea a medianoche o caducar a una hora que no sea las 11:59:59 p. m., los valores de inicio o fin del periodo de licencia en los metadatos de entrada deben incluir los horarios deseados. - -Existen dos tipos de designaciones horarias específicas: relativas y absolutas. - -* Horario relativo: el estreno de una película el sábado por la noche entra en período de disponibilidad a las 9:00 p. m., hora local, para todas las personas usuarias. Una persona usuaria en la zona horaria del este lo ve a las 9:00 p. m., pero una persona usuaria en la zona horaria del Pacífico, en el mismo momento exacto (6:00 p. m. PT), no puede ver ese contenido. -* Horario absoluto: un nuevo episodio de una serie entra en el período de disponibilidad a las 9:00 p. m., hora del este, y pasa a estar disponible inmediatamente en todas las zonas horarias. Una persona usuaria en la zona horaria del Pacífico puede ver el contenido a las 6.:00 p. m., hora local. - -Si bien la configuración horaria la dicta el propietario del contenido, Roku necesitará los metadatos en el siguiente formato: - -* Si el contenido tiene un horario de inicio relativo, ese horario debe indicarse en los metadatos de ingesta y tener el formato “aaaa-mm-ddThh:mm:ss” (2019-11-01T21:00:00) -* Si el contenido tiene un horario de inicio absoluto, ese horario debe indicarse en los metadatos de ingesta. El horario debe presentarse como hora UTC y tener el formato “aaaa-mm-ddThh:mm:ssZ” (2019-11-02T01:00:00Z). -* En este ejemplo, las 9:00 p. m., hora del este, del 1 de noviembre son la 1 a. m., UTC ([https://www.thetimezoneconverter.com](https://www.thetimezoneconverter.com)) -* Si los metadatos de ingesta se reciben sin hora, Roku asumirá una hora de inicio relativa de medianoche y una hora de finalización relativa a las 11:59:59 p. m. - -### Caracteres especiales - -Roku utiliza secciones CDATA para permitir caracteres especiales (p. ej., !@#$%^&*()\{}|[];:’”?/>\<, así como conjuntos de caracteres extranjeros) dentro de determinados valores de nodo del XML de ingesta. Roku recomienda empaquetar los datos en secciones CDATA para asegurar la correcta ingesta del contenido. Los siguientes nodos son los **únicos** nodos que admiten secciones CDATA: - -* title -* long_synopsis -* short_synopsis -* display_name - -Ciertos caracteres en un XML harán que el documento sea ilegible para la plataforma de ingesta de Roku, a menos que se manipulen (escapen) adecuadamente. Los siguientes caracteres deben proporcionarse en su formato de escape para todos los valores de nodo que no admitan secciones CDATA: - -| Nombre del carácter | Carácter | Formato de escape | -| ------------------- | -------- | ----------------- | -| Ampersand | & | `&` | -| Menos de | \< | `<` | -| Mayor de | > | `>` | -| Comillas | " | `"` | -| Apóstrofe | ' | `'` | - -Nunca deben utilizarse caracteres especiales en los nombres de archivo ni en las referencias a nombres de archivo dentro de los metadatos en formato XML o Excel. [Consulta las Pautas de denominación de archivos](#entrega-de-archivos) para obtener más información al respecto. - -### Formatos de metadatos compatibles - -Se prefiere el formato XML. Se debe entregar un XML completo por cada archivo de video de película, clip o episodio de TV entregado. Los metadatos se deben entregar a través de Aspera en la misma carpeta que los archivos de video, subtítulos descriptivos e ilustraciones. - -**Formatos de metadatos compatibles** - -| Nombre del formato | Extensión del formato | Codificación | Versión del paquete | -| ------------------ | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| XML (preferido) | .xml | UTF-8 | clip1.0
film5.0
tv1.0
Cablelabs ADI 1.1

_**La compatibilidad de esquemas XML adicionales se define caso por caso**_ | -| Excel | .xlsx | Consulta [las plantillas de metadatos de Excel](#pautas-y-plantillas-de-metadatos-de-excel-de-roku) y [las pautas de metadatos de Excel de Roku](#pautas-y-plantillas-de-metadatos-de-excel-de-roku) más adelante | | - -### Actualización de metadatos (MDU) y reemplazos de archivos - -Las actualizaciones son automatizadas y pueden enviarse si hay necesidad de modificar metadatos o archivos de activos para cualquier programa que haya sido previamente entregado a Roku Channel. Todas las actualizaciones de metadatos o reemplazos de archivos deben incluir el **Provider** , el **asset_id** y el **Content Type** del programa tal como se entregó originalmente a Roku para que la actualización resulte exitosa. Roku gestionará el control de versiones, no hay necesidad de proporcionar información de versiones en los metadatos. - -Roku actualmente admite la actualización de los siguientes campos de metadatos a través de la MDU automatizada: - -* ID de TMS -* ID de EIDR -* Títulos (principales y localizados) -* Descripciones breves (principales y localizadas) -* Descripciones extensas (principales y localizadas) -* Fecha de lanzamiento -* Títulos de series -* Número de temporada -* Número de episodio -* Idioma (e idiomas localizados) -* Períodos de disponibilidad -* Tipos de licencias -* Países -* Géneros -* Etiquetas de proveedores -* Clasificación de contenido (sistema y clasificación) -* Créditos -* Cortes publicitarios -* Puntos de referencia - -**Actualización de metadatos (MDU)** - -Las actualizaciones de metadatos (MDU) están automatizadas y se procesarán de la misma manera que el contenido que necesita incorporarse a la biblioteca de contenido de Roku Channel. Sigue el procedimiento que se describe a continuación para actualizar solo los metadatos. - -Las actualizaciones de metadatos deben entregarse en el mismo formato que los metadatos para la ingesta. - -Las actualizaciones de metadatos deben incluir **exactamente el mismo asset_id que se incluyó cuando se realizó la ingesta del contenido por primera vez.** - -_Ponte en contacto con [contentoperations@roku.com](mailto:contentoperations@roku.com) si necesitas un listado completo de los asset_id tal y como aparecen en el sistema de Roku Channel._ - -Todas las referencias a nombres de archivo deben eliminarse de una actualización de solo metadatos. Esto incluye: - -* nombre de archivo de video fuente -* nombre de archivo de subtítulos descriptivos -* nombre de archivo de subtítulos -* nombre de archivo de audio de doblaje -* nombres de archivos de arte clave, fondos o ilustraciones de pósters - -Algunos campos deben actualizarse en “grupos”. Para que la actualización se procese correctamente, se deben proporcionar todos los campos obligatorios de un grupo. A continuación, se detallan los grupos actuales: - -* Grupo de metadatos (todos los campos obligatorios deben estar presentes para que se pueda actualizar uno de estos): - -* Idioma (obligatorio) - -* Título (obligatorio) - -* Descripción breve (obligatoria) - -* Descripción extensa (opcional) - -* Grupo de disponibilidad (todos los campos obligatorios deben estar presentes para que se pueda actualizar uno de estos). - -* Tipo de licencia (obligatoria) - -* País (obligatorio) - -* Fecha de inicio (obligatoria) - -* Fecha de finalización (obligatoria) - -Carga la actualización de metadatos en la carpeta “prod” de Aspera - -_Si no ves reflejada la actualización en Roku Channel en un plazo de 24 horas, ponte en contacto con [contentoperations@roku.com](mailto:contentoperations@roku.com)_ - -**Reemplazos y adiciones de archivos** - -Los reemplazos y las adiciones de archivos están automatizados y se procesarán de la misma manera que el contenido que necesita incorporarse en la biblioteca de contenido de Roku Channel. Un reemplazo de archivo reemplazará a un archivo que existe actualmente en la biblioteca de Roku Channel. Una adición de archivo agregará un nuevo archivo a un registro existente en la biblioteca de Roku Channel. Una adición de archivo se utiliza para agregar subtítulos o doblaje localizados a un registro existente. Sigue el procedimiento que se detalla a continuación para reemplazar uno o varios archivos. - -1. Los reemplazos y adiciones de archivos deben entregarse en el mismo formato que los metadatos para la ingesta. -2. Los reemplazos y adiciones de archivos deben incluir **exactamente el mismo asset_id** que se incluyó cuando se realizó la ingesta del contenido por primera vez. - * _Ponte en contacto con [contentoperations@roku.com](mailto:contentoperations@roku.com) si necesitas un listado completo de los asset_id tal y como aparecen en el sistema de Roku Channel._ -3. En el archivo de metadatos solo deben incluirse las referencias a los nombres de los archivos que se reemplazarán o agregarán. Cualquier archivo que no se reemplace o agregue no debe entregarse ni mencionarse en el archivo de metadatos. -4. Si se reemplaza el archivo de video fuente y hay un cambio en la duración de la fuente, cualquier archivo relacionado (subtítulos descriptivos, subtítulos, doblajes de audio) también deberá reemplazarse. -5. Los reemplazos de archivos requieren valores de idioma para su correcta actualización. -6. Carga los metadatos de reemplazo o adición de archivos en la carpeta "prod" de Aspera. - -_Se recomienda proporcionar archivos de reemplazo con un nombre único, tanto en los metadatos como en el mismo archivo. Agregar un número de versión (_v2, _v3, etc.) es suficiente. Por ejemplo:_ `título de_película_v2.mov` - -**Eliminación de contenido** - -Si los derechos cambian desde el momento en que el contenido se entregó originalmente a Roku y es necesario retirarlo de Roku Channel, ya sea de forma inmediata o programada, la fecha de finalización de la disponibilidad se puede cambiar mediante una actualización de metadatos como se define [más adelante](#actualización-de-metadatos-mdu-y-reemplazos-de-archivos). Se deben proporcionar actualizaciones explícitas para todos los territorios en los que se debe eliminar el contenido. Ten en cuenta que las fechas de finalización proporcionadas sin valores de tiempo específicos caducarán a las 11:59:59 p. m. de dicha fecha. - -### Requisitos, muestras y esquemas de metadatos XML de Roku - -| Esquema XML de Roku | Enlace de descarga | -| ---------------------------------------------- | ---------------------------------------------------------- | -| Esquema XML para películas | [Descargar aquí](https://go.roku.com/film-xml-schema) | -| Esquema XML para TV | [Descargar aquí](https://go.roku.com/tv-xml-schema) | -| Esquema XML para clips | [Descargar aquí](https://go.roku.com/clip-xml-schema) | -| **Muestras XML de Roku** | **Enlace de descarga** | -| XML anotado para películas de Roku | [Descargar aquí](https://go.roku.com/film-xml-example) | -| XML anotado para Roku TV | [Descargar aquí](https://go.roku.com/tv-xml-example) | -| XML anotado para clips de Roku | [Descargar aquí](https://go.roku.com/clip-xml-example) | -| **Muestra de metadatos ADI de Cablelabs** | **Enlace de descarga** | -| Ejemplo de XML ADI para películas de Cablelabs | [Descargar aquí](https://go.roku.com/film-adi-xml-example) | -| Ejemplo de XML ADI para TV de Cablelabs | [Descargar aquí](https://go.roku.com/tv-adi-xml-example) | -| Ejemplo de XML ADI para clips de Cablelabs | [Descargar aquí](https://go.roku.com/clip-adi-xml-example) | - -**NOTA:** Las muestras de ADI de Cablelabs tienen fines ilustrativos y no deben tomarse necesariamente como plantillas. Los datos requeridos deben suministrarse en un nodo estático en cada XML. - -*** - -### XML: campos de metadatos de películas - -**package** - -Define el tipo de versión del paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | ----------------- | ----------- | -| `/package/@version` | film5.0 | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**provider** - -Nombre del estudio, cadena o propietario del contenido - -| Xpath XML | Ejemplo | Obligatorio | -| ------------------- | -------------- | ----------- | -| `/package/provider` | Roku Originals | Obligatorio | - -*Ejemplo:* - -```xml -Roku Originals -``` - -**language** - -Idioma principal de los metadatos del paquete. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------ | ----------- | -| `/package/language` | [Valor de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -*Ejemplo:* - -```xml -en -``` - -**type** - -Define el tipo de contenido del paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------- | ----------------- | ----------- | -| `/package/video/type` | film | Obligatorio | - -*Ejemplo:* - -```xml -film -``` - -**asset_id** - -Identificador único e inalterable de una película. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/asset_id` | Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo | Obligatorio | - -*Ejemplo:* - -```xml -movieAssetIdHere -``` - -**eidr** - -ID de EIDR si existe uno - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------- | --------------------------- | ----------- | -| `/package/video/eidr` | Cualquier ID de EIDR válido | Opcional | - -*Ejemplo:* - -```xml - -``` - -**tmsId** - -ID de Gracenote si existe uno - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------- | -------------------------- | ----------- | -| `/package/video/tmsId` | Cualquier ID de TMS válido | Opcional | - -*Ejemplo:* - -```xml - -``` - -**title** - -Título de la película. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - -| Xpath XML | Ejemplo | Obligatorio | -| ---------------------- | --------------------- | ----------- | -| `/package/video/title` | Título de la película | Obligatorio | - -*Ejemplo:* - -```xml -<![CDATA[Título de la película. Obligatorio.]]> -``` - -**short_synopsis** - -Una breve sinopsis del contenido. Sección CDATA compatible. Límite de 250 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------- | -------------------------- | ----------- | -| `/package/video/short_synopsis` | sinopsis de 250 caracteres | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**long_synopsis** - -Una sinopsis larga del contenido. Sección CDATA compatible. Límite de 500 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | -------------------------- | ----------- | -| `/package/video/long_synopsis` | sinopsis de 500 caracteres | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**original_spoken_language** - -Define el idioma original de producción del título que se entrega. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ----------- | -| `/package/video/original_spoken_language` | [Valor de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -*Ejemplo:* - -```xml -en -``` - -**country_of_origin** - -Define el país principal donde se produjo la película y donde están establecidos los principales creadores, el equipo de filmación y los productores. El valor debe ajustarse a uno de los códigos de país compatibles definidos en la lista de códigos de país de 2 caracteres [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html). - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/country_of_origin` | Código de país válido de 2 caracteres según [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html) | Preferido | - -*Ejemplo:* - -```xml -en -``` - -**closedCaptions** - -Indica si el título entregado contiene subtítulos descriptivos. Los valores aceptados son Y o N. Este campo es obligatorio para todo el contenido destinado a Roku Channel en EE. UU. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------- | ----------------- | ---------------------------------------- | -| `/package/video/closedCaptions` | Y o N | Obligatorio para el contenido en EE. UU. | - -*Ejemplo:* - -```xml -Y -``` - -**closedCaptionsExemption** - -Código de exención de la FCC para el requisito de subtítulos descriptivos. Este nodo es obligatorio si el valor `closedCaptions` = “N” - -Valores permitidos y sus definiciones: - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------- | ----------------- | --------------------------------- | -| `/package/video/closedCaptionsExemption` | 1, 2, 3, 4, 5, 6 | Obligatorio si closedCaptions = N | - -*Ejemplo:* - -```xml -1 -``` - -**release_date** - -Fecha original en la que el contenido estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------- | ---------------------------------------- | ----------- | -| `/package/video/release_date` | Conforme al formato ISO 8601: AAAA-MM-DD | Obligatorio | - -*Ejemplo:* - -```xml -AAAA-MM-DD -``` - -**runtime** - -Tiempo de duración total del contenido en minutos enteros - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------ | -------------------- | ----------- | -| `/package/video/runtime` | Solo números enteros | Obligatorio | - -*Ejemplo:* - -```xml -120 -``` - -**genre** - -Clasificación del contenido por género. Roku requiere que cada película se entregue con al menos un género compatible. Consulta la [enumeración](#géneros) de los géneros que admite Roku. - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------- | --------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/genres/genre` | Consulta la [enumeración](#géneros) más adelante. Pueden enviarse hasta 10 géneros por título | Obligatorio | - -*Ejemplo:* - -```xml - - drama - - -``` - -**rating** - -Clasificación por edades o de contenido de la película según una fuente de clasificación. Se facilitará para cada película una clasificación válida de película o TV de parte de la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, incluye una clasificación válida del USA_PR ratingSystem. No existe ningún organismo oficial que asigne clasificaciones para el USA_PR ratingSystem. Toma como referencia las pautas que se enumeran en [http://tvguidelines.org/](http://tvguidelines.org/) para asignar la clasificación adecuada. Valor de clasificación múltiple - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- | -| `/package/video/ratings/rating` `debe incluir el atributo del sistema` | Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación Se permiten múltiples pares de clasificación y sistemas de clasificación | Obligatorio | - -*Ejemplo:* - -```xml - - PG-13 - 12A - 14A - -``` - -**tag** - -La etiqueta es un campo de formato libre que puede utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------- | ------------------------------------------ | ------------------------------- | -| `/package/video/tags/tag` | cualquier cadena de menos de 50 caracteres | Opcional, pero MUY recomendable | - -*Ejemplo:* - -```xml - - energy - dance - - -``` - -**adBreak** **start_time** - -Se utiliza para determinar[los cortes publicitarios del contenido financiado con anuncios](#cortes-publicitarios). Los valores de adBreak deben tener una precisión de milisegundos. Si el video proporcionado incluye fotogramas en negro para comerciales, proporciona el código de tiempo igual al punto medio de dichos fotogramas. Si bien no es necesario para el contenido SVOD, se pueden ingerir datos adBreak con precisión de fotogramas si están disponibles. - -| XPath XML | Valores aceptados | Obligatorio | -| -------------------------------------------- | ----------------- | -------------------------------------- | -| `/package/video/adBreaks/adBreak/start_time` | HH:MM:SS.sss | Preferiblemente para el contenido AVOD | - -*Ejemplo:* - -```xml - - - 00:03:15.000 - - - 00:07:45.425 - - - -``` - -**start_time y end_time de cuePoint** - -Se utiliza para identificar los puntos de entrada y salida de los créditos iniciales, los resúmenes de contenido, los créditos finales y el material de detrás de escena. Las etiquetas cuePoint deben incluir el atributo de tipo. Los valores start_time y end_time de cuePoint deben tener una precisión de milisegundos. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------- | -| `/package/video/cuePoints/cuePoint/start_time` | HH:MM:SS.sss | Preferido | -| `/package/video/cuePoints/cuePoint/end_time` | HH:MM:SS.sss | Preferido | - -*Ejemplo:* - -```xml - - - 00:09:10.456 - 00:09:12.678 - - - 00:07:08.123 - 00:07:59.123 - - - 00:01:08.123 - 00:01:59.123 - - - 00:21:08.123 - 00:21:59.123 - - - 00:41:08.123 - 00:41:59.123 - - -``` - -**Atributo de tipo de cuePoint** - -Define el tipo de cuePoint del cuePoint proporcionado dentro del bloque de cuePoints. El atributo de la etiqueta de cuePoint debe ser de tipo y el valor proporcionado debe ser uno de los siguientes valores: - -| Valor del tipo | Descripción | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ad overlay` | Identifica el cuePoint como el punto dentro del video para anuncios de posicionamiento de productos dentro del programa. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `behind the scenes` | Identifica el cuePoint como material de detrás de escena, normalmente al final de un video. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `intro` | Identifica el cuePoint como los créditos iniciales de un programa. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `recap` | Identifica el cuePoint como un resumen de contenido anterior, típico de los programas de televisión por episodios. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `end` | Identifica el cuePoint como los créditos finales de un programa. En caso de proporcionarse, es obligatorio incluir start_time y end_time | - -**Atributo XPath** - -| Xpath XML | Valores aceptados | -| ----------------------------------- | --------------------------------------------- | -| `/package/video/cuePoints/cuePoint` | Uno de los valores de la enumeración anterior | - -*Ejemplo:* - -```xml - -``` - -**cast display_name** - -Nombre de un miembro del reparto**.** Sección CDATA compatible. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------- | -| `/package/video/cast/cast_member/display_name` | Nombre y apellido | Opcional | - -*Ejemplo:* - -```xml - - - - - - -``` - -**crew display_name** - -Nombre de un miembro del equipo de filmación. Sección CDATA compatible. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------------------------------------- | -| `/package/video/crew/crew_member/display_name` | Nombre y apellido | Obligatorio si se proporciona crew_member | - -*Ejemplo:* - -```xml - -``` - -**role** - -Función del miembro del equipo de filmación que figura en el display_name. Roku requiere que los metadatos incluyan no solo el miembro del equipo de filmación, sino también su función. Consulta la [enumeración](#funciones-del-equipo-de-filmación) de las funciones del equipo de filmación que admite Roku. Las funciones distinguen entre mayúsculas y minúsculas. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| Xpath XML | Valores aceptados | Obligatorio | -| -------------------------------------- | -------------------------------------------------------------------------- | ----------------------------------------- | -| `/package/video/crew/crew_member/role` | Consulta la [enumeración](#funciones-del-equipo-de-filmación) más adelante | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml -director -``` - -**localizations** - -Inicia el bloque de activos que proporciona metadatos localizados para paquetes con múltiples idiomas. Las localizaciones definen el idioma y proporcionan el título, la short_synopsis y la long_synopsis traducidos del paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | ----------------- | ----------- | -| `/package/video/localizations` | | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**localization name attribute** - -Define el idioma del título localizado, la short_synopsis y la long_synopsis que se proporcionan dentro del bloque de localización. El atributo de la etiqueta de localización debe ser el nombre y el valor proporcionado en el nombre debe, como mínimo, ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/localizations/localization` | [Código de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**localized title** - -Título localizado de la película en el idioma especificado en el atributo de nombre de la etiqueta de localización. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD). El `title` localizado debe estar acompañado de una `short_synopsis` localizada y una `long_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------------- | -------------------------------- | ----------- | -| `/package/video/localizations/localization/title` | Título localizado de la película | Obligatorio | - -*Ejemplo:* - -```xml -<![CDATA[Título localizado de la película. Obligatorio.]]> -``` - -**localized short_synopsis** - -Una sinopsis breve localizada del contenido en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 250 caracteres. La `short_synopsis` localizada debe estar acompañada de un `title` localizado y una `long_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/localizations/localization/short_synopsis` | 250 caracteres | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**localized long_synopsis** - -Una sinopsis larga localizada del contenido en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 500 caracteres. La `long_synopsis` localizada debe estar acompañada de un `title` localizado y una `short_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/localizations/localization/long_synopsis` | 500 caracteres | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**playOptions** - -Inicia el bloque de activos que proporciona la información de disponibilidad del paquete. playOptions consiste en la disponibilidad por país o territorio, el tipo de monetización y las fechas de inicio y fin de la disponibilidad del título en el paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------------- | ----------------- | ----------- | -| `/package/video/playOptions` | | Obligatorio | - -*Ejemplo:* - -```xml - -``` - -**country** - -Código de país del territorio en el que está disponible el contenido. Se pueden proporcionar varios nodos de países, siempre que el vodType y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los países. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------- | ----------------- | ----------- | -| `/package/video/playOptions/playOption/country` | US CA GB MX | Preferido | - -*Ejemplo:* - -```xml - - US - - -``` - -**vodType** - -Tipo de monetización de la película. Se pueden proporcionar varios nodos vodType, siempre que el país y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los vodType. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------- | ----------------- | ----------- | -| `/package/video/playOptions/playOption/vodType` | AVOD SVOD | Preferido | - -*Ejemplo:* - -```xml - - AVOD - - -``` - -**licensePeriodStart** - -Fecha de inicio de la disponibilidad del contenido para las personas usuarias de Roku Channel. Se permite una fecha de licensePeriodStart por playOption. Las fechas de licensePeriodStart deben ser cronológicamente anteriores a las de licensePeriodEnd. Las fechas de licensePeriodStart y licensePeriodEnd no deben ser idénticas - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DDTHH:MM:SS - -``` - -**licensePeriodEnd** - -Fecha de finalización de la disponibilidad del contenido para las personas usuarias de Roku Channel. Se permite una fecha de licensePeriodEnd por playOption. Las fechas de licensePeriodEnd deben ser cronológicamente posteriores a las de licensePeriodStart. Las fechas de licensePeriodStart y licensePeriodEnd no deben ser idénticas - -| XPath XML | Valores aceptados | Obligatorio | -| -------------------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DDTHH:MM:SS - -``` - -**assets** - -Inicia el bloque de activos que hace referencia a los archivos entregados en el paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------- | ------------------ | ----------- | -| `/package/video/assets` | media_type="video" | Obligatorio | - -Ejemplo: - -```xml - -``` - -**data_file** -**full source** - -El bloque que describe el archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="source". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="source"` | Obligatorio | - -Ejemplo: - -```xml - - -``` - -**full captions** - -El bloque que describe los subtítulos descriptivos del archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="captions". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | --------------------------------------------------------------------- | ---------------------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="captions"` | Obligatorio en EE. UU. | - -Ejemplo: - -```xml - - -``` - -**full audio** - -El bloque que describe el audio sidecar del archivo de video fuente. El archivo de audio puede ser un doblaje completo para la traducción lingüística o una pista de audio descriptivo para fines de accesibilidad. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="audio" para el doblaje de traducción o role=”audio.descriptive” para fines de accesibilidad. También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="audio"` `data_file role="audio.descriptive"` | Opcional* se prefiere audio.descriptive | - -*_el audio sidecar puede requerirse si se necesitan activos localizados cuando el audio original del archivo fuente no es nativo del territorio de distribución o para cumplir con las normativas de la FCC_ - -Ejemplo: - -```xml - - -``` - -**full subtitles** - -El bloque que describe los subtítulos sidecar del archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="subtitles". También se requieren los nodos \ y \ - - - - - - - - - - - - - - - - - - - - - -
- Xpath XML - - Valores aceptados - - Obligatorio -
- `/package/video/assets/asset/data_file` - - Valores de atributos: `asset type="full"` `data_file role="subtitles"` - - Opcional* -
- * _los subtítulos sidecar pueden requerirse si se necesitan activos localizados cuando el audio original del archivo fuente no es nativo del territorio de distribución._ - - -
- -Ejemplo: - -```xml - - -``` - -**artwork** - -El bloque que describe los archivos de ilustración. El atributo de la etiqueta del activo debe ser type="artwork". También se requieren los nodos \ y \. Consulta [Ilustraciones](#ilustraciones) para conocer las especificaciones completas sobre la entrega de imágenes. - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | -------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="artwork"` | Obligatorio | - -\Ejemplos\ - -```xml - - - - - - -``` - -**locale** - -Identifica el idioma del data_file. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). -Aplica para las funciones del data_file: fuente, subtítulos descriptivos, audio, subtítulos y para el tipo de activo de ilustración. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file/locale` | [Código de idioma compatible](#códigos-de-idioma) | Obligatorio | - -Ejemplo: - -```xml - -``` - -**file_name** - -Nombre de archivo del activo indicado en el atributo de tipo o función del data_file. Todos los valores de file_name distinguen entre mayúsculas y minúsculas y deben tener la extensión de archivo adecuada. - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------------- | --------------------------------------------------------------------- | -------------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | Consulta las especificaciones para la entrega de activos más adelante | Obligatorio para cada activo entregado | -| `/package/video/assets/asset/data_file/file_name` | | Obligatorio | -| `/package/video/assets/asset/data_file/file_name` | Valores de atributos:
`type="background_image"` | Preferido | -| `/package/video/assets/asset/data_file/file_name` | Valores de atributos:
`type="thumbnail_boxcover"` | Preferido | - -Ejemplo: - -```xml -VideoFilename.mxf -``` - -**audio** - -[Descriptor de diseño de audio](#audio-descriptivo) para el archivo de video entregado. Consulta las pautas más adelante - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file/audio` | Valores permitidos: stereoOnly surroundOnly stereoPlusSurround surroundPlusStereo | Opcional | - -Ejemplo: - -```xml - -``` - -*** - -### XML: campos de metadatos de TV por episodios - -**package** - -Define el tipo de versión del paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | ----------------- | ----------- | -| `/package/@version` | tv1.0 | Obligatorio | - -Ejemplo: - -```xml - -``` - -**provider** - -Nombre del estudio, cadena o propietario del contenido - -| Xpath XML | Ejemplo | Obligatorio | -| ------------------- | -------------- | ----------- | -| `/package/provider` | Roku Originals | Obligatorio | - -Ejemplo: - -```xml -Roku Originals -``` - -**language** - -Idioma principal de los metadatos del paquete. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | --------------------------------------------- | ----------- | -| `/package/language` | [Código de idioma válido](#códigos-de-idioma) | Obligatorio | - -Ejemplo: - -```xml -en -``` - -**type** - -Define el tipo de contenido del paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------- | ----------------- | ----------- | -| `/package/video/type` | tv | Obligatorio | - -Ejemplo: - -```xml -tv -``` - -**asset_id** - -Identificador único e inalterable de un episodio. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/asset_id` | Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo | Obligatorio | - -Ejemplo: - -```xml -episodeAssetIdHere -``` - -**eidr** - -ID de EIDR si existe uno - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------- | --------------------------- | ----------- | -| `/package/video/eidr` | Cualquier ID de EIDR válido | Opcional | - -Ejemplo: - -```xml - -``` - -**tmsId** - -ID de Gracenote si existe uno - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------- | -------------------------- | ----------- | -| `/package/video/tmsId` | Cualquier ID de TMS válido | Opcional | - -Ejemplo: - -```xml - -``` - -**title** - -Título del episodio. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - -| Xpath XML | Ejemplo | Obligatorio | -| ---------------------- | ------------------- | ----------- | -| `/package/video/title` | Título del episodio | Obligatorio | - -Ejemplo: - -```xml -<![CDATA[Título del episodio. Obligatorio.]]> -``` - -**episodeNumber** - -Posición numérica del episodio dentro de una temporada de una serie. Este valor determinará el orden en que se verán los episodios en la plataforma. Los valores de episodeNumber deben entregarse tal y como se emitieron o exhibieron originalmente en cualquier plataforma. No deben -proporcionarse números de producción. Solo se permiten valores numéricos (enteros). - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | -------------------- | ----------- | -| `/package/video/episodeNumber` | Solo números enteros | Obligatorio | - -Ejemplo: - -```xml -2 -``` - -**short_synopsis** - -Una breve sinopsis del episodio. Sección CDATA compatible. Límite de 250 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------- | -------------------------- | ----------- | -| `/package/video/short_synopsis` | sinopsis de 250 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**long_synopsis** - -Una sinopsis larga del episodio. Sección CDATA compatible. Límite de 500 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | -------------------------- | ----------- | -| `/package/video/long_synopsis` | sinopsis de 500 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**closedCaptions** - -Indica si el episodio entregado contiene subtítulos descriptivos. Los valores aceptados son Y o N. Este campo es obligatorio para todo el contenido destinado a Roku Channel en EE. UU. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------- | ----------------- | ---------------------------------------- | -| `/package/video/closedCaptions` | Y o N | Obligatorio para el contenido en EE. UU. | - -Ejemplo: - -```xml -Y -``` - -**closedCaptionsExemption** - -Código de exención de la FCC para el requisito de subtítulos descriptivos. Este nodo es obligatorio si el valor `closedCaptions` = “N” - -Valores permitidos y sus definiciones: - -1 - El contenido nunca se emitió por televisión en Estados Unidos. -2 - El contenido solo se emitió por televisión en Estados Unidos sin subtítulos descriptivos. -3 - El contenido no se emite por televisión en Estados Unidos con subtítulos descriptivos desde el 30 de septiembre de 2012. -4 - El contenido no consiste en programación de video de larga duración. -5 - El contenido no pertenece a una categoría de programación en línea que requiera subtítulos descriptivos según la normativa de la FCC (49 C.F.R. § 79.4(b)). -6 - La FCC o el Congreso de EE. UU. concedieron una exención de los requisitos de subtítulos descriptivos para este contenido. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------- | ----------------- | --------------------------------- | -| `/package/video/closedCaptionsExemption` | 1, 2, 3, 4, 5, 6 | Obligatorio si closedCaptions = N | - -Ejemplo: - -```xml -1 -``` - -**release_date** - -Fecha original en la que el episodio estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------- | ---------------------------------------- | ----------- | -| `/package/video/release_date` | Conforme al formato ISO 8601: AAAA-MM-DD | Obligatorio | - -Ejemplo: - -```xml -AAAA-MM-DD -``` - -**runtime** - -Tiempo de duración total del contenido en minutos enteros - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------ | -------------------- | ----------- | -| `/package/video/runtime` | Solo números enteros | Obligatorio | - -Ejemplo: - -```xml -120 -``` - -**rating** - -Clasificación por edades o de contenido del episodio según una fuente de clasificación. Se facilitará para cada episodio una clasificación válida de TV de parte de la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, incluye una clasificación válida del USA_PR ratingSystem. No existe ningún organismo oficial que asigne clasificaciones para el USA_PR ratingSystem. Toma como referencia las pautas que se enumeran en [http://tvguidelines.org/](http://tvguidelines.org/) para asignar la clasificación adecuada. Valor de clasificación múltiple - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/ratings/rating` `debe incluir el atributo del sistema` | Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. Se permiten múltiples pares de clasificación y sistemas de clasificación | Obligatorio | - -Ejemplo: - -```xml - - PG-13 - 12A - 14A - -``` - -**tag** - -La etiqueta es un campo de formato libre que puede utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------- | ------------------------------------------ | ------------------------------- | -| `/package/video/tags/tag` | cualquier cadena de menos de 50 caracteres | Opcional, pero MUY recomendable | - -Ejemplo: - -```xml - - energy - dance - - -``` - -**adBreak start_time** - -Se utiliza para determinar[los cortes publicitarios del contenido financiado con anuncios](#cortes-publicitarios). Los valores de adBreak deben tener una precisión de milisegundos. Si el video proporcionado incluye fotogramas en negro para comerciales, proporciona el código de tiempo igual al punto medio de dichos fotogramas. Si bien no es necesario para el contenido SVOD, se pueden ingerir datos adBreak con precisión de fotogramas si están disponibles. - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------- | ----------------- | -------------------------------------- | -| `/package/video/adBreaks/adBreak` | HH:MM:SS.sss | Preferiblemente para el contenido AVOD | - -Ejemplo: - -```xml - - - 00:03:15.000 - - - 00:07:45.425 - - - -``` - -**start_time y end_time de cuePoint** - -Se utiliza para identificar los puntos de entrada y salida de los créditos iniciales, los resúmenes de contenido, los créditos finales y el material de detrás de escena. Las etiquetas cuePoint deben incluir el atributo de tipo. Los valores start_time y end_time de cuePoint deben tener una precisión de milisegundos. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------- | -| `/package/video/cuePoints/cuePoint/start_time` | HH:MM:SS.sss | Preferido | -| `/package/video/cuePoints/cuePoint/end_time` | HH:MM:SS.sss | Preferido | - -Ejemplo: - -```xml - - - 00:09:10.456 - 00:09:12.678 - - - 00:07:08.123 - 00:07:59.123 - - - 00:01:08.123 - 00:01:59.123 - - - 00:21:08.123 - 00:21:59.123 - - - 00:41:08.123 - 00:41:59.123 - - -``` - -**Atributo de tipo de cuePoint** - -Define el tipo de cuePoint del cuePoint proporcionado dentro del bloque de cuePoints. El atributo de la etiqueta de cuePoint debe ser de tipo y el valor proporcionado debe ser uno de los siguientes valores: - -| Valor del tipo | Descripción | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ad overlay` | Identifica el cuePoint como el punto dentro del video para anuncios de posicionamiento de productos dentro del programa. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `behind the scenes` | Identifica el cuePoint como material de detrás de escena, normalmente al final de un video. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `intro` | Identifica el cuePoint como los créditos iniciales de un programa. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `recap` | Identifica el cuePoint como un resumen de contenido anterior, típico de los programas de televisión por episodios. En caso de proporcionarse, es obligatorio incluir start_time y end_time | -| `end` | Identifica el cuePoint como los créditos finales de un programa. En caso de proporcionarse, es obligatorio incluir start_time y end_time | - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------------- | --------------------------------------------- | --------------------------------------------------- | -| `/package/video/cuePoints/cuePoint` | Uno de los valores de la enumeración anterior | Obligatorio si se proporcionan puntos de referencia | - -Ejemplo: - -```xml - -``` - -**cast display_name** - -Nombre de un miembro del reparto del episodio**.** Sección CDATA compatible. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------- | -| `/package/video/cast/cast_member/display_name` | Nombre Apellido | Opcional | - -Ejemplo: - -```xml - - - - - - -``` - -**crew display_name** - -Nombre de un miembro del equipo de filmación del episodio. Sección CDATA compatible. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------------------------------------- | -| `/package/video/crew/crew_member/display_name` | Nombre Apellido | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml - -``` - -**role** - -Función del miembro del equipo de filmación que figura en el display_name. Roku requiere que los metadatos incluyan no solo el miembro del equipo de filmación, sino también su función. Consulta la [enumeración](#funciones-del-equipo-de-filmación) de las funciones del equipo de filmación que admite Roku. Las funciones distinguen entre mayúsculas y minúsculas. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| Xpath XML | Valores aceptados | Obligatorio | -| -------------------------------------- | -------------------------------------------------------------------------- | ----------------------------------------- | -| `/package/video/crew/crew_member/role` | Consulta la [enumeración](#funciones-del-equipo-de-filmación) más adelante | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml -director -``` - -**localizations** - -Inicia el bloque de activos que proporciona metadatos localizados del episodio para paquetes con múltiples idiomas. Las localizaciones definen el idioma y proporcionan el título, la short_synopsis y la long_synopsis traducidos del paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | ----------------- | ----------- | -| `/package/video/localizations` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localization name attribute** - -Define el idioma del título localizado, la short_synopsis y la long_synopsis que se proporcionan dentro del bloque de localización. El atributo de la etiqueta de localización debe ser el nombre y el valor proporcionado en el nombre debe, como mínimo, ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/localizations/localization` | [Código de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localized title** - -Título localizado del episodio en el idioma especificado en el atributo de nombre de la etiqueta de localización. Incluye únicamente el nombre del episodio tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD). El `title` localizado debe estar acompañado de una `short_synopsis` localizada y una `long_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------------- | ------------------------------ | ----------- | -| `/package/video/localizations/localization/title` | Título del episodio localizado | Obligatorio | - -Ejemplo: - -```xml -<![CDATA[Título del episodio localizado. Obligatorio.]]> -``` - -**localized short_synopsis** - -Una sinopsis breve localizada del episodio en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 250 caracteres. La `short_synopsis` localizada debe estar acompañada de un `title` localizado y una `long_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/localizations/localization/short_synopsis` | 250 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localized long_synopsis** - -Una sinopsis larga localizada del episodio en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 500 caracteres. La `long_synopsis` localizada debe estar acompañada de un `title` localizado y una `short_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/localizations/localization/long_synopsis` | 500 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**series** - -Inicia el bloque de la serie que hace referencia a los metadatos del programa al que pertenece el episodio. Roku sigue la definición de serie de EE. UU. Los episodios están anidados dentro de una temporada de una serie con la siguiente jerarquía: serie -> temporada -> episodio - -| Xpath XML | Ejemplo | Obligatorio | -| ----------------------- | ------- | ----------- | -| `/package/video/series` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**series_id** - -Identificador único e inalterable de una serie. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/series/series_id` | Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo | Obligatorio | - -Ejemplo: - -```xml -seriesIdHere -``` - -**title** - -Título de la serie. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - -| Xpath XML | Ejemplo | Obligatorio | -| ----------------------------- | ------------------- | ----------- | -| `/package/video/series/title` | Título del episodio | Obligatorio | - -Ejemplo: - -```xml -<![CDATA[Título del episodio. Obligatorio.]]> -``` - -**short_synopsis** - -Una breve sinopsis de la serie. Sección CDATA compatible. Límite de 250 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| -------------------------------------- | -------------------------- | ----------- | -| `/package/video/series/short_synopsis` | sinopsis de 250 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**long_synopsis** - -Una sinopsis larga de la serie. Sección CDATA compatible. Límite de 500 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------------- | -------------------------- | ----------- | -| `/package/video/series/long_synopsis` | sinopsis de 500 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**original_spoken_language** - -Define el idioma original de producción del episodio que se entrega. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/series/original_spoken_language` | [Código de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -Ejemplo: - -```xml -en -``` - -**country_of_origin** - -Define el país principal donde se produjo la película y donde están establecidos los principales creadores, el equipo de filmación y los productores. El valor debe ajustarse a uno de los códigos de país compatibles definidos en la lista de códigos de país de 2 caracteres [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html). - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/series/country_of_origin` | Código de país válido de 2 caracteres según [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html) | Preferido | - -Ejemplo: - -```xml -US -``` - -**release_date** - -Fecha original en la que la serie estuvo disponible por primera vez en cualquier presentación. Suele coincidir con la fecha del primer episodio de la serie. Debe incluir, como mínimo, el año correcto del estreno - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------------ | ---------------------------------------- | ----------- | -| `/package/video/series/release_date` | Conforme al formato ISO 8601: AAAA-MM-DD | Obligatorio | - -Ejemplo: - -```xml -AAAA-MM-DD -``` - -**genre** - -Clasificación del contenido por género. Roku requiere que cada episodio se entregue con al menos un género compatible. Consulta la [enumeración](#géneros) de los géneros que admite Roku. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------------ | --------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/series/genres/genre` | Consulta la [enumeración](#géneros) más adelante. Pueden enviarse hasta 10 géneros por título | Obligatorio | - -Ejemplo: - -```xml - - drama - - -``` - -**tag** - -La etiqueta es un campo de formato libre que puede utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - -| Xpath XML | Valores aceptados | Obligatorio | -| -------------------------------- | ------------------------------------------ | ------------------------------- | -| `/package/video/series/tags/tag` | cualquier cadena de menos de 50 caracteres | Opcional, pero MUY recomendable | - -Ejemplo: - -```xml - - energy - dance - - -``` - -**cast display_name** - -Nombre de un miembro del reparto de la serie**.** Sección CDATA compatible. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------------- | ----------------- | ----------- | -| `/package/video/series/cast/cast_member/display_name` | Nombre Apellido | Opcional | - -Ejemplo: - -```xml - - - - - - -``` - -**crew display_name** - -Nombre de un miembro del equipo de filmación de la serie. Sección CDATA compatible. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------------- | ----------------- | ----------------------------------------- | -| `/package/video/series/crew/crew_member/display_name` | Nombre Apellido | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml - -``` - -**role** - -Función del miembro del equipo de filmación que figura en el display_name. Roku requiere que los metadatos incluyan no solo el miembro del equipo de filmación, sino también su función. Consulta la [enumeración](#funciones-del-equipo-de-filmación) de las funciones del equipo de filmación que admite Roku. Las funciones distinguen entre mayúsculas y minúsculas. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------- | -------------------------------------------------------------------------- | ----------------------------------------- | -| `/package/video/series/crew/crew_member/role` | Consulta la [enumeración](#funciones-del-equipo-de-filmación) más adelante | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml -director -``` - -**localizations** - -Inicia el bloque de activos que proporciona metadatos localizados para la serie en paquetes con múltiples idiomas. Las localizaciones definen el idioma y proporcionan el título, la short_synopsis y la long_synopsis traducidos del paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------------- | ----------------- | ----------- | -| `/package/video/series/localizations` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localization name attribute** - -Define el idioma del título localizado, la short_synopsis y la long_synopsis que se proporcionan dentro del bloque de localización. El atributo de la etiqueta de localización debe ser el nombre y el valor proporcionado en el nombre debe, como mínimo, ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/series/localizations/localization` | [Código de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localized title** - -Título localizado de la serie en el idioma especificado en el atributo de nombre de la etiqueta de localización. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD). El `title` localizado debe estar acompañado de una `short_synopsis` localizada y una `long_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| -------------------------------------------------------- | ------------------------------ | ----------- | -| `/package/video/series/localizations/localization/title` | Título del episodio localizado | Obligatorio | - -Ejemplo: - -```xml -<![CDATA[Título del episodio localizado. Obligatorio.]]> -``` - -**localized short_synopsis** - -Una sinopsis breve localizada de la serie en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 250 caracteres. La `short_synopsis` localizada debe estar acompañada de un `title` localizado y una `long_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/series/localizations/localization/short_synopsis` | 250 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localized long_synopsis** - -Una sinopsis larga localizada de la serie en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 500 caracteres. La `long_synopsis` localizada debe estar acompañada de un `title` localizado y una `short_synopsis` localizada - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/series/localizations/localization/long_synopsis` | 500 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**season** - -Inicia el bloque de la temporada que hace referencia a los metadatos para la temporada de la serie a la que pertenece el episodio. Roku sigue la definición de serie de EE. UU. Los episodios están anidados dentro de una temporada de una serie con la siguiente jerarquía: serie -> temporada -> episodio - -| Xpath XML | Ejemplo | Obligatorio | -| ----------------------- | ------- | ----------- | -| `/package/video/season` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**season_id** - -Identificador único e inalterable de una temporada. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/season/season_id` | Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo | Obligatorio | - -Ejemplo: - -```xml -seasonIdHere -``` - -**seasonNumber** - -Posición numérica de la temporada dentro de una serie. Este valor determinará el orden en que se verán los episodios subyacentes en la plataforma. Los valores de seasonNumber deben entregarse tal y como se emitieron o exhibieron originalmente en cualquier plataforma. Solo se permiten valores numéricos (enteros). - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------------ | -------------------- | ----------- | -| `/package/video/season/seasonNumber` | Solo números enteros | Obligatorio | - -Ejemplo: - -```xml -2 -``` - -**playOptions** - -Inicia el bloque de activos que proporciona la información de disponibilidad del paquete. playOptions consiste en la disponibilidad por país o territorio, el tipo de monetización y las fechas de inicio y fin de la disponibilidad del título en el paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------------- | ----------------- | ----------- | -| `/package/video/playOptions` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**country** - -Código de país del territorio en el que está disponible el contenido. Se pueden proporcionar varios nodos de países, siempre que el vodType y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los países. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------- | ----------------- | ----------- | -| `/package/video/playOptions/playOption/country` | US CA GB MX | Preferido | - -Ejemplo: - -```xml - - US - - -``` - -**vodType** - -Tipo de monetización del episodio. Se pueden proporcionar varios nodos vodType, siempre que el país y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los vodType. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------- | ----------------- | ----------- | -| `/package/video/playOptions/playOption/vodType` | AVOD SVOD | Preferido | - -Ejemplo: - -```xml - - AVOD - - -``` - -**licensePeriodStart** - -Fecha de inicio de la disponibilidad del contenido para las personas usuarias de Roku Channel. Se permite una fecha de licensePeriodStart por playOption. Las fechas de licensePeriodStart deben ser cronológicamente anteriores a las de licensePeriodEnd. Las fechas de licensePeriodStart y licensePeriodEnd no deben ser idénticas - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DDTHH:MM:SS - -``` - -**licensePeriodEnd** - -Fecha de finalización de la disponibilidad del contenido para las personas usuarias de Roku Channel. Se permite una fecha de licensePeriodEnd por playOption. Las fechas de licensePeriodEnd deben ser cronológicamente posteriores a las de licensePeriodStart. Las fechas de licensePeriodStart y licensePeriodEnd no deben ser idénticas - -| XPath XML | Valores aceptados | Obligatorio | -| -------------------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DDTHH:MM:SS - -``` - -**assets** - -Inicia el bloque de activos que hace referencia a los archivos entregados en el paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------- | ------------------ | ----------- | -| `/package/video/assets` | media_type="video" | Obligatorio | - -Ejemplo: - -```xml - -``` - -**data_file** -**full source** - -El bloque que describe el archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="source". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="source"` | Obligatorio | - -Ejemplo: - -```xml - - -``` - -**full captions** - -El bloque que describe los subtítulos descriptivos del archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="captions". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | --------------------------------------------------------------------- | ---------------------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="captions"` | Obligatorio en EE. UU. | - -Ejemplo: - -```xml - - -``` - -**full audio** - -El bloque que describe el audio sidecar del archivo de video fuente. El archivo de audio puede ser un doblaje completo para la traducción lingüística o una pista de audio descriptivo para fines de accesibilidad. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="audio" para el doblaje de traducción o role=”audio.descriptive” para fines de accesibilidad. También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="audio"` `data_file role="audio.descriptive"` | Opcional *se prefiere audio.descriptive | - -**el audio sidecar puede requerirse si se necesitan activos localizados cuando el audio original del archivo fuente no es nativo del territorio de distribución o para cumplir con las normativas de la FCC** - -Ejemplo: - -```xml - - -``` - -**full subtitles** - -El bloque que describe los subtítulos sidecar del archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="subtitles". También se requieren los nodos \ y \ - - - - - - - - - - - - - - - - - - - - - -
- Xpath XML - - Valores aceptados - - Obligatorio -
- `/package/video/assets/asset/data_file` - - Valores de atributos: `asset type="full` `data_file role="subtitles"` - - Opcional* -
- * _los subtítulos sidecar pueden requerirse si se necesitan activos localizados cuando el audio original del archivo fuente no es nativo del territorio de distribución._ - - -
- -Ejemplo: - -```xml - - -``` - -**artwork** - -El bloque que describe los archivos de ilustración. El atributo de la etiqueta del activo debe ser type="artwork". El atributo de la etiqueta data_file puede ser type="episode" para la entrega de imágenes al nivel del episodio, o type="series" para la entrega de imágenes al nivel de la serie. También se requieren los nodos \ y \. Consulta [Ilustraciones](#ilustraciones) para conocer las especificaciones completas sobre la entrega de imágenes. - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ----------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="artwork"` `data_file type="episode"` | Preferido | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="artwork"` `data_file type="series"` | Preferido | - -Ejemplo: - -```xml - - - - -``` - -**locale** - -Identifica el idioma del data_file. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). -Aplica para las funciones del data_file: fuente, subtítulos descriptivos, audio, subtítulos y para el tipo de activo de ilustración. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file/locale` | [Código de idioma compatible](#códigos-de-idioma) | Obligatorio | - -Ejemplo: - -```xml - -``` - -**file_name** - -Nombre de archivo del activo indicado en el atributo de tipo o función del data_file. Todos los valores de file_name distinguen entre mayúsculas y minúsculas y deben tener la extensión de archivo adecuada. -En el caso de los archivos de ilustraciones, el atributo de la etiqueta file_name puede omitirse (para indicar arte clave), o ser type="background_image" o type="thumbnail_boxcover". - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------------- | --------------------------------------------------------------------- | -------------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | Consulta las especificaciones para la entrega de activos más adelante | Obligatorio para cada activo entregado | -| `/package/video/assets/asset/data_file/file_name` | | Obligatorio | -| `/package/video/assets/asset/data_file/file_name` | Valores de atributos:
`type="background_image"` | Preferido | -| `/package/video/assets/asset/data_file/file_name` | Valores de atributos:
`type="thumbnail_boxcover"` | Preferido | - -Ejemplo: - -```xml -VideoFilename.mxf -``` - -**audio** - -[Descriptor de diseño de audio](#audio-descriptivo) para el archivo de video entregado. Consulta las pautas más adelante - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file/audio` | Valores permitidos: stereoOnly surroundOnly stereoPlusSurround surroundPlusStereo | Opcional | - -Ejemplo: - -```xml - -``` - -*** - -### XML: campos de metadatos de clips de formato corto - -**package** - -Define el tipo de versión del paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | ----------------- | ----------- | -| `/package/@version` | clip1.0 | Obligatorio | - -Ejemplo: - -```xml - -``` - -**provider** - -Nombre del estudio, cadena o propietario del contenido - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | ----------------------- | ----------- | -| `/package/provider` | Ejemplo: Roku Originals | Obligatorio | - -Ejemplo: - -```xml -Roku Originals -``` - -**language** - -Idioma principal de los metadatos del paquete. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------- | --------------------------------------------- | ----------- | -| `/package/language` | [Código de idioma válido](#códigos-de-idioma) | Obligatorio | - -Ejemplo: - -```xml -en -``` - -**type** - -Define el tipo de contenido del paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------- | ----------------- | ----------- | -| `/package/video/type` | clip | Obligatorio | - -Ejemplo: - -```xml -clip -``` - -**subType** - -Define el subType (subtipo) de contenido del paquete. Actualmente Roku no admite conexiones principales y secundarias de forma nativa. El contenido auxiliar o relacionado puede entregarse e identificarse con uno de los siguientes subtipos (subTypes). _No existe ningún vínculo entre los activos principales y secundarios_ - - - - - - - - - - - - - - - - -
- Xpath XML - - Valores aceptados - - Obligatorio -
- `/package/video/subType` - - * trailer - * highlight - * making_of - * behind_scenes - * interview - * related - * recap - * extra - - Opcional -
- -Ejemplo: - -```xml -trailer -``` - -**asset_id** - -Identificador único e inalterable de un clip de formato corto La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/asset_id` | Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo | Obligatorio | - -Ejemplo: - -```xml -clipAssetIdHere -``` - -**eidr** - -ID de EIDR si existe uno - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------- | --------------------------- | ----------- | -| `/package/video/eidr` | Cualquier ID de EIDR válido | Opcional | - -Ejemplo: - -```xml - -``` - -**tmsId** - -ID de Gracenote si existe uno - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------- | -------------------------- | ----------- | -| `/package/video/tmsId` | Cualquier ID de TMS válido | Opcional | - -Ejemplo: - -```xml - -``` - -**title** - -Título de clip de formato corto Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - -| Xpath XML | Ejemplo | Obligatorio | -| ---------------------- | --------------- | ----------- | -| `/package/video/title` | Título del clip | Obligatorio | - -Ejemplo: - -```xml -<![CDATA[Título del clip. Obligatorio.]]> -``` - -**short_synopsis** - -Una breve sinopsis del contenido. Sección CDATA compatible. Límite de 250 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------- | -------------------------- | ----------- | -| `/package/video/short_synopsis` | sinopsis de 250 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**long_synopsis** - -Una sinopsis larga del contenido. Sección CDATA compatible. Límite de 500 caracteres. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | -------------------------- | ----------- | -| `/package/video/long_synopsis` | sinopsis de 500 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**original_spoken_language** - -Define el idioma original de producción del título que se entrega. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/original_spoken_language` | [Código de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -Ejemplo: - -```xml -en -``` - -**country_of_origin** - -Define el país principal donde se produjo la película y donde están establecidos los principales creadores, el equipo de filmación y los productores. El valor debe ajustarse a uno de los códigos de país compatibles definidos en la lista de códigos de país de 2 caracteres [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html). - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/country_of_origin` | Código de país válido de 2 caracteres según [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html) | Preferido | - -Ejemplo: - -```xml -en -``` - -**closedCaptions** - -Indica si el título entregado contiene subtítulos descriptivos. Los valores aceptados son Y o N. Este campo es obligatorio para todo el contenido destinado a Roku Channel en EE. UU. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------- | ----------------- | ---------------------------------------- | -| `/package/video/closedCaptions` | Y o N | Obligatorio para el contenido en EE. UU. | - -Ejemplo: - -```xml -Y -``` - -**closedCaptionsExemption** - -Código de exención de la FCC para el requisito de subtítulos descriptivos. Este nodo es obligatorio si el valor `closedCaptions` = “N” - -Valores permitidos y sus definiciones: - -1 - El contenido nunca se emitió por televisión en Estados Unidos. -2 - El contenido solo se emitió por televisión en Estados Unidos sin subtítulos descriptivos. -3 - El contenido no se emite por televisión en Estados Unidos con subtítulos descriptivos desde el 30 de septiembre de 2012. -4 - El contenido no consiste en programación de video de larga duración. -5 - El contenido no pertenece a una categoría de programación en línea que requiera subtítulos descriptivos según la normativa de la FCC (49 C.F.R. § 79.4(b)). -6 - La FCC o el Congreso de EE. UU. concedieron una exención de los requisitos de subtítulos descriptivos para este contenido. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------- | ----------------- | --------------------------------- | -| `/package/video/closedCaptionsExemption` | 1, 2, 3, 4, 5, 6 | Obligatorio si closedCaptions = N | - -Ejemplo: - -```xml -1 -``` - -**release_date** - -Fecha original en la que el contenido estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------- | ---------------------------------------- | ----------- | -| `/package/video/release_date` | Conforme al formato ISO 8601: AAAA-MM-DD | Obligatorio | - -Ejemplo: - -```xml -AAAA-MM-DD -``` - -**runtime** - -Tiempo de duración total del contenido en minutos enteros - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------ | -------------------- | ----------- | -| `/package/video/runtime` | Solo números enteros | Obligatorio | - -Ejemplo: - -```xml -120 -``` - -**genre** - -Clasificación del contenido por género. Roku requiere que cada clip de formato corto se entregue con al menos un género compatible. Consulta la [enumeración](#géneros) de los géneros que admite Roku. - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------- | --------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/genres/genre` | Consulta la [enumeración](#géneros) más adelante. Pueden enviarse hasta 10 géneros por título | Obligatorio | - -Ejemplo: - -```xml - - drama - - -``` - -**rating** - -Clasificación por edades o de contenido del clip de formato corto según una fuente de clasificación. Se facilitará para cada clip de formato corto una clasificación válida de película o TV de parte de la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, incluye una clasificación válida del USA_PR ratingSystem. No existe ningún organismo oficial que asigne clasificaciones para el USA_PR ratingSystem. Toma como referencia las pautas que se enumeran en [http://tvguidelines.org/](http://tvguidelines.org/) para asignar la clasificación adecuada. Valor de clasificación múltiple - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/ratings/rating` `debe incluir el atributo del sistema` | Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. Se permiten múltiples pares de clasificación y sistemas de clasificación | Obligatorio | - -Ejemplo: - -```xml - - PG-13 - 12A - 14A - -``` - -**tag** - -La etiqueta es un campo de formato libre que puede utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------- | ------------------------------------------ | ------------------------------- | -| `/package/video/tags/tag` | cualquier cadena de menos de 50 caracteres | Opcional, pero MUY recomendable | - -Ejemplo: - -```xml - - energy - dance - - -``` - -**cast display_name** - -Nombre de un miembro del reparto**.** Sección CDATA compatible. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------- | -| `/package/video/cast/cast_member/display_name` | Nombre Apellido | Opcional | - -Ejemplo: - -```xml - - - - - - -``` - -**crew display_name** - -Nombre de un miembro del equipo de filmación. Sección CDATA compatible. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ----------------- | ----------------------------------------- | -| `/package/video/crew/crew_member/display_name` | Nombre Apellido | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml - -``` - -**role** - -Función del miembro del equipo de filmación que figura en el display_name. Roku requiere que los metadatos incluyan no solo el miembro del equipo de filmación, sino también su función. Consulta la [enumeración](#funciones-del-equipo-de-filmación) de las funciones del equipo de filmación que admite Roku. Las funciones distinguen entre mayúsculas y minúsculas. -*NOTA: Por el momento, director es el único miembro del equipo de filmación (crew_member) que se admite para la ingesta en formato Excel - -| Xpath XML | Valores aceptados | Obligatorio | -| -------------------------------------- | -------------------------------------------------------------------------- | ----------------------------------------- | -| `/package/video/crew/crew_member/role` | Consulta la [enumeración](#funciones-del-equipo-de-filmación) más adelante | Obligatorio si se proporciona crew_member | - -Ejemplo: - -```xml -director -``` - -**localizations** - -Inicia el bloque de activos que proporciona metadatos localizados para paquetes con múltiples idiomas. Las localizaciones definen el idioma y proporcionan el título, la short_synopsis y la long_synopsis traducidos del paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ------------------------------ | ----------------- | ----------- | -| `/package/video/localizations` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localization name attribute** - -Define el idioma del título localizado, la short_synopsis y la long_synopsis que se proporcionan dentro del bloque de localización. El atributo de la etiqueta de localización debe ser el nombre y el valor proporcionado en el nombre debe, como mínimo, ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------- | -| `/package/video/localizations/localization` | [Código de idioma](#códigos-de-idioma) válido (en, es, etc.) También puede incluir códigos de región (en-US, es-MX, etc.) | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localized title** - -Título localizado del clip de formato corto en el idioma especificado en el atributo de nombre de la etiqueta de localización. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - -| XPath XML | Ejemplo | Obligatorio | -| ------------------------------------------------- | -------------------------- | ----------- | -| `/package/video/localizations/localization/title` | Título localizado del clip | Obligatorio | - -Ejemplo: - -```xml -<![CDATA[Título localizado del clip. Obligatorio.]]> -``` - -**localized short_synopsis** - -Una sinopsis breve localizada del contenido en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 250 caracteres. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/localizations/localization/short_synopsis` | 250 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**localized long_synopsis** - -Una sinopsis larga localizada del contenido en el idioma especificado en el atributo de nombre de la etiqueta de localización. Sección CDATA compatible. Límite de 500 caracteres. - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------------------- | ----------------- | ----------- | -| `/package/video/localizations/localization/long_synopsis` | 500 caracteres | Obligatorio | - -Ejemplo: - -```xml - -``` - -**playOptions** - -Inicia el bloque de activos que proporciona la información de disponibilidad del paquete. playOptions consiste en la disponibilidad por país o territorio, el tipo de monetización y las fechas de inicio y fin de la disponibilidad del título en el paquete. - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------------- | ----------------- | ----------- | -| `/package/video/playOptions` | | Obligatorio | - -Ejemplo: - -```xml - -``` - -**country** - -Código de país del territorio en el que está disponible el contenido. Se pueden proporcionar varios nodos de países, siempre que el vodType y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los países. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------- | ----------------- | ----------- | -| `/package/video/playOptions/playOption/country` | US CA GB MX | Preferido | - -Ejemplo: - -```xml - - US - - -``` - -**vodType** - -Tipo de monetización del clip de formato corto Se pueden proporcionar varios nodos vodType, siempre que el país y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los vodType. - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------------- | ----------------- | ----------- | -| `/package/video/playOptions/playOption/vodType` | AVOD SVOD | Preferido | - -Ejemplo: - -```xml - - AVOD - - -``` - -**licensePeriodStart** - -Fecha de inicio de la disponibilidad del contenido para las personas usuarias de Roku Channel. Se permite una fecha de `licensePeriodStart` por playOption. Las fechas de licensePeriodStart deben ser cronológicamente anteriores a las de licensePeriodEnd. Las fechas de licensePeriodStart y licensePeriodEnd no deben ser idénticas - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DDTHH:MM:SS - -``` - -**licensePeriodEnd** - -Fecha de finalización de la disponibilidad del contenido para las personas usuarias de Roku Channel. Se permite una fecha de `licensePeriodEnd` por playOption. Las fechas de licensePeriodEnd deben ser cronológicamente posteriores a las de licensePeriodStart. Las fechas de licensePeriodStart y licensePeriodEnd no deben ser idénticas - -| XPath XML | Valores aceptados | Obligatorio | -| -------------------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DDTHH:MM:SS - -``` - -**assets** - -Inicia el bloque de activos que hace referencia a los archivos entregados en el paquete - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------- | ------------------ | ----------- | -| `/package/video/assets` | media_type="video" | Obligatorio | - -Ejemplo: - -```xml - -``` - -**data_file** -**full source** - -El bloque que describe el archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="source". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="source"` | Obligatorio | - -Ejemplo: - -```xml - - -``` - -**full captions** - -El bloque que describe los subtítulos descriptivos del archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="captions". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | --------------------------------------------------------------------- | ---------------------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="captions"` | Obligatorio en EE. UU. | - -Ejemplo: - -```xml - - -``` - -**full audio** - -El bloque que describe el audio sidecar del archivo de video fuente. El archivo de audio puede ser un doblaje completo para la traducción lingüística o una pista de audio descriptivo para fines de accesibilidad. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="audio" para el doblaje de traducción o role=”audio.descriptive” para fines de accesibilidad. También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="audio"` `data_file role="audio.descriptive"` | Opcional *se prefiere audio.descriptive | - -_el audio sidecar puede requerirse si se necesitan activos localizados cuando el audio original del archivo fuente no es nativo del territorio de distribución o para cumplir con las normativas de la FCC_ - -Ejemplo: - -```xml - - -``` - -**full subtitles** - -El bloque que describe los subtítulos sidecar del archivo de video fuente. El atributo de la etiqueta del activo debe ser type="full" y el atributo de la etiqueta data_file debe ser role="subtitles". También se requieren los nodos \ y \ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ---------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="full"` `data_file role="subtitles"` | Opcional* | - -_los subtítulos sidecar pueden requerirse si se necesitan activos localizados cuando el audio original del archivo fuente no es nativo del territorio de distribución._ - -Ejemplo: - -```xml - - -``` - -**artwork** - -El bloque que describe los archivos de ilustración. El atributo de la etiqueta del activo debe ser type="artwork". También se requieren los nodos \ y \. Consulta [Ilustraciones](#ilustraciones) para conocer las especificaciones completas sobre la entrega de imágenes. - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | -------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file` | Valores de atributos: `asset type="artwork"` | Obligatorio | - -Ejemplo: - -```xml - - -``` - -**locale** -Identifica el idioma del data_file. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). -Aplica para las funciones del data_file: fuente, subtítulos descriptivos, audio y subtítulos, y para el tipo de activo de ilustración. - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------------- | ------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file/locale` | [Código de idioma compatible](#códigos-de-idioma) | Obligatorio | - -Ejemplo: - -```xml - -``` - -**file_name** - -Nombre de archivo del activo indicado en el atributo de tipo o función del data_file. Todos los valores de file_name distinguen entre mayúsculas y minúsculas y deben tener la extensión de archivo adecuada. - -| XPath XML | Valores aceptados | Obligatorio | -| ------------------------------------------------- | --------------------------------------------------------------------- | -------------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | Consulta las especificaciones para la entrega de activos más adelante | Obligatorio para cada activo entregado | - -Ejemplo: - -```xml -VideoFilename.mxf -``` - -**audio** - -[Descriptor de diseño de audio](#audio-descriptivo) para el archivo de video entregado. Consulta las pautas más adelante - -| XPath XML | Valores aceptados | Obligatorio | -| --------------------------------------------- | --------------------------------------------------------------------------------- | ----------- | -| `/package/video/assets/asset/data_file/audio` | Valores permitidos: stereoOnly surroundOnly stereoPlusSurround surroundPlusStereo | Opcional | - -Ejemplo: - -```xml - -``` - -**parentInfo** - -Inicia el bloque de activos que proporciona la información principal del paquete. parentInfo consta del contentType, título del episodio o película, duración del episodio o película, releaseDate, ID de TMS, seriesTitle, seasonNumber y episodeNumber del contenido principal. Se utiliza en combinación con un subType válido - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------- | ----------------- | ----------- | -| `/package/video/parentInfo` | | Opcional | - -Ejemplo: - -```xml - -``` - -**contentType** -Tipo de contenido del contenido principal del cual se deriva o describe el clip - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | -------------------- | ----------- | -| `/package/video/parentInfo/contentType` | episode movie series | Opcional | - -Ejemplo: - -```xml - - episode - -``` - -**title** - -Título del programa principal si este es una película o un episodio - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------- | --------------------------------------- | ----------- | -| `/package/video/parentInfo/title` | Título de la película o serie principal | Opcional | - -Ejemplo: - -```xml - - Título de la película o serie principal - -``` - -**runtime** - -Duración del programa principal si este es una película o episodio - -| Xpath XML | Valores aceptados | Obligatorio | -| ----------------------------------- | ----------------- | ----------- | -| `/package/video/parentInfo/runtime` | Números enteros | Opcional | - -Ejemplo: - -```xml - - 45 - -``` - -**releaseDate** - -Fecha de estreno de la película, episodio o serie principal - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ---------------------------------------- | ----------- | -| `/package/video/parentInfo/releaseDate` | Conforme al formato ISO 8601: AAAA-MM-DD | Opcional | - -Ejemplo: - -```xml - - AAAA-MM-DD - -``` - -**tmsId** - -ID de TMS de la película, episodio o serie principal - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------- | ----------------- | ----------- | -| `/package/video/parentInfo/tmsId` | ID de TMS válido | Opcional | - -Ejemplo: - -```xml - - TMSID - -``` - -**seriesTitle** - -Título de la serie del programa principal si este es un episodio - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------------------- | ---------------------------- | ----------- | -| `/package/video/parentInfo/seriesTitle` | Título de la serie principal | Opcional | - -Ejemplo: - -```xml - - Título de la serie principal - -``` - -**seasonNumber** - -Número de temporada del programa principal si este es un episodio - -| XPath XML | Valores aceptados | Obligatorio | -| ---------------------------------------- | ----------------- | ----------- | -| `/package/video/parentInfo/seasonNumber` | Números enteros | Opcional | - -Ejemplo: - -```xml - - 2 - -``` - -**episodeNumber** - -Número de episodio del programa principal si este es un episodio - -| XPath XML | Valores aceptados | Obligatorio | -| ----------------------------------------- | ----------------- | ----------- | -| `/package/video/parentInfo/episodeNumber` | Números enteros | Opcional | - -Ejemplo: - -```xml - - 14 - -``` - -**sportType** - -Nombre del deporte que aparece en el clip o momento destacado - -| Xpath XML | Valores aceptados | Obligatorio | -| -------------------------- | ------------------ | ---------------------------------- | -| `/package/video/sportType` | Nombre del deporte | Obligatorio para clips de deportes | - -Ejemplo: - -```xml -Baseball -``` - -**sportLeague** - -Nombre de la liga deportiva que aparece en el clip o momento destacado - -| Xpath XML | Valores aceptados | Obligatorio | -| ---------------------------- | --------------------------- | ---------------------------------- | -| `/package/video/sportLeague` | Nombre de la liga deportiva | Obligatorio para clips de deportes | - -Ejemplo: - -```xml -MLB -``` - -**teams** - -Equipos que aparecen en el clip o momento destacado deportivo. Las condiciones de local y visitante de los equipos se definirán en el atributo de Ubicación -_En este momento, Roku solo admite metadatos de participantes basados en equipos. Los deportes individuales serán compatibles en el futuro_ - -| Xpath XML | Valores aceptados | Obligatorio | -| --------------------------- | ------------------------------------------------------------------- | ---------------------------------- | -| `/package/video/teams/team` | Valores de atributos: `team location="away"` `team location="home"` | Obligatorio para clips de deportes | - -Ejemplo: - -```xml - - Chicago Cubs - St. Louis Cardinals - -``` - -*** - -### Pautas y plantillas de metadatos de Excel de Roku - -Los metadatos de Excel solo se aceptarán si se entregan en los formatos aprobados por ROKU que se indican a continuación: - -| Metadatos de Excel | Enlace de descarga | -| ---------------------------------------------- | --------------------------------------------------------- | -| Plantilla de metadatos de Excel para películas | [Descargar aquí](https://go.roku.com/film-excel-template) | -| Plantilla de metadatos de Excel para TV | [Descargar aquí](https://go.roku.com/tv-excel-template) | -| Plantilla de metadatos de Excel para clips | [Descargar aquí](https://go.roku.com/clip-excel-template) | - -La plantilla de metadatos de Excel de Roku debe enviarse con todos los campos obligatorios completos. Roku incluyó consejos en la fila 2 de cada plantilla de metadatos en los que se indica qué celdas se deben resaltar y el formato especial necesario para cada celda. Consulta estos consejos al momento de completar la plantilla de metadatos de Excel. Otras cuestiones a tener en cuenta a la hora de completar una plantilla incluyen: - -* Las fechas deben proporcionarse en formato AAAA-MM-DD (cambia el formato de la celda a “Texto” de ser necesario). -* Los nombres de los archivos no deben tener [caracteres especiales ni espacios](#caracteres-especiales) -* Las fórmulas utilizadas deben convertirse en texto antes del envío. Si se incluye una fórmula, las entregas serán rechazadas y se producirán retrasos o fallos en el procesamiento del contenido -* No incluyas enlaces a datos o libros de Excel externos. Todos los datos deben estar incluidos en el libro de Excel entregado a Roku. -* No agregues hojas adicionales al libro. -* No agregues columnas adicionales al libro. -* No elimines la fila de leyenda y consejos (fila 2). -* No introduzcas los valores “N/A” o “n/a”. Las celdas obligatorias deben contener datos válidos y las opcionales pueden dejarse en blanco. -* Se pueden incluir varias películas, clips y episodios en un mismo libro de Excel. - * Cada fila se considera una experiencia lingüística única de un episodio, película o clip. - * No dejes una fila en blanco entre las entradas de una hoja de cálculo. El sistema dará por terminado el procesamiento en la primera fila vacía. - * No incluyas más de 900 filas en una sola hoja -* Los metadatos de Excel deben guardarse con la extensión .xlsx y exportarse desde Microsoft Excel. Si utilizas otro programa, expórtalos como CSV. - -### Excel: campos de metadatos de películas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Descripción - - Valores aceptados - - Obligatorio -
- provider - - Nombre del estudio, cadena o propietario del contenido - - Ejemplo: Roku Originals - - obligatorio -
- contentType - - Define el tipo de contenido del paquete - - film - - obligatorio -
- language - - Idioma del título, las sinopsis, el video, los subtítulos descriptivos, los subtítulos, los doblajes de audio y las ilustraciones que se enumeran en la fila. El valor debe ajustarse a un [código de idioma](#códigos-de-idioma) compatible. Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). Solo se permite un idioma. - - [Valor de idioma](#códigos-de-idioma) válido - - obligatorio -
- original_spoken_language - - Define el idioma original de producción del título que se entrega. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - - [Valor de idioma](#códigos-de-idioma) válido - - obligatorio -
- country_of_origin - - Define el país principal donde se produjo la película y donde están establecidos los principales creadores, el equipo de filmación y los productores. El valor debe ajustarse a uno de los códigos de país compatibles definidos en la lista de códigos de país de 2 caracteres [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html). - - Código de país válido de 2 caracteres según [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html) - - preferido -
- asset_id - - Identificador único e inalterable de una película. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID del título proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - - Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo - - obligatorio -
- title - - Título de la película en el idioma definido en la columna de idioma. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - - Ejemplo:
Título de película - 		- obligatorio -
- genres - - Clasificación del contenido por género. Roku requiere que cada película se entregue con al menos un género compatible. Consulta la [enumeración](#géneros) de los géneros que admite Roku. - - Consulta la [enumeración](#géneros) más adelante. Pueden enviarse hasta 10 géneros por título - - obligatorio -
- tags - - Las etiquetas son campos de formato libre que pueden utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - - cualquier cadena de menos de 50 caracteres - - MUY recomendado -
- runtime - - Tiempo de duración total del contenido en minutos enteros - - Solo números enteros.
Ejemplo: 90 - 		- obligatorio -
- release_date - - Fecha original en la que el contenido estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - - Conforme al formato ISO 8601: AAAA-MM-DD - - obligatorio -
- adBreaks - - Se utiliza para determinar[los cortes publicitarios del contenido financiado con anuncios](#cortes-publicitarios). Los valores de adBreak deben tener una precisión de milisegundos. Si el video proporcionado incluye fotogramas en negro para comerciales, proporciona el código de tiempo igual al punto medio de dichos fotogramas. Si bien no es necesario para el contenido SVOD, se pueden ingerir datos adBreak con precisión de fotogramas si están disponibles. - - HH:MM:SS.sss - - preferido -
- cuePoints - - Se utiliza para identificar los horarios de inicio y de finalización de los créditos iniciales, los resúmenes de contenido, los créditos finales y el material de detrás de escena. Los valores de los horarios de inicio y finalización de cuePoint deben tener una precisión de milisegundos. lista separada por comas con el siguiente formato: `type`=`startTime`>`endTime` Ejemplo: intro=00:05:10.253>00:07:15:123, recap=00:01:12.456>00:03:12.052 - - Formato:
type=HH:MM:SS.sss
HH:MM:SS.sss
Valores de tipos permitidos:
`ad overlay`
`behind the scenes`
`intro`
`recap`
`end` - 		- opcional -
- ratingSystem - - Para cada película, se proporcionará la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. - - Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. - - obligatorio -
- ratings - - Clasificación por edades o de contenido de la película según una fuente de clasificación. Se facilitará para cada película una clasificación válida de película o TV de parte de la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, incluye una clasificación válida del USA_PR ratingSystem. No existe ningún organismo oficial que asigne clasificaciones para el USA_PR ratingSystem. Toma como referencia las pautas que se enumeran en [http://tvguidelines.org/](http://tvguidelines.org/) para asignar la clasificación adecuada. - - Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. - - obligatorio -
- cast - - Nombres de los miembros del reparto - - Lista de nombres y apellidos separados por comas - - preferido -
- director - - Nombre(s) del director de la película. Por el momento, director es la única función dentro del equipo de filmación que se admite para la ingesta de metadatos de Excel. - - Lista de nombres y apellidos separados por comas - - preferido -
- short_synopsis - - Una sinopsis breve del contenido en el idioma definido en la columna de idioma. Límite de 250 caracteres. - - sinopsis de 250 caracteres - - obligatorio -
- long_synopsis - - Una sinopsis larga del contenido en el idioma definido en la columna de idioma. Límite de 500 caracteres. - - sinopsis de 500 caracteres - - opcional -
- eidr - - ID de EIDR si existe uno - - Cualquier ID de EIDR válido - - opcional -
- tms_id - - ID de Gracenote si existe uno - - Cualquier ID de TMS válido - - opcional -
- closed_captions - - Indica si el título entregado contiene subtítulos descriptivos. Los valores aceptados son Y o N. Este campo es obligatorio para todo el contenido destinado a Roku Channel en EE. UU. - - Y o N - - obligatorio -
- closed_captions_exemption - - Código de exención de la FCC para el requisito de subtítulos descriptivos. Este nodo es necesario si el valor `closedCaptions` = “N” - 1 - El contenido nunca se emitió por televisión en Estados Unidos. - 2 - El contenido solo se emitió por televisión en Estados Unidos sin subtítulos descriptivos. - 3 - El contenido no se emite por televisión en Estados Unidos con subtítulos descriptivos desde el 30 de septiembre de 2012. - 4 - El contenido no consiste en programación de video de larga duración. - 5 - El contenido no pertenece a una categoría de programación en línea que requiera subtítulos descriptivos según la normativa de la FCC (49 C.F.R. § 79.4(b)). - 6 - La FCC o el Congreso de EE. UU. concedieron una exención de los requisitos de subtítulos descriptivos para este contenido. - - - obligatorio en EE. UU. si closed_captions = N -
- video_file_name - - El nombre de archivo del video en el idioma definido en la columna de idioma que se entregó a través de Aspera. Solo se permite 1 video por asset_id. El video_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieVideoFile.mov - 		- obligatorio -
- audio_layout - - [Descriptor de diseño de audio](#audio-descriptivo) para el archivo de video entregado. - - Valores permitidos:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo
- 		- opcional -
- sidecar_audio_file_name - - El nombre del archivo de audio sidecar en el idioma definido en la columna de idioma que se entregó a través de Aspera. El sidecar_audio_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieDubFile.wav - 		- opcional Para la entrega de archivos de audio sidecar con fines de traducción o accesibilidad -
- sidecar_audio_label - - Para uso exclusivo con archivos de descripción de audio. Dejar esta columna en blanco para doblajes de audio. - - Valor permitido:
descripción de audio - 		- obligatorio para archivos de audio descriptivo -
- caption_file_name - - El nombre de archivo de los subtítulos descriptivos en el idioma definido en la columna de idioma que se entregó a través de Aspera. El caption_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieCaptions.srt - 		- obligatorio -
- subtitle_file_name - - El nombre de archivo de los subtítulos completos en el idioma definido en la columna de idioma que se entregó a través de Aspera. El localized_subtitle_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieSubtitle.srt - 		- obligatorio al proporcionar metadatos localizados o activos localizados -
- keyart_file_name - - El nombre de archivo de la imagen de arte clave con texto en el idioma definido en la columna de idioma que se entregó a través de Aspera. El keyart_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieKeyArt.jpg - 		- obligatorio -
- background_file_name - - El nombre de archivo de la imagen de fondo sin texto que se entregó a través de Aspera. El background_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieBGimage.jpg - 		- preferido -
- boxcover_file_name - - El nombre de archivo de la imagen de la portada en el idioma definido en la columna de idioma que se entregó a través de Aspera. boxcover_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieBoxArt.jpg - 		- preferido -
- territory - - Los códigos de país del territorio en el que está disponible el contenido. Se pueden proporcionar varios nodos de países separados por comas, siempre que el vodType y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los países. - - Valores permitidos:
US
CA
GB
MX - 		- preferido -
- vodType - - Tipo de monetización de la película. Se pueden proporcionar varios nodos vodType separados por comas, siempre que el país y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los vodType. - - Ejemplo: avod
svod
avod,svod - 		- preferido -
- license_start_date - - Fecha de inicio de la disponibilidad del contenido para las personas usuarias de Roku Channel. La license_start_date debe ser cronológicamente anterior a la license_end_date. Las license_start_date y license_end_date no deben ser idénticas. - - Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS - - preferido -
- license_end_date - - Fecha de finalización de la disponibilidad del contenido para las personas usuarias de Roku Channel. La license_end_date debe ser cronológicamente posterior a la license_start_date. Las license_start_date y license_end_date no deben ser idénticas. - - Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS - - preferido -
- -*** - -### Excel: campos de metadatos de TV por episodios - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Descripción - - Valores aceptados - - Obligatorio -
- provider - - Nombre del estudio, cadena o propietario del contenido - - Ejemplo:
Roku Originals - 		- obligatorio -
- contentType - - Define el tipo de contenido del paquete - - episodio - - obligatorio -
- Language - - Idioma del título, las sinopsis, el video, los subtítulos descriptivos, los subtítulos, los doblajes de audio y las ilustraciones que se enumeran en la fila. El valor debe ajustarse a un [código de idioma](#códigos-de-idioma) compatible. Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). Solo se permite un idioma. - - Un [valor de idioma](#códigos-de-idioma) válido - - obligatorio -
- original_spoken_language - - Define el idioma original de producción del título que se entrega. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - - Un [valor de idioma](#códigos-de-idioma) válido - - obligatorio -
- country_of_origin - - Define el país principal donde se produjo la película y donde están establecidos los principales creadores, el equipo de filmación y los productores. El valor debe ajustarse a uno de los códigos de país compatibles definidos en la lista de códigos de país de 2 caracteres [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html). - - Un código de país válido de 2 caracteres según [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html) - - preferido -
- series_id - - Identificador único e inalterable de una serie. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID de la serie proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - - Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo - - obligatorio -
- series_title - - Título de la serie en el idioma definido en la columna de idioma. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - - Ejemplo:
Título de la serie - 		- obligatorio -
- series_tmsId - - ID de Gracenote si existe uno - - Cualquier ID de TMS de programa válido - - opcional -
- series_release_date - - Fecha original en que la serie estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - - Conforme al formato ISO 8601: AAAA-MM-DD - - obligatorio -
- series_genres - - Clasificación del contenido por género. Roku requiere que cada película se entregue con al menos un género compatible. Consulta la [enumeración](#géneros) de los géneros que admite Roku. - - Consulta la [enumeración](#géneros) más adelante. Pueden enviarse hasta 10 géneros por título - - obligatorio -
- series_tags - - Las etiquetas son campos de formato libre que pueden utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - - cualquier cadena de menos de 50 caracteres - - MUY recomendado -
- series_cast - - Nombres de los miembros del reparto de la serie - - Lista de nombres y apellidos separados por comas - - preferido -
- series_directors - - Nombre(s) del director de la serie. Por el momento, director es la única función dentro del equipo de filmación que se admite para la ingesta de metadatos de Excel. - - Lista de nombres y apellidos separados por comas - - preferido -
- series_short_synopsis - - Una sinopsis breve de la serie en el idioma definido en la columna de idioma. Límite de 250 caracteres. - - sinopsis de 250 caracteres - - obligatorio -
- series_long_synopsis - - Una sinopsis larga de la serie en el idioma definido en la columna de idioma. Límite de 500 caracteres. - - sinopsis de 500 caracteres - - Opcional -
- season_id - - Identificador único e inalterable de una temporada. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. Límite de 50 caracteres - - Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo - - obligatorio -
- season_number - - Posición numérica de la temporada dentro de una serie. Este valor determinará el orden en que se verán los episodios subyacentes en la plataforma. Los valores de seasonNumber deben entregarse tal y como se emitieron o exhibieron originalmente en cualquier plataforma. Solo se permiten valores numéricos (enteros). - - Solo números enteros - - obligatorio -
- season_tmsIdo - - ID de Gracenote si existe uno - - Cualquier ID de TMS de temporada válido - - opcional -
- asset_id - - Identificador único e inalterable de un episodio. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID del título proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - - Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo - - obligatorio -
- episode_title - - Título del episodio en el idioma definido en la columna de idioma. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - - Ejemplo:
Título de película - 		- obligatorio -
- episode_number - - Posición numérica del episodio dentro de una temporada de una serie. Este valor determinará el orden en que se verán los episodios en la plataforma. Los valores de episodeNumber deben entregarse tal y como se emitieron o exhibieron originalmente en cualquier plataforma. No deben proporcionarse números de producción. Solo se permiten valores numéricos (enteros). - - Solo números enteros - - obligatorio -
- episode_release_date - - Fecha original en la que el contenido estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - - Conforme al formato ISO 8601: AAAA-MM-DD - - obligatorio -
- episode_runtime - - Tiempo de duración total del contenido en minutos enteros - - Solo números enteros.
Ejemplo: 22 - 		- obligatorio -
- episode_adBreaks - - Se utiliza para determinar[los cortes publicitarios del contenido financiado con anuncios](#cortes-publicitarios). Los valores de adBreak deben tener una precisión de milisegundos. Si el video proporcionado incluye fotogramas en negro para comerciales, proporciona el código de tiempo igual al punto medio de dichos fotogramas. Si bien no es necesario para el contenido SVOD, se pueden ingerir datos adBreak con precisión de fotogramas si están disponibles. - - HH:MM:SS.sss - - preferido -
- episode_cuePoints - - Se utiliza para identificar los horarios de inicio y de finalización de los créditos iniciales, los resúmenes de contenido, los créditos finales y el material de detrás de escena. Los valores de los horarios de inicio y finalización de cuePoint deben tener una precisión de milisegundos. lista separada por comas con el siguiente formato: `type`=`startTime`>`endTime` Ejemplo: intro=00:05:10.253>00:07:15:123, recap=00:01:12.456>00:03:12.052 - - Formato:
type=HH:MM:SS.sss
HH:MM:SS.sss
Valores de tipos permitidos:
`ad overlay`
`behind the scenes`
`intro`
`recap`
`end` - 		- opcional -
- ratingSystem - - Para cada película, se proporcionará la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. - - Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. - - Obligatorio -
- episode_ratings - - Clasificación por edades o de contenido para el contenido según una fuente de clasificación. Se facilitará para cada película una clasificación válida de película o TV de parte de la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, incluye una clasificación válida del USA_PR ratingSystem. No existe ningún organismo oficial que asigne clasificaciones para el USA_PR ratingSystem. Toma como referencia las pautas que se enumeran en [http://tvguidelines.org/](http://tvguidelines.org/) para asignar la clasificación adecuada. - - Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. - - obligatorio -
- episode_tags - - Las etiquetas son campos de formato libre que pueden utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - - cualquier cadena de menos de 50 caracteres - - MUY recomendado -
- episode_cast - - Nombres de los miembros del reparto - - Lista de nombres y apellidos separados por comas - - preferido -
- episode_director - - Nombre(s) del director del episodio. Por el momento, director es la única función dentro del equipo de filmación que se admite para la ingesta de metadatos de Excel. - - Lista de nombres y apellidos separados por comas - - preferido -
- episode_short_synopsis - - Una sinopsis breve del episodio en el idioma definido en la columna de idioma. Límite de 250 caracteres. - - sinopsis de 250 caracteres - - obligatorio -
- episode_long_synopsis - - Una sinopsis larga del episodio en el idioma definido en la columna de idioma. Límite de 500 caracteres. - - sinopsis de 500 caracteres - - opcional -
- episode_eidr - - ID de EIDR si existe uno - - Cualquier ID de EIDR de episodio válido - - opcional -
- episode_tmsId - - ID de Gracenote si existe uno - - Cualquier ID de TMS de episodio válido - - opcional -
- closed_captions - - Indica si el título entregado contiene subtítulos descriptivos. Los valores aceptados son Y o N. Este campo es obligatorio para todo el contenido destinado a Roku Channel en EE. UU. - - Y o N - - obligatorio -
- closed_captions_exemption - - Código de exención de la FCC para el requisito de subtítulos descriptivos. Este nodo es necesario si el valor `closedCaptions` = “N” - 1 - El contenido nunca se emitió por televisión en Estados Unidos. - 2 - El contenido solo se emitió por televisión en Estados Unidos sin subtítulos descriptivos. - 3 - El contenido no se emite por televisión en Estados Unidos con subtítulos descriptivos desde el 30 de septiembre de 2012. - 4 - El contenido no consiste en programación de video de larga duración. - 5 - El contenido no pertenece a una categoría de programación en línea que requiera subtítulos descriptivos según la normativa de la FCC (49 C.F.R. § 79.4(b)). - 6 - La FCC o el Congreso de EE. UU. concedieron una exención de los requisitos de subtítulos descriptivos para este contenido. - - - obligatorio en EE. UU. si closed_captions = N -
- video_file_name - - El nombre de archivo del video en el idioma definido en la columna de idioma que se entregó a través de Aspera. Solo se permite 1 video por asset_id. El video_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
episodeVideoFile.mov - 		- obligatorio -
- audio_layout - - [Descriptor de diseño de audio](#audio-descriptivo) para el archivo de video entregado. - - Valores permitidos:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo - 		- opcional -
- sidecar_audio_file_name - - El nombre del archivo de audio sidecar en el idioma definido en la columna de idioma que se entregó a través de Aspera. El sidecar_audio_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieDubFile.wav - 		- opcional Para la entrega de archivos de audio sidecar con fines de traducción o accesibilidad -
- sidecar_audio_label - - Para uso exclusivo con archivos de descripción de audio. Dejar esta columna en blanco para doblajes de audio. - - Valor permitido:
descripción de audio - 		- obligatorio para archivos de audio descriptivo -
- closed_caption_file_name - - El nombre de archivo de los subtítulos descriptivos en el idioma definido en la columna de idioma que se entregó a través de Aspera. El caption_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
episodeCaptions.srt - 		- obligatorio -
- series_keyart_file_name - - El nombre de archivo de la imagen de arte clave con texto en el idioma definido en la columna de idioma que se entregó a través de Aspera. El keyart_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
episodeKeyArt.jpg - 		- obligatorio -
- series_boxcover_file_name - - El nombre de archivo de la imagen de la portada en el idioma definido en la columna de idioma que se entregó a través de Aspera. boxcover_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
episodeBoxArt.jpg - 		- preferido -
- series_background_file_name - - El nombre de archivo de la imagen de fondo sin texto que se entregó a través de Aspera. El background_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
episodeBGimage.jpg - 		- preferido -
- episode_background_file_name - - El nombre de archivo de la imagen de fondo sin texto que se entregó a través de Aspera. El background_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
episodeBGimage.jpg - 		- preferido -
- vodType - - Tipo de monetización de la película. Se pueden proporcionar varios nodos vodType separados por comas, siempre que el país y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los vodType. - - Ejemplo:
avod
svod
avod,svod - 		- preferido -
- territory - - Los códigos de país del territorio en el que está disponible el contenido. Se pueden proporcionar varios nodos de países separados por comas, siempre que el vodType y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los países. - - Valores permitidos:
US
CA
GB
MX - 		- preferido -
- episode_startDate - - Fecha de inicio de la disponibilidad del contenido para las personas usuarias de Roku Channel. La episode_startDate debe ser cronológicamente anterior a la episode_endDate. Las episode_startDate y episode_endDate no deben ser idénticas. - - Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS - - preferido -
- episode_endDate - - Fecha de finalización de la disponibilidad del contenido para las personas usuarias de Roku Channel. La episode_endDate debe ser cronológicamente posterior a la episode_startDate. Las episode_startDate y episode_endDate no deben ser idénticas. - - Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS - - preferido -
- -*** - -### Excel: campos de metadatos de clips de formato corto - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Campo - - Descripción - - Valores aceptados - - Obligatorio -
- provider - - Nombre del estudio, cadena o propietario del contenido - - Ejemplo:
Roku Originals - 		- obligatorio -
- contentType - - Define el tipo de contenido del paquete - - clip - - obligatorio -
- subType - - Define el subType (subtipo) de contenido del paquete. Actualmente Roku no admite conexiones principales y secundarias de forma nativa. El contenido auxiliar o relacionado puede entregarse e identificarse con uno de los siguientes subtipos (subTypes). No existe ningún vínculo entre los activos principales y secundarios subTypes compatibles: -

-
    -
  • trailer
    • -
  • highlight
    • -
  • making_of
    • -
  • behind_scenes
    • -
  • interview
    • -
  • related
    • -
  • recap
    • -
  • extra
    • -
- 		- Valores permitidos:
trailer
highlight
making_of
behind_scenes
interview
related
recap
extra - 		- opcional -
- language - - Idioma del título, las sinopsis, el video, los subtítulos descriptivos, los subtítulos, los doblajes de audio y las ilustraciones que se enumeran en la fila. El valor debe ajustarse a un [código de idioma](#códigos-de-idioma) compatible. Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). Solo se permite un idioma. - - [Valor de idioma](#códigos-de-idioma) válido - - obligatorio -
- original_spoken_language - - Define el idioma original de producción del título que se entrega. Como mínimo, el valor debe ajustarse a un [código de idioma compatible](#códigos-de-idioma). Se recomienda que, al proporcionar el idioma, incluyas también un código de región para brindar información útil, como la distinción entre el español que se habla en México (es-MX) y el que se habla en España (es-ES). - - [Valor de idioma](#códigos-de-idioma) válido - - obligatorio -
- country_of_origin - - Define el país principal donde se produjo la película y donde están establecidos los principales creadores, el equipo de filmación y los productores. El valor debe ajustarse a uno de los códigos de país compatibles definidos en la lista de códigos de país de 2 caracteres [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html). - - Código de país válido de 2 caracteres según [ISO 3166-1 alfa 2](https://www.iso.org/iso-3166-country-codes.html) - - preferido -
- asset_id - - Identificador único e inalterable de una película. La empresa socia debe generar y suministrar los ID para el contenido que se entrega a Roku. El ID en los metadatos de ingesta debe coincidir con el ID del título proporcionado en el documento de avails. Esto será de gran ayuda en el seguimiento del contenido a lo largo de todo el proceso de Roku, desde el envío de Avails hasta su publicación en Roku Channel. Límite de 50 caracteres - - Solo caracteres alfanuméricos, guiones y guiones bajos. 50 caracteres como máximo - - obligatorio -
- title - - Título del clip en el idioma definido en la columna de idioma. Incluye únicamente el nombre del contenido tal y como debe aparecer en la plataforma. No incluyas datos aparte del título entre paréntesis, como un indicador de versión original o nueva, el año de estreno, la temporada o el formato de video, por ejemplo: (Clásica), (1987), (Temporada 1) o (HD) - - Ejemplo:
Título de película - 		- obligatorio -
- genres - - Clasificación del contenido por género. Roku requiere que cada película se entregue con al menos un género compatible. Consulta la [enumeración](#géneros) de los géneros que admite Roku. - - Consulta la [enumeración](#géneros) más adelante. Pueden enviarse hasta 10 géneros por título - - obligatorio -
- tags - - Las etiquetas son campos de formato libre que pueden utilizarse para categorizar el contenido más allá del número limitado de valores de género compatibles. El equipo editorial y el motor de recomendaciones de Roku Channel utilizarán las etiquetas proporcionadas para ayudar a mostrar el contenido en la interfaz de uso de la plataforma de Roku Channel. Cuantas más etiquetas se incluyan en un clip, episodio o película, más formas habrá de seleccionar el contenido y mostrarlo a la persona usuaria final. No hay límite para el número de etiquetas que pueden entregarse con un título y no hay un conjunto definido de etiquetas. Las etiquetas distinguen entre mayúsculas y minúsculas. Por ejemplo, las etiquetas “Rom-Com” y “rom-com” se considerarían dos etiquetas únicas. Asegúrate de que todas las etiquetas se entreguen de forma consistente. - - cualquier cadena de menos de 50 caracteres - - MUY recomendado -
- runtime - - Tiempo de duración total del contenido en minutos enteros - - Solo números enteros.
Ejemplo: 90 - 		- obligatorio -
- release_date - - Fecha original en la que el contenido estuvo disponible por primera vez en cualquier presentación. Debe incluir, como mínimo, el año correcto del estreno - - Conforme al formato ISO 8601: AAAA-MM-DD - - obligatorio -
- adBreaks - - Se utiliza para determinar[los cortes publicitarios del contenido financiado con anuncios](#cortes-publicitarios). Los valores de adBreak deben tener una precisión de milisegundos. Si bien no es necesario para el contenido SVOD, se pueden ingerir datos adBreak con precisión de fotogramas si están disponibles. - - HH:MM:SS.sss - - preferido -
- cuePoints - - - - opcional -
- ratingSystem - - Para cada película, se proporcionará la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. - - Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. - - obligatorio -
- ratings - - Clasificación por edades o de contenido de la película según una fuente de clasificación. Se facilitará para cada película una clasificación válida de película o TV de parte de la autoridad de clasificación (ratingSystem) del territorio en el cual estará disponible el contenido. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, incluye una clasificación válida del USA_PR ratingSystem. No existe ningún organismo oficial que asigne clasificaciones para el USA_PR ratingSystem. Toma como referencia las pautas que se enumeran en [http://tvguidelines.org/](http://tvguidelines.org/) para asignar la clasificación adecuada. - - Consulta [más adelante](#valores-de-clasificación-por-sistema-de-clasificación-y-país) las clasificaciones permitidas por el sistema de clasificación. - - obligatorio -
- cast - - Nombres de los miembros del reparto - - Lista de nombres y apellidos separados por comas - - preferido -
- director - - Nombre(s) del director de la película. Por el momento, director es la única función dentro del equipo de filmación que se admite para la ingesta de metadatos de Excel. - - Lista de nombres y apellidos separados por comas - - preferido -
- short_synopsis - - Una sinopsis breve del contenido en el idioma definido en la columna de idioma. Límite de 250 caracteres. - - sinopsis de 250 caracteres - - obligatorio -
- long_synopsis - - Una sinopsis larga del contenido en el idioma definido en la columna de idioma. Límite de 500 caracteres. - - sinopsis de 500 caracteres - - obligatorio -
- eidr - - ID de EIDR si existe uno - - Cualquier ID de EIDR válido - - opcional -
- tms_id - - ID de Gracenote si existe uno - - Cualquier ID de TMS válido - - opcional -
- closed_captions - - Indica si el título entregado contiene subtítulos descriptivos. Los valores aceptados son Y o N. Este campo es obligatorio para todo el contenido destinado a Roku Channel en EE. UU. - - Y o N - - obligatorio -
- closed_captions_exemption - - Código de exención de la FCC para el requisito de subtítulos descriptivos. Este nodo es necesario si el valor `closedCaptions` = “N” - 1- El contenido nunca se emitió por televisión en Estados Unidos. - 2 - El contenido solo se emitió por televisión en Estados Unidos sin subtítulos descriptivos. - 3 - El contenido no se emite por televisión en Estados Unidos con subtítulos descriptivos desde el 30 de septiembre de 2012. - 4 - El contenido no consiste en programación de video de larga duración. - 5 - El contenido no pertenece a una categoría de programación en línea que requiera subtítulos descriptivos según la normativa de la FCC (49 C.F.R. § 79.4(b)). - 6 - La FCC o el Congreso de EE. UU. concedieron una exención de los requisitos de subtítulos descriptivos para este contenido. - - - obligatorio en EE. UU. si closed_captions = N -
- video_file_name - - El nombre de archivo del video en el idioma definido en la columna de idioma que se entregó a través de Aspera. Solo se permite 1 video por asset_id. El video_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieVideoFile.mov - 		- obligatorio -
- audio_layout - - [Descriptor de diseño de audio](#audio-descriptivo) para el archivo de video entregado. - - Valores permitidos:
stereoOnly
surroundOnly
stereoPlusSurround
surroundPlusStereo - 		- opcional -
- sidecar_audio_file_name - - El nombre del archivo de audio sidecar en el idioma definido en la columna de idioma que se entregó a través de Aspera. El sidecar_audio_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieDubFile.wav - 		- opcional Para la entrega de archivos de audio sidecar con fines de traducción o accesibilidad -
- sidecar_audio_label - - Para uso exclusivo con archivos de descripción de audio. Dejar esta columna en blanco para doblajes de audio. - - Valor permitido:
descripción de audio - 		- obligatorio para archivos de audio descriptivo -
- caption_file_name - - El nombre de archivo de los subtítulos descriptivos en el idioma definido en la columna de idioma que se entregó a través de Aspera. El caption_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieCaptions.srt - 		- obligatorio -
- keyart_file_name - - El nombre de archivo de la imagen de arte clave con texto en el idioma definido en la columna de idioma que se entregó a través de Aspera. El keyart_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieKeyArt.jpg - 		- obligatorio -
- background_file_name - - El nombre de archivo de la imagen de fondo sin texto que se entregó a través de Aspera. El background_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieBGimage.jpg - 		- preferido -
- boxcover_file_name - - El nombre de archivo de la imagen de la portada en el idioma definido en la columna de idioma que se entregó a través de Aspera. boxcover_file_name debe coincidir exactamente con el archivo entregado. Los nombres de archivo distinguen entre mayúsculas y minúsculas y no deben contener espacios en blanco ni caracteres especiales - - Ejemplo:
movieBoxArt.jpg - 		- preferido -
- territory - - Los códigos de país del territorio en el que está disponible el contenido. Se pueden proporcionar varios nodos de países separados por comas, siempre que el vodType y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los países. - - Valores permitidos:
US
CA
GB
MX - 		- preferido -
- vodType - - Tipo de monetización de la película. Se pueden proporcionar varios nodos vodType separados por comas, siempre que el país y las fechas de licensePeriodStart y licensePeriodEnd sean iguales en todos los vodType. - - Ejemplo:
avod
svod
avod,svod - 		- preferido -
- license_start_date - - Fecha de inicio de la disponibilidad del contenido para las personas usuarias de Roku Channel. La license_start_date debe ser cronológicamente anterior a la license_end_date. Las license_start_date y license_end_date no deben ser idénticas. - - Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS - - preferido -
- license_end_date - - Fecha de finalización de la disponibilidad del contenido para las personas usuarias de Roku Channel. La license_end_date debe ser cronológicamente posterior a la license_start_date. Las license_start_date y license_end_date no deben ser idénticas. - - Conforme al formato ISO 8601: AAAA-MM-DDTHH:MM:SS - - preferido -
- parent_type - - Tipo de contenido del contenido principal del cual se deriva o describe el clip - - Valores permitidos: episode movie series - - opcional -
- parent_title - - Título del programa principal si se trata de contenido principal - - Ejemplo:
Título de la película o serie principal - 		- opcional -
- parent_runtime - - Duración del programa principal si este es una película o episodio - - Números enteros - - opcional -
- parent_release_date - - Fecha de estreno de la película, episodio o serie principal - - Conforme al formato ISO 8601: AAAA-MM-DD - - opcional -
- parent_tms_id - - ID de TMS de la película, episodio o serie principal - - Cualquier ID de TMS válido - - opcional -
- parent_series - - Título de la serie del programa principal si este es un episodio - - Ejemplo:
Título de la serie principal - 		- opcional -
- parent_season - - Número de temporada del programa principal si este es un episodio - - Números enteros - - opcional -
- parent_episode - - Número de episodio del programa principal si este es un episodio - - Números enteros - - opcional -
- sport_type - - Nombre del deporte que aparece en el clip o momento destacado - - Nombre del deporte - - obligatorio para clips de deportes -
- sport_league - - Nombre de la liga deportiva que aparece en el clip o momento destacado - - Nombre de la liga deportiva - - obligatorio para clips de deportes -
- sport_teams - - Equipos que aparecen en el clip o momento destacado deportivo. Pueden proporcionarse varios equipos separados por comas. _En este momento, Roku solo admite metadatos de participantes basados en equipos. Los deportes individuales serán compatibles en el futuro._ - - Lista separada por comas. Ejemplo:
Chicago Cubs,St. Louis Cardinals - 		- obligatorio para clips de deportes -
- -
- -*** - -## Valores que admite Roku - -### Funciones del equipo de filmación - -* Actor -* Anchor -* Host -* Narrator -* Voice -* Director -* Producer -* Screenwriter - -### Géneros - -| | | | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 3x3 basketball
action
action sports
adventure
aerobics
agriculture
animals
animated
anime
anthology
archery
arm wrestling
art
artistic gymnastics
artistic swimming
arts/crafts
athletics
auction
auto
auto racing
aviation
awards
badminton
ballet
baseball
basketball
beach soccer
beach volleyball
biathlon
bicycle
bicycle racing
billiards
biography
blackjack
bmx racing
boat
boat racing
bobsled
bodybuilding
bowling
boxing
bullfighting
bus./financial
canoe
canoe/kayak
card games
ceremony
cheerleading
children
children-music
children-special
children-talk
collectibles
comedy
comedy drama
community
computers
consumer
cooking
cricket
crime
crime drama
curling
cycling
dance
dark comedy
darts
debate
diving
docudrama
documentary
dog racing
dog show
dog sled
drag racing
drama | educational
entertainment
environment
equestrian
erotic
event
exercise
faith
fantasy
fashion
fencing
field hockey
figure skating
fishing
food
football
fundraiser
gaelic football
game show
gaming
gay/lesbian
golf
gymnastics
handball
health
historical drama
history
hockey
holiday
holiday music
holiday music special
holiday special
holiday-children
holiday-children special
home improvement
horror
horse
house/garden
how-to
hunting
hurling
hydroplane racing
indoor soccer
interview
intl soccer
judo
karate
kayaking
lacrosse
law
live
luge
martial arts
medical
military
miniseries
mixed martial arts
modern pentathlon
motorcycle
motorcycle racing
motorsports
mountain biking
music
music special
music talk
musical
musical comedy
mystery
nature
news
newsmagazine
olympics
opera
outdoors
parade
paranormal | parenting
performing arts
playoff sports
poker
politics
polo
pool
pro wrestling
public affairs
racquet
reality
religious
rhythmic gymnastics
ringuette
road cycling
rodeo
roller derby
romance
romantic comedy
rowing
rugby
running
sailing
science
science fiction
self improvement
shooting
shopping
sitcom
skateboarding
skating
skeleton
skiing
snooker
snowboarding
snowmobile
soap
soap special
soap talk
soccer
softball
special
speed skating
sport climbing
sports
sports talk
squash
standup
sumo wrestling
surfing
suspense
swimming
table tennis
taekwondo
talk
technology
tennis
theater
thriller
track cycling
track/field
trampoline
travel
triathlon
variety
volleyball
war
water polo
water skiing
watersports
weather
weightlifting
western
wrestling
yacht racing | - -### Valores de clasificación por sistema de clasificación y país - -Se facilitará para cada película, episodio o video de formato corto una clasificación válida de cine o TV de parte de la autoridad de clasificación (fuente de clasificación) del territorio en el cual estará disponible el título. Si el título no ha sido clasificado por la autoridad oficial de clasificación de ese territorio, se puede proporcionar una clasificación NR (sin clasificar). Sin embargo, ten en cuenta que Roku prefiere una clasificación más específica para todo el contenido. Los títulos con calificación NR (sin clasificar) estarán sujetos a verificación manual, lo que puede retrasar el proceso de selección y publicación en Roku Channel. La visibilidad en Roku Channel también puede verse afectada en el caso de títulos con clasificación NR (sin clasificar) y se prohibirá su inclusión en la experiencia para toda la familia. En lugar de la clasificación NR (sin clasificar), el título debe autoclasificarse con el sistema de clasificación USA_PR. Las pautas relativas a las calificaciones USA_PR pueden consultarse [aquí](http://tvguidelines.org) - -| **Autoridades de clasificación y territorio** | **País** | **ratingSystem** | **Valor de clasificación** | -| ------------------------------------------------------------------- | -------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| British Board of Film Classification
Reino Unido | GB | BBFC | U
PG
12A
12-A
12
15
18
NR
R18
R-1 | -| Canadian Home Video Rating System
Canadá | CA | CHVRS | G
PG
14A
14-A
18A
18-A
NR
RE | -| Motion Picture Associate of America
Estados Unidos | US | MPAA | G
PG
PG13
PG-13
R
NC-17
NC17
NR | -| Canadian Parental Rating
Canadá | CA | CPR | 14+
18+
C
C8
C-8
G
NR
PG
E | -| Dirección General de Radio, Televisión y Cinematografía
México | MX | RTC | AA
A
B
B-15
B15
C
DD
D
NR | -| USA Parental Rating (V-Chip)
Estados Unidos | US | USA_PR | TV-Y
TVY
TV-Y7
TVY7
TV-G
TVG
TV-PG
TVPG
TV-14
TV14
TV-MA
TVMA
NR | - -### Códigos de idioma - -La siguiente lista contiene todos los códigos de idioma que Roku admite actualmente para la ingesta de contenido. Esta lista es una versión simplificada de la especificación [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646). - -| Código de idioma | Language | Código de idioma | Language | -| ---------------- | ------------------------- | ---------------- | ------------------------------ | -| af | Afrikáans | km | Jemer | -| sq | Albanés | rw | Kinyarwanda | -| am | Amhárico | ko | Coreano | -| ar | Árabe | ko-kr | Coreano (Corea) | -| ar-dz | Árabe (Algeria) | ku | Kurdo | -| ar-bh | Árabe (Baréin) | ky | Kirguís | -| ar-eg | Árabe (Egipto) | lo | Lao | -| ar-iq | Árabe (Irak) | la | Latín | -| ar-jo | Árabe (Jordania) | lv | Letón | -| ar-kw | Árabe (Kuwait) | lt | Lituano | -| ar-lb | Árabe (Líbano) | mk | Macedonio | -| ar-ly | Árabe (Libia) | mg | Malgache | -| ar-ma | Árabe (Marruecos) | ms | Malayo | -| ar-om | Árabe (Omán) | ms-my | Malayo (Malasia) | -| ar-qa | Árabe (Catar) | ml | Malabar | -| ar-sa | Árabe (Arabia Saudita) | mt | Maltés | -| ar-sy | Árabe (Siria) | mr | Maratí | -| ar-tn | Árabe (Túnez) | mn | Mongol | -| ar-ae | Árabe (E.A.U.) | nd | Ndebele | -| ar-ye | Árabe (Yemen) | ne | Nepalí | -| hy | Armenio | no | Noruego | -| as | Asamés | no-no | Noruego (Noruega) | -| az | Azerí | or | Oriya | -| eu | Vasco | om | Oromo | -| be | Bielorruso | ps | Pastún | -| bn | Bengalí | fa | Persa (Farsi) | -| bh | Bihari | pl | Polaco | -| bs | Bosnio | pl-pl | Polaco (Polonia) | -| bg | Búlgaro | pt | Portugués | -| bg-bg | Búlgaro (Bulgaria) | pt-br | Portugués (Brasil) | -| my | Birmano | pt-pt | Portugués (Portugal) | -| ca | Catalán | pa | Panyabí | -| zh | Chino | qu | Quechua | -| zh-hk | Chino (Hong Kong) | rm | Retorrománico | -| zh-cn | Chino (RPC) | ro | Rumano | -| zh-sg | Chino (Singapur) | ro-md | Rumano (Moldavia) | -| zh-tw | Chino (Taiwán) | ro-ro | Rumano (Rumania) | -| zh-hans | Chino (simplificado) | rn | Kirundi | -| zh-hant | Chino (tradicional) | ru | Ruso | -| hr | Croata | ru-md | Ruso (Moldavia) | -| hr-hr | Croata (Croacia) | ru-ru | Ruso (Rusia) | -| cs | Checo | se | Sami | -| cs-cz | Checo (República Checa) | sa | Sánscrito | -| da | Danés | gd | Escocés (gaélico) | -| da-dk | Danés (Dinamarca) | sr | Serbio | -| dv | Divehi | sn | Shona | -| nl | Neerlandés | ii | Yi de Sichuan | -| nl-be | Neerlandés (Bélgica) | sd | Sindi | -| nl-nl | Neerlandés (Países Bajos) | si | Singalés | -| dz | Dzongkha | sk | Eslovaco | -| en | Inglés | sl | Esloveno | -| en-au | Inglés (Australia) | sl-si | Esloveno (Eslovenia) | -| en-bz | Inglés (Belice) | so | Somalí | -| en-ca | Inglés (Canadá) | st | Sesoto | -| en-ie | Inglés (Irlanda) | es | Español | -| en-jm | Inglés (Jamaica) | es-ar | Español (Argentina) | -| en-nz | Inglés (Nueva Zelanda) | es-bo | Español (Bolivia) | -| en-za | Inglés (Sudáfrica) | es-cl | Español (Chile) | -| en-tt | Inglés (Trinidad) | es-co | Español (Colombia) | -| en-gb | Inglés (Reino Unido) | es-cr | Español (Costa Rica) | -| en-us | Inglés (Estados Unidos) | es-do | Español (República Dominicana) | -| et | Estonio | es-ec | Español (Ecuador) | -| fo | Feroés | es-sv | Español (El Salvador) | -| fi | Finlandés | es-gt | Español (Guatemala) | -| fr | Francés | es-hn | Español (Honduras) | -| fr-be | Francés (Bélgica) | es-mx | Español (México) | -| fr-ca | Francés (Canadá) | es-ni | Español (Nicaragua) | -| fr-lu | Francés (Luxemburgo) | es-pa | Español (Panamá) | -| fr-ch | Francés (Suiza) | es-py | Español (Paraguay) | -| fy | Frisón | es-pe | Español (Perú) | -| ff | Fulfulfe (Fula) | es-pr | Español (Puerto Rico) | -| gl | Gallego | es-es | Español (España) | -| ka | Georgiano | es-uy | Español (Uruguay) | -| de | Alemán | es-ve | Español (Venezuela) | -| de-at | Alemán (Austria) | sw | Suajili | -| de-de | Alemán (Alemania) | sv | Sueco | -| de-li | Alemán (Liechtenstein) | sv-fi | Sueco (Finlandia) | -| de-lu | Alemán (Luxemburgo) | sv-se | Sueco (Suecia) | -| de-ch | Alemán (Suiza) | tl | Tagalo | -| el | Griego | ty | Tahitiano | -| el-gr | Griego (Grecia) | tg | Tayiko | -| gn | Guaraní | ta | Tamil | -| gu | Guyarati | tt | Tártaro | -| ht | Haitiano (criollo) | te | Télugu | -| ha | Hausa | th | Tailandés | -| he | Hebreo | th-th | Tailandés (Tailandia) | -| hi | Hindi | bo | Tibetano | -| hu | Húngaro | ti | Tigriña | -| hu-hu | Húngaro (Hungría) | ts | Tsonga | -| is | Islandés | tn | Setsuana | -| ig | Igbo | tr | Turco | -| id | Indonesio | tr-tr | Turco (Turquía) | -| iu | Inuit | tk | Turcomano | -| ik | Iñupiaq | uk | Ucraniano | -| ga | Irlandés | ur | Urdu | -| it | Italiano | uz | Uzbeko | -| it-it | Italiano (Italia) | ve | Venda | -| it-ch | Italiano (Suiza) | vi | Vietnamita | -| ja | Japonés | vi-vn | Vietnamita (Vietnam) | -| ja-jp | Japonés (Japón) | cy | Galés | -| kn | Canarés | xh | Xhosa | -| kr | Kanuri | yi | Yidis | -| ks | Cachemiro | yo | Yoruba | -| kk | Kazajo | zu | Zulú | - -## Glosario - -| Término | Definición | -| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Paquete / Paquete completo / Paquete de activos / Paquete de activos completo | Entrega completa de una película, episodio o video de formato corto. Un paquete está compuesto por: video, subtítulos descriptivos (si están disponibles), ilustraciones y metadatos. Cuando se entregan títulos en varios idiomas, el paquete también puede incluir: doblaje de audio, subtítulos, ilustraciones localizadas y metadatos localizados. | -| MDU | [Actualización de metadatos](#actualización-de-metadatos-mdu-y-reemplazos-de-archivos) | - -*** - -## Recursos - -| Recurso | Enlace | -| ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Plantilla de metadatos de Excel para películas | [https://go.roku.com/film-excel-template](https://go.roku.com/film-excel-template) | -| Plantilla de metadatos de Excel para TV | [https://go.roku.com/tv-excel-template](https://go.roku.com/tv-excel-template) | -| Plantilla de metadatos de Excel para clips | [https://go.roku.com/clip-excel-template](https://go.roku.com/clip-excel-template) | -| Esquema XML para películas | [https://go.roku.com/film-xml-schema](https://go.roku.com/film-xml-schema) | -| Esquema XML para TV | [https://go.roku.com/tv-xml-schema](https://go.roku.com/tv-xml-schema) | -| Esquema XML para clips | [https://go.roku.com/clip-xml-schema](https://go.roku.com/clip-xml-schema) | -| XML anotado para películas | [https://go.roku.com/film-xml-example](https://go.roku.com/film-xml-example) | -| XML anotado para TV | [https://go.roku.com/tv-xml-example](https://go.roku.com/tv-xml-example) | -| XML anotado para clips | [https://go.roku.com/clip-xml-example](https://go.roku.com/clip-xml-example) | -| Ejemplo de XML ADI para películas | [https://go.roku.com/film-adi-xml-example](https://go.roku.com/film-adi-xml-example) | -| Ejemplo de XML ADI para TV | [https://go.roku.com/tv-adi-xml-example](https://go.roku.com/tv-adi-xml-example) | -| Ejemplo de XML ADI para clips | [https://go.roku.com/clip-adi-xml-example](https://go.roku.com/clip-adi-xml-example) | -| Todas las plantillas, ejemplos y esquemas de metadatos | [https://go.roku.com/metadata-docs](https://go.roku.com/metadata-docs) | -| Prácticas recomendadas: etiquetas y metadatos del contenido | [https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md](https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md) | -| Envío de hojas de referencia musical | [https://go.roku.com/music-cue-sheet-submission](https://go.roku.com/music-cue-sheet-submission) | -| Aspera Client | [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client&release=All&platform=All&function=all](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software\&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all) | -| Sistema de clasificaciones de la MPAA de EE. UU. | [https://www.filmratings.com/](https://www.filmratings.com/) | -| Sistema de clasificaciones de TV de EE. UU. | [http://tvguidelines.org/](http://tvguidelines.org/) | -| Sistema de clasificaciones de la BBFC del Reino Unido | [https://bbfc.co.uk/](https://bbfc.co.uk/) | -| Sistema de clasificaciones de cine canadiense | [https://www.mpa-canada.org/film-ratings/](https://www.mpa-canada.org/film-ratings/) | -| Sistema de clasificaciones de TV canadiense | [https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/](https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/) | - -## Registro de cambios - -**v2.3 - 03-02-2025** - -* Se actualizaron todas las referencias a The Roku Channel a Roku Channel. -* Se agregó la compatibilidad con MovieLabs y EMA. -* Se agregó una descripción de la personalización de ilustraciones de Gracenote utilizada por Roku Channel. -* Se agregaron las expectativas posteriores a la incorporación. -* Se agregó la política de contenido financiado con anuncios. -* Se agregaron la definición y algunos ejemplos de llamadas a la acción. -* Se agregó un enlace para enviar las hojas de referencia musical. -* Se actualizaron los requisitos de video para requerir video con muy poco texto. -* Se actualizaron los archivos de subtítulos descriptivos y subtítulos sidecar preferidos de Roku. -* Se identificaron qué subtítulos descriptivos y subtítulos sidecar admiten datos de posición. -* Se actualizaron los requisitos y las preferencias de clasificación. Se desaconsejó la clasificación NR y se eliminó la compatibilidad con la clasificación UR. -* Se actualizó la resolución mínima de imagen en 2:3 para alinear las dimensiones a exactamente 2:3. -* Se actualizaron los ejemplos de imágenes en la plataforma. -* Se agregaron algunas pautas sobre el suministro de imágenes. -* Se indicó que las imágenes por episodios deben ser únicas para cada episodio. -* Se indicó que los subtítulos y subtítulos descriptivos sidecar no deben ser archivos vacíos. -* Se agregó un enlace a la página “creado para niños” de Roku. -* Se corrigió un error tipográfico en la muestra de Xpath para el tipo de contenido de “episodio” a “tv”. -* Se indicó que los documentos de Excel no deben contener enlaces a datos externos. -* Se aclaró que las fechas de inicio deben ser cronológicamente anteriores a las de finalización. -* Se aclaró que las fechas de inicio y fin no pueden ser idénticas. -* Se actualizaron las plantillas de ingesta para agregar consejos adicionales. -* Se agregaron nodos de metadatos de deportes a las especificaciones y plantillas de clips. -* Se eliminó el enlace a la plantilla de actualización de archivos. -* Se actualizaron los documentos XSD para reflejar los cambios anteriores. - -**v2.2 - 18-05-2023** - -* Se eliminó la compatibilidad con las MDU heredadas. -* Se eliminaron los requisitos de long_synopsis. -* Se actualizó el lenguaje para los reemplazos de archivos y las MDU automatizadas -* Se agregó una política de retención de 30 días para los archivos en la ubicación de entrega. -* Se agregó una lista de caracteres permitidos y prohibidos para los nombres de archivo. -* Se agregó un enlace a la página Prácticas recomendadas: etiquetas de contenido y metadatos. -* Se agregó end_time como requisito para los cuePoint de los créditos -* Se agregó la compatibilidad con cuePoints de superposición de anuncios. -* Se agrego lenguaje sobre la prohibición de entrega de segmentos de videos fragmentados. -* Se agregó lenguaje sobre la posibilidad de entregar miniaturas por episodios en formato letterboxed o pillarboxed. -* Se agregó un enlace a un archivo .zip con todos los documentos de muestra. -* Se corrigieron errores tipográficos. - -**v2.1 - 28-10-2022** - -* Se actualizó la documentación de MDU, se agregó la compatibilidad con las MDU automatizadas y se cambió el nombre del método heredado. -* Se separaron las descripciones de campos de metadatos de Excel de las descripciones de campos de metadatos de XML. -* Se modificó el formato de las descripciones de campos de metadatos de XML para mejorar su legibilidad. -* Se aclaró el etiquetado de los canales de audio. -* Se aclararon los requisitos de audio sidecar. -* Se aclararon los requisitos de los subtítulos sidecar. -* Se actualizó la lista de códigos de idioma compatibles. -* Se agregó la compatibilidad con la ingesta de cuePoints de créditos. -* Se agregaron las clasificaciones y el sistema de clasificación de contenido de México (RTC) - -**v2.0 - 25-04-2022** - -* Se identificó al formato .srt como la entrada preferida de subtítulos descriptivos sidecar. - -* Se aclararon los requisitos de número de episodios. - -* Se reorganizó el documento para que finalice con los metadatos. - -* Se modificó el formato de las definiciones de los nodos de metadatos para mostrar los nombres de las columnas Excel y xpath. - -* Se reforzaron y aclararon los requisitos de video. - -* Se agregó la cantidad aceptable de video en negro al principio y al final. - -* Se actualizaron los requisitos de las películas para permitir release_date en lugar de theatrical_release_date. - -* Se agregó la compatibilidad con información de disponibilidad diferente entre licenseTypes y territorios. - -* Se agregó la compatibilidad con la entrega en varios idiomas, entre los que se incluyen: - * Language - * Idioma oral original - * País de origen - * Metadatos localizados - * Audio sidecar - * Subtítulos sidecar - * Ilustraciones localizadas - -* Se agregó una lista de archivos de subtítulos compatibles. - -* Se agregó una lista de archivos de audio sidecar compatibles. - -* Se agregó una lista de códigos de idioma compatibles. - -* Se agregó la compatibilidad con la entrega de audio descriptivo. - -* Se aclararon los requisitos del código de idioma para los metadatos y activos localizados. - -* Se actualizaron las muestras de XML para incluir la compatibilidad con varios idiomas. - -* Se actualizó el XSD para validar el XML en varios idiomas. - -* Se actualizaron las muestras de Excel para incluir la compatibilidad con varios idiomas. - -* Se agregó un glosario de terminología. - -* Se agregó un enlace externo a la página de la FTC que describe el cumplimiento de la ley COPPA. - -* Se actualizó el nombre de los descriptores de diseño de audio a consejos de diseño de audio para evitar confusiones con el audio descriptivo. - -* Se actualizó la política de adBreak según la última política de anuncios de Roku. diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/_order.yaml deleted file mode 100644 index 2b30d862..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/_order.yaml +++ /dev/null @@ -1,5 +0,0 @@ -- movielabs -- metadata-updates-mdu-and-file-replacements -- xml-metadata -- excel-metadata -- enumerations diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/_order.yaml deleted file mode 100644 index 153c2531..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/_order.yaml +++ /dev/null @@ -1,4 +0,0 @@ -- crew-roles -- genres -- rating-values-by-rating-system-and-country -- language-codes diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/crew-roles.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/crew-roles.md deleted file mode 100644 index a88c16b8..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/crew-roles.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Crew roles -excerpt: Fixed list of supported crew role values. -deprecated: false -hidden: true -metadata: - robots: index ---- -Roku supports the following crew member role values, referenced by the `role` field wherever crew metadata is delivered (see the Film/TV/Clip XML and Excel metadata references). **Roles are case-sensitive** — deliver exactly as listed below. - -> **Cross-format note:** Director is currently the **only** crew role supported for **Excel** metadata ingest. The full list below applies to **XML** delivery. - -| Crew Role | -| ------------ | -| Actor | -| Anchor | -| Host | -| Narrator | -| Voice | -| Director | -| Producer | -| Screenwriter | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/genres.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/genres.md deleted file mode 100644 index 2d2232b7..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/genres.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Genres -excerpt: Fixed list of supported genre values. -deprecated: false -hidden: true -metadata: - robots: index ---- -Roku supports the following genre values, referenced by the `genre`/`genres` field wherever genre metadata is delivered (see the Film/TV/Clip XML and Excel metadata references). Each title **must** be delivered with **at least one** supported genre, and **no more than 10** genres per title. - -| | | | | -| ------------------- | ------------------------ | ------------------- | ---------------- | -| 3x3 basketball | consumer | how-to | rowing | -| action | cooking | hunting | rugby | -| action sports | cricket | hurling | running | -| adventure | crime | hydroplane racing | sailing | -| aerobics | crime drama | indoor soccer | science | -| agriculture | curling | interview | science fiction | -| animals | cycling | intl soccer | self improvement | -| animated | dance | judo | shooting | -| anime | dark comedy | karate | shopping | -| anthology | darts | kayaking | sitcom | -| archery | debate | lacrosse | skateboarding | -| arm wrestling | diving | law | skating | -| art | docudrama | live | skeleton | -| artistic gymnastics | documentary | luge | skiing | -| artistic swimming | dog racing | martial arts | snooker | -| arts/crafts | dog show | medical | snowboarding | -| athletics | dog sled | military | snowmobile | -| auction | drag racing | miniseries | soap | -| auto | drama | mixed martial arts | soap special | -| auto racing | educational | modern pentathlon | soap talk | -| aviation | entertainment | motorcycle | soccer | -| awards | environment | motorcycle racing | softball | -| badminton | equestrian | motorsports | special | -| ballet | erotic | mountain biking | speed skating | -| baseball | event | music | sport climbing | -| basketball | exercise | music special | sports | -| beach soccer | faith | music talk | sports talk | -| beach volleyball | fantasy | musical | squash | -| biathlon | fashion | musical comedy | standup | -| bicycle | fencing | mystery | sumo wrestling | -| bicycle racing | field hockey | nature | surfing | -| billiards | figure skating | news | suspense | -| biography | fishing | newsmagazine | swimming | -| blackjack | food | olympics | table tennis | -| bmx racing | football | opera | taekwondo | -| boat | fundraiser | outdoors | talk | -| boat racing | gaelic football | parade | technology | -| bobsled | game show | paranormal | tennis | -| bodybuilding | gaming | parenting | theater | -| bowling | gay/lesbian | performing arts | thriller | -| boxing | golf | playoff sports | track cycling | -| bullfighting | gymnastics | poker | track/field | -| bus./financial | handball | politics | trampoline | -| canoe | health | polo | travel | -| canoe/kayak | historical drama | pool | triathlon | -| card games | history | pro wrestling | variety | -| ceremony | hockey | public affairs | volleyball | -| cheerleading | holiday | racquet | war | -| children | holiday music | reality | water polo | -| children-music | holiday music special | religious | water skiing | -| children-special | holiday special | rhythmic gymnastics | watersports | -| children-talk | holiday-children | ringuette | weather | -| collectibles | holiday-children special | road cycling | weightlifting | -| comedy | home improvement | rodeo | western | -| comedy drama | horror | roller derby | wrestling | -| community | horse | romance | yacht racing | -| computers | house/garden | romantic comedy | | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/index.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/index.md deleted file mode 100644 index ad37238c..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/index.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Enumerations -excerpt: >- - Landing page for supported-value lists: crew roles, genres, ratings, - languages. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This section is the **single source of truth** for enumerated (fixed-list) values referenced throughout the Film, TV, and Clip metadata specifications — both XML and Excel. Rather than repeating these lists on every page that uses them, each metadata field links back here. - -| Page | Covers | Referenced From | -| --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | -| [**Crew Roles**](https://developer.roku.com/dev/update/docs/crew-roles) | The fixed set of supported crew member role values | `role` field in the Film/TV/Clip XML and Excel references | -| [**Genres**](https://developer.roku.com/dev/update/docs/genres) | The fixed set of supported genre values | `genre`/`genres` field in the Film/TV/Clip XML and Excel references | -| [**Rating Values by Rating System and Country**](https://developer.roku.com/dev/update/docs/rating-values-by-rating-system-and-country) | Supported rating authorities, their territory/country, and valid rating values per authority | `rating`/`ratings`/`rating_system` field in the Film/TV/Clip XML and Excel references | -| [**Language Codes**](https://developer.roku.com/dev/update/docs/language-codes) | The supported set of language codes (with optional region variants) | `language`, `original_spoken_language`, `locale`, and related fields across all metadata references | - -Each sub-page is a flat reference list — there are no requirement levels or delivery rules on these pages themselves; those live on the field-level pages that link here. \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/language-codes.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/language-codes.md deleted file mode 100644 index c7f6b771..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/language-codes.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -title: Language codes -excerpt: Full list of supported language codes and regional variants. -deprecated: false -hidden: true -metadata: - robots: index ---- -The list below is the full set of language codes Roku currently supports for content ingest. This is a simplified version of the [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646) specification. - -Where a region-specific variant exists (e.g., `es-mx` for Spanish (Mexico) vs. `es-es` for Spanish (Spain)), including the region code is a best practice wherever the field description recommends it. See the individual field references in the Film/TV/Clip XML and Excel metadata pages. - -| Language Code | Language | Language Code | Language | -| ------------- | ------------------------ | ------------- | ------------------------------ | -| af | Afrikaans | km | Khmer | -| sq | Albanian | rw | Kinyarwanda | -| am | Amharic | ko | Korean | -| ar | Arabic | ko-kr | Korean (Korea) | -| ar-dz | Arabic (Algeria) | ku | Kurdish | -| ar-bh | Arabic (Bahrain) | ky | Kyrgyz | -| ar-eg | Arabic (Egypt) | lo | Lao | -| ar-iq | Arabic (Iraq) | la | Latin | -| ar-jo | Arabic (Jordan) | lv | Latvian | -| ar-kw | Arabic (Kuwait) | lt | Lithuanian | -| ar-lb | Arabic (Lebanon) | mk | Macedonian | -| ar-ly | Arabic (Libya) | mg | Malagasy | -| ar-ma | Arabic (Morocco) | ms | Malay | -| ar-om | Arabic (Oman) | ms-my | Malay (Malaysia) | -| ar-qa | Arabic (Qatar) | ml | Malayalam | -| ar-sa | Arabic (Saudi Arabia) | mt | Maltese | -| ar-sy | Arabic (Syria) | mr | Marathi | -| ar-tn | Arabic (Tunisia) | mn | Mongolian | -| ar-ae | Arabic (U.A.E.) | nd | Ndebele | -| ar-ye | Arabic (Yemen) | ne | Nepali | -| hy | Armenian | no | Norwegian | -| as | Assamese | no-no | Norwegian (Norway) | -| az | Azerbaijani | or | Oriya | -| eu | Basque | om | Oromo | -| be | Belarusian | ps | Pashto | -| bn | Bengali | fa | Persian (Farsi) | -| bh | Bihari | pl | Polish | -| bs | Bosnian | pl-pl | Polish (Poland) | -| bg | Bulgarian | pt | Portuguese | -| bg-bg | Bulgarian (Bulgaria) | pt-br | Portuguese (Brazil) | -| my | Burmese | pt-pt | Portuguese (Portugal) | -| ca | Catalan | pa | Punjabi | -| zh | Chinese | qu | Quechua | -| zh-hk | Chinese (Hong Kong) | rm | Rhaeto-Romanic | -| zh-cn | Chinese (PRC) | ro | Romanian | -| zh-sg | Chinese (Singapore) | ro-md | Romanian (Republic of Moldova) | -| zh-tw | Chinese (Taiwan) | ro-ro | Romanian (Romania) | -| zh-hans | Chinese (Simplified) | rn | Rundi | -| zh-hant | Chinese (Traditional) | ru | Russian | -| hr | Croatian | ru-md | Russian (Republic of Moldova) | -| hr-hr | Croatian (Croatia) | ru-ru | Russian (Russia) | -| cs | Czech | se | Sami | -| cs-cz | Czech (Czech Republic) | sa | Sanskrit | -| da | Danish | gd | Scottish (Gaelic) | -| da-dk | Danish (Denmark) | sr | Serbian | -| dv | Divehi | sn | Shona | -| nl | Dutch | ii | Sichuan Yi | -| nl-be | Dutch (Belgium) | sd | Sindhi | -| nl-nl | Dutch (Netherlands) | si | Sinhalese | -| dz | Dzongkha | sk | Slovak | -| en | English | sl | Slovenian | -| en-au | English (Australia) | sl-si | Slovenian (Slovenia) | -| en-bz | English (Belize) | so | Somali | -| en-ca | English (Canada) | st | Sotho | -| en-ie | English (Ireland) | es | Spanish | -| en-jm | English (Jamaica) | es-ar | Spanish (Argentina) | -| en-nz | English (New Zealand) | es-bo | Spanish (Bolivia) | -| en-za | English (South Africa) | es-cl | Spanish (Chile) | -| en-tt | English (Trinidad) | es-co | Spanish (Colombia) | -| en-gb | English (United Kingdom) | es-cr | Spanish (Costa Rica) | -| en-us | English (United States) | es-do | Spanish (Dominican Republic) | -| et | Estonian | es-ec | Spanish (Ecuador) | -| fo | Faeroese | es-sv | Spanish (El Salvador) | -| fi | Finnish | es-gt | Spanish (Guatemala) | -| fr | French | es-hn | Spanish (Honduras) | -| fr-be | French (Belgium) | es-mx | Spanish (Mexico) | -| fr-ca | French (Canada) | es-ni | Spanish (Nicaragua) | -| fr-lu | French (Luxembourg) | es-pa | Spanish (Panama) | -| fr-ch | French (Switzerland) | es-py | Spanish (Paraguay) | -| fy | Frisian | es-pe | Spanish (Peru) | -| ff | Fulfulde (Fulah) | es-pr | Spanish (Puerto Rico) | -| gl | Galician | es-es | Spanish (Spain) | -| ka | Georgian | es-uy | Spanish (Uruguay) | -| de | German | es-ve | Spanish (Venezuela) | -| de-at | German (Austria) | sw | Swahili | -| de-de | German (Germany) | sv | Swedish | -| de-li | German (Liechtenstein) | sv-fi | Swedish (Finland) | -| de-lu | German (Luxembourg) | sv-se | Swedish (Sweden) | -| de-ch | German (Switzerland) | tl | Tagalog | -| el | Greek | ty | Tahitian | -| el-gr | Greek (Greece) | tg | Tajik | -| gn | Guarani | ta | Tamil | -| gu | Gujarati | tt | Tatar | -| ht | Haitian (Creole) | te | Telugu | -| ha | Hausa | th | Thai | -| he | Hebrew | th-th | Thai (Thailand) | -| hi | Hindi | bo | Tibetan | -| hu | Hungarian | ti | Tigrigna | -| hu-hu | Hungarian (Hungary) | ts | Tsonga | -| is | Icelandic | tn | Tswana | -| ig | Igbo | tr | Turkish | -| id | Indonesian | tr-tr | Turkish (Turkey) | -| iu | Inuktitut | tk | Turkmen | -| ik | Inupiaq | uk | Ukrainian | -| ga | Irish | ur | Urdu | -| it | Italian | uz | Uzbek | -| it-it | Italian (Italy) | ve | Venda | -| it-ch | Italian (Switzerland) | vi | Vietnamese | -| ja | Japanese | vi-vn | Vietnamese (Vietnam) | -| ja-jp | Japanese (Japan) | cy | Welsh | -| kn | Kannada | xh | Xhosa | -| kr | Kanuri | yi | Yiddish | -| ks | Kashmiri | yo | Yoruba | -| kk | Kazakh | zu | Zulu | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/rating-values-by-rating-system-and-country.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/rating-values-by-rating-system-and-country.md deleted file mode 100644 index f7422cbd..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/enumerations/rating-values-by-rating-system-and-country.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Rating values by rating system and country -excerpt: Supported rating authorities and values by territory. -deprecated: false -hidden: true -metadata: - robots: index ---- -A valid film or TV rating from the rating authority (`ratingSystem`) of the territory where a title will be available **must** be provided for each movie, episode, or shortForm video. - -## If the Title Has Not Been Officially Rated - -If a title has not been rated by that territory's official rating authority, a rating of **NR (Not Rated)** may be provided — however: - -> **⚠️ Roku strongly prefers an actual rating on all content.** Titles rated **NR** are subject to **manual verification**, which can delay **or prevent** selection and publishing to Roku Channel. Discoverability may also be impacted, and **placement within the Kids & Family experience will be prohibited** for NR titles. - -**In lieu of NR**, self-rate the title using the `USA_PR` rating system instead. Guidelines for `USA_PR` ratings are available at [tvguidelines.org](http://tvguidelines.org/). - -## Supported Rating Systems - -> **Note:** Canada and the United States each appear **twice** below, under two different rating systems. This is intentional — each country has more than one recognized rating authority depending on context (e.g., home video/theatrical vs. TV/V-Chip self-rating), not a duplicate entry. - -| Ratings Authority and Territory | Country | `ratingSystem` | Rating Values | -| --------------------------------------------------------------------- | ------- | -------------- | ------------------------------------------------------------------------------------------------------ | -| British Board of Film Classification
(United Kingdom) | GB | `BBFC` | `U`, `PG`, `12A`, `12-A`, `12`, `15`, `18`, `NR`, `R18` | -| Canadian Home Video Rating System
(Canada) | CA | `CHVRS` | `G`, `PG`, `14A`, `14-A`, `18A`, `18-A`, `NR`, `R`, `E` | -| Motion Picture Association of America
(United States) | US | `MPAA` | `G`, `PG`, `PG13`, `PG-13`, `R`, `NC-17`, `NC17`, `NR` | -| Canadian Parental Rating
(Canada) | CA | `CPR` | `14+`, `18+`, `C`, `C8`, `C-8`, `G`, `NR`, `PG`, `E` | -| Dirección General de Radio, Televisión y Cinematografía
(Mexico) | MX | `RTC` | `AA`, `A`, `B`, `B-15`, `B15`, `C`, `DD`, `D`, `NR` | -| USA Parental Rating
_AKA V-Chip_
(United States) | US | `USA_PR` | `TV-Y`, `TVY`, `TV-Y7`, `TVY7`, `TV-G`, `TVG`, `TV-PG`, `TVPG`, `TV-14`, `TV14`, `TV-MA`, `TVMA`, `NR` | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/_order.yaml deleted file mode 100644 index b01521b2..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/_order.yaml +++ /dev/null @@ -1,3 +0,0 @@ -- excel-film-metadata-fields -- excel-episodic-tv-metadata-fields -- excel-shortform-clip-metadata-fields diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-episodic-tv-metadata-fields.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-episodic-tv-metadata-fields.md deleted file mode 100644 index 8c21cf51..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-episodic-tv-metadata-fields.md +++ /dev/null @@ -1,475 +0,0 @@ ---- -title: Excel - episodic TV metadata fields -excerpt: Field-by-field reference for the TV Excel template. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field reference for the **TV** Excel metadata template, following Roku's `series > season > episode` hierarchy. For template downloads and workbook-level rules (formatting, structure, row limits, file format), see the [Excel Metadata Overview](#roku-excel-metadata-overview). - -**Each row represents one language experience of a single episode.** As in the Excel Film template, several fields repeat conceptually at different hierarchy levels — this reference groups them by level (**Series**, **Season**, **Episode**) to keep that distinction clear. - -Fields are grouped into: **Package Info**, **Series Block**, **Season Block**, **Episode Content Descriptors**, **Ad Breaks & Cue Points**, **Episode Cast & Crew**, **Assets**, **Artwork**, and **Availability**. - -*** - -## Package Info - -### provider - -Name of the content owner/studio/network. - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------------- | -------- | -| `provider` | Example: Roku Originals | Required | - -### contentType - -Defines the content type of the package. For the TV Excel template, this value is `episode` (distinct from the `tv` value used to identify the TV content type elsewhere, e.g., in the [TV XML Reference](#)'s `/package/video/type` field). - -| Excel Column | Accepted Values | Required | -| ------------- | --------------- | -------- | -| `contentType` | `episode` | Required | - -### language - -Language of the title, synopses, video, captions, subtitles, audio dubs, and/or artwork listed on the row. Must conform to a supported [language code](#language-codes). Best practice: include a region code (e.g., `es-MX` vs. `es-ES`). **Only one language allowed per row.** - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------------- | -------- | -| `language` | One valid [language value](#language-codes) | Required | - -### asset_id - -Immutable, unique identifier for an **episode**. Generated/supplied by the partner; should match the Title ID provided in the Avails document, to aid tracking across Roku's pipeline. **50-character limit.** - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------------------------------------------------ | -------- | -| `asset_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -### episode_eidr - -EIDR ID for the episode, if one exists. - -| Excel Column | Accepted Values | Required | -| -------------- | -------------------------- | -------- | -| `episode_eidr` | Any valid episodic EIDR ID | Optional | - -### episode_tms_id - -Gracenote ID for the episode, if one exists. - -| Excel Column | Accepted Values | Required | -| ---------------- | ------------------------- | -------- | -| `episode_tms_id` | Any valid episodic TMS ID | Optional | - -*** - -## Series Block - -### series_id - -Immutable, unique identifier for a series. Generated/supplied by the partner; should match the Series ID provided in the Avails document. **50-character limit.** - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------------------------------------------------ | -------- | -| `series_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -### series_title - -Title of the series, in the language defined in the `language` column. Include **only** the name as it should appear on platform — no non-title parentheticals. - -| Excel Column | Accepted Values | Required | -| -------------- | --------------------- | -------- | -| `series_title` | Example: Series Title | Required | - -### series_tms_id - -Gracenote ID for the series, if one exists. - -| Excel Column | Accepted Values | Required | -| --------------- | --------------------- | -------- | -| `series_tms_id` | Any valid Show TMS ID | Optional | - -### series_release_date - -Original date the series was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| Excel Column | Accepted Values | Required | -| --------------------- | ----------------------------- | -------- | -| `series_release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -### series_genres - -Genre classification of the content. Each series **must** be delivered with **at least one** supported genre. See the [enumerated genre list](#genres). - -> **Note:** Genre is a **series-level** field only — there is no separate episode-level genre field, consistent with the [TV XML Reference](#). - -| Excel Column | Accepted Values | Required | -| --------------- | ----------------------------------------------------------------- | -------- | -| `series_genres` | See [enumerated list](#genres). No more than 10 genres per title. | Required | - -### series_tags - -Freeform categorization field beyond Genre. Used by Roku's editorial team and recommendations engine to surface content. No limit on count; no defined tag set. **Case-sensitive** — deliver consistently. - -| Excel Column | Accepted Values | Required | -| ------------- | ------------------------------ | ---------------------- | -| `series_tags` | Any string under 50 characters | **Highly recommended** | - -### series_cast - -Names of series cast members. - -| Excel Column | Accepted Values | Required | -| ------------- | -------------------------------------------- | --------- | -| `series_cast` | Comma-separated list of `Firstname Lastname` | Preferred | - -### series_directors - -Name(s) of the series director(s). - -> **Cross-format note:** Director is currently the **only** crew member role supported for Excel metadata ingest. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------------------------- | --------- | -| `series_directors` | Comma-separated list of `Firstname Lastname` | Preferred | - -### series_short_synopsis - -A short synopsis of the series, in the language defined in the `language` column. **250-character limit.** - -| Excel Column | Accepted Values | Required | -| ----------------------- | ---------------------- | -------- | -| `series_short_synopsis` | 250-character synopsis | Required | - -### series_long_synopsis - -A long synopsis of the series, in the language defined in the `language` column. **500-character limit.** - -| Excel Column | Accepted Values | Required | -| ---------------------- | ---------------------- | -------- | -| `series_long_synopsis` | 500-character synopsis | Optional | - -*** - -## Season Block - -### season_id - -Immutable, unique identifier for a season. Generated/supplied by the partner. **50-character limit.** - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------------------------------------------------ | -------- | -| `season_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -### season_number - -Numerical position of the season within the series — determines viewing order of underlying episodes. Values **must** reflect original broadcast/exhibition order. Integers only; **must be greater than 0.** - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------------------- | -------- | -| `season_number` | Integers greater than 0 only | Required | - -*** - -## Episode Content Descriptors - -### episode_title - -Title of the episode, in the language defined in the `language` column. Include **only** the name as it should appear on platform — no non-title parentheticals. - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------------- | -------- | -| `episode_title` | Example: Episode Title | Required | - -### episode_number - -Numerical position of the episode within its season — determines viewing order on platform. Values **must** reflect original broadcast/exhibition order; production numbers **must not** be used. Integers only. - -| Excel Column | Accepted Values | Required | -| ---------------- | --------------- | -------- | -| `episode_number` | Integers only | Required | - -### original_spoken_language - -Original production language of the **episode**. At minimum, must conform to a [supported language code](#language-codes). Best practice: include a region code (e.g., `es-MX` vs. `es-ES`). - -> **Note:** this field is not prefixed `episode_` in the template, but applies at the **episode level**, not the series level. - -| Excel Column | Accepted Values | Required | -| -------------------------- | ------------------------------------------- | -------- | -| `original_spoken_language` | One valid [language value](#language-codes) | Required | - -### country_of_origin - -The primary country where the **episode** was produced, and where the main creators, crew, and producers are established. Must conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) code. - -> **Note:** this field is not prefixed `episode_` in the template, but applies at the **episode level**, not the series level. - -| Excel Column | Accepted Values | Required | -| ------------------- | ------------------------------------------------------------------------------------------------------------ | --------- | -| `country_of_origin` | One valid 2-character country code per [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -### episode_release_date - -Original date the episode was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| Excel Column | Accepted Values | Required | -| ---------------------- | ----------------------------- | -------- | -| `episode_release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -### episode_runtime - -Total runtime of the episode, in **whole minutes**. - -| Excel Column | Accepted Values | Required | -| ----------------- | ---------------------------- | -------- | -| `episode_runtime` | Integers only. Example: `22` | Required | - -### rating_system and episode_ratings - -`rating_system` holds the rating authority (e.g., `MPAA`), and `episode_ratings` holds the corresponding rating value (e.g., `TV-14`) for that authority — the same intentional two-column split confirmed for the [Excel Film Reference](#rating_system-and-ratings). A valid TV rating from the rating authority of the territory where the content will be available **must** be provided for each episode. If not rated by that territory's official authority, use a valid `USA_PR` rating instead, per [tvguidelines.org](http://tvguidelines.org/) guidelines. - -> **Note:** Rating is an **episode-level** field only — there is no separate series-level rating field. - -| Excel Column | Accepted Values | Required | -| ----------------- | -------------------------------------------------------------------------------------- | -------- | -| `rating_system` | See [rating values by system and country](#rating-values-by-rating-system-and-country) | Required | -| `episode_ratings` | See [rating values by system and country](#rating-values-by-rating-system-and-country) | Required | - -### episode_tags - -Freeform categorization field beyond Genre, same rules as [series_tags](#series_tags) above. - -| Excel Column | Accepted Values | Required | -| -------------- | ------------------------------ | ---------------------- | -| `episode_tags` | Any string under 50 characters | **Highly recommended** | - -### closed_captions - -Indicates whether the delivered title contains closed captions. **Required for all content intended for Roku Channel in the US.** - -| Excel Column | Accepted Values | Required | -| ----------------- | --------------- | -------- | -| `closed_captions` | `Y` or `N` | Required | - -### closed_captions_exemption - -FCC exemption code for the closed caption requirement. **Required in the US if **`closed_captions`** = **`N`**.** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -| Excel Column | Accepted Values | Required | -| --------------------------- | ---------------------------- | ----------------------------------------- | -| `closed_captions_exemption` | `1`, `2`, `3`, `4`, `5`, `6` | Required in US if `closed_captions` = `N` | - -> _Note: the Accepted Values for this field were missing from the source table — restored above as _`1`_–_`6`_, consistent with the [TV XML Reference](#)._ - -*** - -## Ad Breaks & Cue Points - -> **Note:** ad breaks and cue points are **episode-level** fields only — there are no separate series-level equivalents. - -### episode_ad_breaks - -Used to determine [Ad Breaks for Ad Supported Content](#ad-breaks). Values **must** be accurate to the millisecond. If commercial blacks are present, provide the timecode at the **midpoint**. Not required for SVOD, but frame-accurate data can be ingested if available. - -| Excel Column | Accepted Values | Required | -| ------------------- | --------------- | --------- | -| `episode_ad_breaks` | `HH:MM:SS.sss` | Preferred | - -### episode_cue_points - -Identifies start/end times of opening credits, recaps, end credits, and behind-the-scenes footage. Values **must** be accurate to the millisecond. - -> **Note:** as in the Excel Film template, this is a **single comma-separated text string** in one cell, encoding the same concept described in the [TV XML Reference](#cuepoint-start_time-and-end_time)'s nested `cuePoint` elements. - -**Format:** a comma-separated list of `type=startTime>endTime` pairs. - -**Example:** - -``` -intro=00:05:10.253>00:07:15.123,recap=00:01:12.456>00:03:12.052 -``` - -| Excel Column | Accepted Values | Required | -| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -------- | -| `episode_cue_points` | Format: `type=HH:MM:SS.sss>HH:MM:SS.sss`. Allowable `type` values: `ad overlay`, `behind the scenes`, `intro`, `recap`, `end` | Optional | - -*** - -## Episode Cast & Crew - -### episode_cast - -Names of cast members for the episode. - -| Excel Column | Accepted Values | Required | -| -------------- | -------------------------------------------- | --------- | -| `episode_cast` | Comma-separated list of `Firstname Lastname` | Preferred | - -### episode_director - -Name(s) of the episode's director. - -> **Cross-format note:** Director is currently the only crew member role supported for Excel metadata ingest. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------------------------- | --------- | -| `episode_director` | Comma-separated list of `Firstname Lastname` | Preferred | - -*** - -## Assets - -### video_file_name - -File name of the video, in the language defined in the `language` column, delivered via Aspera. **Only one video allowed per **`asset_id`**.** Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ----------------- | ------------------------------- | -------- | -| `video_file_name` | Example: `episodeVideoFile.mov` | Required | - -### video_file_language - -Primary language of the video file's spoken dialogue and/or visible text. If there is no dialogue or visible text, use the language spoken by the intended audience. **Also applies to** `closed_caption_file_name` and `forced_subtitle_file_name`. **Only one language allowed.** - -| Excel Column | Accepted Values | Required | -| --------------------- | ------------------------------------------- | -------- | -| `video_file_language` | One valid [language value](#language-codes) | Required | - -### audio_layout - -[Audio layout descriptor](#audio-channel-layout-hints) for the delivered video file. - -| Excel Column | Accepted Values | Required | -| -------------- | ------------------------------------------------------------------------ | -------- | -| `audio_layout` | `stereoOnly`, `surroundOnly`, `stereoPlusSurround`, `surroundPlusStereo` | Optional | - -### descriptive_audio_file_name - -For audio description files only. File name of the descriptive audio file, in the language defined in `descriptive_audio_language`, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ----------------------------- | --------------------------- | ----------------------------------------------------------------------------------- | -| `descriptive_audio_file_name` | Example: `movieDubFile.wav` | Required when providing a sidecar descriptive audio file for accessibility purposes | - -### descriptive_audio_language - -For audio description files only. Primary language of the audio file's spoken dialogue track. **Only one language allowed.** - -| Excel Column | Accepted Values | Required | -| ---------------------------- | ------------------------------------------- | ----------------------------------------------- | -| `descriptive_audio_language` | One valid [language value](#language-codes) | Required when providing descriptive audio files | - -### closed_caption_file_name - -File name of the closed captions, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. Its language is derived from `video_file_language`. - -| Excel Column | Accepted Values | Required | -| -------------------------- | ------------------------------ | -------- | -| `closed_caption_file_name` | Example: `episodeCaptions.srt` | Required | - -### forced_subtitle_file_name - -File name of the forced narrative subtitle, in the language defined in `video_file_language`, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. Its language is derived from `video_file_language`. - -| Excel Column | Accepted Values | Required | -| --------------------------- | ------------------------------------ | -------------------------------------------------- | -| `forced_subtitle_file_name` | Example: `episodeForcedSubtitle.srt` | Required when providing forced narrative subtitles | - -*** - -## Artwork - -### series_keyart_file_name - -File name of the texted key art image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ------------------------- | ---------------------------- | -------- | -| `series_keyart_file_name` | Example: `episodeKeyArt.jpg` | Required | - -### series_boxcover_file_name - -File name of the texted boxcover image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| --------------------------- | ---------------------------- | --------- | -| `series_boxcover_file_name` | Example: `episodeBoxArt.jpg` | Preferred | - -### series_poster_file_name - -File name of the texted poster image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ------------------------- | --------------------------- | --------- | -| `series_poster_file_name` | Example: `seriesPoster.jpg` | Preferred | - -### series_background_file_name - -File name of the textless **series**-level background image, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -> _Corrected from the source, which showed the same example filename (_`episodeBGimage.jpg`_) for both _`series_background_file_name`_ and _`episode_background_file_name`_ — updated below to a series-specific example so the two are visually distinct._ - -| Excel Column | Accepted Values | Required | -| ----------------------------- | ---------------------------- | --------- | -| `series_background_file_name` | Example: `seriesBGimage.jpg` | Preferred | - -### episode_background_file_name - -File name of the textless **episode**-level background image, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ------------------------------ | ----------------------------- | --------- | -| `episode_background_file_name` | Example: `episodeBGimage.jpg` | Preferred | - -*** - -## Availability - -> **Note:** as in the [Excel Film Reference](#availability), none of these fields are marked Required — consistent with the confirmed XML behavior for `playOptions` and its children. - -### vod_type - -Monetization type of the episode. Multiple comma-separated values allowed, provided `territory`, `episode_start_date`, and `episode_end_date` are identical across them. - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------ | --------- | -| `vod_type` | Example: `avod`, `svod`, `avod,svod` | Preferred | - -### territory - -Country code(s) of the territory where the content is available. Multiple comma-separated country codes allowed, provided `vod_type`, `episode_start_date`, and `episode_end_date` are identical across them. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------------- | --------- | -| `territory` | `US`, `CA`, `GB`, `MX` | Preferred | - -### episode_start_date - -Start date of content availability. Must be chronologically **before** `episode_end_date`; the two **must not** be identical. - -| Excel Column | Accepted Values | Required | -| -------------------- | -------------------------------------- | --------- | -| `episode_start_date` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Preferred | - -### episode_end_date - -End date of content availability. Must be chronologically **after** `episode_start_date`; the two **must not** be identical. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------------------- | --------- | -| `episode_end_date` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Preferred | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-film-metadata-fields.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-film-metadata-fields.md deleted file mode 100644 index 799808ff..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-film-metadata-fields.md +++ /dev/null @@ -1,365 +0,0 @@ ---- -title: Excel - film metadata fields -excerpt: Field-by-field reference for the Film Excel template. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field reference for the **Film** Excel metadata template. For template downloads and workbook-level rules (formatting, structure, row limits, file format), see the [Excel Metadata Overview](#roku-excel-metadata-overview). - -**Each row represents one language experience of a single movie** — the `language` column defines which language applies to the title, synopses, video, captions, subtitles, audio dub, and artwork referenced in that row (see [Excel Metadata Overview](#multiple-entries-and-volume-limits)). - -Fields are grouped below into: **Package Info**, **Content Descriptors**, **Ad Breaks & Cue Points**, **Cast & Crew**, **Assets**, **Artwork**, and **Availability**. - -*** - -## Package Info - -### provider - -Name of the content owner/studio/network. - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------------- | -------- | -| `provider` | Example: Roku Originals | Required | - -### contentType - -Defines the content type of the package. - -| Excel Column | Accepted Values | Required | -| ------------- | --------------- | -------- | -| `contentType` | `film` | Required | - -### language - -Language of the title, synopses, video, captions, subtitles, audio dubs, and/or artwork listed on the row. Must conform to a supported [language code](#language-codes). Best practice: include a region code (e.g., `es-MX` vs. `es-ES`). **Only one language allowed per row.** - -| Excel Column | Accepted Values | Required | -| ------------ | --------------------------------------- | -------- | -| `language` | Valid [language value](#language-codes) | Required | - -### original_spoken_language - -Original production language of the title. At minimum, must conform to a [supported language code](#language-codes) (region code recommended). - -| Excel Column | Accepted Values | Required | -| -------------------------- | --------------------------------------- | -------- | -| `original_spoken_language` | Valid [language value](#language-codes) | Required | - -### country_of_origin - -The primary country where the film was produced, and where the main creators, crew, and producers are established. Must conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) code. - -| Excel Column | Accepted Values | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -### asset_id - -Immutable, unique identifier for a movie. Generated/supplied by the partner; should match the Title ID provided in the Avails document, to aid tracking across Roku's pipeline. **50-character limit.** - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------------------------------------------------ | -------- | -| `asset_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -### eidr - -EIDR ID, if one exists. - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------- | -------- | -| `eidr` | Any valid EIDR ID | Optional | - -### tms_id - -Gracenote ID, if one exists. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------- | -------- | -| `tms_id` | Any valid TMS ID | Optional | - -*** - -## Content Descriptors - -### title - -Title of the movie, in the language defined in the `language` column. Include **only** the name as it should appear on platform — no non-title parentheticals (e.g., `(Classic)`, `(1987)`, `(Season 1)`, `(HD)`). - -| Excel Column | Accepted Values | Required | -| ------------ | -------------------- | -------- | -| `title` | Example: Movie Title | Required | - -### genres - -Genre classification of the content. Each movie **must** be delivered with **at least one** supported genre. See the [enumerated genre list](#genres). - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------------------------------------------------------- | -------- | -| `genres` | See [enumerated list](#genres). No more than 10 genres per title. | Required | - -### tags - -Freeform categorization field beyond Genre. Used by Roku's editorial team and recommendations engine to surface content. No limit on count; no defined tag set. **Case-sensitive** — deliver consistently (e.g., `"Rom-Com"` and `"rom-com"` are two distinct tags). - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------ | ---------------------- | -| `tags` | Any string under 50 characters | **Highly recommended** | - -### runtime - -Total runtime of the content, in **whole minutes**. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------------------- | -------- | -| `runtime` | Integers only. Example: `90` | Required | - -### release_date - -Original date the content was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| Excel Column | Accepted Values | Required | -| -------------- | ----------------------------- | -------- | -| `release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -### rating_system and ratings - -A valid movie or TV rating from the rating authority (`ratingSystem`) of the territory where the content will be available **must** be provided for each movie. If not rated by that territory's official authority, use a valid `USA_PR` rating instead, per [tvguidelines.org](http://tvguidelines.org/) guidelines (there is no official ratings body for `USA_PR`). - -| Excel Column | Accepted Values | Required | -| --------------- | -------------------------------------------------------------------------------------- | -------- | -| `rating_system` | See [rating values by system and country](#rating-values-by-rating-system-and-country) | Required | -| `ratings` | See [rating values by system and country](#rating-values-by-rating-system-and-country) | Required | - -### short_synopsis - -A short synopsis of the content, in the language defined in the `language` column. **250-character limit.** - -| Excel Column | Accepted Values | Required | -| ---------------- | ---------------------- | -------- | -| `short_synopsis` | 250-character synopsis | Required | - -### long_synopsis - -A long synopsis of the content, in the language defined in the `language` column. **500-character limit.** - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------------- | -------- | -| `long_synopsis` | 500-character synopsis | Optional | - -### closed_captions - -Indicates whether the delivered title contains closed captions. **Required for all content intended for Roku Channel in the US.** - -| Excel Column | Accepted Values | Required | -| ----------------- | --------------- | -------- | -| `closed_captions` | `Y` or `N` | Required | - -### closed_captions_exemption - -FCC exemption code for the closed caption requirement. **Required in the US if **`closed_captions`** = **`N`**.** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -| Excel Column | Accepted Values | Required | -| --------------------------- | ---------------------------- | ----------------------------------------- | -| `closed_captions_exemption` | `1`, `2`, `3`, `4`, `5`, `6` | Required in US if `closed_captions` = `N` | - -> _Note: the Accepted Values for this field were missing from the source table (only the code definitions appeared in the Description column) — restored above as _`1`_–_`6`_, consistent with the [Film XML Reference](#)._ - -*** - -## Ad Breaks & Cue Points - -### ad_breaks - -Used to determine [Ad Breaks for Ad Supported Content](#ad-breaks). Values **must** be accurate to the millisecond. If commercial blacks are present, provide the timecode at the **midpoint**. Not required for SVOD, but frame-accurate data can be ingested if available. - -| Excel Column | Accepted Values | Required | -| ------------ | --------------- | --------- | -| `ad_breaks` | `HH:MM:SS.sss` | Preferred | - -### cue_points - -Identifies start/end times of opening credits, recaps, end credits, and behind-the-scenes footage. Values **must** be accurate to the millisecond. - -> **Note:** unlike the XML format's nested `cuePoint` elements, Excel expresses this as a **single comma-separated text string** in one cell — this is an Excel-specific encoding of the same underlying concept described in the [Film XML Reference](#cuepoint-start_time-and-end_time), not a different data model. - -**Format:** a comma-separated list of `type=startTime>endTime` pairs. - -**Example:** - -``` -intro=00:05:10.253>00:07:15.123,recap=00:01:12.456>00:03:12.052 -``` - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------------------------------------------------------------------------------------------------------------------- | -------- | -| `cue_points` | Format: `type=HH:MM:SS.sss>HH:MM:SS.sss`. Allowable `type` values: `ad overlay`, `behind the scenes`, `intro`, `recap`, `end` | Optional | - -*** - -## Cast & Crew - -### cast - -Names of cast members. - -| Excel Column | Accepted Values | Required | -| ------------ | -------------------------------------------- | --------- | -| `cast` | Comma-separated list of `Firstname Lastname` | Preferred | - -### director - -Name(s) of the movie's director. - -> **Cross-format note:** Director is currently the **only** crew member role supported for **Excel** metadata ingest — the full crew role list supported in XML (see the [Film XML Reference](#cast--crew)) is not available here. - -| Excel Column | Accepted Values | Required | -| ------------ | -------------------------------------------- | --------- | -| `director` | Comma-separated list of `Firstname Lastname` | Preferred | - -*** - -## Assets - -### video_file_name - -File name of the video, in the language defined in the `language` column, delivered via Aspera. **Only one video allowed per **`asset_id`**.** Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ----------------- | ----------------------------- | -------- | -| `video_file_name` | Example: `movieVideoFile.mov` | Required | - -### video_file_language - -Primary language of the video file's spoken dialogue and/or visible text. If there is no dialogue or visible text, use the language spoken by the intended audience. **Also applies to** `caption_file_name` and `forced_subtitle_file_name`. **Only one language allowed.** - -| Excel Column | Accepted Values | Required | -| --------------------- | ------------------------------------------- | -------- | -| `video_file_language` | One valid [language value](#language-codes) | Required | - -### audio_layout - -[Audio layout descriptor](#audio-channel-layout-hints) for the delivered video file. - -| Excel Column | Accepted Values | Required | -| -------------- | ------------------------------------------------------------------------ | -------- | -| `audio_layout` | `stereoOnly`, `surroundOnly`, `stereoPlusSurround`, `surroundPlusStereo` | Optional | - -### descriptive_audio_file_name - -For audio description files only. File name of the descriptive audio file, in the language defined in `descriptive_audio_language`, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ----------------------------- | --------------------------- | ----------------------------------------------------------------------------------- | -| `descriptive_audio_file_name` | Example: `movieDubFile.wav` | Required when providing a sidecar descriptive audio file for accessibility purposes | - -### descriptive_audio_language - -For audio description files only. Primary language of the audio file's spoken dialogue track. **Only one language allowed.** - -| Excel Column | Accepted Values | Required | -| ---------------------------- | ------------------------------------------- | ----------------------------------------------- | -| `descriptive_audio_language` | One valid [language value](#language-codes) | Required when providing descriptive audio files | - -### caption_file_name - -File name of the closed captions, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. Its language is derived from `video_file_language`. - -| Excel Column | Accepted Values | Required | -| ------------------- | ---------------------------- | -------- | -| `caption_file_name` | Example: `movieCaptions.srt` | Required | - -### forced_subtitle_file_name - -File name of the forced narrative subtitle, in the language defined in `video_file_language`, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. Its language is derived from `video_file_language`. - -| Excel Column | Accepted Values | Required | -| --------------------------- | ---------------------------------- | -------------------------------------------------- | -| `forced_subtitle_file_name` | Example: `movieForcedSubtitle.srt` | Required when providing forced narrative subtitles | - -*** - -## Artwork - -### keyart_file_name - -File name of the texted key art image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------- | -------- | -| `keyart_file_name` | Example: `movieKeyArt.jpg` | Required | - -### background_file_name - -File name of the textless background image, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ---------------------- | --------------------------- | --------- | -| `background_file_name` | Example: `movieBGimage.jpg` | Preferred | - -### boxcover_file_name - -File name of the texted boxcover image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| -------------------- | -------------------------- | --------- | -| `boxcover_file_name` | Example: `movieBoxArt.jpg` | Preferred | - -### poster_file_name - -File name of the texted poster image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------- | --------- | -| `poster_file_name` | Example: `moviePoster.jpg` | Preferred | - -*** - -## Availability - -> **Note:** as in the [Film XML Reference](#play-options--availability), none of the four fields below are marked Required. Unlike XML — where a wrapper element (`playOptions`) at least made the container itself Required or Optional as a unit — Excel has no equivalent wrapper, so there's no parallel "block-level" requirement to point to here at all. This is presented as expected/consistent with the confirmed XML behavior, not re-flagged as a new gap. - -### territory - -Country code(s) of the territory where the content is available. Multiple comma-separated country codes allowed, provided `vod_type`, `license_start_date`, and `license_end_date` are identical across them. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------------- | --------- | -| `territory` | `US`, `CA`, `GB`, `MX` | Preferred | - -### vod_type - -Monetization type of the movie. Multiple comma-separated values allowed, provided `territory`, `license_start_date`, and `license_end_date` are identical across them. - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------ | --------- | -| `vod_type` | Example: `avod`, `svod`, `avod,svod` | Preferred | - -### license_start_date - -Start date of content availability. Must be chronologically **before** `license_end_date`; the two **must not** be identical. - -| Excel Column | Accepted Values | Required | -| -------------------- | -------------------------------------- | --------- | -| `license_start_date` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Preferred | - -### license_end_date - -End date of content availability. Must be chronologically **after** `license_start_date`; the two **must not** be identical. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------------------- | --------- | -| `license_end_date` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Preferred | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-shortform-clip-metadata-fields.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-shortform-clip-metadata-fields.md deleted file mode 100644 index 8c643bc9..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/excel-shortform-clip-metadata-fields.md +++ /dev/null @@ -1,421 +0,0 @@ ---- -title: Excel - shortForm clip metadata fields -excerpt: Field-by-field reference for the Clip Excel template. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field reference for the **Clip** Excel metadata template. For template downloads and workbook-level rules (formatting, structure, row limits, file format), see the [Excel Metadata Overview](#roku-excel-metadata-overview). - -**Each row represents one language experience of a single clip.** Clips support two optional feature sets not present in Film/TV: `sub_type`**/**`parent_*`** fields** (identifying a clip as ancillary to a parent program) and **sports metadata** (`sport_type`, `sport_league`, `sport_teams`) — mirroring the [Clip XML Reference](#). - -Fields are grouped into: **Package Info**, **Content Descriptors**, **Cast & Crew**, **Assets**, **Artwork**, **Availability**, **Parent Info**, and **Sports Metadata**. - -*** - -## Package Info - -### provider - -Name of the content owner/studio/network. - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------------- | -------- | -| `provider` | Example: Roku Originals | Required | - -### contentType - -Defines the content type of the package. - -| Excel Column | Accepted Values | Required | -| ------------- | --------------- | -------- | -| `contentType` | `clip` | Required | - -### sub_type - -Defines the content sub-type of the package. Roku does **not** currently support native parent/child connections — ancillary or related content can be identified using one of the sub-types below, but **there is no system-level link created between the parent and child asset**. (See [Parent Info](#parent-info) below for descriptive, non-linking context about a parent program.) - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------------------------------------------------------------------------------------- | -------- | -| `sub_type` | `trailer`, `highlight`, `making_of`, `behind_scenes`, `interview`, `related`, `recap`, `extra` | Optional | - -### language - -Language of the title, synopses, video, captions, subtitles, audio dubs, and/or artwork listed on the row. Must conform to a supported [language code](#language-codes). Best practice: include a region code (e.g., `es-MX` vs. `es-ES`). **Only one language allowed per row.** - -| Excel Column | Accepted Values | Required | -| ------------ | --------------------------------------- | -------- | -| `language` | Valid [language value](#language-codes) | Required | - -### original_spoken_language - -Original production language of the clip. At minimum, must conform to a [supported language code](#language-codes) (region code recommended). - -| Excel Column | Accepted Values | Required | -| -------------------------- | --------------------------------------- | -------- | -| `original_spoken_language` | Valid [language value](#language-codes) | Required | - -### country_of_origin - -The primary country where the clip was produced, and where the main creators, crew, and producers are established. Must conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) code. - -> _Corrected from the source, which referred to "the film" here — this field applies to the clip, consistent with the rest of this template._ - -| Excel Column | Accepted Values | Required | -| ------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -### asset_id - -Immutable, unique identifier for a clip. Generated/supplied by the partner; should match the Title ID provided in the Avails document, to aid tracking across Roku's pipeline. **50-character limit.** - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------------------------------------------------ | -------- | -| `asset_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -### eidr - -EIDR ID, if one exists. - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------- | -------- | -| `eidr` | Any valid EIDR ID | Optional | - -### tms_id - -Gracenote ID, if one exists. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------- | -------- | -| `tms_id` | Any valid TMS ID | Optional | - -*** - -## Content Descriptors - -### title - -Title of the clip, in the language defined in the `language` column. Include **only** the name as it should appear on platform — no non-title parentheticals (e.g., `(Classic)`, `(1987)`, `(Season 1)`, `(HD)`). - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------- | -------- | -| `title` | Example: Clip Title | Required | - -### genres - -Genre classification of the content. Each clip **must** be delivered with **at least one** supported genre. See the [enumerated genre list](#genres). - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------------------------------------------------------- | -------- | -| `genres` | See [enumerated list](#genres). No more than 10 genres per title. | Required | - -### tags - -Freeform categorization field beyond Genre. Used by Roku's editorial team and recommendations engine to surface content. No limit on count; no defined tag set. **Case-sensitive** — deliver consistently (e.g., `"Rom-Com"` and `"rom-com"` are two distinct tags). - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------ | ---------------------- | -| `tags` | Any string under 50 characters | **Highly recommended** | - -### runtime - -Total runtime of the content, in **whole minutes**. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------------------- | -------- | -| `runtime` | Integers only. Example: `90` | Required | - -### release_date - -Original date the content was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| Excel Column | Accepted Values | Required | -| -------------- | ----------------------------- | -------- | -| `release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -### rating_system and ratings - -`rating_system` holds the rating authority (e.g., `MPAA`), and `ratings` holds the corresponding rating value (e.g., `PG-13`) for that authority — the same intentional two-column split confirmed for the [Excel Film Reference](#rating_system-and-ratings). A valid movie or TV rating from the rating authority of the territory where the content will be available **must** be provided for each clip. If not rated by that territory's official authority, use a valid `USA_PR` rating instead, per [tvguidelines.org](http://tvguidelines.org/) guidelines. - -| Excel Column | Accepted Values | Required | -| --------------- | -------------------------------------------------------------------------------------- | -------- | -| `rating_system` | See [rating values by system and country](#rating-values-by-rating-system-and-country) | Required | -| `ratings` | See [rating values by system and country](#rating-values-by-rating-system-and-country) | Required | - -### short_synopsis - -A short synopsis of the content, in the language defined in the `language` column. **250-character limit.** - -| Excel Column | Accepted Values | Required | -| ---------------- | ---------------------- | -------- | -| `short_synopsis` | 250-character synopsis | Required | - -### long_synopsis - -A long synopsis of the content, in the language defined in the `language` column. **500-character limit.** - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------------- | -------- | -| `long_synopsis` | 500-character synopsis | Optional | - -### closed_captions - -Indicates whether the delivered title contains closed captions. **Required for all content intended for Roku Channel in the US.** - -| Excel Column | Accepted Values | Required | -| ----------------- | --------------- | -------- | -| `closed_captions` | `Y` or `N` | Required | - -### closed_captions_exemption - -FCC exemption code for the closed caption requirement. **Required in the US if **`closed_captions`** = **`N`**.** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -| Excel Column | Accepted Values | Required | -| --------------------------- | ---------------------------- | ----------------------------------------- | -| `closed_captions_exemption` | `1`, `2`, `3`, `4`, `5`, `6` | Required in US if `closed_captions` = `N` | - -> _Note: the Accepted Values for this field were missing from the source table — restored above as _`1`_–_`6`_, consistent with the [Clip XML Reference](#)._ - -*** - -## Cast & Crew - -### cast - -Names of cast members. - -| Excel Column | Accepted Values | Required | -| ------------ | -------------------------------------------- | --------- | -| `cast` | Comma-separated list of `Firstname Lastname` | Preferred | - -### director - -Name(s) of the clip's director. - -> **Cross-format note:** Director is currently the **only** crew member role supported for Excel metadata ingest. - -| Excel Column | Accepted Values | Required | -| ------------ | -------------------------------------------- | --------- | -| `director` | Comma-separated list of `Firstname Lastname` | Preferred | - -*** - -## Assets - -### video_file_name - -File name of the video, in the language defined in the `language` column, delivered via Aspera. **Only one video allowed per **`asset_id`**.** Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ----------------- | ----------------------------- | -------- | -| `video_file_name` | Example: `movieVideoFile.mov` | Required | - -### video_file_language - -Primary language of the video file's spoken dialogue and/or visible text. If there is no dialogue or visible text, use the language spoken by the intended audience. **Also applies to** `caption_file_name` and `forced_subtitle_file_name`. **Only one language allowed.** - -| Excel Column | Accepted Values | Required | -| --------------------- | ------------------------------------------- | -------- | -| `video_file_language` | One valid [language value](#language-codes) | Required | - -### audio_layout - -[Audio layout descriptor](#audio-channel-layout-hints) for the delivered video file. - -| Excel Column | Accepted Values | Required | -| -------------- | ------------------------------------------------------------------------ | -------- | -| `audio_layout` | `stereoOnly`, `surroundOnly`, `stereoPlusSurround`, `surroundPlusStereo` | Optional | - -### descriptive_audio_file_name - -For audio description files only. File name of the descriptive audio file, in the language defined in `descriptive_audio_language`, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ----------------------------- | --------------------------- | ----------------------------------------------------------------------------------- | -| `descriptive_audio_file_name` | Example: `movieDubFile.wav` | Required when providing a sidecar descriptive audio file for accessibility purposes | - -### descriptive_audio_language - -For audio description files only. Primary language of the audio file's spoken dialogue track. **Only one language allowed.** - -| Excel Column | Accepted Values | Required | -| ---------------------------- | ------------------------------------------- | ----------------------------------------------- | -| `descriptive_audio_language` | One valid [language value](#language-codes) | Required when providing descriptive audio files | - -### caption_file_name - -File name of the closed captions, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. Its language is derived from `video_file_language`. - -| Excel Column | Accepted Values | Required | -| ------------------- | ---------------------------- | -------- | -| `caption_file_name` | Example: `movieCaptions.srt` | Required | - -### forced_subtitle_file_name - -File name of the forced narrative subtitle, in the language defined in `video_file_language`, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. Its language is derived from `video_file_language`. - -| Excel Column | Accepted Values | Required | -| --------------------------- | ---------------------------------- | -------------------------------------------------- | -| `forced_subtitle_file_name` | Example: `movieForcedSubtitle.srt` | Required when providing forced narrative subtitles | - -*** - -## Artwork - -> **Note:** unlike Film and TV, the Clip template includes only **one** artwork field — consistent with the [Artwork Specification](#), where Clips require only a single 16:9 Key Art image type. - -### keyart_file_name - -File name of the texted key art image, in the language defined in the `language` column, delivered via Aspera. Must exactly match the delivered file. **Case-sensitive**; no whitespace or special characters. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------- | -------- | -| `keyart_file_name` | Example: `movieKeyArt.jpg` | Required | - -*** - -## Availability - -### territory - -Country code(s) of the territory where the content is available. Multiple comma-separated country codes allowed, provided `vod_type`, `license_start_date`, and `license_end_date` are identical across them. - -| Excel Column | Accepted Values | Required | -| ------------ | ---------------------- | --------- | -| `territory` | `US`, `CA`, `GB`, `MX` | Preferred | - -### vod_type - -Monetization type of the clip. Multiple comma-separated values allowed, provided `territory`, `license_start_date`, and `license_end_date` are identical across them. - -| Excel Column | Accepted Values | Required | -| ------------ | ------------------------------------ | --------- | -| `vod_type` | Example: `avod`, `svod`, `avod,svod` | Preferred | - -### license_start_date - -Start date of content availability. Must be chronologically **before** `license_end_date`; the two **must not** be identical. - -| Excel Column | Accepted Values | Required | -| -------------------- | -------------------------------------- | --------- | -| `license_start_date` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Preferred | - -### license_end_date - -End date of content availability. Must be chronologically **after** `license_start_date`; the two **must not** be identical. - -| Excel Column | Accepted Values | Required | -| ------------------ | -------------------------------------- | --------- | -| `license_end_date` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Preferred | - -*** - -## Parent Info - -These fields provide **descriptive, contextual** metadata about the program a clip is derived from or related to — used in combination with a valid [`sub_type`](#sub_type) value above. **This is descriptive metadata only; it does not create a navigable link or on-platform relationship** between the clip and its parent (consistent with the `sub_type` note above that Roku does not natively support parent/child connections). - -### parent_type - -Content type of the parent the clip is derived from or describes. - -| Excel Column | Accepted Values | Required | -| ------------- | ---------------------------- | -------- | -| `parent_type` | `episode`, `movie`, `series` | Optional | - -### parent_title - -Title of the parent program, if the parent is a movie or episode. - -| Excel Column | Accepted Values | Required | -| -------------- | ---------------------------------------- | -------- | -| `parent_title` | Example: Title of Parent Movie or Series | Optional | - -### parent_runtime - -Runtime of the parent program, if the parent is a movie or episode. - -| Excel Column | Accepted Values | Required | -| ---------------- | --------------- | -------- | -| `parent_runtime` | Integer | Optional | - -### parent_release_date - -Release date of the parent movie, episode, or series. - -| Excel Column | Accepted Values | Required | -| --------------------- | ----------------------------- | -------- | -| `parent_release_date` | ISO 8601 format: `YYYY-MM-DD` | Optional | - -### parent_tms_id - -TMS ID of the parent movie, episode, or series. - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------- | -------- | -| `parent_tms_id` | Any valid TMS ID | Optional | - -### parent_series - -Series title of the parent program, if the parent is an episode. - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------------------- | -------- | -| `parent_series` | Example: Parent Series Title | Optional | - -### parent_season - -Season number of the parent program, if the parent is an episode. - -| Excel Column | Accepted Values | Required | -| --------------- | ---------------------- | -------- | -| `parent_season` | Integer greater than 0 | Optional | - -### parent_episode - -Episode number of the parent program, if the parent is an episode. - -| Excel Column | Accepted Values | Required | -| ---------------- | --------------- | -------- | -| `parent_episode` | Integer | Optional | - -*** - -## Sports Metadata - -The following fields are **required specifically for sports clips**. - -### sport_type - -Name of the sport featured in the clip/highlight. - -| Excel Column | Accepted Values | Required | -| ------------ | ----------------- | ------------------------- | -| `sport_type` | Name of the sport | Required for sports clips | - -### sport_league - -Name of the sport league featured in the clip/highlight. - -| Excel Column | Accepted Values | Required | -| -------------- | ------------------------ | ------------------------- | -| `sport_league` | Name of the sport league | Required for sports clips | - -### sport_teams - -Teams featured in the sport clip/highlight. Multiple comma-separated teams may be provided. - -| Excel Column | Accepted Values | Required | -| ------------- | ----------------------------------------------------------------- | ------------------------- | -| `sport_teams` | Comma-separated list. Example: `Chicago Cubs,St. Louis Cardinals` | Required for sports clips | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/index.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/index.md deleted file mode 100644 index 936286a8..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/excel-metadata/index.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -title: Excel metadata -excerpt: 'Workbook rules for Excel metadata: formatting, structure, and file format.' -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -Excel metadata **can only be accepted** if delivered using one of Roku's approved templates below. This page covers rules that apply across all three templates; field-level detail for each content type lives on its own sub-page: - -- [**Roku Excel: Film**](https://developer.roku.com/dev/update/docs/excel-film-metadata-fields) -- [**Roku Excel: TV**](https://developer.roku.com/dev/update/docs/excel-episodic-tv-metadata-fields) -- [**Roku Excel: Clip**](https://developer.roku.com/dev/update/docs/excel-shortform-clip-metadata-fields) - -*** - -## Templates - -| Excel Metadata | Download Link | -| ---------------------------- | ----------------------------------------------------------------------- | -| Film Metadata Excel Template | [Film Metadata Excel Template](https://go.roku.com/film-excel-template) | -| TV Metadata Excel Template | [TV Metadata Excel Template](https://go.roku.com/tv-excel-template) | -| Clip Metadata Excel Template | [Clip Metadata Excel Template](https://go.roku.com/clip-excel-template) | - -*** - -## Template Completion Rules - -The Roku Excel metadata template **must** be submitted with all required fields populated. - -- **Row 2** of each template contains hints highlighting required cells and any special formatting needed — refer to these hints when filling out the template. -- **Do not delete** the legend/hint row (row 2). - -*** - -## Formatting Requirements - -- Dates **must** be provided in `YYYY-MM-DD` format. (Change the cell formatting to **"Text"** if Excel is auto-converting the value.) -- File names **must not** contain [special characters or spaces](#special-characters). - -*** - -## Workbook Structure Rules - -- **Do not** link to external data or other Excel workbooks — all data **must** be self-contained within the workbook delivered to Roku. -- **Do not** add additional sheets to the workbook. -- **Do not** add additional columns to the workbook. -- Any formulas used **must** be converted to plain text before submission. **⚠️ Including a live formula will result in rejected deliveries and processing delays/failures.** - -*** - -## Data Population Rules - -- **Do not** supply a value of `"N/A"` or `"n/a"` anywhere in the workbook. - - Required cells **must** contain valid data. - - Optional cells **may** be left blank. - -*** - -## Multiple Entries and Volume Limits - -Multiple entries of the **same content type** may be supplied in a single Excel workbook (e.g., several movies in one Film workbook, or several episodes in one TV workbook) — since each content type has its own dedicated template, a single workbook is not intended to mix Film, TV, and Clip rows together. - -- **Each row** represents a unique **language experience** of a single episode/movie/clip. -- **⚠️ Do not leave a blank row between entries.** Roku's system will **terminate processing at the first empty row** — anything after a blank row will silently fail to process. -- **Do not include more than 900 rows** in a single sheet. - -*** - -## File Format and Export - -Roku accepts `.xlsx` and `.csv` — `.xls`** is not supported.** - -- If exporting from **Microsoft Excel**, save as `.xlsx`. -- If using a different spreadsheet program (one that doesn't produce a valid `.xlsx` file), export as `.csv` instead. \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/index.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/index.md deleted file mode 100644 index dc4c1723..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/index.md +++ /dev/null @@ -1,221 +0,0 @@ ---- -title: Metadata -excerpt: >- - Content type definitions, ID rules, availability windows, and supported - formats. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -Roku uses a **transform engine** that normalizes different metadata formats to fit Roku's ingestion needs. The exact element or field names you use matter less than **consistent delivery** of agreed-upon element/field names — but regardless of naming, the _data_ within any field **must** conform to the Roku Channel Ingest Specification. - -- If you already use an XML format to deliver content to other platforms, you **may** be able to repurpose it for Roku delivery. -- You **may** provide a sample of your existing metadata format during onboarding for Roku to evaluate its validity for ingest. -- Regardless of which format is delivered, **all required elements/fields must be provided** in the metadata deliverable. - -### Related Documentation - -This page covers concepts that apply across all metadata delivery formats. Format-specific field-level detail lives in dedicated sub-pages: - -- **MovieLabs**: MEC/MMC delivery (see the MovieLabs Migration Playbook / MovieLabs guide) -- **Roku XML**: three sub-pages, one per content type: **Film**, **TV**, **Clip** -- **Roku Excel**: three sub-pages, one per content type: **Film**, **TV**, **Clip** - -*** - -## Content Type Definitions - -Roku Channel supports **three content types**: `tv`, `film`, and `clip`. All content **must** be delivered as one of these three types, and titles **must** be delivered under the same content type in which the program was originally released. - -### TV - -Content structured in a **series > season > episode** hierarchy should be delivered under the TV specification. - -- **Series** — a collection of programs/episodes released under a common title with a consistent narrative, characters, or theme. In North America, each year of a series is called a season; a series can span several seasons. -- **Season** — a group of programs/episodes released in one year, attributed to one series. -- **Episode** — a single self-contained narrative or informational segment of a series. An episode belongs to exactly one season of exactly one series. - -### Film - -Full-length, stand-alone titles should be delivered under the Film specification — any program **not** intended to nest in a series/season/episode hierarchy. This includes stand-alone TV specials and short films. - -### Clip - -Short-form, stand-alone or ancillary titles intended as a companion to a longer program (e.g., sporting events, movies, TV series) should be delivered under the Clip specification. - -**Clip presentation and on-platform behavior differs from Film:** - -- Runtime and title are **superimposed directly on the content tile** — a viewer sees this information without clicking in. -- Clips **do not** have a content details page. Unlike Film, a viewer cannot click into a Clip to reach a synopsis or additional information screen. -- A Clip's synopsis is instead accessible by pressing the **\* (asterisk/options) button** on the Roku remote. - -*** - -## Minimum Required Metadata by Content Type - -### Film / Clip — Required Fields - -- `provider` -- `content_type` -- `asset_id` -- `title` -- `release_date` -- `runtime` -- `genres` -- `rating` -- `rating_system` -- `short_synopsis` -- `video file_name` -- `captions file_name` _(if captions are required)_ -- `key_art file_name` - -### TV — Required Fields - -**Episode-level:** - -- `provider` -- `content_type` -- `asset_id` -- `episode title` -- `episodeNumber` -- `episode release_date` -- `runtime` -- `rating` -- `rating_system` -- `episode short_synopsis` -- `video file_name` -- `captions file_name` _(if captions are required)_ -- `episode thumbnail file_name` - -**Series-level:** - -- `series_id` -- `series title` -- `series release_date` -- `series genres` -- `series short_synopsis` -- `series key_art file_name` - -**Season-level:** - -- `season_id` -- `seasonNumber` - -> Film/Clip and TV field lists are shown separately (rather than side-by-side) because they don't correspond 1:1 — TV carries substantially more required fields due to its series/season/episode hierarchy. - -*** - -## ID Requirements and Expectations - -- Roku does **not** supply IDs — all IDs are generated and supplied **by the partner**. -- Every **clip and movie** must be delivered with an `asset_id`. -- Every **episode** must be delivered with **three IDs**: `asset_id`, `series_id`, and `season_id`. -- IDs should be **meaningful to your team**, since they are how Roku positively identifies a title in its system. -- The `asset_id` in the ingest metadata **must match** the Title ID provided in the Avails document — this links the content across Roku's pipeline, from Avails submission through publication. -- Any update to a title already ingested into Roku's system **MUST** be accompanied by its `asset_id`. - -**All ID types share these rules:** - -- **Maximum 50 characters** -- **Alphanumeric characters, hyphens, and underscores only** -- **⚠️ Spaces or special characters in any ID will fail ingestion** - -| ID | Identifies | Uniqueness / Consistency Rule | Required For | -| ----------- | -------------------------------- | --------------------------------------------------------------------------------------------------------------- | ------------ | -| `asset_id` | A single clip, episode, or movie | Immutable, unique per asset | All content | -| `series_id` | A series | Immutable; must be consistent across **all** episodes of that series; cannot equal the season or episode ID | TV content | -| `season_id` | A season of a series | Immutable; must be consistent across all episodes **within that season**; cannot equal the series or episode ID | TV content | - -*** - -## Availability Sheets / Planners - -- At onboarding, Roku requests an **initial launch list** of titles/episodes/clips currently available for licensing, plus a schedule for when content will be refreshed. -- For ongoing delivery, Roku requests: - - **Avails** at least **60 days** prior to the licensing window start - - **Content delivery** at least **30 days** before curation onto the channel - -This lead time allows for processing and QC before the content goes live. Delivery capacity is coordinated after signing. - -| Document | Link | -| ------------------- | ----------------------------------------------------------- | -| Roku Avail Spec | [View specification](https://go.roku.com/trc-avail-spec) | -| Roku Avail Template | [Download template](https://go.roku.com/trc-avail-template) | - -*** - -## Availability Windows - -By default, content becomes available at **12:00 AM (midnight)** and expires at **11:59:59 PM** in each user's local time zone. If a title must go live or expire at a specific time, that time **must** be included in the license window start/end values in the ingest metadata. - -Roku supports two time designations: - -| Type | Behavior | Example | -| ------------ | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **Relative** | Content goes into window at the specified time in **each user's own local time zone** | A Saturday 9:00 PM premiere is available at 9:00 PM Eastern for Eastern-zone users, and separately at 9:00 PM Pacific for Pacific-zone users (i.e., three hours later in real time) | -| **Absolute** | Content goes into window at a **single fixed moment worldwide** | A new episode set for 9:00 PM Eastern (absolute) becomes available to Pacific users at 6:00 PM their local time — the same real-world instant | - -### Time Value Format - -| Time Type | Format | Example | -| -------------- | ---------------------- | ---------------------- | -| Relative | `yyyy-mm-ddThh:mm:ss` | `2019-11-01T21:00:00` | -| Absolute (UTC) | `yyyy-mm-ddThh:mm:ssZ` | `2019-11-02T01:00:00Z` | - -- **Absolute times must be expressed in UTC.** In the example above, 9:00 PM Eastern on November 1 is 1:00 AM UTC on November 2. -- **If no time is provided**, Roku assumes a relative start of `12:00:00 AM` and a relative end of `11:59:59 PM`. - -*** - -## Special Characters - -Roku uses **CDATA sections** to allow special characters (e.g., `! @ # $ % ^ & * ( ) { } | [ ] ; : ' " ? / < >`, as well as foreign character sets) within **certain** node values in the ingest XML. Roku **highly recommends** wrapping such data in CDATA sections to ensure proper ingest. - -> **This is a different context from file-naming rules.** The [File Delivery Specification](#) forbids most of these same characters in **file names**. Here, the rules apply to **metadata field values** (like title or synopsis text) — the two rule sets govern different things and are not in conflict. - -**Only the following nodes support CDATA sections:** - -- `title` -- `long_synopsis` -- `short_synopsis` -- `display_name` - -**For every other node** (i.e., any field not in the list above), certain characters will render the XML document unreadable to Roku's ingest platform unless properly escaped. These characters **must** be provided in their escaped form: - -| Character Name | Character | Escaped Form | -| -------------- | --------- | ------------ | -| Ampersand | `&` | `&` | -| Less-than | `<` | `<` | -| Greater-than | `>` | `>` | -| Quotes | `"` | `"` | -| Apostrophe | `'` | `'` | - -**Special characters should never be used in file names** or file name references within XML or Excel metadata — see the [File Naming Guidelines](#file-naming) for the complete forbidden-character list for file names specifically. - -*** - -## Supported Metadata Formats - -- **XML** is the **preferred** format. -- **One complete XML file** must be delivered for **each** movie, clip, or TV episode video file delivered. -- Metadata **must** be delivered via Aspera to the **same folder location** as its associated video, captions, and artwork files. - -| Format | Extension | Encoding | Package Version(s) | -| ----------------- | --------- | -------- | ---------------------------------------------------------------------------------------------------- | -| XML _(preferred)_ | `.xml` | UTF-8 | `clip1.0`, `film5.0`, `tv1.0`, `Cablelabs ADI 1.1` _(additional XML schemas supported case-by-case)_ | -| Excel | `.xlsx` | — | See [Roku Excel Metadata Guidelines](#roku-excel-metadata-guidelines-and-templates) and templates | - -*** - -## Glossary - -| Term | Definition | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| **Transform engine** | Roku's internal system that normalizes differently-named metadata fields from partner formats into Roku's ingest schema. | -| **CDATA section** | An XML construct (``) that tells a parser to treat enclosed content as literal text, allowing special characters without requiring them to be escaped. | -| **Avail / Title ID** | The identifier for a title as declared in the Avails (licensing/availability) document — this must match the `asset_id` used in ingest metadata to link the two records. | -| **Relative time** | An availability time interpreted in each viewer's own local time zone, so the same title goes live at different real-world moments across time zones. | -| **Absolute time** | An availability time fixed to a single real-world instant (expressed in UTC), so the title goes live simultaneously worldwide regardless of viewer time zone. | diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/metadata-updates-mdu-and-file-replacements.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/metadata-updates-mdu-and-file-replacements.md deleted file mode 100644 index 89b5c9dd..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/metadata-updates-mdu-and-file-replacements.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -title: Metadata updates (MDU) and file replacements -excerpt: How to update metadata or replace/add files post-delivery. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -Updates are **automated** and can be sent whenever metadata or asset files need to change for a program **already delivered** to Roku Channel. - -Every metadata and/or file-replacement update **must** include the following, exactly as originally delivered, for the update to succeed: - -- **Provider** -- **Asset ID** -- **Content Type** - -**Version control is handled entirely by Roku's system** — there is no need to provide versioning information in the metadata itself. - -> **Note — two different meanings of "versioning":** this rule refers to Roku's internal _record_ versioning (you don't need to tell Roku "this is version 3 of the metadata"). It is separate from the file-naming rule under [File Replacements and Additions](#file-replacements-and-additions) below, which requires giving a **replacement file itself** a unique name (e.g., a `_v2` suffix). Both are true at once and don't conflict — one is about metadata records, the other is about file names. - -### Supported Fields for Automated Metadata Update (MDU) - -Roku currently supports updating the following fields via automated MDU: - -- TMS ID -- EIDR ID -- Titles (primary and localized) -- Short Descriptions (primary and localized) -- Long Descriptions (primary and localized) -- Release Date -- Series Titles -- Season Number -- Episode Number -- Language (and localized languages) -- Availability Windows -- License Types -- Countries -- Genres -- Provider Tags -- Content Ratings (system & rating) -- Credits -- Ad Breaks -- Cue Points - -*** - -## Metadata Update (MDU) - -Metadata updates are processed the same way as new ingest content. To update metadata **only** (no file changes), follow the requirements below. - -### Requirements - -- Metadata updates **must** be delivered in the **same format** as the original ingest metadata. -- Metadata updates **must** include the **exact same Asset ID** used at original ingest. _(Need a full listing of asset IDs as they exist in Roku's system? Contact [contentoperations@roku.com](mailto:contentoperations@roku.com).)_ -- **All file name references must be removed** from a metadata-only update. This includes: - - Source video file name - - Closed captions file name - - Subtitle file name - - Audio dub file name - - Key, background, and/or poster art file names - -### Field Groups - -Some fields must be updated together, in complete groups — **all required fields in a group must be provided**, or the update will not process. - -**Metadata group:** - -| Field | Required? | -| ----------------- | ------------ | -| Language | Required | -| Title | Required | -| Short description | Required | -| Long description | **Optional** | - -**Availability group:** - -| Field | Required? | -| ------------ | --------- | -| License Type | Required | -| Country | Required | -| Start Date | Required | -| End Date | Required | - -### Procedure - -1. Upload the metadata update to the `/prod` folder in Aspera. - -> If the update isn't reflected on Roku Channel within **24 hours**, contact [contentoperations@roku.com](mailto:contentoperations@roku.com). - -*** - -## File Replacements and Additions - -File replacements and additions are processed the same way as new ingest content. - -- A **file replacement** replaces a file that currently exists in Roku Channel's library. -- A **file addition** adds a new file to an existing record — for example, adding localized subtitles or dubs to a title that didn't previously have them. - -### Requirements - -- File replacements/additions **must** be delivered in the **same format** as the original ingest metadata. -- File replacements/additions **must** include the **exact same Asset ID** used at original ingest. _(Need a full asset ID listing? Contact [contentoperations@roku.com](mailto:contentoperations@roku.com).)_ -- Replacement files **must** be delivered with a **unique name**, both in the metadata and on the file itself, for the update to succeed. Adding a version suffix (`_v2`, `_v3`, etc.) is sufficient — e.g., `movie_title_v2.mov`. - - _MovieLabs file replacements may use the _`md5`_ node instead of a versioned file name._ -- Replacement files **must** be delivered to the **exact same folder** as the original delivery. -- **Only** the file name references for files actually being replaced or added should appear in the metadata file. Files not being replaced or added should **not** be delivered or referenced. -- If the source video file is replaced **and** its duration changes, any related files (captions, subtitles, audio dubs) **should** also be replaced to stay in sync. -- File replacements **require language values** to be provided in order to update properly. - -### Files Supported for Automated Replacement/Addition - -- Video file -- Series key art file -- Series poster art file -- Series background image file -- Episode image file -- Movie key art file -- Movie poster art file -- Movie background image file -- Shortform key art file -- Closed caption file -- Full subtitle file -- Forced narrative subtitle file -- Sidecar audio file (audio dubs and descriptive audio) - -### Procedure - -1. Upload the file replacement/addition metadata to the `/prod` folder in Aspera. - -*** - -## Content Takedown - -If rights change after content has been delivered to Roku, and content needs to be removed from Roku Channel — either immediately or on a scheduled future date — the **availability end date** can be changed via a metadata update, following the [Metadata Update (MDU)](#metadata-update-mdu) process above. - -- **Explicit updates must be provided for every territory** from which the content should be removed — a takedown in one territory does not automatically apply elsewhere. -- **Be aware:** end dates provided without an explicit time value will expire at **11:59:59 PM** on that date (local time), per the default behavior described in the Metadata Overview's [Availability Windows](#availability-windows) section. - -*** - -## Glossary - -| Term | Definition | -| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -| **MDU** | Metadata Update — an automated update to a title's metadata fields without changing any delivered files. | -| **Asset ID** | The immutable, partner-assigned identifier for a piece of content; required, unchanged, on every update to that content. | -| **Field group** | A set of fields that must all be supplied together for an update to that group to succeed — providing only some fields in a group will not process. | -| **md5 node** | A MovieLabs MMC/MEC element that can identify a replacement file by checksum instead of relying on a versioned file name. | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/movielabs.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/movielabs.md deleted file mode 100644 index 21d72b77..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/movielabs.md +++ /dev/null @@ -1,218 +0,0 @@ ---- -title: MovieLabs -excerpt: Roku-specific MovieLabs delivery order, tags, markers, and schema validation. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page covers **Roku-specific** implementation details for MovieLabs metadata delivery — schema versions in use, Roku-specific field mappings (tags, TMS IDs, artwork), ad-break markers, and schema validation. It assumes familiarity with MovieLabs MEC/MMC concepts generally; for foundational MovieLabs concepts, see the MovieLabs guide. - -*** - -## Delivery Order - -Order of delivery is **critical**. Roku cannot process content without successful delivery of **both** the MMC and MEC XMLs, and there are two distinct ordering dependencies to satisfy. - -### 1. Media Files Must Precede Their XML - -- For each **MMC**, all files referenced within it **must** be delivered before the MMC XML itself, for the delivery to be considered successful. -- For each **MEC**, all files referenced within it **must** be delivered before the MEC XML itself, for the delivery to be considered successful. - -### 2. Hierarchy Ingest Order (Series > Season > Episode) - -- **Movies and Episodes** require successful delivery of **both** MMC and MEC to ingest. -- **Series and Seasons** require successful delivery of **at least the MEC** to ingest. (Series and Season MMCs are supported if artwork references are delivered via MMC.) -- An **Episode** cannot ingest until the **MEC of its Season** has been successfully delivered and ingested. -- A **Season** cannot ingest until the **MEC of its Series** has been successfully delivered and ingested. - -**If content arrives out of order:** - -- An Episode processed before its Series and/or Season is held in an **un-ingested state** until the Series and/or Season has been successfully delivered. -- A Season processed before its Series and/or an Episode belonging to it is held in an **un-ingested state** until the Series and/or an Episode has been successfully delivered. -- A Series processed before a Season and an Episode belonging to it is held in an **un-ingested state** until a Season and Episode have been successfully delivered. - -*** - -## Roku-Specific Metadata and Media Files - -Roku Channel supports metadata delivery via the MovieLabs specification, using the following schemas: - -- **MMC and MEC** — Roku Channel's MovieLabs service is built on **MEC v2.9** and **MMC v1.10**, as defined on [MovieLabs' site](https://www.movielabs.com/md/). -- **EMA Avails** — Roku Channel supports the latest version of the [EMA specification](https://movielabs.com/md/avails/), delivered via `.xlsx`. - -All [video](#video-requirements), [audio](#audio-requirements), [closed caption](#closed-captions), [subtitle](#subtitles), and [image](#artwork) files, along with [minimum metadata requirements](#minimum-required-metadata-by-content-type), [genres](#genres), and [ratings/rating sources](#rating-values-by-rating-system-and-country), **must** adhere to the formats and requirements defined elsewhere in this specification — this page covers only the MovieLabs-specific delivery mechanics for that same content. - -### Tags - -Tags for merchandising/curation can be delivered via the `Keyword` node, supported in the MovieLabs MEC XML. See the [MovieLabs MEC Schema](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link116) for proper placement. - -```xml - - Great Title of My Show - Short summary of my show. - Longer summary of my show. - - keyword - -``` - -### TMS IDs - -Gracenote TMS IDs can be delivered via the MovieLabs MEC XML, as an `Identifier` with `Namespace` `TMSID` inside the `AltIdentifier` node. See the [MovieLabs MEC Schema](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link121) for proper structure. - -```xml - - TMSID - EP012345678910 - -``` - -### MMC XML Ad Breaks and Cue Points - -Ad break, intro credit, and end credit cue points are supplied in the MovieLabs MMC XML via the `Markers` node. See the [MovieLabs MMC Schema](https://movielabs.com/md/manifest/v1.10/manifest-v1.10/manifest-v1.10.html#Link184) for proper structure. - -**Note:** Roku only needs a single **start point** for ad-break markers — Roku's player pauses playback at that point, plays the ad pod, and resumes from the same point. - -```xml - - - - - 155.071 - FIRST_FRAME_EPISODE_INTRO - FFEI - - - 200.867 - LAST_FRAME_EPISODE_INTRO - LFEI - - - - - - 3669.207 - FIRST_FRAME_UP_NEXT - FFUN - - - 3812.517 - LAST_FRAME_UP_NEXT - LFUN - - - - - - 737.111 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 1361.276 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 1948.821 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 2841.421 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - - 3270.100 - FIXED_POINT_CANDIDATE_INSERTION - FPCI - - -``` - -### MEC ArtReference for Roku Channel - -Roku-specific image files are identified using the MovieLabs MEC `ArtReference` `purpose` attribute: - -| `purpose` Attribute Value | Roku Artwork Type | -| ------------------------- | ------------------------------------------------------------------------------------------------------------ | -| `keyart` | 16:9 texted key art with title treatment for movies/shortform/series **OR** 16:9 textless image for episodes | -| `boxcover` | 4:3 or 3:4 texted box art with title treatment | -| `poster` | 2:3 texted poster art with title treatment | -| `background` | 16:9 textless background image | - -```xml - - Ahed's Knee - - - - 16x9_texted_image_with_title_treatment.jpg - - - 16x9_textless_episode_image.jpg - - - 4x3_texted_image_with_title_treatment.jpg - 3x4_texted_image_with_title_treatment.jpg - - - 2x3_texted_image_with_title_treatment.jpg - - - 16x9_textless_background_image.jpg - - Short Summary of the program in the language specified - Long Summary of the program in the language specified - Drama - -``` - -*** - -## MovieLabs Schema Validation - -Roku uses Apache [xmlbeans](https://xmlbeans.apache.org/download/index.html) to parse and validate MEC/MMC XML files. Its command-line validation tool can be used to pre-check files before delivery. - -1. Download and extract xmlbeans locally. -2. From the command line, `cd` to the xmlbeans `bin` directory. -3. Inside `bin`, locate the `validate` tool. -4. Download the official MovieLabs schema XSD files locally: - - [manifest-v1.10.xsd](https://movielabs.com/schema/manifest/v1.10/manifest-v1.10.xsd) (for MMC) - - [mdmec-v2.9.xsd](https://movielabs.com/schema/mdmec/v2.9/mdmec-v2.9.xsd) (for MEC) -5. Run: `validate schema.xsd instance.xml` — point `schema.xsd` to `mdmec-v2.9.xsd` for MEC files, or `manifest-v1.10.xsd` for MMC files. -6. The command-line output will indicate whether the given XML is valid. - -**Example usage:** - -```bash -./validate ~/dev/movielabsSpec/schema/mdmec-v2.9.xsd /path/to/file/directory/MEC_SAMPLE_123456789.xml -``` - -**Example response:** - -```text -XMLBEANS_LIB=./../lib -ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... -/path/to/file/directory/MEC_SAMPLE_123456789.xml valid -``` - -> **📌 Note — expected validation behavior:** the official MovieLabs schema **may fail validation** when using Roku's supported genre values. **This is expected and not a problem** — submission of Roku's supported genre values will **not** fail validation in Roku's own ingest pipeline, even though the standalone xmlbeans tool may flag it. Don't treat a genre-related xmlbeans failure as a signal that your file is invalid for Roku delivery. - -*** - -## Glossary - -| Term | Definition | -| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| **MEC** | Media Entertainment Core — the MovieLabs metadata schema describing the content itself. | -| **MMC** | Media Manifest Core — the MovieLabs schema describing the manifest of deliverable assets (video, audio, images) tied to a title. | -| **EMA Avails** | The MovieLabs/EMA specification expressing licensing and availability terms for content. | -| **Markers node** | The MMC XML element carrying cue-point timecodes for ad breaks, intro credits, and end credits. | -| **ArtReference** | The MEC XML element that references an artwork file, tagged with a `purpose` attribute identifying which Roku image type it represents. | -| **TMS ID** | A Gracenote-assigned identifier for a title, deliverable via the MEC `AltIdentifier` node. | -| **xmlbeans** | An Apache library/tool Roku uses to validate MEC/MMC XML files against the official MovieLabs schema. | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/_order.yaml deleted file mode 100644 index dd24d5cc..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/_order.yaml +++ /dev/null @@ -1,3 +0,0 @@ -- xml-film-metadata-fields -- xml-episodic-tv-metadata-fields -- xml-shortform-clip-metadata-fields diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/index.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/index.md deleted file mode 100644 index 20879749..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/index.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: XML metadata -excerpt: Index of Roku's XML schemas and annotated samples by content type. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is a **resource index** for Roku's XML metadata delivery. Schema downloads and annotated samples for each content type. It does not itself contain field-level requirements; those live on the dedicated per-content-type sub-pages: - -- [**Roku XML: Film**](https://developer.roku.com/dev/update/docs/xml-film-metadata-fields) -- [**Roku XML: TV**](https://developer.roku.com/dev/update/docs/xml-episodic-tv-metadata-fields) -- [**Roku XML: Clip**](https://developer.roku.com/dev/update/docs/xml-shortform-clip-metadata-fields) - -Use this page to locate the correct schema and sample files while working from those sub-pages. - -*** - -## Roku XML Schemas - -| Roku XML Schema | Download Link | -| --------------- | ------------------------------------------------------ | -| Film XML Schema | [Film XML Schema](https://go.roku.com/film-xml-schema) | -| TV XML Schema | [TV XML Schema](https://go.roku.com/tv-xml-schema) | -| Clip XML Schema | [Clip XML Schema](https://go.roku.com/clip-xml-schema) | - -*** - -## Roku XML Samples (Annotated) - -| Roku XML Sample | Download Link | -| ----------------------- | --------------------------------------------------------------- | -| Annotated Roku Film XML | [Annotated Roku Film XML](https://go.roku.com/film-xml-example) | -| Annotated Roku TV XML | [Annotated Roku TV XML](https://go.roku.com/tv-xml-example) | -| Annotated Roku Clip XML | [Annotated Roku Clip XML](https://go.roku.com/clip-xml-example) | - -*** - -## Sample Cablelabs ADI Metadata - -These are **alternate-format** examples — Cablelabs ADI 1.1 is a supported package version (see the [Metadata Overview](#supported-metadata-formats)), but MovieLabs or Roku's own XML schemas above remain the **preferred** format. - -| Cablelabs ADI Sample | Download Link | -| ------------------------------ | -------------------------------------------------------------------------- | -| Cablelabs Film ADI XML Example | [Cablelabs Film ADI XML Example](https://go.roku.com/film-adi-xml-example) | -| Cablelabs TV ADI XML Example | [Cablelabs TV ADI XML Example](https://go.roku.com/tv-adi-xml-example) | -| Cablelabs Clip ADI XML Example | [Cablelabs Clip ADI XML Example](https://go.roku.com/clip-adi-xml-example) | - -> **Note:** Cablelabs ADI samples are intended as **illustrative examples only**, not as ready-to-use templates. The required data must still be supplied in a static node in each XML. \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-episodic-tv-metadata-fields.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-episodic-tv-metadata-fields.md deleted file mode 100644 index 792d0239..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-episodic-tv-metadata-fields.md +++ /dev/null @@ -1,937 +0,0 @@ ---- -title: XML - episodic TV metadata fields -excerpt: Field-by-field XML reference for TV series/season/episode delivery. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field XML reference for the **TV** content type, following Roku's `series > season > episode` hierarchy (see [Content Type Definitions](#content-type-definitions)). For the schema download and annotated sample, see the [Roku XML Metadata Overview](#roku-xml-metadata-overview). - -**A note on structure:** because TV metadata is delivered as a nested hierarchy, several field names repeat at different levels — `title`, `short_synopsis`, `long_synopsis`, `cast`, `crew`, and `localizations` all exist once for the **episode** and again for the **series**. Each is labeled below with its level (e.g., "Episode Title" vs. "Series Title") to keep them distinct. - -Fields are grouped into: **Package Info**, **Episode Content Descriptors**, **Ad Breaks & Cue Points**, **Episode Cast & Crew**, **Episode Localizations**, **Series Block**, **Season Block**, **Play Options / Availability**, and **Assets**. - -*** - -## Package Info - -### package - -Defines the package version type. - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/@version` | `tv1.0` | Required | - -```xml - -``` - -### provider - -Name of the content owner/studio/network. - -| XML XPath | Example | Required | -| ------------------- | -------------- | -------- | -| `/package/provider` | Roku Originals | Required | - -```xml -Roku Originals -``` - -### language - -Primary language of the package metadata. At minimum, must conform to a [supported language code](#language-codes). Best practice: include a region code (e.g., `es-MX` vs. `es-ES`). - -| XML XPath | Accepted Values | Required | -| ------------------- | -------------------------------------- | -------- | -| `/package/language` | [Valid language code](#language-codes) | Required | - -```xml -en -``` - -### type - -Defines the content type of the package. - -| XML XPath | Accepted Values | Required | -| --------------------- | --------------- | -------- | -| `/package/video/type` | `tv` | Required | - -```xml -tv -``` - -### asset_id (Episode) - -Immutable, unique identifier for an **episode**. IDs are generated and supplied by the partner. Should match the ID provided in the Avails document, to aid tracking across Roku's pipeline. **50-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------- | ------------------------------------------------------------------------------ | -------- | -| `/package/video/asset_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -```xml -episodeAssetIdHere -``` - -### eidr - -EIDR ID, if one exists. - -| XML XPath | Accepted Values | Required | -| --------------------- | ----------------- | -------- | -| `/package/video/eidr` | Any valid EIDR ID | Optional | - -```xml - -``` - -### tmsId - -Gracenote ID, if one exists. - -| XML XPath | Accepted Values | Required | -| ---------------------- | ---------------- | -------- | -| `/package/video/tmsId` | Any valid TMS ID | Optional | - -```xml - -``` - -*** - -## Episode Content Descriptors - -### Episode Title - -Title of the episode. Include **only** the name as it should appear on platform — no non-title parentheticals (e.g., `(Classic)`, `(1987)`, `(Season 1)`, `(HD)`). - -| XML XPath | Example | Required | -| ---------------------- | ------------- | -------- | -| `/package/video/title` | Episode Title | Required | - -```xml -<![CDATA[Episode Title. Required.]]> -``` - -### episodeNumber - -Numerical position of the episode within its season — determines viewing order on platform. Values **must** reflect original broadcast/exhibition order; production numbers **must not** be used. Integers only. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/episodeNumber` | Integers only | Required | - -```xml -2 -``` - -### Episode short_synopsis - -A short synopsis of the episode. CDATA supported. **250-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------- | ---------------------- | -------- | -| `/package/video/short_synopsis` | 250-character synopsis | Required | - -```xml - -``` - -### Episode long_synopsis - -A long synopsis of the episode. CDATA supported. **500-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------ | ---------------------- | -------- | -| `/package/video/long_synopsis` | 500-character synopsis | Optional | - -```xml - -``` - -### closedCaptions - -Indicates whether the episode contains closed captions. **Required for all content intended for Roku Channel in the US.** - -| XML XPath | Accepted Values | Required | -| ------------------------------- | --------------- | ----------------------- | -| `/package/video/closedCaptions` | `Y` or `N` | Required for US content | - -```xml -Y -``` - -### closedCaptionsExemption - -FCC exemption code for the closed caption requirement. **Required if **`closedCaptions`** = **`N`**.** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------------------- | ---------------------------------- | -| `/package/video/closedCaptionsExemption` | `1`, `2`, `3`, `4`, `5`, `6` | Required if `closedCaptions` = `N` | - -```xml -1 -``` - -### release_date (Episode) - -Original date the episode was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ----------------------------- | -------- | -| `/package/video/release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -```xml -YYYY-MM-DD -``` - -### runtime - -Total runtime of the episode, in **whole minutes**. - -| XML XPath | Accepted Values | Required | -| ------------------------ | --------------- | -------- | -| `/package/video/runtime` | Integers only | Required | - -```xml -45 -``` - -### rating (Episode) - -Parental/content advisory rating from a rating source. A valid TV rating from the rating authority (`ratingSystem`) of the territory where the content will be available **must** be provided for each episode. If not rated by that territory's official authority, use a valid `USA_PR` rating instead, per [tvguidelines.org](http://tvguidelines.org/) guidelines (there is no official ratings body for `USA_PR`). - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/ratings/rating` (must include the `system` attribute) | See [rating values by system and country](#rating-values-by-rating-system-and-country). Multiple rating/rating-system pairs allowed. | Required | - -```xml - -PG-13 -12A -14A - -``` - -### tag (Episode) - -Freeform categorization field beyond Genre. Used by Roku's editorial team and recommendations engine to surface content. No limit on count; no defined tag set. **Case-sensitive** — deliver consistently. - -| XML XPath | Accepted Values | Required | -| ------------------------- | ------------------------------ | ------------------------------------ | -| `/package/video/tags/tag` | Any string under 50 characters | Optional, but **highly recommended** | - -```xml - - energy - dance - - -``` - -*** - -## Ad Breaks & Cue Points - -### adBreak start_time - -Used to determine [Ad Breaks for Ad Supported Content](#ad-breaks). Values **must** be accurate to the millisecond. If commercial blacks are present, provide the timecode at the **midpoint**. Not required for SVOD, but frame-accurate data can be ingested if available. - -| XML XPath | Accepted Values | Required | -| --------------------------------- | --------------- | -------------------------- | -| `/package/video/adBreaks/adBreak` | `HH:MM:SS.sss` | Preferred for AVOD content | - -```xml - - - 00:03:15.000 - - - 00:07:45.425 - - - -``` - -### cuePoint start_time and end_time - -Identifies in/out points of opening credits, recaps, end credits, and behind-the-scenes footage. `cuePoint` tags **must** include the `type` attribute. Values **must** be accurate to the millisecond. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | --------------- | --------- | -| `/package/video/cuePoints/cuePoint/start_time` | `HH:MM:SS.sss` | Preferred | -| `/package/video/cuePoints/cuePoint/end_time` | `HH:MM:SS.sss` | Preferred | - -```xml - - - 00:09:10.456 - 00:09:12.678 - - - 00:07:08.123 - 00:07:59.123 - - - 00:01:08.123 - 00:01:59.123 - - - 00:21:08.123 - 00:21:59.123 - - - 00:41:08.123 - 00:41:59.123 - - -``` - -### cuePoint type attribute - -Defines the type of a given `cuePoint`. Attribute name **must** be `type`. **For every type below: if providing that cuePoint, **`start_time`** and **`end_time`** are both required.** - -| Type Value | Description | -| ------------------- | --------------------------------------------------------------------------- | -| `ad overlay` | The point within the video for in-program product placement advertisements. | -| `behind the scenes` | Behind-the-scenes footage, typically at the tail of a video. | -| `intro` | The opening credits of the program. | -| `recap` | A recap of previous content, typically for episodic television. | -| `end` | The end credits of the program. | - -| XML XPath | Accepted Values | Required | -| ----------------------------------- | ----------------------- | ------------------------------- | -| `/package/video/cuePoints/cuePoint` | One of the values above | Required if providing cuePoints | - -```xml - -``` - -*** - -## Episode Cast & Crew - -### Episode cast display_name - -Name of a cast member for the episode. CDATA supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | -------- | -| `/package/video/cast/cast_member/display_name` | Firstname Lastname | Optional | - -```xml - - - - - - -``` - -### Episode crew display_name - -Name of a crew member for the episode. CDATA supported. - -> **Cross-format note:** Director is currently the **only** `crew_member` role supported for **Excel** ingest (this XML reference supports the full crew role list; the limitation is specific to the Excel delivery format). - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | ------------------------------------- | -| `/package/video/crew/crew_member/display_name` | Firstname Lastname | Required if providing a `crew_member` | - -```xml - -``` - -### Episode crew role - -Role of the crew member named in `display_name`. Every crew member **must** also include their role. See the [enumerated crew roles list](#crew-roles). **Roles are case-sensitive.** - -> **Cross-format note:** as above, Director is currently the only `crew_member` role supported for Excel ingest. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------- | ---------------------------------- | ------------------------------------- | -| `/package/video/crew/crew_member/roles/role` | See [enumerated list](#crew-roles) | Required if providing a `crew_member` | - -```xml -Director -``` - -*** - -## Episode Localizations - -### Episode localizations - -Begins the block providing localized episode metadata — language, translated title, `short_synopsis`, and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/localizations` | — | Required | - -```xml - -``` - -### Episode localization name attribute - -Defines the language of the localized fields within an episode `localization` block. Attribute name **must** be `name`; value must, at minimum, conform to a [supported language code](#language-codes) (region code recommended, e.g. `es-MX` vs. `es-ES`). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------- | --------------------------------------------------------------- | -------- | -| `/package/video/localizations/localization` | Valid [language code](#language-codes); may include region code | Required | - -```xml - -``` - -### Localized Episode Title - -Localized episode title. Same non-title-parenthetical restrictions as [Episode Title](#episode-title) above. **Must be accompanied by** localized `short_synopsis` and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | ----------------------- | -------- | -| `/package/video/localizations/localization/title` | Localized Episode Title | Required | - -```xml -<![CDATA[Localized Episode Title. Required.]]> -``` - -### Localized Episode short_synopsis - -CDATA supported. **250-character limit.** Must be accompanied by localized `title` and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/short_synopsis` | 250 characters | Required | - -```xml - -``` - -### Localized Episode long_synopsis - -CDATA supported. **500-character limit.** Must be accompanied by localized `title` and `short_synopsis`. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/long_synopsis` | 500 characters | Optional | - -```xml - -``` - -*** - -## Series Block - -### series - -Begins the block referencing metadata for the show to which the episode belongs. Roku follows the US definition of a series. Episodes nest as `series > season > episode`. - -| XML XPath | Example | Required | -| ----------------------- | ------- | -------- | -| `/package/video/series` | — | Required | - -```xml - -``` - -### series_id - -Immutable, unique identifier for a series. Generated/supplied by the partner; should match the Avails document ID. **50-character limit.** - -| XML XPath | Accepted Values | Required | -| --------------------------------- | ------------------------------------------------------------------------------ | -------- | -| `/package/video/series/series_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -```xml -seriesIdHere -``` - -### Series Title - -Title of the series. Include **only** the name as it should appear on platform — no non-title parentheticals. - -| XML XPath | Example | Required | -| ----------------------------- | ------------ | -------- | -| `/package/video/series/title` | Series Title | Required | - -```xml -<![CDATA[Series Title. Required.]]> -``` - -### Series short_synopsis - -CDATA supported. **250-character limit.** - -| XML XPath | Accepted Values | Required | -| -------------------------------------- | ---------------------- | -------- | -| `/package/video/series/short_synopsis` | 250-character synopsis | Required | - -```xml - -``` - -### Series long_synopsis - -CDATA supported. **500-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------------- | ---------------------- | -------- | -| `/package/video/series/long_synopsis` | 500-character synopsis | Optional | - -```xml - -``` - -### original_spoken_language - -Original production language of the series. At minimum, must conform to a [supported language code](#language-codes) (region code recommended). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------ | --------------------------------------------------------------- | -------- | -| `/package/video/series/original_spoken_language` | Valid [language code](#language-codes); may include region code | Required | - -```xml -en -``` - -### country_of_origin - -The primary country where the **series** was produced, and where the main creators, crew, and producers are established. Must conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) code. - -> _Corrected from the source, which referred to "the film" here — this field applies to the series, consistent with the rest of this block._ - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `/package/video/series/country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -```xml -US -``` - -### release_date (Series) - -Original date the series was first made available — typically the same date as the first episode. Must include an accurate **year of release** at minimum. - -| XML XPath | Accepted Values | Required | -| ------------------------------------ | ----------------------------- | -------- | -| `/package/video/series/release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -```xml -YYYY-MM-DD -``` - -### genre - -Genre classification. Each episode **must** be delivered with **at least one** supported genre via its series record. See the [enumerated genre list](#genres). - -| XML XPath | Accepted Values | Required | -| ------------------------------------ | ----------------------------------------------------------------- | -------- | -| `/package/video/series/genres/genre` | See [enumerated list](#genres). No more than 10 genres per title. | Required | - -```xml - - drama - - -``` - -### tag (Series) - -Freeform categorization field beyond Genre, same rules as [Episode tag](#tag-episode) above — case-sensitive, no limit, no defined set. - -| XML XPath | Accepted Values | Required | -| -------------------------------- | ------------------------------ | ------------------------------------ | -| `/package/video/series/tags/tag` | Any string under 50 characters | Optional, but **highly recommended** | - -```xml - - energy - dance - - -``` - -### Series cast display_name - -Name of a cast member of the series. CDATA supported. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------------- | ------------------ | -------- | -| `/package/video/series/cast/cast_member/display_name` | Firstname Lastname | Optional | - -```xml - - - - - - -``` - -### Series crew display_name - -Name of a crew member of the series. CDATA supported. - -> **Cross-format note:** Director is currently the only `crew_member` role supported for Excel ingest. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------------- | ------------------ | ------------------------------------- | -| `/package/video/series/crew/crew_member/display_name` | Firstname Lastname | Required if providing a `crew_member` | - -```xml - -``` - -### Series crew role - -Role of the crew member named in `display_name`. See the [enumerated crew roles list](#crew-roles). **Case-sensitive.** - -> **Cross-format note:** as above, Director is currently the only `crew_member` role supported for Excel ingest. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------- | ---------------------------------- | ------------------------------------- | -| `/package/video/series/crew/crew_member/roles/role` | See [enumerated list](#crew-roles) | Required if providing a `crew_member` | - -```xml -Director -``` - -### Series localizations - -Begins the block providing localized series metadata for multi-language packages. - -| XML XPath | Accepted Values | Required | -| ------------------------------------- | --------------- | -------- | -| `/package/video/series/localizations` | — | Required | - -```xml - -``` - -### Series localization name attribute - -Defines the language of localized fields within a series `localization` block. Attribute name **must** be `name`; value must, at minimum, conform to a [supported language code](#language-codes) (region code recommended). - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------- | --------------------------------------------------------------- | -------- | -| `/package/video/series/localizations/localization` | Valid [language code](#language-codes); may include region code | Required | - -```xml - -``` - -### Localized Series Title - -Localized series title. Same non-title-parenthetical restrictions as [Series Title](#series-title) above. **Must be accompanied by** localized `short_synopsis` and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | ---------------------- | -------- | -| `/package/video/series/localizations/localization/title` | Localized Series Title | Required | - -```xml -<![CDATA[Localized Series Title. Required.]]> -``` - -### Localized Series short_synopsis - -CDATA supported. **250-character limit.** Must be accompanied by localized `title` and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------------------------- | --------------- | -------- | -| `/package/video/series/localizations/localization/short_synopsis` | 250 characters | Required | - -```xml - -``` - -### Localized Series long_synopsis - -CDATA supported. **500-character limit.** Must be accompanied by localized `title` and `short_synopsis`. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------------- | --------------- | -------- | -| `/package/video/series/localizations/localization/long_synopsis` | 500 characters | Optional | - -```xml - -``` - -*** - -## Season Block - -### season - -Begins the block referencing metadata for the season of the series to which the episode belongs. Episodes nest as `series > season > episode`. - -| XML XPath | Example | Required | -| ----------------------- | ------- | -------- | -| `/package/video/season` | — | Required | - -```xml - -``` - -### season_id - -Immutable, unique identifier for a season. Generated/supplied by the partner; should match the Avails document ID. **50-character limit.** - -| XML XPath | Accepted Values | Required | -| --------------------------------- | ------------------------------------------------------------------------------ | -------- | -| `/package/video/season/season_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -```xml -seasonIdHere -``` - -### seasonNumber - -Numerical position of the season within the series — determines viewing order of underlying episodes. Values **must** reflect original broadcast/exhibition order. Integers only; **must not be 0.** - -| XML XPath | Accepted Values | Required | -| ------------------------------------ | ---------------------------- | -------- | -| `/package/video/season/seasonNumber` | Integers greater than 0 only | Required | - -```xml -2 -``` - -*** - -## Play Options / Availability - -### playOptions - -Begins the block providing availability information: country/territory availability, monetization type, and availability start/end dates. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | --------------- | -------- | -| `/package/video/playOptions` | — | Optional | - -```xml - -``` - -### country - -Country code of the territory where the content is available. Multiple `country` nodes allowed if `vodType`, `licensePeriodStart`, and `licensePeriodEnd` are identical across them. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | ---------------------- | --------- | -| `/package/video/playOptions/playOption/country` | `US`, `CA`, `GB`, `MX` | Preferred | - -```xml - - US - - -``` - -### vodType - -Monetization type of the episode. Multiple `vodType` nodes allowed if `country`, `licensePeriodStart`, and `licensePeriodEnd` are identical across them. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | --------------- | --------- | -| `/package/video/playOptions/playOption/vodType` | `AVOD`, `SVOD` | Preferred | - -```xml - - AVOD - - -``` - -### licensePeriodStart - -Start date of content availability. **One** per `playOption`. Must be chronologically **before** `licensePeriodEnd`; the two **must not** be identical. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | -------------------------------------- | -------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Optional | - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -### licensePeriodEnd - -End date of content availability. **One** per `playOption`. Must be chronologically **after** `licensePeriodStart`; the two **must not** be identical. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | -------------------------------------- | -------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Optional | - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -*** - -## Assets - -The `assets` block references every file delivered with the package (video, captions, audio, subtitles, artwork), described via `asset`/`data_file` pairs with attributes identifying type and role. - -### assets - -Begins the asset block. - -| XML XPath | Accepted Values | Required | -| ----------------------- | -------------------- | -------- | -| `/package/video/assets` | `media_type="video"` | Required | - -```xml - -``` - -### Full Source (Video) - -Describes the source video file. `asset type="full"`; `data_file role="source"`. `` and `` also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="source"` | Required | - -```xml - - -``` - -### Full Captions - -Describes closed captions for the source video file. `asset type="full"`; `data_file role="captions"`. `` and `` also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------ | -------------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="captions"` | Required in US | - -```xml - - -``` - -### Full Audio - -Describes sidecar audio for the source video file — either a full audio dub for language translation, or a descriptive audio track for accessibility. `asset type="full"`; `data_file role="audio"` (translation dub) or `role="audio description"` (accessibility). `` and `` also required. - -**Sidecar audio may be required** when localized assets are needed (source audio not native to the distribution territory) or to comply with FCC regulations. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="audio"` or `role="audio description"` | Optional\* — audio description strongly preferred | - -```xml - - -``` - -### Full Subtitles - -Describes sidecar subtitles for the source video file. `asset type="full"`; `data_file role="subtitles"`. `` and `` also required. - -**Sidecar subtitles may be required** when localized assets are needed (source audio not native to the distribution territory). - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="subtitles"` | Optional\* | - -```xml - - -``` - -### Forced Subtitles - -Describes sidecar forced narrative subtitles for the source video file. `asset type="full"`; `data_file role="forced subtitles"`. `` and `` also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | -------------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="forced subtitles"` | Optional\* | - -```xml - - -``` - -### Artwork - -Describes artwork file(s) at either the episode or series level. `asset type="artwork"`. `` and `` also required. See [Artwork](#artwork) for full image delivery specifications. - -**Confirmed:** the distinguishing attribute is `role` (`role="episode"` / `role="series"`), not `type`. The source document's prose describing this as a `type` attribute was inaccurate and has been corrected below. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | -------------------------------------------------- | --------- | -| `/package/video/assets/asset/data_file` | `asset type="artwork"`; `data_file role="episode"` | Preferred | -| `/package/video/assets/asset/data_file` | `asset type="artwork"`; `data_file role="series"` | Preferred | - -```xml - - -``` - -```xml - - -``` - -### locale - -Identifies the language of the `data_file`. At minimum, must conform to a [supported language code](#language-codes) (region code recommended). Applicable to `data_file` roles `source`, `captions`, `audio`, `subtitles`, and asset type `artwork`. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/locale` | [Supported language code](#language-codes) | Required | - -```xml - -``` - -### file_name - -Filename of the asset indicated by the enclosing `data_file`'s `role` or `type` attribute. All values are **case-sensitive** and **must** include the proper file extension. - -For artwork files specifically, the `file_name` tag's `type` attribute can be **omitted** (indicating **key art**), or set to `type="background_image"`, `type="boxcover"`, or `type="poster"`. - -| Asset Type | Required | -| --------------------------------------------------------------------------------- | --------------------------------- | -| Video / captions / audio / subtitles / forced subtitles (source assets generally) | Required for each asset delivered | -| Artwork — omitted attribute (key art) | Required | -| Artwork — `type="background_image"` | Preferred | -| Artwork — `type="boxcover"` | Preferred | -| Artwork — `type="poster"` | Preferred | - -```xml -VideoFilename.mxf -``` - -### audio - -[Audio layout descriptor](#audio-channel-layout-hints) for the delivered video file. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ------------------------------------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/audio` | `stereoOnly`, `surroundOnly`, `stereoPlusSurround`, `surroundPlusStereo` | Optional | - -```xml - -``` \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-film-metadata-fields.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-film-metadata-fields.md deleted file mode 100644 index 4284558e..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-film-metadata-fields.md +++ /dev/null @@ -1,687 +0,0 @@ ---- -title: XML - film metadata fields -excerpt: Field-by-field XML reference for Film content delivery. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field XML reference for the **Film** content type. For the schema download and annotated sample, see the [Roku XML Metadata Overview](#roku-xml-metadata-overview). For general metadata concepts (content type definitions, ID rules, availability windows) that apply across all content types, see the [Metadata Overview](#roku-metadata-overview). - -Fields are grouped below into: **Package Info**, **Content Descriptors**, **Ad Breaks & Cue Points**, **Cast & Crew**, **Localizations**, **Play Options / Availability**, and **Assets**. - -*** - -## Package Info - -### package - -Defines the package version type. - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/@version` | `film5.0` | Required | - -```xml - -``` - -### provider - -Name of the content owner/studio/network. - -| XML XPath | Example | Required | -| ------------------- | -------------- | -------- | -| `/package/provider` | Roku Originals | Required | - -```xml -Roku Originals -``` - -### language - -Primary language of the package metadata. At minimum, the value **must** conform to a supported [language code](#language-codes). As a best practice, **include a region code** as well — e.g., to distinguish Spanish spoken in Mexico (`es-MX`) from Spanish spoken in Spain (`es-ES`). - -| XML XPath | Accepted Values | Required | -| ------------------- | ------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/language` | Valid [language value](#language-codes) (`en`, `es`, etc.); may include region code (`en-US`, `es-MX`, etc.) | Required | - -```xml -en -``` - -### type - -Defines the content type of the package. - -| XML XPath | Accepted Values | Required | -| --------------------- | --------------- | -------- | -| `/package/video/type` | `film` | Required | - -```xml -film -``` - -### asset_id - -Immutable, unique identifier for a movie. IDs are generated and supplied **by the partner**. The ID in the ingest metadata **should** match the ID provided in the Avails document — this aids tracking across Roku's pipeline, from Avails submission through publication. **50-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------- | ------------------------------------------------------------------------------ | -------- | -| `/package/video/asset_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -```xml -movieAssetIdHere -``` - -### eidr - -EIDR ID, if one exists. - -| XML XPath | Accepted Values | Required | -| --------------------- | ----------------- | -------- | -| `/package/video/eidr` | Any valid EIDR ID | Optional | - -```xml - -``` - -### tmsId - -Gracenote ID, if one exists. - -| XML XPath | Accepted Values | Required | -| ---------------------- | ---------------- | -------- | -| `/package/video/tmsId` | Any valid TMS ID | Optional | - -```xml - -``` - -*** - -## Content Descriptors - -### title - -Title of the movie. Include **only** the name of the content as it should appear on platform — do **not** include non-title parentheticals such as an original/remake indicator, year of release, season, or video format (e.g., `(Classic)`, `(1987)`, `(Season 1)`, `(HD)`). - -| XML XPath | Example | Required | -| ---------------------- | ----------- | -------- | -| `/package/video/title` | Movie Title | Required | - -```xml -<![CDATA[Movie Title. Required.]]> -``` - -### short_synopsis - -A short synopsis of the content. CDATA supported. **250-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------- | ---------------------- | -------- | -| `/package/video/short_synopsis` | 250-character synopsis | Required | - -```xml - -``` - -### long_synopsis - -A long synopsis of the content. CDATA supported. **500-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------ | ---------------------- | -------- | -| `/package/video/long_synopsis` | 500-character synopsis | Optional | - -```xml - -``` - -### original_spoken_language - -The original production language of the title. At minimum, the value **must** conform to a [supported language code](#language-codes). As a best practice, **include a region code** as well (see [language](#language) above for the `es-MX` / `es-ES` example). - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | ----------------------------------------------------------------------------------- | -------- | -| `/package/video/original_spoken_language` | Valid [language value](#language-codes) (`en`, `es`, etc.); may include region code | Required | - -```xml -en -``` - -### country_of_origin - -The primary country where the film was produced and where the main creators, crew, and producers are established. Value **must** conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) 2-character country code. - -| XML XPath | Accepted Values | Required | -| ---------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `/package/video/country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -```xml -US -``` - -### closedCaptions - -Indicates whether the delivered title contains closed captions. **Required for all content intended for Roku Channel in the US.** - -| XML XPath | Accepted Values | Required | -| ------------------------------- | --------------- | ----------------------- | -| `/package/video/closedCaptions` | `Y` or `N` | Required for US content | - -```xml -Y -``` - -### closedCaptionsExemption - -FCC exemption code for the closed caption requirement. **Required if **`closedCaptions`** = **`N`**.** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------------------- | ---------------------------------- | -| `/package/video/closedCaptionsExemption` | `1`, `2`, `3`, `4`, `5`, `6` | Required if `closedCaptions` = `N` | - -```xml -1 -``` - -### release_date - -Original date the content was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ----------------------------- | -------- | -| `/package/video/release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -```xml -YYYY-MM-DD -``` - -### runtime - -Total runtime of the content, in **whole minutes**. - -| XML XPath | Accepted Values | Required | -| ------------------------ | --------------- | -------- | -| `/package/video/runtime` | Integers only | Required | - -```xml -120 -``` - -### genre - -Genre classification of the content. Each movie **must** be delivered with **at least one** supported genre. See the [enumerated genre list](#genres). - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ----------------------------------------------------------------- | -------- | -| `/package/video/genres/genre` | See [enumerated list](#genres). No more than 10 genres per title. | Required | - -```xml - - drama - - -``` - -### rating - -Parental/content advisory rating from a rating source. A valid movie or TV rating from the rating authority (`ratingSystem`) of the territory where the content will be available **must** be provided for each movie. If the title hasn't been rated by that territory's official authority, include a valid rating from the `USA_PR` rating system instead — there is no official ratings body for `USA_PR`; use the guidelines at [tvguidelines.org](http://tvguidelines.org/) to assign the appropriate rating. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/ratings/rating` (must include the `system` attribute) | See [rating values by system and country](#rating-values-by-rating-system-and-country). Multiple rating/rating-system pairs allowed. | Required | - -```xml - - PG-13 - 12A - 14A - -``` - -### tag - -A freeform field for categorizing content beyond the limited set of supported Genre values. Roku's editorial team and recommendations engine use Tags to help surface content in the platform UI — more tags generally means more ways content can be curated/surfaced. There is **no limit** on the number of tags and **no defined/enumerated tag set**. - -- Tags are **case-sensitive** — `"Rom-Com"` and `"rom-com"` are two distinct tags. Deliver tags **consistently**. - -| XML XPath | Accepted Values | Required | -| ------------------------- | ------------------------------ | ------------------------------------ | -| `/package/video/tags/tag` | Any string under 50 characters | Optional, but **highly recommended** | - -```xml - - energy - dance - - -``` - -*** - -## Ad Breaks & Cue Points - -### adBreak start_time - -Used to determine [Ad Breaks for Ad Supported Content](#ad-breaks). Values **must** be accurate to the millisecond. If the video includes commercial blacks, provide the timecode at the **midpoint** of the commercial black. Not required for SVOD content, but frame-accurate adBreak data can be ingested if available. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------- | --------------- | -------------------------- | -| `/package/video/adBreaks/adBreak/start_time` | `HH:MM:SS.sss` | Preferred for AVOD content | - -```xml - - - 00:03:15.000 - - - 00:07:45.425 - - - -``` - -### cuePoint start_time and end_time - -Used to identify the in/out points of opening credits, content recaps, end credits, and behind-the-scenes footage. `cuePoint` tags **must** include the `type` attribute. Values **must** be accurate to the millisecond. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | --------------- | --------- | -| `/package/video/cuePoints/cuePoint/start_time` | `HH:MM:SS.sss` | Preferred | -| `/package/video/cuePoints/cuePoint/end_time` | `HH:MM:SS.sss` | Preferred | - -```xml - - - 00:09:10.456 - 00:09:12.678 - - - 00:07:08.123 - 00:07:59.123 - - - 00:01:08.123 - 00:01:59.123 - - - 00:21:08.123 - 00:21:59.123 - - - 00:41:08.123 - 00:41:59.123 - - -``` - -### cuePoint type attribute - -Defines the type of a given `cuePoint`. The attribute name **must** be `type`, with one of the following values. **For every type below: if providing that cuePoint, **`start_time`** and **`end_time`** are both required.** - -| Type Value | Description | -| ------------------- | --------------------------------------------------------------------------- | -| `ad overlay` | The point within the video for in-program product placement advertisements. | -| `behind the scenes` | Behind-the-scenes footage, typically at the tail of a video. | -| `intro` | The opening credits of the program. | -| `recap` | A recap of previous content, typically for episodic television. | -| `end` | The end credits of the program. | - -| XML XPath | Accepted Values | Required | -| ----------------------------------- | ----------------------- | ------------------------------- | -| `/package/video/cuePoints/cuePoint` | One of the values above | Required if providing cuePoints | - -```xml - -``` - -*** - -## Cast & Crew - -### cast display_name - -Name of a cast member. CDATA supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | -------- | -| `/package/video/cast/cast_member/display_name` | Firstname Lastname | Optional | - -```xml - - - - - - -``` - -### crew display_name - -Name of a crew member. CDATA supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | ------------------------------------- | -| `/package/video/crew/crew_member/display_name` | Firstname Lastname | Required if providing a `crew_member` | - -```xml - -``` - -> **Cross-format note:** Director is currently the **only** `crew_member` role supported for **Excel** ingest (this XML reference supports the full crew role list below; the limitation is specific to the Excel delivery format). - -### role - -Role of the crew member named in `display_name`. Every crew member included **must** also include their role. See the [enumerated crew roles list](#crew-roles). **Roles are case-sensitive.** - -> **Cross-format note:** as above, Director is currently the only `crew_member` role supported for Excel ingest. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------- | ---------------------------------- | ------------------------------------- | -| `/package/video/crew/crew_member/roles/role` | See [enumerated list](#crew-roles) | Required if providing a `crew_member` | - -```xml -Director -``` - -*** - -## Localizations - -### localizations - -Begins the block providing localized metadata for multi-language packages — language, translated title, `short_synopsis`, and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/localizations` | — | Required | - -```xml - -``` - -### localization name attribute - -Defines the language of the localized fields within a `localization` block. The attribute name **must** be `name`, and its value **must**, at minimum, conform to a [supported language code](#language-codes) — include a region code as a best practice (see [language](#language) above). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------- | --------------------------------------------------------------- | -------- | -| `/package/video/localizations/localization` | Valid [language code](#language-codes); may include region code | Required | - -```xml - -``` - -### localized title - -Localized title of the movie, in the language specified by the enclosing `localization` block's `name` attribute. Same non-title-parenthetical restrictions as [title](#title) above. **Must be accompanied by** a localized `short_synopsis` and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | --------------------- | -------- | -| `/package/video/localizations/localization/title` | Localized Movie Title | Required | - -```xml -<![CDATA[Localized Movie Title. Required.]]> -``` - -### localized short_synopsis - -Localized short synopsis, in the language specified by the enclosing `localization` block. CDATA supported. **250-character limit.** Must be accompanied by localized `title` and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/short_synopsis` | 250 characters | Required | - -```xml - -``` - -### localized long_synopsis - -Localized long synopsis, in the language specified by the enclosing `localization` block. CDATA supported. **500-character limit.** Must be accompanied by localized `title` and `short_synopsis`. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/long_synopsis` | 500 characters | Optional | - -```xml - -``` - -*** - -## Play Options / Availability - -### playOptions - -Begins the block providing availability information for the package: country/territory availability, monetization type, and availability start/end dates. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | --------------- | -------- | -| `/package/video/playOptions` | — | Optional | - -```xml - -``` - -### country - -Country code of the territory where the content is available. Multiple `country` nodes are allowed, provided `vodType`, `licensePeriodStart`, and `licensePeriodEnd` are identical across them. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | ---------------------- | --------- | -| `/package/video/playOptions/playOption/country` | `US`, `CA`, `GB`, `MX` | Preferred | - -```xml - - US - - -``` - -### vodType - -Monetization type of the movie. Multiple `vodType` nodes are allowed, provided `country`, `licensePeriodStart`, and `licensePeriodEnd` are identical across them. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | --------------- | --------- | -| `/package/video/playOptions/playOption/vodType` | `AVOD`, `SVOD` | Preferred | - -```xml - - AVOD - - -``` - -### licensePeriodStart - -Start date of content availability to Roku Channel users. **One** `licensePeriodStart` per `playOption`. Must be chronologically **before** `licensePeriodEnd`; the two **must not** be identical. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | -------------------------------------- | -------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Optional | - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -### licensePeriodEnd - -End date of content availability to Roku Channel users. **One** `licensePeriodEnd` per `playOption`. Must be chronologically **after** `licensePeriodStart`; the two **must not** be identical. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | -------------------------------------- | -------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Optional | - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -*** - -## Assets - -The `assets` block references every file delivered as part of the package (video, captions, audio, subtitles, artwork). Each individual file is described by an `asset`/`data_file` pair, with attributes identifying the asset's type and role. - -### assets - -Begins the asset block. - -| XML XPath | Accepted Values | Required | -| ----------------------- | -------------------- | -------- | -| `/package/video/assets` | `media_type="video"` | Required | - -```xml - -``` - -### Full Source (Video) - -Describes the source video file. The `asset` tag's attribute must be `type="full"`, and the `data_file` tag's attribute must be `role="source"`. `` and `` are also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="source"` | Required | - -```xml - - -``` - -### Full Captions - -Describes closed captions for the source video file. `asset type="full"`; `data_file role="captions"`. `` and `` are also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------ | -------------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="captions"` | Required in US | - -```xml - - -``` - -### Full Audio - -Describes sidecar audio for the source video file — either a full audio dub for language translation, or a descriptive audio track for accessibility. `asset type="full"`; `data_file role="audio"` (translation dub) or `role="audio description"` (accessibility). `` and `` are also required. - -**Sidecar audio may be required** when localized assets are needed (i.e., the source's original audio is not native to the distribution territory) or when complying with FCC regulations. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="audio"` or `role="audio description"` | Optional\* — audio description strongly preferred | - -```xml - - -``` - -### Full Subtitles - -Describes sidecar subtitles for the source video file. `asset type="full"`; `data_file role="subtitles"`. `` and `` are also required. - -**Sidecar subtitles may be required** when localized assets are needed (i.e., the source's original audio is not native to the distribution territory). - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="subtitles"` | Optional\* | - -```xml - - -``` - -### Forced Subtitles - -Describes sidecar forced narrative subtitles for the source video file. `asset type="full"`; `data_file role="forced subtitles"`. `` and `` are also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | -------------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="forced subtitles"` | Optional\* | - -```xml - - -``` - -### Artwork - -Describes artwork file(s). `asset type="artwork"`. `` and `` are also required. See [Artwork](#artwork) for full image delivery specifications. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------- | -------- | -| `/package/video/assets/asset/data_file` | `asset type="artwork"` | Required | - -```xml - - - - - - - - - - - -``` - -> **Confirmed:** the unlabeled/default `file_name` (no `type` attribute) is understood to represent **key art** — this is expected behavior, not a gap. Explicit `type` values are only needed for `background_image`, `boxcover`, and `poster`. - -### locale - -Identifies the language of the `data_file`. At minimum, the value **must** conform to a [supported language code](#language-codes); include a region code as a best practice. Applicable to `data_file` roles `source`, `captions`, `audio`, `subtitles`, and asset type `artwork`. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/locale` | [Supported language code](#language-codes) | Required | - -```xml - -``` - -### file_name - -Filename of the asset indicated by the enclosing `data_file`'s `role` or `type` attribute. All `file_name` values are **case-sensitive** and **must** include the proper file extension. - -| Asset Type | Required | -| --------------------------------------------------------------------------------- | --------------------------------- | -| Video / captions / audio / subtitles / forced subtitles (source assets generally) | Required for each asset delivered | -| Artwork — default/unlabeled | Required | -| Artwork — `type="background_image"` | Preferred | -| Artwork — `type="boxcover"` | Preferred | -| Artwork — `type="poster"` | Preferred | - -```xml -VideoFilename.mxf -``` - -### audio - -[Audio layout descriptor](#audio-channel-layout-hints) for the delivered video file. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ------------------------------------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/audio` | `stereoOnly`, `surroundOnly`, `stereoPlusSurround`, `surroundPlusStereo` | Optional | - -```xml - -``` \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-shortform-clip-metadata-fields.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-shortform-clip-metadata-fields.md deleted file mode 100644 index 71578f8d..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/metadata/xml-metadata/xml-shortform-clip-metadata-fields.md +++ /dev/null @@ -1,785 +0,0 @@ ---- -title: XML - shortForm clip metadata fields -excerpt: Field-by-field XML reference for Clip content delivery. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field XML reference for the **Clip** content type — short-form, stand-alone or ancillary titles (see [Content Type Definitions](#content-type-definitions)). For the schema download and annotated sample, see the [Roku XML Metadata Overview](#roku-xml-metadata-overview). - -Clips support two optional feature sets not present in Film/TV: `subType`**/**`parentInfo` (identifying a clip as ancillary to a parent program) and **sports metadata** (`sportType`, `sportLeague`, `teams`). - -Fields are grouped into: **Package Info**, **Content Descriptors**, **Cast & Crew**, **Localizations**, **Play Options / Availability**, **Assets**, **Parent Info**, and **Sports Metadata**. - -*** - -## Package Info - -### package - -Defines the package version type. - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/@version` | `clip1.0` | Required | - -```xml - -``` - -### provider - -Name of the content owner/studio/network. - -| XML XPath | Accepted Values | Required | -| ------------------- | --------------- | -------- | -| `/package/provider` | Roku Originals | Required | - -```xml -Roku Originals -``` - -### language - -Primary language of the package metadata. At minimum, must conform to a [supported language code](#language-codes). Best practice: include a region code (e.g., `es-MX` vs. `es-ES`). - -| XML XPath | Accepted Values | Required | -| ------------------- | -------------------------------------- | -------- | -| `/package/language` | [Valid language code](#language-codes) | Required | - -```xml -en -``` - -### type - -Defines the content type of the package. - -| XML XPath | Accepted Values | Required | -| --------------------- | --------------- | -------- | -| `/package/video/type` | `clip` | Required | - -```xml -clip -``` - -### subType - -Defines the content sub-type of the package. Roku does **not** currently support native parent/child connections — ancillary or related content can be identified using one of the sub-types below, but **there is no system-level link created between the parent and child asset**. (See [Parent Info](#parent-info) below for how descriptive, non-linking context about a parent program can still be provided.) - -| XML XPath | Accepted Values | Required | -| ------------------------ | ---------------------------------------------------------------------------------------------- | -------- | -| `/package/video/subType` | `trailer`, `highlight`, `making_of`, `behind_scenes`, `interview`, `related`, `recap`, `extra` | Optional | - -```xml -trailer -``` - -### asset_id - -Immutable, unique identifier for a shortForm clip. Generated/supplied by the partner; should match the Avails document ID, to aid tracking across Roku's pipeline. **50-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------- | ------------------------------------------------------------------------------ | -------- | -| `/package/video/asset_id` | Alphanumeric characters, hyphens, and underscores only. 50 characters maximum. | Required | - -```xml -clipAssetIdHere -``` - -### eidr - -EIDR ID, if one exists. - -| XML XPath | Accepted Values | Required | -| --------------------- | ----------------- | -------- | -| `/package/video/eidr` | Any valid EIDR ID | Optional | - -```xml - -``` - -### tmsId - -Gracenote ID, if one exists. - -| XML XPath | Accepted Values | Required | -| ---------------------- | ---------------- | -------- | -| `/package/video/tmsId` | Any valid TMS ID | Optional | - -```xml - -``` - -*** - -## Content Descriptors - -### title - -Title of the shortForm clip. Include **only** the name as it should appear on platform — no non-title parentheticals (e.g., `(Classic)`, `(1987)`, `(Season 1)`, `(HD)`). - -| XML XPath | Example | Required | -| ---------------------- | ---------- | -------- | -| `/package/video/title` | Clip Title | Required | - -```xml -<![CDATA[Clip Title. Required.]]> -``` - -### short_synopsis - -A short synopsis of the content. CDATA supported. **250-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------- | ---------------------- | -------- | -| `/package/video/short_synopsis` | 250-character synopsis | Required | - -```xml - -``` - -### long_synopsis - -A long synopsis of the content. CDATA supported. **500-character limit.** - -| XML XPath | Accepted Values | Required | -| ------------------------------ | ---------------------- | -------- | -| `/package/video/long_synopsis` | 500-character synopsis | Optional | - -```xml - -``` - -### original_spoken_language - -Original production language of the title. At minimum, must conform to a [supported language code](#language-codes) (region code recommended). - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | --------------------------------------------------------------- | -------- | -| `/package/video/original_spoken_language` | Valid [language code](#language-codes); may include region code | Required | - -```xml -en -``` - -### country_of_origin - -The primary country where the clip was produced, and where the main creators, crew, and producers are established. Must conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) code. - -| XML XPath | Accepted Values | Required | -| ---------------------------------- | -------------------------------------------------------------------------------------------------------- | --------- | -| `/package/video/country_of_origin` | Valid 2-character country code per [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) | Preferred | - -```xml -US -``` - -### closedCaptions - -Indicates whether the delivered title contains closed captions. **Required for all content intended for Roku Channel in the US.** - -| XML XPath | Accepted Values | Required | -| ------------------------------- | --------------- | ----------------------- | -| `/package/video/closedCaptions` | `Y` or `N` | Required for US content | - -```xml -Y -``` - -### closedCaptionsExemption - -FCC exemption code for the closed caption requirement. **Required if **`closedCaptions`** = **`N`**.** - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from caption requirements for this content. | - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------------------- | ---------------------------------- | -| `/package/video/closedCaptionsExemption` | `1`, `2`, `3`, `4`, `5`, `6` | Required if `closedCaptions` = `N` | - -```xml -1 -``` - -### release_date - -Original date the content was first made available in any presentation. Must include an accurate **year of release** at minimum. - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ----------------------------- | -------- | -| `/package/video/release_date` | ISO 8601 format: `YYYY-MM-DD` | Required | - -```xml -YYYY-MM-DD -``` - -### runtime - -Total runtime of the content, in **whole minutes**. - -| XML XPath | Accepted Values | Required | -| ------------------------ | --------------- | -------- | -| `/package/video/runtime` | Integers only | Required | - -```xml -3 -``` - -### genre - -Genre classification of the content. Each shortForm clip **must** be delivered with **at least one** supported genre. See the [enumerated genre list](#genres). - -| XML XPath | Accepted Values | Required | -| ----------------------------- | ----------------------------------------------------------------- | -------- | -| `/package/video/genres/genre` | See [enumerated list](#genres). No more than 10 genres per title. | Required | - -```xml - - drama - - -``` - -### rating - -Parental/content advisory rating from a rating source. A valid movie or TV rating from the rating authority (`ratingSystem`) of the territory where the content will be available **must** be provided for each shortForm clip. If not rated by that territory's official authority, use a valid `USA_PR` rating instead, per [tvguidelines.org](http://tvguidelines.org/) guidelines (there is no official ratings body for `USA_PR`). - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------- | -| `/package/video/ratings/rating` (must include the `system` attribute) | See [rating values by system and country](#rating-values-by-rating-system-and-country). Multiple rating/rating-system pairs allowed. | Required | - -```xml - - PG-13 - 12A - 14A - -``` - -### tag - -Freeform categorization field beyond Genre. Used by Roku's editorial team and recommendations engine to surface content. No limit on count; no defined tag set. **Case-sensitive** — deliver consistently. - -| XML XPath | Accepted Values | Required | -| ------------------------- | ------------------------------ | ------------------------------------ | -| `/package/video/tags/tag` | Any string under 50 characters | Optional, but **highly recommended** | - -```xml - - energy - dance - - -``` - -*** - -## Cast & Crew - -### cast display_name - -Name of a cast member. CDATA supported. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | -------- | -| `/package/video/cast/cast_member/display_name` | Firstname Lastname | Optional | - -```xml - - - - - - -``` - -### crew display_name - -Name of a crew member. CDATA supported. - -> **Cross-format note:** Director is currently the **only** `crew_member` role supported for **Excel** ingest (this XML reference supports the full crew role list; the limitation is specific to the Excel delivery format). - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------ | ------------------------------------- | -| `/package/video/crew/crew_member/display_name` | Firstname Lastname | Required if providing a `crew_member` | - -```xml - -``` - -### role - -Role of the crew member named in `display_name`. Every crew member **must** also include their role. See the [enumerated crew roles list](#crew-roles). **Roles are case-sensitive.** - -> **Cross-format note:** as above, Director is currently the only `crew_member` role supported for Excel ingest. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------- | ---------------------------------- | ------------------------------------- | -| `/package/video/crew/crew_member/roles/role` | See [enumerated list](#crew-roles) | Required if providing a `crew_member` | - -```xml -Director -``` - -*** - -## Localizations - -### localizations - -Begins the block providing localized metadata for multi-language packages — language, translated title, `short_synopsis`, and `long_synopsis`. - -| XML XPath | Accepted Values | Required | -| ------------------------------ | --------------- | -------- | -| `/package/video/localizations` | — | Required | - -```xml - -``` - -### localization name attribute - -Defines the language of the localized fields within a `localization` block. Attribute name **must** be `name`; value must, at minimum, conform to a [supported language code](#language-codes) (region code recommended). - -| XML XPath | Accepted Values | Required | -| ------------------------------------------- | --------------------------------------------------------------- | -------- | -| `/package/video/localizations/localization` | Valid [language code](#language-codes); may include region code | Required | - -```xml - -``` - -### localized title - -Localized title of the shortForm clip. Same non-title-parenthetical restrictions as [title](#title) above. - -| XML XPath | Example | Required | -| ------------------------------------------------- | -------------------- | -------- | -| `/package/video/localizations/localization/title` | Localized Clip Title | Required | - -```xml -<![CDATA[Localized Clip Title. Required.]]> -``` - -### localized short_synopsis - -CDATA supported. **250-character limit.** - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/short_synopsis` | 250 characters | Required | - -```xml - -``` - -### localized long_synopsis - -CDATA supported. **500-character limit.** - -| XML XPath | Accepted Values | Required | -| --------------------------------------------------------- | --------------- | -------- | -| `/package/video/localizations/localization/long_synopsis` | 500 characters | Optional | - -```xml - -``` - -*** - -## Play Options / Availability - -### playOptions - -Begins the block providing availability information: country/territory availability, monetization type, and availability start/end dates. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | --------------- | -------- | -| `/package/video/playOptions` | — | Required | - -```xml - -``` - -### country - -Country code of the territory where the content is available. Multiple `country` nodes allowed if `vodType`, `licensePeriodStart`, and `licensePeriodEnd` are identical across them. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | ---------------------- | --------- | -| `/package/video/playOptions/playOption/country` | `US`, `CA`, `GB`, `MX` | Preferred | - -```xml - - US - - -``` - -### vodType - -Monetization type of the shortForm clip. Multiple `vodType` nodes allowed if `country`, `licensePeriodStart`, and `licensePeriodEnd` are identical across them. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------------- | --------------- | --------- | -| `/package/video/playOptions/playOption/vodType` | `AVOD`, `SVOD` | Preferred | - -```xml - - AVOD - - -``` - -### licensePeriodStart - -Start date of content availability. **One** per `playOption`. Must be chronologically **before** `licensePeriodEnd`; the two **must not** be identical. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------------------- | -------------------------------------- | -------- | -| `/package/video/playOptions/playOption/licensePeriodStart` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Optional | - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -### licensePeriodEnd - -End date of content availability. **One** per `playOption`. Must be chronologically **after** `licensePeriodStart`; the two **must not** be identical. - -| XML XPath | Accepted Values | Required | -| -------------------------------------------------------- | -------------------------------------- | -------- | -| `/package/video/playOptions/playOption/licensePeriodEnd` | ISO 8601 format: `YYYY-MM-DDTHH:MM:SS` | Optional | - -```xml - - YYYY-MM-DDTHH:MM:SS - -``` - -*** - -## Assets - -The `assets` block references every file delivered as part of the package (video, captions, audio, subtitles, artwork), each described by an `asset`/`data_file` pair. - -### assets - -Begins the asset block. - -| XML XPath | Accepted Values | Required | -| ----------------------- | -------------------- | -------- | -| `/package/video/assets` | `media_type="video"` | Required | - -```xml - -``` - -### Full Source (Video) - -Describes the source video file. `asset type="full"`; `data_file role="source"`. `` and `` also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------------------------------- | -------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="source"` | Required | - -```xml - - -``` - -### Full Captions - -Describes closed captions for the source video file. `asset type="full"`; `data_file role="captions"`. `` and `` also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------ | -------------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="captions"` | Required in US | - -```xml - - -``` - -### Full Audio - -Describes sidecar audio for the source video file — either a full audio dub for language translation, or a descriptive audio track for accessibility. `asset type="full"`; `data_file role="audio"` (translation dub) or `role="audio description"` (accessibility). `` and `` also required. - -**Sidecar audio may be required** when localized assets are needed (source audio not native to the distribution territory) or to comply with FCC regulations. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="audio"` or `role="audio description"` | Optional\* — audio description strongly preferred | - -```xml - - -``` - -### Full Subtitles - -Describes sidecar subtitles for the source video file. `asset type="full"`; `data_file role="subtitles"`. `` and `` also required. - -**Sidecar subtitles may be required** when localized assets are needed (source audio not native to the distribution territory). - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="subtitles"` | Optional\* | - -```xml - - -``` - -### Forced Subtitles - -Describes sidecar forced narrative subtitles for the source video file. `asset type="full"`; `data_file role="forced subtitles"`. `` and `` also required. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | -------------------------------------------------------- | ---------- | -| `/package/video/assets/asset/data_file` | `asset type="full"`; `data_file role="forced subtitles"` | Optional\* | - -```xml - - -``` - -### Artwork - -Describes the artwork file(s). `asset type="artwork"`. `` and `` also required. See [Artwork](#artwork) for full image delivery specifications. - -> **Note:** unlike Film and TV, Clip artwork does not break out into `background_image`/`boxcover`/`poster` variants here — this is consistent with the [Artwork Specification](#), where Clips require only a single 16:9 Key Art image type. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------- | -------- | -| `/package/video/assets/asset/data_file` | `asset type="artwork"` | Required | - -```xml - - -``` - -### locale - -Identifies the language of the `data_file`. At minimum, must conform to a [supported language code](#language-codes) (region code recommended). Applicable to `data_file` roles `source`, `captions`, `audio`, and `subtitles`, and asset type `artwork`. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------------- | ------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/locale` | [Supported language code](#language-codes) | Required | - -```xml - -``` - -### file_name - -Filename of the asset indicated by the enclosing `data_file`'s `role` or `type` attribute. All values are **case-sensitive** and **must** include the proper file extension. - -| XML XPath | Accepted Values | Required | -| ------------------------------------------------- | ------------------------------------------------------ | --------------------------------- | -| `/package/video/assets/asset/data_file/file_name` | See guidelines above for asset delivery specifications | Required for each asset delivered | - -```xml -VideoFilename.mxf -``` - -### audio - -[Audio layout descriptor](#audio-channel-layout-hints) for the delivered video file. - -| XML XPath | Accepted Values | Required | -| --------------------------------------------- | ------------------------------------------------------------------------ | -------- | -| `/package/video/assets/asset/data_file/audio` | `stereoOnly`, `surroundOnly`, `stereoPlusSurround`, `surroundPlusStereo` | Optional | - -```xml - -``` - -*** - -## Parent Info - -`parentInfo` provides **descriptive, contextual** metadata about the program a clip is derived from or related to — used in combination with a valid [`subType`](#subtype) value above. **This is descriptive metadata only; it does not create a navigable link or on-platform relationship** between the clip and its parent (consistent with the `subType` note above that Roku does not natively support parent/child connections). - -### parentInfo - -Begins the block providing parent information for the package. - -| XML XPath | Accepted Values | Required | -| --------------------------- | --------------- | -------- | -| `/package/video/parentInfo` | — | Optional | - -```xml - -``` - -### parent contentType - -Content type of the parent the clip is derived from or describes. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ---------------------------- | -------- | -| `/package/video/parentInfo/contentType` | `episode`, `movie`, `series` | Optional | - -```xml - - episode - -``` - -### parent title - -Title of the parent program, if the parent is a movie or episode. - -| XML XPath | Accepted Values | Required | -| --------------------------------- | ------------------------------- | -------- | -| `/package/video/parentInfo/title` | Title of Parent Movie or Series | Optional | - -```xml - - Title of Parent Movie or Series - -``` - -### parent runtime - -Runtime of the parent program, if the parent is a movie or episode. - -| XML XPath | Accepted Values | Required | -| ----------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/runtime` | Integer | Optional | - -```xml - - 45 - -``` - -### parent releaseDate - -Release date of the parent movie, episode, or series. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ----------------------------- | -------- | -| `/package/video/parentInfo/releaseDate` | ISO 8601 format: `YYYY-MM-DD` | Optional | - -```xml - - YYYY-MM-DD - -``` - -### parent tmsId - -TMS ID of the parent movie, episode, or series. - -| XML XPath | Accepted Values | Required | -| --------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/tmsId` | Valid TMS ID | Optional | - -```xml - - TMSID - -``` - -### parent seriesTitle - -Series title of the parent program, if the parent is an episode. - -| XML XPath | Accepted Values | Required | -| --------------------------------------- | ------------------- | -------- | -| `/package/video/parentInfo/seriesTitle` | Parent Series Title | Optional | - -```xml - - Parent Series Title - -``` - -### parent seasonNumber - -Season number of the parent program, if the parent is an episode. - -| XML XPath | Accepted Values | Required | -| ---------------------------------------- | ---------------------- | -------- | -| `/package/video/parentInfo/seasonNumber` | Integer greater than 0 | Optional | - -```xml - - 2 - -``` - -### parent episodeNumber - -Episode number of the parent program, if the parent is an episode. - -| XML XPath | Accepted Values | Required | -| ----------------------------------------- | --------------- | -------- | -| `/package/video/parentInfo/episodeNumber` | Integer | Optional | - -```xml - - 14 - -``` - -*** - -## Sports Metadata - -The following fields are **required specifically for sports clips**. - -### sportType - -Name of the sport featured in the clip/highlight. - -| XML XPath | Accepted Values | Required | -| -------------------------- | ----------------- | ------------------------- | -| `/package/video/sportType` | Name of the sport | Required for sports clips | - -```xml -Baseball -``` - -### sportLeague - -Name of the sport league featured in the clip/highlight. - -| XML XPath | Accepted Values | Required | -| ---------------------------- | ------------------------ | ------------------------- | -| `/package/video/sportLeague` | Name of the sport league | Required for sports clips | - -```xml -MLB -``` - -### teams - -Teams featured in the sport clip/highlight. Home and away teams are defined via the `location` attribute. - -> **Note:** at this time, Roku only supports **team-based** participant metadata. Individual/solo sports (e.g., tennis, golf) will be supported at a later date. - -| XML XPath | Accepted Values | Required | -| --------------------------- | ---------------------------------------------- | ------------------------- | -| `/package/video/teams/team` | `team location="away"`; `team location="home"` | Required for sports clips | - -```xml - - Chicago Cubs - St. Louis Cardinals - -``` \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/resources.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/resources.md deleted file mode 100644 index 356d135f..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/resources.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -title: Helpful Links -excerpt: Consolidated external resources referenced throughout the spec. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Metadata Templates, Schemas, and Samples - -| Resource | Link | -| --------------------------------------- | ---------------------------------------------------------------------------- | -| Film Metadata Excel Template | [go.roku.com/film-excel-template](https://go.roku.com/film-excel-template) | -| TV Metadata Excel Template | [go.roku.com/tv-excel-template](https://go.roku.com/tv-excel-template) | -| Clip Metadata Excel Template | [go.roku.com/clip-excel-template](https://go.roku.com/clip-excel-template) | -| Film XML Schema | [go.roku.com/film-xml-schema](https://go.roku.com/film-xml-schema) | -| TV XML Schema | [go.roku.com/tv-xml-schema](https://go.roku.com/tv-xml-schema) | -| Clip XML Schema | [go.roku.com/clip-xml-schema](https://go.roku.com/clip-xml-schema) | -| Annotated Film XML | [go.roku.com/film-xml-example](https://go.roku.com/film-xml-example) | -| Annotated TV XML | [go.roku.com/tv-xml-example](https://go.roku.com/tv-xml-example) | -| Annotated Clip XML | [go.roku.com/clip-xml-example](https://go.roku.com/clip-xml-example) | -| Film ADI XML Example | [go.roku.com/film-adi-xml-example](https://go.roku.com/film-adi-xml-example) | -| TV ADI XML Example | [go.roku.com/tv-adi-xml-example](https://go.roku.com/tv-adi-xml-example) | -| Clip ADI XML Example | [go.roku.com/clip-adi-xml-example](https://go.roku.com/clip-adi-xml-example) | -| All Metadata Templates/Examples/Schemas | [go.roku.com/metadata-docs](https://go.roku.com/metadata-docs) | - -## Best Practices and Guides - -| Resource | Link | -| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| Best Practices: Content Tags and Metadata | [developer.roku.com — content-tags-and-metadata](https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md) | -| Music Cue Sheet Submission | [go.roku.com/music-cue-sheet-submission](https://go.roku.com/music-cue-sheet-submission) | - -## Delivery Tools - -| Resource | Link | -| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Aspera Client (IBM Fix Central) | [IBM Fix Central — Aspera Desktop Client](https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Other%20software\&product=ibm/Other%20software/IBM%20Aspera%20Desktop%20Client\&release=All\&platform=All\&function=all) | -| IBM Aspera for Desktop | [ibmaspera.com/help/downloads/desktop](https://ibmaspera.com/help/downloads/desktop) | -| Roku's Aspera Shares URL | [aspera.sr.roku.com](https://aspera.sr.roku.com) | -| Creating an SSH Key (Aspera docs) | [Aspera SSH key documentation](https://download.asperasoft.com/download/docs/ascp/3.5.2/html/dita/creating_public_key.html) | -| Global Bandwidth Settings (IBM docs) | [IBM docs — global bandwidth settings](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-global-bandwidth-settings) | -| Adding/Editing Connections (IBM docs) | [IBM docs — adding/editing connections](https://www.ibm.com/docs/en/asdc/4.4.x?topic=gui-adding-editing-connections) | -| Configuring Transfer Settings (Aspera Shares) | [IBM docs — configuring transfer settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=options-configuring-transfer-settings) | -| Configuring User Settings (Aspera Shares) | [IBM docs — configure user settings](https://www.ibm.com/docs/en/aspera-shares/1.10?topic=accounts-configure-user-settings) | - -## Avails - -| Resource | Link | -| ------------------- | ------------------------------------------------------------------------ | -| Roku Avail Spec | [go.roku.com/trc-avail-spec](https://go.roku.com/trc-avail-spec) | -| Roku Avail Template | [go.roku.com/trc-avail-template](https://go.roku.com/trc-avail-template) | - -## FCC Regulatory - -| Resource | Link | -| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | -| FCC Audio Description | [fcc.gov/audio-description](https://www.fcc.gov/audio-description) | -| FCC Closed Captioning — Internet Video Programming | [fcc.gov/consumers/guides/captioning-internet-video-programming](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming) | - -## MovieLabs - -| Resource | Link | -| ------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -| MovieLabs Metadata Site | [movielabs.com/md](https://www.movielabs.com/md/) | -| EMA Avails Specification | [movielabs.com/md/avails](https://movielabs.com/md/avails/) | -| MEC Schema — Keyword Node | [MEC v2.9 schema — Keyword](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link116) | -| MEC Schema — AltIdentifier Node | [MEC v2.9 schema — AltIdentifier](https://movielabs.com/md/mec/v2.9/mdmec-v2.9/mdmec-v2.9.html#Link121) | -| MMC Schema — Markers Node | [MMC v1.10 schema — Markers](https://movielabs.com/md/manifest/v1.10/manifest-v1.10/manifest-v1.10.html#Link184) | -| Apache xmlbeans | [xmlbeans.apache.org](https://xmlbeans.apache.org/download/index.html) | -| MMC Schema XSD (manifest-v1.10) | [manifest-v1.10.xsd](https://movielabs.com/schema/manifest/v1.10/manifest-v1.10.xsd) | -| MEC Schema XSD (mdmec-v2.9) | [mdmec-v2.9.xsd](https://movielabs.com/schema/mdmec/v2.9/mdmec-v2.9.xsd) | - -## Rating Authorities - -| Resource | Link | -| --------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -| US MPAA Ratings | [filmratings.com](https://www.filmratings.com/) | -| US TV Ratings | [tvguidelines.org](http://tvguidelines.org/) | -| UK BBFC Ratings | [bbfc.co.uk](https://bbfc.co.uk/) | -| Canadian Film Ratings | [mpa-canada.org/film-ratings](https://www.mpa-canada.org/film-ratings/) | -| Canadian TV Ratings | [cbsc.ca — English CA and third-language broadcasters](https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/) | - -## Standards References - -| Resource | Link | -| -------------------------------- | -------------------------------------------------------------------------------------- | -| ISO 3166-1 alpha-2 Country Codes | [iso.org/iso-3166-country-codes](https://www.iso.org/iso-3166-country-codes.html) | -| RFC 5646 (Language Tags) | [datatracker.ietf.org/doc/html/rfc5646](https://datatracker.ietf.org/doc/html/rfc5646) | - -## Support Contacts - -| Contact | Purpose | -| ----------------------------------------------------------------------- | ---------------------------------------------- | -| [deliverynotifications@roku.com](mailto:deliverynotifications@roku.com) | Delivery notifications | -| [contentoperations@roku.com](mailto:contentoperations@roku.com) | Asset ID lookups, metadata/file update support | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/s3-connection.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/s3-connection.md deleted file mode 100644 index 2ef0654d..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/s3-connection.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: Direct S3 connection for content delivery -hidden: true ---- -Roku supports a direct S3 to S3 method for content delivery. The Roku delivery bucket for S3 direct connect uses a customer-managed KMS key. Since we are performing cross-account transfers, a KMS key and policy which grants external accounts permissions will be required. - -## What Roku need from Partners - -IAM role ARN, which will be used (assumed) for multipart upload/s3 copy. Once we receive the ARN, we will add it into our KMS/policy allow list. Typically, the ARN will be in the form of: - -``` -arn:aws:iam:::role/ -``` - -The IAM role will need to allow KMS related actions: - -```json -{ - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "kms:\*", - "s3:\*" - ], - "Resource": "\*" - } - ] - } -``` - -## What Partners need from Roku - -1. Roku’s production environment bucket name for direct ingest - - ``` - ingest-direct1-886239521314 - ``` - -2. Partner-specific prefix within the bucket. This will be supplied by Roku during the onboarding cycle and will follow the convention below: Convention - - ``` - ingest// - ``` - - Full bucket path example - - ``` - ingest-direct1-886239521314/ingest// - ``` - -### Best practices/optimization - -Roku’s S3 bucket is located in the **us-east-1** region. Cross region transfers are expected to be slower. Transfers can be optimized by configuring multipart upload/copy settings: - -``` - aws configure set default.s3.multipart_chunksize 128MB - aws configure set default.s3.max_concurrent_requests 30** -``` - -### Testing - -To validate the configuration, perform the following test - -1. Test upload file to Roku S3 bucket and the designated partner prefix -2. Test copy file from Partner S3 bucket to Roku S3 bucket and the designated partner prefix diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/trailer-delivery.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/trailer-delivery.md deleted file mode 100644 index fa25fe58..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/trailer-delivery.md +++ /dev/null @@ -1,151 +0,0 @@ ---- -title: Trailers -excerpt: MovieLabs-only trailer delivery requirements, including parent-title linking. -deprecated: false -hidden: true -metadata: - robots: index ---- - - ### Current trailer support is limited to a single trailer at a movie or series level only. Season and episode level trailers are not currently supported. - - -## Overview - -Roku accepts trailers **exclusively via MovieLabs delivery.** Trailers are treated as **separate entities** from their parent content and are displayed on-platform at the movie or series level. - -Much of the video, audio, and general delivery guidance in this document mirrors the [general Video Specification](https://developer.roku.com/dev/update/docs/video-requirements) and [Audio Specification](https://developer.roku.com/dev/update/docs/audio-requirements) — this doc calls out only trailer-specific requirements and deltas. Where a rule is copied inline below (e.g., "full program only" rules), it is intentionally kept in sync with those specs rather than a fork; if the two ever diverge, the general specs are authoritative for non-trailer-specific rules. - -## Delivery Method - -- Trailers **must** be delivered via **MovieLabs** (MEC/MMC/Avails) exclusively — no legacy delivery path is supported. -- Each trailer **must** be delivered with its **own** MEC, MMC, and Avails — a trailer does not inherit these from its parent title. - -*** - -## Avails Requirements - -**Avails are required to publish a trailer.** A trailer will not go live on Roku Channel without an associated avail — this is a publish-blocking requirement, not merely preferred. See [Avails and Committed Title Lists for The Roku Channel](https://developer.roku.com/dev/update/docs/title-avail-specifications) for the full submission process. - -**Trailers intended to be viewable in front of the paywall** (i.e., accessible without an active subscription, even though tied to SVOD content) **require an FVOD availability window.** The FVOD window **must** be fully contained within an active SVOD window for the trailer's parent title — Roku does not support FVOD-only availability. See [FVOD submissions](https://developer.roku.com/dev/update/docs/unlocking-svod-content-as-free-fvod) for the complete FVOD window rules, valid/invalid examples, and delivery instructions. - -*** - -## MEC (Media Entertainment Core) - -A valid MEC per MovieLabs schema is **required** for each trailer. - -- `WorkType` **must** be delivered as `promotion`. -- The `Parent` element **must** be present to link the trailer to its parent program (movie or series). -- The `@relationshipType` attribute is expected to be `ispromotionfor`. -- `ParentContentID` **must** be the **exact** `ContentID` of the movie or series. IDs are **case-sensitive** and must match exactly, or the trailer will fail to link to its parent program. - -```xml - promotion -... - - md:cid:org:roku:1234567_89_00 - -``` - -*** - -## MMC (Media Manifest Core) - -A valid MMC per MovieLabs schema is **required** for each trailer. - -Roku **prefers** that the `CardsetList` element be included, with `Cardset` `Type` set to `Trailer`, to further identify the promotional video as a trailer. - -- This is **not strictly required** — trailers will still display on-platform if `CardsetList` is omitted. - -```xml - - - Trailer - - -``` - -*** - -## Video - -### Content Standards - -- Trailers **must** accurately represent the main program. -- Trailer content **must** be suitable for a general audience. **"Red Band" trailers are not accepted:** - - Trailers **must not** contain nudity or graphic sexual content. - - Trailers **must not** contain profanity or objectionable language. - - Trailers **must not** contain graphic violence. - -### Program Content & Editorial - -Trailer videos **must** be **full program only**: - -- No bars/tone or slates at the start -- No textless video after the end -- No FBI warnings or MPAA cards -- No promotional material referencing theatrical, home video, or streaming release dates -- Calls to action (CTAs) or links to external platforms/sites (including QR codes) are **not permissible** and must be removed prior to delivery - -### Aspect Ratio & Frame - -- HD video content **must** be delivered in a 16:9 container. -- **Full-frame presentation (1.78 aspect ratio) is preferred** whenever available. -- Letterboxed 16:9 is allowed but **should be minimized**. -- SD 16:9 content **must not** be delivered in a 4:3 container with letterboxing. - -### File Quality - -- **High-quality mezzanine-level files are preferred** — the highest bitrate and resolution available should be used. - -*** - -## Audio - -- Trailer audio **must** be delivered in a language that is also present in the main program (i.e., at least one trailer audio language must match one of the main program's delivered audio languages). A trailer **is not required** to include a separate audio track for every language delivered on the main program. - -*** - -## Artwork - -- Each trailer **must** include a thumbnail image: a clear, **textless 16:9** image sourced directly from the trailer video. - -**Note on scope:** unlike parent movie/series content — which requires up to six image types (Key Art, Box Cover, Poster, Background, etc. — see the [Artwork Specification](https://developer.roku.com/dev/update/docs/artwork-requirements)) — trailers require **only this single thumbnail image type**. No other trailer-specific artwork is needed. - -*** - -## On-Platform Trailer Experience - -### Movie Trailer Experience - -Clickable trailer button on a movie details page. - -![Movie trailer button](https://image.roku.com/ZHZscHItMTc2/movie-trailer-button.png) - -### TV Trailer Experience - -Clickable trailer button on a series details page. - -![TV trailer button](https://image.roku.com/ZHZscHItMTc2/tv-trailer-button.png) - -### Premium Subscriptions Page Trailer Experience - -Auto-play trailer experience within the branded Premium Subscriptions publisher page. **Auto-play trailers apply only** to Premium Subscriptions content within the branded publisher page. - -![Premium Subscriptions auto-play trailer](https://image.roku.com/ZHZscHItMTc2/trailer-glow-up-small.gif) - -*** - -## Glossary - -| Term | Definition | -| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| **MEC** | Media Entertainment Core — the MovieLabs metadata schema describing the content itself (title, work type, parent/child relationships, etc.). | -| **MMC** | Media Manifest Core — the MovieLabs schema describing the manifest of deliverable assets (video, audio, images) associated with a title. | -| **Avails** | EMA Avails — the metadata format expressing licensing/availability terms (territory, window, rights) for a piece of content. | -| **ParentContentID / relationshipType** | The mechanism by which a trailer's MEC links back to its parent movie or series: `relationshipType="ispromotionfor"` declares the relationship, and `ParentContentID` supplies the exact, case-sensitive ID of the parent title. | -| **Cardset** | An MMC element used to categorize a promotional asset (e.g., tagging a video as a `Trailer`) beyond its base `WorkType`. | -| **Red Band trailer** | Industry term for a trailer containing mature content (graphic violence, nudity, strong language) not suitable for general audiences. Not accepted by Roku. | -| **Avails** _(publish requirement)_ | An availability submission required before a trailer can go live — distinct from the EMA Avails metadata format referenced above; see [Avails and Committed Title Lists](https://developer.roku.com/dev/update/docs/title-avail-specifications). | -| **FVOD** | Free Video on Demand — a license type allowing temporarily free access to otherwise-SVOD content; required for trailers viewable in front of the paywall. See [FVOD submissions](https://developer.roku.com/dev/update/docs/unlocking-svod-content-as-free-fvod). | diff --git a/docs/THE ROKU CHANNEL/video-on-demand/delivery/video-requirements.md b/docs/THE ROKU CHANNEL/video-on-demand/delivery/video-requirements.md deleted file mode 100644 index 6f0d8311..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/delivery/video-requirements.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -title: Video -excerpt: Video file, format, resolution, and editorial requirements for all deliveries. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Language & Version Policy - -Roku supports **one video file per title**. Where a title requires additional language support, that support **must** be delivered as: - -- Sidecar subtitle files, and/or -- Additional audio tracks - -associated with the single video asset — **not** as separate video files. - -**Discrete video versions produced in alternate languages** (e.g., dubbed or regionally re-cut video files) are **not supported** as separate deliverable assets for a given title, regardless of territory. Only one video per title will be ingested across all territories. Any additional-language requirements must be expressed through sidecar audio or subtitle elements mapped to that single video file. - -> **Exception:** Partners requiring delivery of alternate-language video versions (e.g., open-captioned or hardcoded-subtitle versions) should coordinate directly with Roku Content Operations. These deliveries fall outside standard EMA Avails/MovieLabs MEC-MMC ingest support and may require a separate title record or delivery arrangement outside this specification. - -*** - -## Program Content & Editorial - -All video delivered to Roku **must** contain the **full program only**: - -- No bars/tone or slates at program start -- No textless video after program end -- No more than 2 seconds of black at program start (**head black**) -- No more than 2 seconds of black after program end (**tail black**) -- No FBI warnings or MPAA cards -- No promotional material referencing theatrical, home video, or streaming release dates - -Video files **should** be **semi-textless** — meaning opening and end credit text may remain, but all subtitles for foreign dialogue must be removed. _(Also referred to as "texted with no subtitles" or "textless with main, ends, and graphic text.")_ - -*** - -## Advertising & Commercial Blacks - -- Do **not** include advertisements within the video. All ad insertion points for ad-supported content are provided separately in the metadata file, per [Roku Ad Policy guidelines](#ad-policy). -- **Commercial blacks** (black frames at internal ad-break points, distinct from head/tail black above) **may** be included, provided each is no longer than 2 seconds. -- Commercial blacks are acceptable for episodic TV content but not expected for movie content. - -*** - -## File Delivery Format - -- Video **must** be delivered as a **single, seamless file**. -- Do **not** deliver hard-parted files (i.e., broken into segments at ad-break points). -- Calls to action (CTAs) or links to external platforms/sites (including QR codes) are **not permissible** and must be removed prior to delivery. -- **High-quality mezzanine-level files are preferred** — the highest bitrate and resolution available should be used. - -*** - -## Aspect Ratio & Frame - -- **Full-frame presentation (1.78 aspect ratio) is preferred** whenever available. -- Letterboxed 16:9 is allowed but **should be minimized**. -- HD video content **must** be delivered in a 16:9 container. -- SD 16:9 content **must not** be delivered in a 4:3 container with letterboxing (i.e., do not pillarbox 16:9 content into a 4:3 frame). - -*** - -## Video Frame Rate - -Roku supports a variety of frame rates and scan types. All video files **must** be delivered in their **original native frame rate and scan type** — no frame rate conversion. - -*** - -## Video Resolution - -| Type | Width | Height | Pixel Aspect Ratio | -| ----- | ----- | ------ | ------------------------------- | -| SD | 720 | 480 | 4:3 or 16:9 (anamorphic pixels) | -| SD | 640 | 480 | 1:1 (square pixels) | -| SD | 853 | 480 | 1:1 (square pixels) | -| SD | 720 | 576 | 4:3 or 16:9 (anamorphic pixels) | -| SD | 768 | 576 | 1:1 (square pixels) | -| SD | 1024 | 576 | 1:1 (square pixels) | -| HD | 1280 | 720 | 1:1 (square pixels) | -| FHD | 1920 | 1080 | 1:1 (square pixels) | -| UHD\* | 3840 | 2160 | 1:1 (square pixels) | - -\* UHD is supported as an **input resolution only**. Roku does not currently encode to or display 4K UHD video on Roku Channel. - -*** - -## Video Formats - -| Name | Codecs | Extension | Bitrate | -| ------------- | ---------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------ | -| Apple® ProRes | ProRes 444 (all profiles)
ProRes 4444 (all profiles)
ProRes 422 (all profiles) | .mov | 50 Mbps or greater | -| XDCam | | .mxf | 50 Mbps or greater | -| MPEG-2 | MPEG-2 | .ts, .mpg | HD = 15 Mbps or greater
SD = 3.75 Mbps or greater | -| MPEG-4 | H.264 | .mp4 | 5 Mbps or greater | - -*** - -## Glossary - -| Term | Definition | -| --------------------- | ---------------------------------------------------------------------------------------------------------------------- | -| **Sidecar file** | A subtitle or audio file delivered alongside (not embedded in) the video file, mapped to it via metadata. | -| **Mezzanine file** | A high-quality, typically near-lossless master file used as the source for further encoding. | -| **Anamorphic pixels** | Non-square pixels used to fit a widescreen image into a standard frame size. | -| **Square pixels** | Pixels with a 1:1 aspect ratio, common in modern digital video. | -| **Hard-parted** | A video file physically split into multiple segments at ad-break points, rather than delivered as one continuous file. | -| **Semi-textless** | Video with opening/end credit text intact but with foreign-dialogue subtitles removed. | diff --git a/docs/THE ROKU CHANNEL/video-on-demand/index.md b/docs/THE ROKU CHANNEL/video-on-demand/index.md deleted file mode 100644 index 9189589b..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/index.md +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: Video on Demand -hidden: false ---- -## Content submissions - -If you have content that you would like to submit for The Roku Channel, please fill out our avails template (series and feature/movies on separate templates) and send to [trc-avod-submissions@roku.com](mailto:trc-avod-submissions@roku.com). Avails templates are available in the [Title Avails Specifications](doc:title-avail-specifications). If you own or control the necessary rights for only a small volume of VOD titles, please consider working with one of Roku’s Preferred Aggregators. - -## Specifications - -* [Roku-Hosted (Ingest) Specs](doc:delivery#ingest-specifications) -* [Partner-Hosted (Feed) Specs](doc:live-feed-specifications) - -## Analytics & reporting - -### Analytics dashboard - -#### Overview - -The Roku Channel partners have access to web-based performance analytics through Roku's Content Partner Portal. This allows you to analyze the health, viewership trends, and metrics for specific titles. - -[Learn more](https://developer.roku.com/dev/docs/roku-content-partner-portal-analytics) - -### Payout & revenue reporting - -#### Overview - -The Roku Channel Partners must enroll in Roku’s Partner Payouts Program, which is the vehicle through which partners receive payments for content served to Roku Users. - -#### Enrolling in Roku's Partner Payouts Program - -To sign up for Roku Partner Payouts Program: - -* Create a [Roku customer account](https://developer.roku.com/enrollment/standard) -* Enroll your [Roku account in the Developer Program](https://developer.roku.com/developer/billing) -* Enroll in the [Roku Partner Payouts Program](https://developer.roku.com/developer/billing) - -In order to enroll in the Roku Partner Payout Program, you will need to provide the following to - -* Contact information -* Bank information -* Tax forms (W9, W8-BEN, or W8-BEN-E) - -#### The Roku Channel partner payouts & revenue reports - -Partners can select between three payout methods when enrolling in the Roku Partner Payouts Program: - -* PayPal -* Direct deposit / ACH -* Wire transfer -* **Please note that for partners outside the United States, only PayPal and wire transfers are available (direct deposit/ACH is not available).** -* For all partners, wire transfer and ACH payments are made in USD only. If there are transactions received that are non-USD, they are converted to USD using the average foreign exchange rate for the month the payment is for. -* With PayPal, there is no payment fee. With wire transfers and ACH payments, your bank will charge you bank fees. - -Payments and revenue reports are sent out quarterly, 60 days post-quarter closing. See table below. Payments will be sent directly to the payout method in your Developer Dashboard. Revenue reports will be sent via e-mail. If you would like to be included in the revenue report distribution list, please contact [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com). - -| Quarter | Date | -| :------ | :--------------- | -| Q1 | By May 31st | -| Q2 | By August 31st | -| Q3 | By November 30th | -| Q4 | By February 28th | - -Note that partners will not be paid until the aggregate sums due are equal to or exceed $100.00. Detailed payout terms are found in the Commercial Terms Exhibit of the [Roku Distribution Agreement](https://docs.roku.com/doc/developerdistribution/en-us). diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/_order.yaml deleted file mode 100644 index d5448620..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/_order.yaml +++ /dev/null @@ -1,12 +0,0 @@ -- branded-prod-guidelines -- alternative-prod-guidelines -- scripted-prod-guidelines -- alt-prod-legal-guidelines -- scr-prod-legal-guidelines -- post-branded-specs -- post-alternative-specs -- post-scripted-specs -- post-spanish-specs -- features-specs -- acquisitions-specs -- post-live-event-specs \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/acquisitions-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/acquisitions-specs.md deleted file mode 100644 index e8f836e6..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/acquisitions-specs.md +++ /dev/null @@ -1,545 +0,0 @@ ---- -title: Acquired content - scripted media delivery specifications -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -_Version 3.0_ - _August 2025_ - -## 1. General overview - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Originals Post Production Delivery Specifications outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -The specifications below encompass deliverables for Roku Originals Post Production, as they relate to previously completed, acquired series. It is not comprehensive of all deliverables that may be required as part of your agreement. Please continue to utilize the [The Roku Channel Ingest Specifications](https://go.roku.com/rokuchannel-ingest-vod) document for all other areas noted below: - -* Ad Policy -* Kids Directed Content Policy -* External Branding and Calls to Action -* Artwork and Marketing Deliverables -* File Delivery Setup - -If the Roku Originals Content Development teams will be a part of the creative, editorial process, please reach out to Roku Post Production to obtain the correct specifications. - -## 2. Deliverables - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and confirmed by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -### 2.1 Roku originals logo - -All acquired content that will be branded as a Roku Original series will be required to add the Roku Originals Logo to their end credits. The Roku Originals Logo should be placed last in the end credits. **Please reach out directly to Roku Post for access to the most current Roku Original Logo at: [dlropost@roku.com](mailto:dlropost@roku.com)** - -### 2.2 Quality control (QC) - -Each Production is responsible for covering the cost of and delivering 100% Quality Control approved content. - -All masters noted below will be required to be submitted to Quality Control: - -* Texted Master – Inclusive of Roku Originals End Logo addition -* Textless Master – Inclusive of Roku Originals End Logo addition - -All required versions for each episode should be delivered to the Quality Control facility on the same day. This will ensure the Quality Control operator is able to verify that there is no variation between the texted/textless timings. - -Please be sure to build time into your delivery schedule to account for the Roku Quality Control process. Roku advises that you set aside three weeks for each episode to complete the Quality Control of all horizontal masters. Delivery will not be considered ‘Final’ unless all masters have received a passing report from one of Roku’s approved vendors. A list of these vendors will be provided in the Post Kickoff Packet. - -If an episode has passed Quality Control but a revision is necessary (incorrect titles, production card modification, etc.) you **must** reach out to Roku Post before any redelivery is made. Please send an email with a detailed and time coded breakdown of what fixes are being requested so that Roku can review and determine the impact it will have on each team and the show premiere itself. - -#### 2.2.1 Text spotting list (TSL) - -You will be required to deliver a Text Spotting List file for each episode when it is submitted for Quality Control. This list will help Quality Control vendors verify that creatively intended text is included in the final file. A Roku Text Spotting List template was provided in your Post Kickoff zip file. This single file should be updated as episodes are sent to Quality Control so that all information for the series is included in the same master spreadsheet. - -The Text Spotting List should contain any and all text that is burned into picture, and the corresponding timecodes for each. If an episode has no burned-in text, you will still be required to deliver this file, but will specify the lack of text by checking the box at the top of the template. - -### 2.3 Filename specifications - -#### 2.3.1 Paper deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -* ShowCode_ ProdNumber_AirOrder_Version_LangCode_Date_FINAL -* GABH_ 301_Air_1_PostVendorList_enUS_20250303_FINAL - -#### 2.3.2 Master video deliverables - -All master* video files should be labeled as follows: - -ShowCode_ProdNumber_AirOrder_Version_LangCode_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov - -Example: - -NION_101_AIR_1_TXTD_enUS_UHD_SDR_FN_2CH_23976p_20190701-v2.mov - -Production Number = As listed on Post Grids - -Air Order = Please list even if the Air Order is the same as the Production Number - -| File Name Segment | File Name Abbreviation | -| ----------------- | ----------------------------------------------------------------------------------------------- | -| Version | TXTD (Texted), TXLS (Textless), or PROXY | -| Language | enUS (American English) or esMX (Neutral Latin American Spanish) | -| Resolution | UHD or HD + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | 2CH (Interleaved) or 8CH (5.1 and Stereo) – 7.1 audio not permitted on any masters at this time | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Revision Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of QC and track the latest version for delivery | - -*See 2.4.5 for Proxy file naming. - -#### 2.3.3 Master audio deliverables - -Audio materials should be named to include all appropriate information: - -ShowCode_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_102_v04_20220919_enUS_PM_Nearfield_2ch_48k_24b_23976.L.wav - -MAMA_102_v03_20220919_esMX_FXSTEM_6ch_48k_24b_23976.R.wav - -MAMA_102_v02_20220919_esMX_ME_Nearfield_6ch_48k_24b_23976.C.wav - -| Material Type | Abbreviation | -| --------------------------------------------- | --------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, FFFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | - -**Channel types** - -| Channel Type | Abbreviation | -| ------------ | ------------ | -| Mono | Mono | -| Stereo | 2CH | -| 5.1 Surround | 6CH | - -**Track assignments** - -| Track Assignment | Abbreviation | -| ---------------- | -------------------- | -| Mono | N/A | -| Stereo | LT, RT | -| 5.1 Surround | L, R, C, LFE, LS, RS | - -### 2.4 Video deliverables - -All video should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher of the export settings mentioned in 2.4.3, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate that was captured (for example, if the camera captured ProRes 422, then final export should be ProRes 422 or equivalent instead of 4444 XQ). - -_Roku Best Practices_ - -If your capture workflow is different than specified above, please contact Roku Post Production before final mastering begins. It is important to keep master sequences (VAM/CTM) and final deliverables in alignment with dailies capture specifications (i.e. free of any up-scaling, cross-conversions, or up-conversions). - -#### 2.4.1 Video formatting - -All files should be formatted to start at 00:00:00:00. - -Files should begin with program and end on the last frame of the Roku Originals Logo end card. - -All video files **MUST NOT** contain any of the following: bars and tone, bumpers, segment recaps or previews, Vertical Interval time code, advertisements, slates, rating cards, FBI warning cards, placards, overlay branding, promotional bugs, informational bugs, watermarks, or website link callouts. - -If promotional bugs or watermarks are required by a 3rd party, Roku Content Legal should be notified. - -#### 2.4.2 Audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 2.4.3 for specifications based on delivery codec. - -Mixing Specifications: - -**The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all texted and textless masters.** - -* If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered. -* Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export. - -Mixing Specifications: - -* Target - 24 LKFS +/- 2 (any average between -22 & -26). Based on ITU-R 1170-3 measurement. -* Audio should not peak above -2 dBfs (True Peak) - -#### 2.4.3 Texted video masters - -The formatting requested below is a subset of the [Roku Channel Ingest Specifications](https://go.roku.com/rokuchannel-ingest-vod). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Video CodecProRes
ContainerMOV
Profile4444XQ Preferred (If available)
ProRes 422 HQ
Minimum Bitrate175-400 mbit/s (based on Profile)
Landscape aspect ratio16:9 (1.77:1) - (no black bars)
W3840 x H2160 (UHD)
Pixel aspect ratioSquare pixels (1:1)
Scan typeProgressive scan type
Chroma Subsampling4:4:4
Color SpaceBT.709 Legal Video Range (16 to 940)
Bit depth10-bit or 12-bit
Constant Frame Rate23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p
Native frame rateNo 3:2 pulldown flags
Text Track/CaptionsOmit empty embedded text tracks
Captions should be delivered as sidecar assets
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Audio CodecPCM
Format2 Interleaved Tracks or 8 Mono Tracks
Track LayoutInterleaved: Track 1: 5.1, L-R-C-LFE-Ls-Rs Track 2: Stereo, LT/RT
Mono: L, R, C, LFE, Ls, Rs, Stereo LT, Stereo RT
7.1 audio is not permitted on any masters at this time
Sample Rate/Bit Depth48000Hz/24-bit
Channel Mapping & Metadata TaggingSee 2.4.2 - Verify correct audio channel mapping and metadata tagging.
- -#### 2.4.4 Textless delivery - -Textless Masters are a Roku Original-specific deliverable. They protect for any potential distribution outside of the United States. - -If your content includes burned-in on screen text, you will be required to deliver a separate Textless Reel or Full Episode. This reel should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Masters noted above. - -Audio mapping label verification as noted in 2.4.2 must be verified in textless master. - -Additionally, if foreign language subtitles cover 30% or more of a given episode, you will be required to deliver a fully textless version of that episode. All episodes should be delivered with the same formatting; if one episode requires a textless master, versus a reel, then all remaining episodes should also be delivered as textless masters. - -#### 2.4.5 Final proxy files (clean & visible timecode) - -Proxy files are a Roku Original-specific deliverable. They are utilized by multiple internal teams both pre and post launch. - -From each Texted Master created, please export following proxy files: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Video CodecH.264
ContainerMOV or MP4
Picture(1) Clean & (1) w/Vis.TC UR (1) Series Opener Only
Bitrate5mbit/s (total file size \< 1gb to 2gb)
DimensionsW1920 x H1080 (HD)
Scan TypeProgressive scan type
Color SpaceBT.709 Legal Video Range
Bit Depth10-bit or 12-bit
Constant Frame RateShould Match Master
Native Frame RateShould Match Master
AudioCh.1 Stereo Left, Ch.2 Stereo Right
FilenameShowCode\_ProdNumber\_AirOrder\_Language\_Proxy\_HD\_
FN(if applicable)\_Audio\_Timecode(Clean or VisTC)*RevisionDate-v#*(Final or Pre-QC).mov

THAM\_101\_AIR\_1\_PROXY\_enUS\_HD\_FN\_2CH\_CLEAN\_20200916\_V4\_FINAL.mov
- -### 2.5 Audio delivery - -Audio stems are a Roku Original-specific deliverable. Full audio stem delivery may not be required for each series. Please reach out to Roku Post Production to determine if your series will be required to delivery these materials. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. - -#### 2.5.1 Domestic episodic stems - -Provided below are the stems required for delivery of each episode/project: - -* Mono Dialogue, Music, and Special Effects stems -* Stereo & 5.1 Printmasters -* Stereo & 5.1 M&E - Fully Filled (Scripted Series) -* Stereo & 5.1 Music -* Stereo & 5.1 Dialogue -* Stereo & 5.1 Sound Effects -* Pro Tools Session Files (.ptx) - -Provided below are the stems Roku would like to receive, if available (and applicable): - -* Stereo & 5.1 Mix minus narration -* Score or Original Composition (pending rights) -* Mono M&E Stems - Opticals, Backgrounds, etc. - -All audio should be archived as 24-bit, 48kHz WAV files. - -Please see section 2.3.3 for full guidelines on labeling audio files. - -ShowCode_ProdNumber_Vers_LangCode_MaterialType_Channel#_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_102_v04_enUS_PM_Nearfield_2ch_48k_24b_23976.L.wav - -_Roku Best Practices_ - -* Roku requires that all music be cleared for both domestic and international use across all media on all devices. -* Optional tracks (foreign language, grunts, breathing, etc.) are preferred, if applicable -* If budget permits, please create Fully Filled FX stems as part of delivery - -### 2.6 Timed text file delivery - -Roku Originals content should be delivered in each of the following timed-text formats in order to support the hearing impaired: - -* Subtitles: Language solely (no inclusion of sound descriptors) - * Foreign subtitle files should also include any translated forced narratives that are currently burned into picture in English - -* SDH: Language in addition to sound descriptors (no forced narratives) - -* FN: Forced Narratives solely - -Roku requires closed captions and subtitles in **2** of the [Roku Ingest Specification](https://go.roku.com/rokuchannel-ingest-vod) formats: SRT and WebVTT. The files have to have the same timecode and frame rate as the video and audio delivered. Character encoding MUST be UTF-8. - -**Languages & Formats Required:** - -English (American, Code: enUS): Subtitles, SDH, & FN - -**All files should be labeled as follows:** - -ShowCode-ProdNumber-LanguageCode_Format-RevisionDate.srt - -**Filename Examples:** - -NION-101-enUS_SDH-20190701 - -NION-101-enUS_FN-20190701 - -### 2.7 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Post Manager. - -#### 2.7.1 Roku metadata ingest template - -Metadata allows Roku to ingest and display all series related information for our customers. Marketing and/or the Roku Content Executive may tweak the information to ensure it’s as effective as possible on the Roku platform. - -Please find the most recent Roku metadata templates and guidelines [HERE](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates). - -The required details will include, but are not limited to, the following: - -* Show - Title, Description, Primary Spoken Language, Production Companies -* Season - Title, Description (leave blank if not applicable) -* Episode - Title, Production Number, Air Order, Total Run Time (TRT) - -Please note that air order and episode titles must be a decision made with your Content Executive. The episode titles must be creatively driven (e.g. not “Episode 1”) and should be written with the show writers or receive writer approval. Episode Titles should be locked after Rough Cut 1s. - -#### 2.7.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. PNG files relating to the Title Logo and any other logos submitted should be uploaded to [Frame.io](http://frame.io/). - -2. *Cast & Crew Metadata Template - Required in .xlsx format should be uploaded to the Hub. - 1. Please label the Cast & Crew document as “Production Final.” - -3. Please ensure the Series and all necessary Episodic tabs are included within the same master spreadsheet. Episodes should not be delivered as separate files. - -4. Traditional Episodic Credits Lists that detail the specific credits tied to each episode should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -*Please note that the Cast & Crew Template is for direct ingest into the Roku Channel - please check spelling before submitting. If you need to resubmit the Cast & Crew Template (due to adding/removing credits, spell change, position change, etc.) please email the updated .xlsx to Roku Post upload to the Hub with the changes highlighted. **For cast/crew with multiple credits**, place each on a separate line repeating the cast/crew member name. - -#### 2.7.3 Segment rundowns - -You will be required to deliver a detailed breakdown of the timecodes pertaining to all segments in each episode. Please utilize the Roku Segment Rundown Template provided in your Kick-Off Delivery Packet. - -Roku requires that the timecodes within this document be delivered in HH:MM:SS:FF format. Any spreadsheets submitted without this formatting will not be accepted by Roku. - -#### 2.7.4 As Broadcast scripts - -Please deliver one set of As Broadcast Scripts for each series to the Hub. As Broadcast Transcript files should have a timecode-based breakdown of each line of dialogue. You are approved to submit the ABS’s in any format that a Roku approved vendor utilizes. - -#### 2.7.5 Final font memo - -Please deliver one document that details the font name and size utilized for opening credits, identifiers and/or other on-screen text added to each episode (where applicable) to the Hub. If applicable, please also note which vendor created the show logo. - -#### 2.7.6 Final vendor list - -Please deliver your final version of the Roku Vendor List that you received in the Kick-Off Delivery Packet to the Hub. - -#### 2.7.7 Final text spotting list - -Please deliver the Text Spotting List that was used to Quality Control the final episodes to the Hub. Please ensure that any changes made during Quality Control are reflected in the final document that is delivered to Roku via The Hub. Please deliver a single excel, via Roku’s template, with episodes separated onto their own tabs. - -#### 2.7.8 Episodic delivery checklist - -Please deliver the final version of the Roku Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. All of the following must be completed: - -* All applicable file version dates and delivery locations for each asset -* All Quality Control Start and End/Approval dates for Texted and Textless Masters -* Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -* If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 2.7.9 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the American Society of Composers, Authors and Publishers (ASCAP) website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Grossberg at [sgrossberg@roku.com](mailto:sgrossberg@roku.com). - -#### 2.7.10 Not applicable form - -In cases where a paper deliverable is non-applicable to the project, please upload the Roku Not Applicable Form to the Hub with a written explanation of why this deliverable does not apply. - -## 3. Archival - -Archival delivery is not required for all acquired content. Please reach out to Roku Post Production to determine if your series will be required to delivery these materials. - -### 3.1 High resolution masters & source material - -Reach out to Roku Post if you do not see a pre-existing folder structure on [Frame.io](http://frame.io/) for Final Archive. It is required that you utilize the [Frame.io Transfer App](https://support.frame.io/en/articles/3978929-frame-io-transfer-download-and-upload-files-folders-and-projects) for your uploads. - -When adding video assets to [Frame.io](http://frame.io/), do not create additional sub-folders. Keep all media (proxies, texted/textless masters) only in the folders provided. Audio files should be grouped by episode (where applicable). - -The following are required deliverables that must be uploaded to the Final Archive folder on [Frame.io](http://frame.io/): - -Required: - -* Final Texted Masters -* Final Textless Masters -* H.264 Proxies -* Final Audio Stems -* Graphic Elements – Main title card, credit PNGs, end credit PNGs, on-screen graphics, interstitials, etc. - -Any and all series that are wholly owned by Roku will require delivery of Video Asset Management (VAM), Color Timed Masters (CTM), and final Visual Effects shots (where applicable) via LTO9 or greater. LTOs should be formatted LTFs and include a digital manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. These manifests should be uploaded to The Hub. - -For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -* VAMs – Un-color-corrected, textless, DPX or TIFF format (**Compress** to .ZIP or .TAR) - * Associated Avid bins or Edit Decision Lists - -* CTM – Color-corrected, textless, DPX or TIFF format (**Compress** to .ZIP or .TAR) - * Associated Look-up Tables or color-grading files - -* Final Visual Effects Shots – Un-color-corrected preferred (if applicable) - -## 4. Change log - -### V3.0 - -* 2.1 - Roku Originals end card updated -* 2.3.1 - Paper deliverable labeling revised -* 2.4.3 - ProRes 422 HQ added as Profile option for Texted Video Master -* 2.4.4 - If one episode in a series requires a full textless asset delivery, now all episodes in that series will require a fully textless master -* 2.7.1 - Link to current metadata templates and guidelines added -* 2.7.10 -'Not Applicable' Form added -* 3.1 - LTO9 is the newest version of the Linear Tape-Open and this is the version that should always be used - -### V2.0 - -* Multiple Sections - 5.1 & Stereo Mix required. 7.1 mix no longer being requested. -* 2.3.2 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX) -* 2.4.3 - Text Track/Captions formatting updated -* 2.4.5 - Final Proxy file size changed to a maximum of 2gb -* 2.6 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX); Removed SCC file requirement -* 2.6.1 - Audio Deliverables updated -* 2.7.1 - Roku Ingest Specs Link added for access most updated Metadata Template -* 3.1 - Frame.io Transfer App required for all uploads to the app - -[v1.9 intentionally skipped) - -### V1.8 - -* 2.1 – Roku Originals Logo must be placed last in end credits; download link provided -* 2.3.2 – Master Video Deliverables file naming modified -* 2.3.3 – Master Audio Deliverables file naming modified -* 2.4.2 – Audio Channel mapping and tagging of metadata must be verified -* 2.4.3 – Texted Video Masters audio track layout updated -* 2.5.4 – Audio mapping label verification as noted in 8.4.2 must be verified in Textless Master -* 3.1 – [Frame.io](http://frame.io/) & High Resolution Masters instructions revised - -### V1.7 - -* 2.2.1 – Text Spotting List updated -* 2.3 – File naming format for both paper and media deliverables modified. -* 2.5.5 – Additional proxy deliverable added. -* 2.7 – Replaced Latin American (LAS) labeling with Mexican Spanish (esMX). -* 2.8 – Further clarification provided across paper deliverables. - -### V1.6 (Skipped to line up with April 2022 update to all specs) - -### V1.5 – December 2021 - -* 2.6.2 – Audio Description files added as a new deliverable diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/alt-prod-legal-guidelines.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/alt-prod-legal-guidelines.md deleted file mode 100644 index 472ec036..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/alt-prod-legal-guidelines.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: "Alternative production legal guidelines" -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- - - -In creating content for exhibition on Roku, there are a few guidelines that the Roku Production Legal team would like you to keep in mind. As a reminder, we expect you to retain your own production legal counsel to represent your interests, as the Roku Production Legal team represents Roku. Please review these guidelines with your legal counsel. If you have any questions or concerns after reviewing, let’s set a time to discuss. - -## Production legal approvals - -Please reach out to Roku Production Legal for approval before engaging in any of the following: - -- Product Placement and Trade Outs – Product placement and trade outs may be allowed at Roku’s discretion. Please inform Roku Production Legal of potential product placement and/or trade outs in advance so that we can discuss and provide our “Trade Out Request Form." -- Diligence - Prior to engaging in any diligence on talent or crew (i.e., background checks, medical examinations, psychiatric/psychological counseling/testing), please discuss with your legal counsel and provide your diligence plan to Roku Production Legal for approval. -- Clearances - It is your responsibility to obtain all necessary clearances for the production, synchronization, exhibition, performance, distribution, marketing, and exploitation of the content by Roku, including musical compositions and sound recordings contained therein (except for public performance rights). Any potential third-party contractual restrictions that could impact Roku’s rights must be approved by Roku Production Legal in advance. -- Music – Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please only source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. -- Talent Approvals and Restrictions – When negotiating Talent deals, please advise Roku Production Legal of any restrictions Talent wishes to place on Roku’s ability to exhibit, market or promote such Talent. -- Unions/Guilds - If the Series is produced on a guild/union-covered basis, please reach out to Roku Production Legal to discuss the guild/union classification of the production. -- Contests, Sweepstakes or Competitions - Please discuss with Roku Production Legal prior to including any of these items in creative content. For competition shows, all rules must be approved by Roku Production Legal in advance. -- Insurance - Roku’s insurance requirements are included in the Indemnity Agreement or Standard Terms and Conditions negotiated by your legal counsel. Please send Certificates of Insurance to Roku Production Legal for approval. - - - -## Additional production legal expectations - -- Casting Notices - Roku is committed to diversity in all of its productions. Casting notices should solicit people of various ages, ethnicities, and socio-economic backgrounds to apply. Please note that certain characteristics are protected by anti-discrimination laws (e.g., age, race, religion, etc.), and generally should not be referenced in casting notices unless central to the core creative of a production. If necessary to include, consult with your legal counsel on how to do so appropriately. Reminder - please do not include the Roku name or logo on casting notices, unless approved by Roku Production Legal. -- Talent - Please make sure all talent sign their agreements/releases prior to appearing on camera. If for any reason you think this will not occur, please give Roku Production Legal a heads up. Please reach out to Roku Production Legal before giving talent the right to dub their voice in another language. For each talent agreement, please provide Roku Production Legal with a written summary of any approvals, restrictions, or requirements that may impact Roku’s marketing, publicity or promotional activities. -- Identifiable Brands - Roku does not generally restrict the appearance of branded products or services in content - there is no need to use only generics or mask/blur brands; however, if you wish to include any identifiable brand in “hero” shots, please raise to Roku Production Legal. -- Charities - If you plan to highlight a charity in a production (e.g., have someone sponsor/donate/call out for donations to a charity), please have your counsel confirm the tax-exempt status of the charity and inform Roku Production Legal in advance. -- Smoking - It is Roku’s policy to not show anyone smoking tobacco or electronic cigarettes on camera. This is of particular concern for talent/participants who are minors. If it is considered critical to the creative of the program for a particular individual to be shown smoking, please discuss with your Roku Production Executive. -- Safety/Respect in the Workplace - Roku is committed to supporting safe and respectful work environments. Please consult with your legal counsel to ensure that your production adheres to required health and safety practices and is in compliance with all applicable workplace regulations, including any state-required sexual harassment training. -- Titles and Fair Use - Roku expects content titles to be cleared for exhibition, marketing, and promotion on and in connection with the Roku platform. Please keep Roku Production Legal informed of any “fair use” content within the Series. Proof of bound E&O coverage, including title and fair use, should be provided to Roku Production Legal. - - - -## Compliance with all laws - -Federal, state and local laws (including laws of foreign countries, if applicable) should be respected at all times in creating content for Roku. As a reminder, the following each raise unique legal concerns when producing content: - -- Filming with children - Laws prohibiting child porn, permitting requirements, court-approval of minor contracts, and safety issues may all be relevant to your production. -- Filming with politicians or government officials - Federal and state rules regarding the payments/gifts to candidates or public officials can arise during production (e.g., talent fees for an appearance could equal a campaign gift). -- Filming with medical professionals (e.g., doctors, nurses, therapists) - You may need to obtain special HIPPA releases in connection with filming. -- Filming potentially illegal conduct (e.g., marijuana use/sales, minors smoking, etc.) - A variety of laws and regulations can be implicated when filming such activities depending on the jurisdiction. -- Shooting a ride-along with law enforcement, emergency personnel, or firefighters - Both safety concerns and tort liability risks can arise during such shoots. -- Use of hidden cameras or private investigator - State-by-state and country-specific regulations related to recording individuals without their consent may be relevant to your production. -- Emergency Action System tones (actual or simulated) - The transmission of EAS alarm tones, under any circumstance other than a genuine alert or authorized test, violates Federal law. The FCC has issued large fines related to the exhibition of content including the EAS tone. -- Filming with drones - In the United States, FAA regulations govern the use of unmanned aerial vehicles (UAVs) for commercial filming and various international jurisdictions have similar regulations and permitting requirements. - - - -Please raise any applicable concerns with your legal counsel - preferably in advance of filming! \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/alternative-prod-guidelines.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/alternative-prod-guidelines.md deleted file mode 100644 index d3c82811..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/alternative-prod-guidelines.md +++ /dev/null @@ -1,775 +0,0 @@ ---- -title: Alternative & documentary production guidelines -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -_Version 2.3 - February 2024_ - -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, Mexico and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices.  - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Production Guidelines outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -## 2. Welcome to Roku production - -We look forward to working with you! You should have received a “Welcome to Roku Production” email along with the Production Kick-Off documents outlined below. Please review the documents in their entirety, upon series pick-up Roku Production will reach out to schedule a kick-off call. During the call we can address any questions you may have. - -### 2.1 Production kick-off documents - -#### 2.1.1 Alternative production guidelines - -* Roku production document for alternative & documentary series – document you are currently reading -* Located on the Roku Deliverables Hub (Hub) in the Production - Alternative folder - -#### 2.1.2 Alternative media delivery specifications - -* Roku Alternative Hour-Long Delivery Specifications -* Roku Alternative Half-Hour Long Delivery Specifications -* Roku Alternative Short Form Delivery Specifications -* Roku Alternative Feature and Special Delivery Specifications -* Roku Alternative Spanish Language Delivery Specifications - * Roku technical specifications for alternative series - * Located on the Roku Deliverables Hub (Hub) in the Post - Alternative folder - -#### 2.1.3 Alternative production legal guidelines - -* Roku Production Legal guidelines when creating content for exhibition on Roku - -## 3. Roku communication - -### 3.1 Roku emails - -For email correspondence, Roku requests that the **full name** of the project be included in the subject line. Please do not use acronyms for the title. - -### 3.2 Roku alternative contact sheet - -The Roku Alternative Contact Sheet is for Partner use only. Please do not distribute. The contact sheet can be found on the Hub in the Production – Alternative folder. - -### 3.3 Roku distribution list - -Roku Production will send you a distribution list. You will find the Roku Alternative Distribution List via the Hub in the Production – Alternative folder. The distro list will include the name, title, email, and required documents / media for each Roku recipient. There are a handful of documents we request be emailed directly to Roku that include, but are not limited to: - -* Budgets -* Call Sheets -* Scripts / Episode Outlines -* Prep Schedules -* Production Calendars -* Cast & Crew Lists -* Wrap Reports -* Daily Production Reports (Prelim & Approved) -* Cost Reports - -**Do not include the Roku name or logo on any documents** (including contact sheets, call sheets, production reports, casting notices etc.) without written approval from Roku Production Legal. - -### 3.4 Roku calls - -Upon the below milestones, calls will be set with Roku Production: - -* Production Kick-Off Call -* Weekly Prep calls before commencement of Principal Photography -* Weekly or Bi-Weekly Production Call throughout Principal Photography -* Wrap of Principal Photography -* Any major production or overall schedule changes -* 1 week before Delivery of the Final Episode to QC - -Upon completion of Principal Photography or one week prior to delivery of RC 1, Roku Post will initiate weekly post calls. - -### 3.5 Roku notifications - -Please inform Roku Production, at least 2 weeks prior to any of the following activities or events: - -* Applying for tax incentives -* Traveling and filming outside the domestic United States -* Filming in aircraft/watercraft, including private planes and yachts -* Filming physically challenging or hazardous activities (including filming with firearms) -* Filming with minors or animals -* Filming a ride-along with law enforcement -* Filming nudity and/or sexual activities -* Filming hoaxes, using hidden cameras, and/or private investigators -* Filming any potential illegal activities -* Filming any on-camera or behind-the-scenes involving medical personnel, procedures, patients, facilities; psychological/psychiatric counseling; life coaching or other forms of therapy -* Filming with government officials, employees, and candidates, including any of the following: - * Faculty and teachers at government owned or controlled businesses or institutions (e.g., public universities, hospitals, national telecom companies) - * Employees of public international organizations, like the United Nations or World Bank - * An elected or appointed official, candidate for public office, or their family or staff - * Members of Royal Families - * Public school employees, firemen, law enforcement, military, etc. - * An elected or appointed official, candidate for public office, or their family or staff - -### 3.6 Roku emergency notifications - -In the event of an emergency or incident, once the situation is stable, please contact Roku Production immediately. If you cannot reach Roku Production, please call Production Legal. Incidents include, but are not limited to: - -* Stopping down pre-production, production, and/or post -* Unplanned hiatus or postponement -* Projected or occurring natural events (i.e., earthquakes, wildfires, hurricanes, tornadoes, etc.) -* Any suspected or confirmed drug use by on-camera talent, crew, or producers -* Cast, Crew, and general public medical concern including: - * Physical Altercations - * Hospitalization - * Arrest - * Personal Accident/Injury - * Vehicle accident -* Covid-19 health-related situation involving an individual, location, or government -* Planning to file an insurance claim due to force majeure -* Any allegation of cheating or unfairness in connection with a competition show -* Any claim or potential claim arising in connection with the production including threat of litigation -* Any other event (or planned event) that may pose a legal or reputation risk to Roku -* Any event, occurring or projected, that may impact any person(s) and/or actual production, physical production, or delivery of the series to Roku -* Any contact by the press or media regarding any aspect of the production, including talent and Covid-19 - -**AFTER** informing Roku, please email detailed information, while respecting the privacy of the individuals, regarding the incident to [altprod@roku.com](mailto:altprod@roku.com): - -* Title the subject of your email as follows: “Show Name” - Notification - CONFIDENTIAL -* If the incident is sensitive in nature, in the body of your email please relay that an incident has occurred and request an immediate call with Roku Production and Production Legal - -In the event of any non-emergency incident (property/location damage, equipment damage): - -* Please inform Roku Production -* Please be sure to note in the Production Report - -**SPECIAL NOTE:** In the event you are not able to immediately reach your Roku Production or Production Legal Executive please proceed with emailing [altprod@roku.com](mailto:altprod@roku.com) but use discretion in the details you share. - -## 4. Roku production - -### 4.1 Budget - -Roku Production looks forward to partnering with you to ensure delivery of the best content to The Roku Channel. Below are some guidelines to assist with budgeting, scheduling and cost reporting for your project. Please reach out to Roku Production with any questions. - -#### 4.1.1 Chart of accounts (COA) - -Please reach out to Roku Production for the Roku COA template when you are ready to begin budgeting for your project. The COA is to be used throughout the lifecycle of the project: i.e., subsequent budget revisions and all Cost Reports, Variance Reports, General Ledgers, etc. - -The COA template is provided in movie magic budgeting format. - -#### 4.1.2 Assumptions page - -Please reach out to Roku Production to provide the Roku Assumptions Template. Please make sure the following information, when applicable, is included on the assumptions page: - -* Title, version #, ‘as of’ date matching budget -* Writing, Prep, Shoot, and Post Dates -* Include customary Budget Top Sheet header information such as: - * Name of the production company(ies) involved - * # of episodes - * Minutes per episode - * Name of person that prepared the budget - * Names of Executive Producers, Showrunner, Producers, and Director - * Key shoot locations (i.e., Los Angeles, NYC, etc.) - * Collective bargaining agreements (unions) - * If none, then note: Non-Union - * Number of shoot days per episode and total shoot weeks - * Number of edit days per episodes and total post weeks - * Total weeks from start to final delivery - * Budgeted Shooting Hours - * Foreign Exchange Rate -* Note if staff member on a show is staff at Prod Co / Studio -* FX rate (if any work is to take place outside of the United States) -* Tax incentive estimate, including estimated sales rate for transferable tax credits if applicable -* Residuals estimate, broken out by guild, and including any foreign residual buyouts -* List out all budgetary exclusions against fee calculations (see deal for customary exclusions) -* Please specify whether you will be utilizing music libraries, originally composed music, popular music, or a combination of all -* Please list out the following types of equipment/software: - * Camera, audio, and monitor/monitoring equipment - * Edit software (i.e., Final Cut, Premiere, Avid) - * Coloring and grading software -* List “Roku Alternative Media Delivery Specifications” version & date -* List “Roku Alternative Production Guidelines” (this document) version & date - -#### 4.1.3 Budget requirements - -Roku Production asks that the following information, when applicable, be included/considered when budgeting: - -* Include the budget as a PDF of the Movie Magic Budget (MMB) using Roku’s provided Chart of Accounts (COA) - -* Include title, version #, ‘as of’ date and page numbers - -* Include Budget Top Sheet header information as noted in [Section 4.1.2](#412-assumptions-page) - -* Avoid large flat allowances. Provide details instead (cost per day/week/month etc.) - -* Fringes should be by category and broken out -- avoid flat fringe rates - -* Include a variance column between your last budget and current budget - -* Suppress zero and empty accounts - -* Budget must be in US dollars - -* Do not include any overhead percentages - -* Do not include equipment loss and damage lines - -* Budget for worldwide title clearance and opinion letter - -* Include any security and general safety costs, include fees for risk managers or assessments and safety consultants - -* Budget for insurance as it relates to creative – minding stunts, aircraft, watercraft etc - -* Production counsel should reflect no more than 1.5% of the budget with customary exclusions - -* Agency Package Fee (if applicable) - -* Extraordinary talent fees and costs should be excluded from all fee calculations - -* Budget for all necessary worldwide clearances in **all media** for music and footage - * All licenses required for the production, synchronization, exhibition, performance, distribution, and exploitation (including in context marketing and promotion) of the Program by Roku for the term of the license - * Include music label waiver costs, if required - * Include AFM fees if applicable - * Reach out to Roku Legal with specific questions related to required terms - -* Computer Box Rentals are capped at $50/week and cannot exceed $500 overall - * Please provide an inventory with values for larger box rentals - * Larger rentals are capped at 50% of the total value over the course of the project - -* Edit bays (equipment & bay) should not exceed $750 per bay/week. Story stations should not exceed $250 per bay/week – if costs exceed these rates, please provide a quote. - -* Include any applicable tax incentive amounts and associated auditing costs - -* Refer to your Roku Alternative Media Delivery Specifications for the following: - * Cut Review Process for budgeting Post - * Include captioning, subtitles, and technical QC in your budget - * A list of preferred vendors will be provided by Roku Post - -* Spend beyond the Approved Budget is never authorized without **written** approval from Roku Production - -* For each budget revision please be sure to note the date, version and bullet point relevant changes in the body of the email - -#### 4.1.4 Foreign exchange rate (aka FX) - -If shooting in a location outside of the United States please be sure to note what foreign exchange rate you have assumed in your budget. - -* Partner is responsible for noting the FX on the top of the budget top sheet as well as the assumptions. - -#### 4.1.5 Tax incentives - -If shooting in a location in which a tax incentive or rebate is accessible, please be mindful of the below: - -* Partner is responsible for confirming whether production is eligible for potential incentives based on the project format and minimum production spend - -* Roku Production to confirm in writing how / who is responsible for applying for tax incentives/rebates - * Please work with Roku Production when filing for incentives/rebates - -* Please reference closed deal for contractual funding; for example, if Roku funds the Net budget -- differential between the Gross and Net budget is the responsibility of the Studio/Production Company - * Roku **does not** pay interest associated to financing the tax incentive - * Roku **will allow** the following incentive related expenses to be line items in the approved budget: - * Audit Fees associated with filing for the incentive (e.g., Certified Public Accountant or Third-Party Auditor/Firm) - * Post Accounting as needed in finalizing expenses in conjunction with submitting final documentation - * Tax Credit Analysis, Applications, and Admin Fees - * Fees associated with transferring/selling credit - * Bank Fees, i.e., account set-up (not fees related to negligence of Partner e.g., late fees, return checks) - * Roku requires confirmation of the final tax incentive allocation for the production - * If you plan to access a transferable credit, confirmation of the estimated sales rate should be listed in the budget and assumptions - * Final tax incentive allocation is required to close out the show cost report - * Final documentation will vary based on the location in which you shoot, and the type of credit received. Below is a list of items that may be required when wrapping out your production: - * Tax Credit Certificate - * Application/Letter of Transfer/Sale - * Approval Letter - * Eligibility Certificate and/or Completion Certificate - * Please reflect all VAT tax in the Cost Report and flag those costs the General Ledger within the naming convention “VAT” - * Please review the Roku Credit Requirements per the Roku Media Delivery Specifications prior to agreeing to any embedded logo credit related to receiving tax credits or incentive uplift - -#### 4.1.6 Guild and union affiliation(s) - -Email Roku Production and Roku Legal prior to engaging with the guild(s) / union(s). - -#### 4.1.7 Agency package fee - -When applicable, please include an Agency Package Fee within the production budget. - -* Alternative & Documentary Package Fees should be calculated at 3% of the 80% total budget, unless otherwise noted by Roku Business Affairs. - -#### 4.1.8 Unapproved budgetary line items - -Roku does not typically allow the following examples, or similar, to be included as line items in Approved Budgets: - -* Copyright Costs -* Contingencies -* Partner Overhead -* Legal Fees (over 1.5%) -* Entity Fees -* State Filings -* Bank Fees -* Partner travel and associated expenses -* Partner software licenses (i.e., PIX, DAX, Adobe Cloud, etc.) -* Advanced financing interest, loans, etc. -* All expenses related to the program beyond Roku delivery and exhibition - -#### 4.1.9 Approved budget - -All Conditions Precedent and required certificates of insurance (e.g., General Liability, Errors & Omissions) must be fulfilled prior to the official Greenlight/Budget Approval being issued. Additionally, prior to Roku Production sending the official Greenlight / Budget approval, Roku requires a final budget packet to review. The packet should consist of the following items: - -* Assumptions -* Budget -* Current Calendar -* Supporting Documents as applicable - -Upon review and acceptance of the final budget packet, Roku Production will issue the official Greenlight / Budget Approval via email. The Budget Approval email will trigger cash flow or milestone payment review and approval. - -* Upon receipt of the greenlight email, if you have not already done so, send Roku Production the locked budget you will be cost reporting against. - -### 4.2 Calendars - -Revised calendars are required whenever there is a schedule adjustment. Please use the following when submitting calendars: - -* Every version of the calendar should have title, version #, ‘as of’ date and page numbers -* Once in production, any changes to the post schedule/calendar must be submitted to [altprod@roku.com](mailto:altprod@roku.com) and [dlropost@roku.com](mailto:dlropost@roku.com) for approval within 24 hours -* In the body of the email that comes with calendar revisions, bullet point relevant changes to current calendar. Roku Production will review and confirm via email if approved. -* Master delivery dates cannot shift without **written** approval by Roku Production and Post - -#### 4.2.1 Calendar requirements - -Your calendar should cover all phases of production (i.e., casting, pre-production, physical production, post, QC and final delivery) and include key dates, as applicable, for the following: - -* Pre-production - * Writing (if/when applicable) - * Casting weeks including deadlines - * Key hire start and end dates - * Set design milestones, tech scout -* Production - * Prep, set-build/load in, equipment set up, rehearsal(s), shoot, and wrap dates - * Please identify on your calendar when you plan to shoot and deliver your camera test (see [Section 4.2.3](#423-camera-test-milestone), Camera Test Milestone) -* Post - * Start and wrap, finishing (i.e., audio and color), delivery of cuts and when notes are due, and master delivery dates - * Please refer to your Alternative Media Delivery Specs, Review Cut Process, as you build out your schedule - * Visual effects milestones (i.e., Visual effects review 1, Visual effects review 2) - * Please be sure to build time into your delivery schedule to account for the Roku QC process. Roku advises that you set aside two weeks for each episode to complete QC of all masters. - * Roku Post will provide a list of approved QC vendors - -#### 4.2.2 Game play/table reads/blocking/rehearsal - -* If applicable, Roku requests game play, table reads, and blocking rehearsal for our content -* Typically, game play is a full run-through to time of the game or challenge course to determine the course, camera positioning, and coverage -* Typically, the table read is a one-time read-thru of all the scripts, with at least the lead talent in attendance -* Unless otherwise discussed with Roku Production, the rehearsal covers set design, lighting, color tones, and any/all department presentations depending on the specific creative needs of the show -* Please reach out to Roku Production for an invitation list to game play, table reads and / or rehearsal -* Please provide a dial-in/video conference line for Roku representatives who may not be able to attend the table read in-person - -#### 4.2.3 Camera test milestone - -* The Director, Director of Photography and/or producing team should oversee the camera test -* Please provide scratch framing mocks or test storyboard compositions - * It can be a “slap-comp sequence” or “center-punching sequence,” generated by the Editor or Assistant Editor - * Ideally this is sent prior to commencement of principal photography. If that isn’t possible, within the first two days of shooting or rehearsal -* Your Roku Post Manager will create a specific folder via [Frame.io](http://frame.io/) for uploading the camera test - -#### 4.2.4 Production meetings/rehearsals/tech scouts - -Roku Production will attend in person or via dial-in. It is asked that a phone dial-in be made available, for all attending Roku departments. - -### 4.3 Internal ad sales needs - -As the The Roku Channel is 100% ad supported, we will reach out prior to commencement of principal photograpy to discuss capturing a very simple, straight forward message from talent about the show to be used internally only. - -* This is a very simple video, straight to camera, not color corrected, for internal use only. -* Roku will manage all aspects of the content (i.e. wording). This should take no more than 10-20 minutes to capture. -* For example, talent talking straight to camera says: “Hey, I’m TBD, coming to you live from the set of _insert Show Title here_ streaming soon on The Roku Channel!” - -### 4.4 Set visits - -Make sure to plan for additional IFB’s/Audio and monitors to accommodate Roku Executive and Talent Reps visiting set. If uncertain, please reach out to your Roku Production Point to get a list of guests. - -* This could include but is not limited to; IFB’s, monitors, chair(s), etc. - -### 4.5 Cost report requirements - -Deliver Cost Reports to Roku Production and Production Finance weekly on Thursdays, throughout all phases of production, using industry standard software. Please use the following when submitting cost reports: - -* The cost report should reflect the Approved Production Costs -* The approved budget column must match the amounts and chart of accounts of the budget submitted and approved by Roku Production -* Cost report must include the following columns: actuals to date, committed costs, total costs, estimate to complete, estimated final costs, approved budget and variance (over/under) -* In the event of Roku approved breakage, the approved breakage amount must appear in an approved overage column in the cost report. Cost report software must have this capability -* Fringes should be per category to match the approved budget -* No negative ETC's -* Cost report to be accompanied with general ledger, trial balance, purchase order log, and variance report -* If applicable - Please reflect all VAT tax in the Cost Report and flag those costs the General Ledger within the naming convention “VAT” -* Movement between budget accounts in an amount less than $10,000 is permissible. Amounts at or over $10,000 are subject to written approval by Roku Production - * Any movement from the following accounts need prior approval from Roku Production: - * Cast - * VFX - * Music - * Safety Costs - * Adjusting number of shooting days - -Roku will not be responsible for any amounts in excess of the Approved Budget without prior **written** approval by Roku Production. - -### 4.6 Staff & crew - -Roku Content, Production and Post reserves customary approval of department heads, key creative and key production staff. This can include, but is not limited to: - -* Showrunner, Casting Director/Company, Director, Director of Photography, Line Producer, Accountant, Post Supervisor and Editors - * Please submit credit, resume and/or reel (as applicable) to the appropriate Roku Content, Production, or Post contact - -* Please do not put any key production hires on “pay or play” deals without prior **written** approval from Roku Business Affairs - -* Outside production counsel must be experienced and qualified based on the nature of the program - -### 4.7 Covid-19 - -Roku follows the guidance of the AMPTP and local regulations when it comes to Covid-19 health and safety guidance. Please work with Roku Production if you have any questions. - -## 5. Finance - -### 5.1 Payments - -* Cash Flow Approval and funding occurs after all Conditions Precedent have been met and the official greenlight / budget approval email has been sent by Roku Production; including but not limited to, receipt and approval of COIs -* Cash Flow Template will be provided Roku Production Finance -* Submit payment schedule to Roku Production Finance and cc your Roku Production Executive for review and approval - * Include invoice due dates, percentage, and amounts -* If applicable, Production Company Fee, Breakage, and Residuals/Buyouts can be listed, but should not roll up into the total milestone payments - -#### 5.1.1 Payment descriptions - -Possible payment milestones and when to submit invoices for processing listed below: - -* Complete Delivery / Complete & Final Delivery - Invoice due upon receipt and approval of all Roku Post Paper and Media Deliverables. -* *Production Company Fee – Invoice due upon receipt and approval of all Paper Deliverables and Final Cost Report -* Audit - Reference closed project deal terms for audit language - -#### 5.1.2 Invoices - -All invoices should be sent via email to [roinvoices@roku.com](mailto:roinvoices@roku.com) - -When submitting invoices, the subject line should read “Project Name” | Invoice “Description” - -* For example: Best Show Ever | Invoice: December Cashflow - -Email must include: - -* Vendor Name -* Project Name -* Season # -* Invoice description (i.e., December Cash Flow or Commencement of Principal Photography) - -### 5.2 Changes to banking information - -If your banking information changes at any given point, Partners must send an email to [roinvoices@roku.com](mailto:roinvoices@roku.com). - -Please note this email must come from an employee of the company or will not be accepted. - -The subject line should read “Vendor Name” | “Project Name” - UPDATED Banking Information - -The email must include: - -* Studio/ProdCo name -* Project Name -* What Banking Information has been updated - i.e. Routing or account or both -* Attachment with updated information on company letter head -* Contact information for the point person: Name and phone number - -Please note, AP will need to verify validity with a phone call to the point person noted above. - -Sample email below: - -_Hello,_ - -_This email is to let you know we "INSERT COMPANY/VENDOR NAME" have updated routing and/or account information for the project currently known as "INSERT PROJECT NAME". Please see attached updated information._ - -* _TBD Studio_ -* _Project Title_ -* _Updated routing number attached (or updated account number attached)_ -* _Contact: TBD at xxx.xxx.xxxx_ - -Once AP confirms the update has been made, Production Finance will let you that you may submit your invoices. - -Important Notes: - -* Roku requires 1 week to amend in the system. -* Invoice(s) may be submitted no earlier than 1 week from any bank change requests. -* Invoice(s) must be submitted no later than EOD Thursday to potentially make the following week pay run. - -### 5.3 Production company fee calculation - -Please refer to your agreement to determine if a Production Company fee is applicable. If so, please see below. - -* Calculate your prod co fee with applicable exclusions as per your closed deal and include the prod co fee amount on the Budget Assumption Page - -### 5.4 Residual calculation - -The Roku Channel is a free to consumer ad supported platform (AVOD). Roku asks that Partners calculate the estimated residuals, again **please be mindful of The Roku Channel’s AVOD status**. - -* Check the definition of “accountable receipts” or “distributor’s gross” with the applicable guild -* Include the project residual estimate on the Budget Assumptions Page -* Residuals should **not** be a line item in the budget - * For purposes of calculating a rebate, if you need to include buyouts in your budget please discuss with Roku production -* Roku may request an updated residual estimate prior to closing out the project - -Please check with your Roku Production Executive if this applies to this project. - -### 5.5 Overages & breakage - -Roku will not be responsible for any overages. Production spend over and above the Approved Budget is never authorized without written approval from Roku Production. If there is a request made by Roku that materially changes the creative elements or delivery of the project it is the responsibility of the Prod Co/Studio to reach out to Roku Production to discuss the financial implications **before** any decisions/changes are made. - -* Approved talent breakage is paid 50% upon commencement of principal photography, 50% on the completion of principal photography - -* Fringe is paid on actuals which is typically in the last 50% payment or later - -* If circumstances call for non-talent related breakage (i.e “Other” breakage) this payment is held until Roku Production receives and vets the final cost report - -* Underages will offset approved breakage, unless approved in writing by Roku Production - -### 5.6 Close out - -In order to start the project close out process Roku must receive and approve all media and paper deliverables including the final cost report. Please follow the below when submitting your final cost report: - -* For a cost report to be considered finalized all PO’s and ETC’s should be zeroed out unless agreed to in writing by Roku Production -* When sending through your final cost report packet, please note “FINAL Cost Report” in the subject line and confirm in the body of the email that all costs for the project are accounted for -* In the case of open PO’s (e.g., Music Rights) Roku requires backup for all pending expenses before approving the final cost report -* When Roku Production confirms the final cost report is approved, Roku Finance will release the final payment (i.e., Production Company fee) - -### 5.7 Audit - -Please reference the closed deal regarding Audit election and timelines. - -* Roku will notify Partner in writing as to whether it intends to conduct an audit -* Roku Production Legal will provide Partners with the "Roku Audit Requirements". -* Audit Requirements Document will elaborate on the following: - * Non-reimbursable expenses unless previously approved - * Overages/Breakage - * Required documentation - -****PLEASE NOTE:**** The Audit holdback payment will not be released until the audit is complete or waived. In the event Roku elects not to proceed with an audit: - -* * You will be notified by Roku Production if there will be no audit - * If the audit is waived, the Audit Holdback payment will be released upon reconciliation of final cost report and submission of the final invoice - -### 5.8 Roku marketing / publicity - -You will be introduced to Roku Marketing during or following the production kick-off call. - -Unless otherwise discussed and approved by Roku Production, all Marketing and PR costs are expected to be excluded from the budget. - -There may be circumstances when Roku requests assistance with marketing efforts. In the event Roku pre-approved any marketing expenses (i.e., unit photography, behind the scenes, hair and make-up, etc.) please review the below: - -* Marketing invoices should be sent to your Roku Marketing contact -* Marketing expenses should not be included as part of the series budget -* Marketing expenses should not be included as an expense in the cost report - -### 5.9 Trade-outs - -When budgeting, do **NOT** assume any trade-outs will be allowed. We are an ad-supported platform and cannot guarantee trade-outs. Product placement and trade-outs may be allowed at Roku’s discretion. - -* If a trade-out opportunity presents itself, please fill out the Trade-Out Request form located in the downloadables folder on the Hub. -* Submit the form to Roku Production and Production Legal for approval using the email template below. If you do not yet have access to the Hub, please reach out to Roku Production and we will send you the form. -* Roku Production will reply to your email confirming approved or not. Your legal counsel will then email Roku Legal and Production any legal documents associated with the trade-out prior to signature and filming. -* If applicable, you may include a deadline of when you need to have an answer to move forward with the trade-out. - -_**To:** Production Lead_ - -_**cc:** Melissa Hamilton, Michelle Bado, Production Legal Lead_ - -_**Subject line:** Show Name | Trade-out request_ - -_**Body of email:**_ - -_Trade-out request form attached and details below:_ - -_Company:_ - -_Cash Value of Production Donation:_ - -_Exposure: Is this guaranteed or non guaranteed trade out? + Detail of exposure (I.e., special thanks, verbal, etc.)_ - -_Additional/Social Requests:_ - -_Company to Provide: List out what brand/company is supplying_ - -## 6. Production legal - -Prior to creating content for exhibition on The Roku Channel, please review the Roku Production Legal Guidelines below with your legal counsel. Reach out to Roku Production Legal if there are any questions or concerns. - -### 6.1 Roku production legal guidelines - -The Roku Production Legal Guidelines will cover the topics listed below. You can review the complete legal guidelines via the link sent to you. If you do not have it, please reach out to your Roku Production point. - -* Guilds/Unions -* Clearances -* Integrations/Sponsorship/Trade-Outs -* Cast Notices -* Talent Publicity and Promotion -* Risk & Safety -* Safety/Respect in the Workplace -* Music (approved PRO's) - -### 6.2 Insurance - -We rely on our production Partners to acquire the appropriate coverage as deemed necessary for each production. When binding coverage please ensure it satisfies all of Roku’s insurance requirements with the exception of Workers’ Compensation/Employer’s Liability, Owned Automobile, Guild Travel Accident (if your production is union) and any local foreign compulsory coverage(s) (such as auto liability) which are collectively the responsibility of the production company. - -#### 6.2.1 Certificates of insurance - -Certificates of Insurance should be bound and sent to Roku Production / Production Legal prior to the commencement of any production activities. - -Below is a list of Certificates of Insurance that may be required by Roku. This information along with coverage limits for this project shall be provided by Production Legal. - -* Errors & Omissions -* General Liability -* Auto Liability -* Statutory Workers Compensation Coverage -* Umbrella/Excess -* Entertainment Package -* Applicable Collective Bargaining Agreement/Guild Travel Accident Coverage -* Foreign General Liability (if applicable) -* Cast Insurance - * The necessary cast members should be declared so they are eligible for cast insurance. - * Please discuss with Roku Production Legal whether your talent needs to be declared separately for Cast Insurance Coverage; and additionally, whether accident-only or full coverage would be preferable. -* Higher-Hazards & Special Risk Coverage (i.e., Aircraft/Watercraft Liability, etc.) - * There may be special risks associated with your project. This includes but is not limited to stunts, firearms, minors, pyrotechnics, precision driving, aircraft, drones, watercraft, railroads, foreign activities, animals, or any unusual or hazardous exposures and/or conditions involving either cast or crew. Special Risk Coverage may be required for your production, please budget accordingly. - -Roku must be named as an additional insured. Please use the following for issuing COIs to Roku: - -Purple Tag Originals, LLC -1173 Coleman Avenue -San Jose, CA 95110 - -Under “Description” on COIs, please list: - -Purple Tag Originals, LLC, its parent, its subsidiaries and affiliates and their respective officers, directors, agents and employees, as now or hereafter may exist and any other persons or entities as Roku may designate to Produce from time to time. - -Please inform Roku Production and Production Legal in writing, of any claims, threats of claims, suits, damage to property or any other loss. Roku Production will need to be updated throughout the claim process and any receipts that will offset production costs. - -### 6.3 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-contect promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -Please reach out to your Roku Production Executive with specific questions or if there are cost implications above and beyond what is in the budget to license per the aforementioned guidelines. - -### 6.4 Content takedown request - -We understand there may be occasions when content needs to be removed from The Roku Channel (e.g., 3rd party rights issues, legal orders, Public Relations concerns). In the event content needs to be removed, please email Roku Production and Roku Production Legal. - -We ask that you provide the following information in the body of your email request: - -* The episode # and title -* The specific reason for the removal request (e.g., "wrong photo included in opening shot," "music was not cleared properly") -* A point of contact along with email and phone number to call for any follow up questions -* An ETA for delivery of a replacement episode -* Ideally when requesting that content be removed from the Roku eco-system, you will be able to provide a replacement episode ASAP. If this is not possible (or deemed not necessary based on the content), Roku will address on a case-by-case basis - -## 7. Post - -Please review the Roku Alternative Media Delivery Specifications for a comprehensive breakdown of all post workflows and media deliverables. The document can be found via the “Welcome to Roku Production” site or the Hub in the Post – Alternative Folder. - -Roku’s approved platform for dailies, rough cut release, and final archive is [Frame.io](http://frame.io/), which Roku provides free of charge to our production partners. All content sent to Roku for review needs to be shared via [Frame.io](http://frame.io/). - -### 7.1 Music cue sheets - -Music cue sheets are required for all projects. Please use the cue sheet template found on the ASCAP website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub under the Production Legal – Alternative folder. - -Upload completed cue sheets to the Hub. If you have any specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Grossberg at [sgrossberg@roku.com](mailto:sgrossberg@roku.com). - -## 8. Paper deliverables - -Roku uses a deliverables Hub (“Hub”) to receive specific production documents. The Hub is project specific and will serve as the portal for key paper deliverables. Please remember the materials and folders are confidential and may not be shared beyond authorized parties. With a few exceptions, the Hub is used in lieu of emailing various Roku teams relevant documentation. - -Prior to pre-production you will receive an email with instructions for accessing the Hub. - -Due to the **confidential** nature of the requested paper deliverables, access to the Hub will be limited to four (4) key project personnel. Only those who are responsible for uploading the deliverables as noted in [section 8.1](#81-required-paper-deliverables), should have access. - -### 8.1 Required paper deliverables - -Productions should be uploading documents to the Hub on an ongoing basis throughout all phases of production, starting with pre-production and concluding with uploading final documents during wrap. - -Below you’ll find a list of **paper** deliverables for Production, Post and Production Legal. Please be aware, this list is subject to amendment (within reason) at any time. Make sure to follow specific instructions for each document and upload accordingly. Please note other departments may have additional required deliverables. - -#### 8.1.1 Production - -* Call Sheets & Maps (upload at the same time as distribution to crew) -* Cast Lists (all approved and final versions) (If applicable) -* Field Notes -* Hot Sheets -* Format Bible (if applicable) -* Episode Outlines & “Scripts” (if applicable) (all approved and final versions) -* Schedules (all approved and final versions) -* Staff & Crew Lists (all approved and final versions) -* Production Calendar (all approved and final versions) -* Production Reports (final versions to be uploaded weekly) -* Completed Deliverables Checklist -* Vendor List -* Workflow Documentation (if applicable) -* Trade-Out Request Form -* Trade-Out Grid - -#### 8.1.2 Post - -* Post Calendar (all approved and final versions) -* As Broadcast Scripts -* CC/Sub/FN Files -* Episodic Delivery Checklist -* Final Post Contact List -* Final Vendor List -* Font Memo -* Metadata Spreadsheet -* QC Reports -* Credits (also vetted by Business Affairs) -* Music Cue Sheets (vetted by Production Legal) -* Text Spotting List (TSL) -* Segment Rundown - -#### 8.1.3 Production legal - -* Ad/Promo Restrictions -* Fair Use Grid (if applicable) -* Insurance Certificates - GL & E&O -* Pence Document -* Tax Incentive Registration, Certificate, Evidence of Sale/Transfer (if applicable) -* Title Report & Legal Opinion -* Workers Comp -* Talent Agreement(s) -* Background Checks (if applicable) -* Location Agreements -* Guild & Union Documentation (if applicable) -* Employment Agreements - -#### 8.1.4 Public relations/marketing - -* Approved Bios -* Still Photography - -### 8.2 Deliverables checklist - -On the Hub you will find a deliverables checklist, the checklist is considered part of your paper deliverables. - -Please only mark items as complete once the final versions have been uploaded. If an item is not applicable (“N/A”), please upload a word document that says N/A and a short explanation as to why it is not applicable to your production. You may then mark that item complete on the checklist. - -Email Roku Production once all items have been delivered and the checklist is filled out completely. Once final delivery is received and approved, access to the Hub will be removed. - -For questions or concerns please reach out to Roku Production at [altprod@roku.com](mailto:altprod@roku.com). - -### 8.3 Naming conventions - -All Roku projects have a unique Project Title ID (PTID). You must follow specific naming conventions for the files to be considered acceptable. Examples of how each file(s) should be named can be found on the Hub, in the Production - Alternative folder. - -If items are not delivered correctly, they will not be accepted. Please do not add or remove folders. If you have questions or can't find specific folders, please reach out to Roku Production. - -### 8.4 Guidelines and templates - -There is a “Guidelines & Templates'” section located on the Roku Deliverables Hub. Here you will find folders containing key documents in relation to each department (Production Legal, Post, Production).  - -#### 8.4.1 Post – alternative folder - -* Alternative Media Delivery Specs -* Credits Approval Form -* Episodic Delivery Checklist -* Ingest Metadata Template -* Post Grid Template -* Preferred Vendor List -* Segment Rundown -* Text Spotting List - -#### 8.4.2 Production legal – alternative folder - -* Ad Promo Template -* Insurance Guidelines -* Music Cue Sheet Template - -#### 8.4.3 Production – alternative folder - -* Alternative Production Guidelines -* Chart of accounts (COA) diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/branded-prod-guidelines.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/branded-prod-guidelines.md deleted file mode 100644 index 34e1cd18..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/branded-prod-guidelines.md +++ /dev/null @@ -1,633 +0,0 @@ ---- -title: "Branded production guidelines" -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- - -*Version 3.0 - August 2024* - -## 1. General Overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, Mexico, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices.  - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Production Guidelines outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -## 2. Welcome to Roku production - -We look forward to working with you! You should have received a “Welcome to Roku Production” email along with the Production Kick-Off documents outlined below. Please review the documents in their entirety, upon series pick-up Roku Production will reach out to schedule a kick-off call. During the call we can address any questions you may have. - -### **2.1 Production kick-off documents** - -#### **2.1.1 Branded Production Guidelines** - -- Roku production document for branded content & branded series – document you are currently reading - -#### **2.1.2 Branded media delivery specifications** - -- Roku post specifications for branded content & branded series - -#### **2.1.3 Branded production legal guidelines** - -- Roku Production Legal guidelines when creating content for exhibition on Roku - -## 3. Roku communication - -### **3.1 Roku emails** - -For email correspondence, Roku asks that the **full name** of the project be included in the subject line. Please do not use acronyms for the title. - -### **3.2 Roku branded content contact sheet** - -The Roku Branded Content Contact Sheet is for Partner use only. Please do not distribute. - -### **3.3 Roku distribution list** - -Roku Production will send you a distribution list. The distro list will include the name, title, email, and required documents / media for each Roku recipient. There are a handful of documents we request be emailed directly to Roku that include, but are not limited to: - -- Budgets -- Call Sheets -- Scripts / Episode Outlines -- Prep Schedules -- Production Calendars -- Cast & Crew Lists -- Wrap Reports -- Daily Production Reports (Prelim & Approved) -- Cost Reports - -**Do not include the Roku name or logo on any documents** (including contact sheets, call sheets, production reports, casting notices etc.) without written approval from Roku Production Legal. - -### **3.4 Roku calls** - -Upon the below milestones, calls will be set with Roku Production: - -- Production Kick-Off Call -- Weekly Prep calls before commencement of Principal Photography -- Weekly Production Call throughout Principal Photography -- Wrap of Principal Photography -- Any major production or overall schedule changes -- 1 week before Delivery of the Final Episode - -Upon completion of Principal Photography or one week prior to delivery of RC 1, Roku Post will initiate weekly post calls. - -### **3.5 Roku notifications** - -Please inform Roku Production, at least 2 weeks prior to any of the following activities or events: - -- Applying for tax incentives -- Traveling and filming outside the domestic United States -- Filming in aircraft/watercraft, including private planes and yachts -- Filming physically challenging or hazardous activities (including filming with firearms) -- Filming with minors or animals -- Filming a ride-along with law enforcement -- Filming nudity and/or sexual activities -- Filming hoaxes, using hidden cameras, and/or private investigators -- Filming any potential illegal activities -- Filming any on-camera or behind-the-scenes involving medical personnel, procedures, patients, facilities; psychological/psychiatric counseling; life coaching or other forms of therapy -- Filming with government officials, employees, and candidates, including any of the following: -- Faculty and teachers at government owned or controlled businesses or institutions (e.g., public universities, hospitals, national telecom companies) -- Employees of public international organizations, like the United Nations or World Bank -- An elected or appointed official, candidate for public office, or their family or staff -- Members of Royal Families -- Public school employees, firemen, law enforcement, military, etc. -- An elected or appointed official, candidate for public office, or their family or staff - -### **3.6 Roku emergency notifications** - -In the event of an emergency or incident, once the situation is stable, please contact Roku Production immediately. If you cannot reach Roku production, please call Production Legal. Incidents include, but are not limited to: - -- Stopping down pre-production, production, and/or post -- Unplanned hiatus or postponement -- Projected or occurring natural events (i.e., earthquakes, wildfires, hurricanes, tornadoes, etc.) -- Any suspected or confirmed drug use by on-camera talent, crew, or producers -- Cast, Crew, and general public medical concern including: -- Physical Altercations -- Hospitalization -- Arrest -- Personal Accident/Injury -- Vehicle accident -- Covid-19 health-related situation involving an individual, location, or government -- Planning to file an insurance claim due to force majeure -- Any allegation of cheating or unfairness in connection with a competition show -- Any claim or potential claim arising in connection with the production including threat of litigation -- Any other event (or planned event) that may pose a legal or reputation risk to Roku -- Any event, occurring or projected, that may impact any person(s) and/or actual production, physical production, or delivery of the series to Roku -- Any contact by the press or media regarding any aspect of the production, including talent and Covid-19 - -**AFTER** informing Roku, please email detailed information, while respecting the privacy of the individuals, regarding the incident to [altprod@roku.com](mailto:altprod@roku.com): - -- Title the subject of your email as follows: “Show Name” - Notification - CONFIDENTIAL -- If the incident is sensitive in nature, in the body of your email please relay that an incident has occurred and request an immediate call with Roku Production and Production Legal - -In the event of any non-emergency incident (property/location damage, equipment damage): - -- Please inform Roku Production -- Please be sure to note in the Production Report - -**SPECIAL NOTE:** In the event you are not able to immediately reach your Roku Production or Production Legal Executive please proceed with emailing [altprod@roku.com](mailto:altprod@roku.com) but use discretion in the details you share. - -## 4. Roku production - -### **4.1 Budget** - -Roku Production looks forward to partnering with you to ensure delivery of the best content to The Roku Channel. Below are some guidelines to assist with budgeting, scheduling and cost reporting for your project. Please reach out to Roku Production with any questions. - -#### **4.1.1 Chart of accounts (COA)** - -Please reach out to Roku Production for the Roku COA template when you are ready to begin budgeting for your project. The COA will be used throughout the project's lifecycle: subsequent budget revisions and all Cost Reports, Variance Reports, General Ledgers, etc. - -The COA template is provided in movie magic budgeting format. - -#### **4.1.2 Assumptions page** - -Please reach out to Roku Production to provide the Roku Assumptions Template. Please make sure the following information, when applicable, included on the assumptions page: - -- Title, version #, ‘as of’ date matching budget -- Writing, Prep, Shoot, and Post Dates -- Include customary Budget Top Sheet header information such as: - - Name of the production company(ies) involved - - \# of episodes - - Minutes per episode - - Name of person that prepared the budget - - Names of Executive Producers, Showrunner, Producers, and Director - - Key shoot locations (i.e., Los Angeles, NYC, etc.) - - Collective bargaining agreements (unions) - - If none, then note: Non-Union - - Number of shoot days per episode and total shoot weeks - - Number of edit days per episodes and total post weeks - - Total weeks from start to final delivery - - Budgeted Shooting Hours - - Foreign Exchange Rate -- Note if staff member on a show is staff at Prod Co/Studio -- FX rate (if any work is to take place outside of the United States) -- Include itemized breakout of any custom deliverables (i,e., additional trailer, cut downs, etc.) -- Tax incentive estimate, including estimated sales rate for transferable tax credits if applicable -- Residuals estimate, broken out by guild, and including any foreign residual buyouts -- List out all budgetary exclusions against fee calculations (see deal for customary exclusions) -- Please specify whether you will be utilizing music libraries, originally composed music, popular music, or a combination of all - - Please reach out to your Production point regarding access to a music library -- Please list out the following types of equipment/software: - - Camera, audio, and monitor/monitoring equipment - - Edit software (i.e., Final Cut, Premiere, Avid) - - Coloring and grading software -- List “Roku Branded Media Delivery Specifications” version & date -- List “Roku Branded Production Guidelines” (this document) version & date - -#### **4.1.3 Budget requirements** - -Roku Production asks that the following information, when applicable, be included/considered when budgeting: - -- Include the budget as a PDF of the Movie Magic Budget (MMB) using Roku’s provided COA -- Include title, version #, ‘as of’ date and page numbers -- Include Budget Top Sheet header information as noted in Section 4.1.2 -- Avoid large flat allowances. Provide details instead (cost per day/week/month etc.) -- Fringes should be by category and broken out -- avoid flat fringe rates -- Include a variance column between your last budget and current budget -- Suppress zero and empty accounts -- Budget must be in US dollars -- Do not include any overhead percentages -- Do not include equipment loss and damage lines -- Budget for worldwide title clearance and opinion letter -- Include any security and general safety costs, include fees for risk managers or assessments and safety consultants -- Budget for insurance as it relates to creative – minding stunts, aircraft, watercraft etc -- Production counsel should reflect no more than 1.5% of the budget with customary exclusions -- Agency Package Fee (if applicable) -- Extraordinary talent fees and costs should be excluded from all fee calculations -- Check with Roku Production when budgeting for all clearances (i.e. music). - - All licenses required for the production, synchronization, exhibition, performance, distribution, and exploitation (including in context marketing and promotion) of the Program by Roku for the term of the license - - Include music label waiver costs, if required - - Include AFM fees if applicable - - Reach out to Roku Legal with specific questions related to required terms -- Computer Box Rentals are capped at $50/week and cannot exceed $500 overall - - Please provide an inventory with values for larger box rentals - - Larger rentals are capped at 50% of the total value over the course of the project -- Edit bays (equipment & bay) should not exceed $750 per bay/week. Story stations should not exceed $250 per bay/week – if costs exceed these rates, please provide a quote. -- Include any applicable tax incentive amounts and associated auditing costs -- Refer to your Roku Branded Media Delivery Specifications for the following: - - Cut Review Process for budgeting Post - - Include captioning, subtitles in your budget - - A list of preferred vendors will be provided by Roku Post Post - - i.e. GFX, Captioning, QC, etc. -- Spend beyond the Approved Budget is never authorized without **written** approval from Roku Production -- For each budget revision please be sure to note the date, version and bullet point relevant changes in the body of the email to Roku Production. - -#### **4.1.4 Foreign exchange rate (aka FX)** - -If shooting in a location outside of the United States please be sure to note what foreign exchange rate you have assumed in your budget. - -- Partner is responsible for noting the FX on the top of the budget top sheet as well as the assumptions. - -#### **4.1.5 Tax Incentives** - -If shooting in a location in which a tax incentive or rebate is accessible, please be mindful of the below: - -- Partner is responsible for confirming whether production is eligible for potential incentives based on the project format and minimum production spend -- Roku Production to confirm in writing how / who is responsible for applying for tax incentives/rebates - - Please work with Roku Production when filing for incentives/rebates -- Please reference closed deal for contractual funding; for example, if Roku funds the Net budget -- differential between the Gross and Net budget is the responsibility of the Studio / Production Company - - Roku **does not** pay interest associated to financing the tax incentive - - Roku **will allow** the following incentive related expenses to be line items in the approved budget: - - Audit Fees associated with filing for the incentive (e.g., CPA or Third-Party Auditor/Firm) - - Post Accounting as needed in finalizing expenses in conjunction with submitting final documentation - - Tax Credit Analysis, Applications, and Admin Fees - - Fees associated with transferring/selling credit - - Bank Fees, i.e., account set-up (not fees related to negligence of Partner e.g., late fees, return checks) - - Roku requires confirmation of the final tax incentive allocation for the production - - If you plan to access a transferable credit, confirmation of the estimated sales rate should be listed in the budget and assumptions - - Final tax incentive allocation is required to close out the show cost report - - Final documentation will vary based on the location in which you shoot, and the type of credit received. Below is a list of items that may be required when wrapping out your production: - - Tax Credit Certificate - - Application/Letter of Transfer/Sale - - Approval Letter - - Eligibility Certificate and/or Completion Certificate - - Please reflect all VAT tax in the Cost Report and flag those costs the General Ledger within the naming convention “VAT” - - Please review the Roku Credit Requirements per the Roku Media Delivery Specifications prior to agreeing to any embedded logo credit related to receiving tax credits or incentive uplift. - -**4.1.6 Guild and union affiliation(s)** - -Email Roku Production and Roku Legal prior to engaging with the guild(s) / union(s). - -**4.1.7 Unapproved budgetary line items** - -Roku does not typically allow the following examples, or similar, to be included as line items in Approved Budgets: - -- Copyright Costs -- Contingencies -- Partner Overhead -- Legal Fees (over 1.5%) -- Entity Fees -- State Filings -- Bank Fees -- Partner travel and associated expenses -- Partner software licenses (i.e., PIX, DAX, Adobe Cloud, etc.) -- Advanced financing interest, loans, etc. -- All expenses related to the program beyond Roku delivery and exhibition - -**4.1.8 Approved budget** - -All Conditions Precedent and required certificates of insurance (e.g., GL, E&O) must be fulfilled prior to the official Greenlight / Budget Approval being issued. Additionally, prior to Roku Production sending the official Greenlight / Budget approval, Roku requires a final budget packet to review. The packet should consist of the following items: - -- Assumptions -- Budget -- Current Calendar -- Supporting Documents as applicable - -Upon review and acceptance of the final budget packet, Roku Production will issue the official Greenlight / Budget Approval via email. The Budget Approval email will trigger cash flow or milestone payment review and approval. - -- Upon receipt of the greenlight email, if you have not already done so, send Roku Production the locked budget you will be cost reporting against. - -### **4.2 Calendars** - -Revised calendars are required whenever there is a schedule adjustment. Please use the following when submitting calendars: - -- Every version of the calendar should have title, version #, ‘as of’ date and page numbers -- Once in production, any changes to the post schedule/calendar must be submitted to [altprod@roku.com](mailto:altprod@roku.com) and [dlropost@roku.com](mailto:dlropost@roku.com) for approval within 24 hours -- In the body of the email that comes with calendar revisions, bullet point relevant changes to current calendar. Roku Production will review and confirm via email if approved. -- Master delivery dates cannot shift without **written** approval by Roku Production and Post - -#### **4.2.1 Calendar requirements** - -Your calendar should cover all phases of production (i.e., casting, pre-production, physical production, post, QC and final delivery) and include key dates, as applicable, for the following: - -- Pre-production - - Writing (if / when applicable) - - Casting weeks including deadlines - - Key hire start and end dates - - Set design milestones, tech scout -- Production - - Prep, set-build/load in, ESU, rehearsal(s), shoot, and wrap dates - - Please identify on your calendar when you plan to shoot and deliver your camera test (see [Section 4.2.3](#423-camera-test-milestone), Camera Test Milestone) -- Post - - Start and wrap, finishing (i.e., audio and color), delivery of cuts and when notes are due, and master delivery dates - - Please refer to your Branded Media Delivery Specs, Review Cut Process, as you build out your schedule - - GFX milestones (i.e. GFX review 1, GFX review 2) - - VFX milestones (i.e., VFX review 1, VFX review 2) - -#### **4.2.2 Game play / blocking / rehearsal** - -- If applicable, Roku requests game play, and blocking rehearsal for our content -- Typically, game play is a full run-through to time of the game or challenge course to determine the course, camera positioning, and coverage -- Unless otherwise discussed with Roku Production, the rehearsal covers set design, lighting, color tones, and any/all department presentations depending on the specific creative needs of the show -- Please reach out to Roku Production for an invitation list to game play and / or rehearsal -- Please provide a dial-in/video conference line for Roku representatives who may not be able to attend the table read in-person - -#### **4.2.3 Camera test milestone** - -Roku Production will alert you if the below is applicable to your project. - -- The Director, Director of Photography and/or producing team should oversee the camera test -- Please provide scratch framing mocks or test storyboard compositions - - It can be a “slap-comp sequence” or “center-punching sequence,” generated by the Editor or Assistant Editor - - Ideally this is sent prior to commencement of principal photography. If that isn’t possible, within the first two days of shooting or rehearsal -- Your Roku Post Manager will create a specific folder via [Frame.io](http://frame.io/) for uploading the camera test - -#### **4.2.4 Production Meetings / rehearsals / tech scouts** - -If applicable, Roku Production will attend in person or via dial-in. It is asked that a phone dial-in be made available for all attending Roku departments - -### **4.4 Set visits** - -Make sure to plan for additional IFB’s/Audio and monitors to accommodate Client Reps, Roku Executive and, Talent Reps visiting set. If uncertain, please reach out to your Roku Production Point to get a list of guests. - -- This could include but is not limited to; IFB’s, monitors, chair(s), etc. - -### **4.5 Cost report requirements** - -After greenlight and milestone approval, connect with your Production Lead on if / when cost reports are expected for this project. - -- The cost report should reflect the Approved Production Costs -- The approved budget column must match the amounts and chart of accounts of the budget submitted and approved by Roku Production -- Cost report must include the following columns: actuals to date, committed costs, total costs, estimate to complete, estimated final costs, approved budget and variance (over/under) -- In the event of Roku approved breakage, the approved breakage amount must appear in an approved overage column in the cost report. Cost report software must have this capability -- Fringes should be per category to match the approved budget -- No negative ETC’s -- Cost report to be accompanied with general ledger, trial balance, PO log, and variance report -- If applicable - Please reflect all VAT tax in the Cost Report and flag those costs the General Ledger within the naming convention “VAT” -- When applicable, movement between budget accounts in an amount less than $10,000 is permissible. Amounts at or over $10,000 are subject to written approval by Roku Production - - Any movement from the following accounts need prior approval from Roku Production: - - Cast - - VFX - - Music - - Safety Costs - - Adjusting number of shooting days - -Roku will not be responsible for any amounts in excess of the Approved Budget without prior **written** approval by Roku Production. - -### **4.6 Staff & crew** - -Roku Content, Production and Post reserves customary approval of department heads, key creative and key production staff. This can include, but is not limited to: - -- Showrunner, Casting Director/Company, Director, Director of Photography, Line Producer, Accountant, Post Supervisor and Editors - - Please submit credit, resume and/or reel (as applicable) to the appropriate Roku Content, Production, or Post contact -- Please do not put any key production hires on “pay or play” deals without prior **written** approval from Roku Business Affairs -- Outside production counsel must be experienced and qualified based on the nature of the program - -### **4.7 Covid-19** - -Roku follows the guidance of the AMPTP and local regulations when it comes to Covid-19 health and safety guidance. Please work with Roku Production if you have any questions. - -## 5. Finance - -### **5.1 Payments** - -- Cash Flow Approval and funding occurs after all Conditions Precedent have been met and the official greenlight / budget approval email has been sent by Roku Production; including but not limited to, receipt and approval of COIs -- Submit payment schedule to Roku Production Finance and cc your Roku Production Executive for review and approval - - Include invoice due dates, percentage, and amounts -- If applicable, Production Company Fee, Breakage, and Residuals/Buyouts can be listed, but should not roll up into the total milestone payments - -#### **5.1.1 Payment descriptions** - -Possible payment milestones and when to submit invoices for processing listed below: - -- Complete Delivery / Complete & Final Delivery - Invoice due upon receipt and approval of all Roku Post Paper and Media Deliverables. -- Production Company Fee – Invoice due receipt and approval of all Paper Deliverables and Final Cost Report -- Audit - Reference closed project deal terms for audit language - -#### **5.1.2 Invoices** - -All invoices should be sent via email to [roinvoices@roku.com](mailto:roinvoices@roku.com) - -When submitting invoices, the subject line should read “Project Name” | Invoice: “Description” - -- For example: Best Show Ever | Invoice: December Cashflow - -Email must include: - -- Vendor Name -- Project Name -- Season # -- Invoice description (i.e., December Cash Flow or Commencement of Principal Photography) - -**5.2 Changes to banking information** - -If your banking information changes at any given point, Partners must send an email to [roinvoices@roku.com](mailto:roinvoices@roku.com). - -Please note this email must come from an employee of the company or will not be accepted. - -The subject line should read “Vendor Name” | “Project Name” - UPDATED Banking Information - -The email must include: - -- Studio/ProdCo name -- Project Name -- What Banking Information has been updated - i.e. Routing or account or both -- Attachment with updated information on company letter head -- Contact information for the point person: Name and phone number - -Please note, AP will need to verify validity with a phone call to the point person noted above. - -Sample email below: - -*Hello,* - -*This email is to let you know we "INSERT COMPANY/VENDOR NAME" have updated routing and/or account information for the project currently known as "INSERT PROJECT NAME". Please see attached updated information.* - -- *TBD Studio* -- *Project Title* -- *Updated routing number attached (or updated account number attached)* -- *Contact: TBD at xxx.xxx.xxxx* - -Once AP confirms the update has been made, Production Finance will let you know that you may submit your invoices. - -Important Notes: - -- Roku requires 1 week to amend in the system. -- Invoice(s) may be submitted no earlier than 1 week from any bank change requests. -- Invoice(s) must be submitted no later than EOD Thursday to potentially make the following week pay run. - -### **5.3 Production company fee calculation** - -Please refer to your agreement to determine if a Production Company fee is applicable. If so, please see below. - -- Calculate your prod co fee with applicable exclusions as per your closed deal and include the prod co fee amount on the Budget Assumption Page - -### **5.4 Residual calculation** - -The Roku Channel is a free to consumer ad supported platform (AVOD). Please consult your labor counsel and reach out to Roku Legal and Production with any specific questions. - -Please check with your Roku Production Executive if this applies to this project. - -### **5.5 Overages & breakage** - -Roku will not be responsible for any overages. Production spend over and above the Approved Budget is never authorized without written approval from Roku Production. If there is a request made by Roku that materially changes the creative elements or delivery of the project it is the responsibility of the Prod Co/Studio to reach out to Roku Production to discuss the financial implications **before** any decisions/changes are made. - -- Approved talent breakage is paid 50% upon commencement of principal photography, 50% on the completion of principal photography - - Fringe is paid on actuals which is typically in the last 50% payment or later -- If circumstances call for non-talent related breakage (i.e “Other” breakage) this payment is held until Roku Production receives and vets the final cost report - - Underages will offset approved breakage, unless approved in writing by Roku Production - -### **5.6 Close out** - -In order to start the project close out process Roku must receive and approve all media and paper deliverables including the final cost report. Please follow the below when submitting your final cost report: - -- For a cost report to be considered finalized all PO’s and ETC’s should be zeroed out unless agreed to in writing by Roku Production -- When sending through your final cost report packet, please note “FINAL Cost Report” in the subject line and confirm in the body of the email that all costs for the project are accounted for -- In the case of open PO’s (e.g., Music Rights) Roku requires backup for all pending expenses before approving the final cost report -- When Roku Production confirms the final cost report is approved, Roku Finance will release the final payment (i.e., Production Company fee) - -## 6. Production legal - -Prior to creating content for exhibition on The Roku Channel, please review the Roku Production Legal Guidelines below with your legal counsel. Reach out to Roku Production Legal if there are any questions or concerns. - -### **6.1 Roku production legal guidelines** - -The Roku Production Legal Guidelines will cover the topics listed below. You can review the complete legal guidelines via the link sent to you. If you do not have it, please reach out to your Roku Production point. - -- Guilds/Unions -- Clearances -- Integrations/Sponsorship/Trade-Outs -- Cast Notices -- Talent Publicity and Promotion -- Risk & Safety -- Safety/Respect in the Workplace -- Music (approved PRO’s) - -### **6.2 Insurance** - -We rely on our production Partners to acquire the appropriate coverage as deemed necessary for each production. When binding coverage please ensure it satisfies all of Roku’s insurance requirements with the exception of Workers’ Compensation/Employer’s Liability, Owned Automobile, Guild Travel Accident (if your production is union) and any local foreign compulsory coverage(s) (such as auto liability) which are collectively the responsibility of the production company. - -#### **6.2.1 Certificates of insurance** - -Certificates of insurance (COIs) should be bound and sent to Roku Production / Production Legal prior to the commencement of any production activities. - -Below is a list of COIs that may be required by Roku. This information along with coverage limits for this project shall be provided by Production Legal. - -- Errors & Omissions -- General Liability -- Auto Liability -- Statutory Workers Compensation Coverage -- Umbrella/Excess -- Entertainment Package -- Applicable Collective Bargaining Agreement/Guild Travel Accident Coverage -- Foreign General Liability (if applicable) -- Cast Insurance - - The necessary cast members should be declared so they are eligible for cast insurance. - - Please discuss with Roku Production Legal whether your talent needs to be declared separately for Cast Insurance Coverage; and additionally, whether accident-only or full coverage would be preferable. -- Higher-Hazards & Special Risk Coverage (i.e., Aircraft/Watercraft Liability, etc.) - - There may be special risks associated with your project. This includes but is not limited to stunts, firearms, minors, pyrotechnics, precision driving, aircraft, drones, watercraft, railroads, foreign activities, animals, or any unusual or hazardous exposures and/or conditions involving either cast or crew. Special Risk Coverage may be required for your production, please budget accordingly. - -Roku must be named as an additional insured. Please use the following for issuing COIs to Roku: - -Purple Tag Branded Content, LLC -1173 Coleman Avenue -San Jose, CA 95110 - -Under “Description” on COIs, please list: - -Purple Tag Branded Content, LLC, its parent, its subsidiaries and affiliates and their respective officers, directors, agents and employees, as now or hereafter may exist and any other persons or entities as Roku may designate to Produce from time to time. - - Please inform Roku Production and Production Legal in writing, of any claims, threats of claims, suits, damage to property or any other loss. Roku Production will need to be updated throughout the claim process and any receipts that will offset production costs. - -### **6.3 Music** - -Please reach out to Roku Production and Legal for clearance requirements specific to this project. Music should be cleared the full term of the project, and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -Please reach out to Roku Production for access to our music library or with any specific questions or cost implications above and beyond what is in the budget to license per the aforementioned guidelines. - -### **6.4 Content takedown request** - -We understand there may be occasions when content needs to be removed from The Roku Channel (e.g., 3rd party rights issues, legal orders, PR concerns). In the event content needs to be removed, please email Roku Production and Roku Production Legal. - -We ask that you provide the following information in the body of your email request: - -- The episode # and title -- The specific reason for the removal request (e.g., "wrong photo included in opening shot," "music was not cleared properly") -- A point of contact along with email and phone number to call for any follow up questions -- An ETA for delivery of a replacement episode - - Ideally when requesting that content be removed from the Roku eco-system, you will be able to provide a replacement episode ASAP. If this is not possible (or deemed not necessary based on the content), Roku will address on a case-by-case basis - -## 7. Post - -Please review the Roku Branded Media Delivery Specifications for a comprehensive breakdown of all post workflows and media deliverables. - -Roku’s approved platform for dailies, rough cut release, and final archive is [Frame.io](http://frame.io/), which Roku provides free of charge to our production partners. All content sent to Roku for review needs to be shared via [Frame.io](http://frame.io/). - -### **7.1 Music cue sheets** - -Music cue sheets are required for all projects. Please use the cue sheet template found on the ASCAP website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub under the Production Legal – Branded folder. - -Upload completed cue sheets to the Hub. If you have any specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Grossberg at [sgrossberg@roku.com](mailto:sgrossberg@roku.com). - -## 8. Paper deliverables - -Roku uses a deliverables Hub (“Hub”) to receive specific production documents. The Hub is project specific and will serve as the portal for key paper deliverables. Please remember the materials and folders are confidential and may not be shared beyond authorized parties. With a few exceptions, the Hub is used in lieu of emailing various Roku teams relevant documentation. - -Prior to pre-production you will receive an email with instructions for accessing the Hub. - -Due to the **confidential** nature of the requested paper deliverables, access to the Hub will be limited to four (4) key project personnel. Only those who are responsible for uploading the deliverables as noted in **section 8.1**, should have access. - -### **8.1 Required paper deliverables** - -Productions should be uploading documents to the Hub on an ongoing basis throughout all phases of production, starting with pre-production and concluding with uploading final documents during wrap. - -Below you’ll find a list of **paper** deliverables for Production, Post and Production Legal. Please be aware, this list is subject to amendment (within reason) at any time. Make sure to follow specific instructions for each document and upload accordingly. Please note other departments may have additional required deliverables. - -#### **8.1.1 Production** - -- Beat Sheets -- Call Sheets & Maps (upload at the same time as distribution to crew) -- Camera Plot, Equipment and Assignments -- Cast Lists (all approved and final versions) (If applicable) -- Completed Deliverables Checklist -- Hot Sheets -- Episode Outlines & “Scripts” (if applicable) (all approved and final versions) -- Paid Cast List Template -- Production Calendar -- Production Reports -- Production Vendor List -- Set Design and Stage Plot (if applicable) -- Schedules (all approved and final versions) -- Staff & Crew Lists (all approved and final versions) - -#### **8.1.2 Post** - -- CC/Sub/FN Files -- Episodic Delivery Checklist -- Final Post Contact List -- Final Post Vendor List -- Font Memo -- Ingest Metadata Template -- Original Music -- Post Grids -- Final Credits (also vetted by Business Affairs) -- Music Cue Sheets (vetted by Production Legal) - -#### **8.1.3 Production legal** - -- Chain of Title Agreements -- Fair Use Grid (if applicable) -- Guild & Union Documentation (if applicable) -- Location Agreements -- Insurance Certificates - GL & E&O -- Residuals Information -- Title Report & Legal Opinion -- Workers Comp -- Release and License Agreements -- Tax Incentive Registration, Certificate, Evidence of Sale/Transfer (if applicable) -- Talent Agreements -- Employment Agreements -- Music Licenses -- Music Supervisor Agreements -- Workers Comp - -### **8.2 Deliverables checklist** - -On the Hub you will find a deliverables checklist, the checklist is considered part of your paper deliverables. - -Please only mark items as complete once the final versions have been uploaded. If an item is not applicable (“N/A”), please upload a word document that says N/A and a short explanation as to why it is not applicable to your production. You may then mark that item complete on the checklist. - -Email Roku Production once all items have been delivered and the checklist is filled out completely. Once final delivery is received and approved, access to the Hub will be removed. - -For questions or concerns please reach out to Roku Production at [altprod@roku.com](mailto:altprod@roku.com). - -### **8.3 Naming conventions** - -All Roku projects have a unique Project Title ID (PTID). You must follow specific naming conventions for the files to be considered acceptable. Examples of how each file(s) should be named can be found on the Hub, in the Production - Branded folder. - - If items are not delivered correctly, they will not be accepted. Please do not add or remove folders. If you have questions or can't find specific folders, please reach out to Roku Production. \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/features-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/features-specs.md deleted file mode 100644 index 928f1506..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/features-specs.md +++ /dev/null @@ -1,994 +0,0 @@ ---- -title: Feature/doc/special - media delivery specifications -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -_Version 4.0 - May 2026_ - -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices. - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Post Production Delivery Specifications outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -## 2. Post kick-off - -Post Producer resumes should be sent to Roku for prior approval. one week prior to Production start, please reach out to Roku Post Production to set up a kick-off call. In prep for this call, please review this full specification document so that we can address any follow up questions you may have. - -### 2.1 Startup documents - -Additionally, please make sure to send the preliminary versions of all documents noted below to Roku Post Production prior to the first day of Production. Available templates have been provided in the Post Kickoff zip file. - -1. Post Grid (Please send in excel format, not PDF) -2. Post Production Contact List -3. Preliminary Vendor List -4. Dailies Memo - -#### 2.1.1 Show numbering and post grid workflow - -Post Grids accuracy must be confirmed weekly, either via revised grid or an email reflecting that no changes have been made. For distribution, Roku requires these grids to be both uploaded to The Hub and emailed to a distribution list that Roku Post Production will provide prior to Production. - -Please note that the Post Grid template provides columns for multiple types of series, as noted below. If a specific column does not apply to your show, you can disregard it. - -- **Production Number**: Prefix “MV” and 3-digit number that reflects an original film versus a sequel (MV100, MV200, etc.) - -### 2.2 Notifications workflow - -- Once in production, any changes to the post schedule/calendar must be communicated to Roku Post Production immediately (within 24 hours) -- **Quality Control Delivery and Final Delivery dates cannot shift without written approval by Roku Post Production** -- At the below milestones please set a call with the Roku Post Production Manager at the email address provided on the contact sheet: - - one week prior to Production - - one week prior to the first scheduled rough cut release date - - Within one week of production wrap - -### 2.3 Misc. - -- Please be sure to include the full name of the show in the subject line of all email correspondence -- Do not include the Roku name or logo on any documents (including contact sheets, call sheets, PR’s, casting notices etc.) without written permission from Roku Production -- The Roku Contact sheet is for Studio use and should not be distributed widely - -### 2.4 Roku marketing - -Marketing will be directly involved in the Main Title treatment creative process. - -### 2.5 Roku localization - -Roku’s Localization Team will handle the creation of Latin Spanish subtitles and Audio Descriptions files (AD). - -## 3. Production - -### 3.1 Capture specifications - -- Content Type - - Scripted - - Unless otherwise approved by Roku Production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of UHD (3840x2160) and an Aspect Ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. - - Unscripted - - Unless otherwise approved by Roku Production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of HD (1920x1080) and an Aspect Ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. -- All material should be captured, transferred, and mastered in a progressive frame rate. Please do not apply any cross-conversions to content. -- Please do not apply in-camera upscaling or de-squeezing to any camera masters. If your desire is to work with cameras that do not natively capture in 4k, please reach out to Roku Post Production to discuss workflow options. -- Any material that is being shot or used for Visual Effects must match capture resolution. This resolution must remain consistent throughout the Visual Effects creation and final delivery process. - -### 3.2 Camera tests - -- Prior to principal photography, please plan to shoot camera tests and post to [Frame.io](http://frame.io/) (Rough Cut 1 folder) for Roku review. -- These do not need to contain talent, final lighting, or even audio. They will solely be utilized to confirm the efficacy of camera capture and dailies workflows. -- Camera test material can be a quick compilation of various shots and angles; it is not necessary to cut a full scene together. -- Roku Post Production will provide a distribution list for all camera test material. If you have not received it, please reach out to your Roku Post Manager. - -### 3.3 Dailies - -#### 3.3.1 Dailies distribution - -Dailies are requested for visibility and early Marketing preparation. Roku Post will provide a user list for Dailies prior to production. - -- Scripted projects: Allow for dailies across all days of production. -- Documentary projects: Allow for three total 5-10 minute dailies-selects reels, one from each of three discrete shooting days. These do not all need to be from the first three days of principal, but please utilize at least one of the initial few days. Prioritize diversity of environments, subjects, etc. when choosing which days to send. - -Roku’s approved platform for dailies, rough cut release, and final archive is [Frame.io](http://frame.io/). All content being sent for review by the Roku team will need to be shared via this platform. [Frame.io](http://frame.io/)’s platform is compatible with most commonly used codecs, so if you are working with a partner who utilizes a different review platform, this may not require an extra render (pending specifications for each). - -The Roku Post team will initiate onboarding prior to the first day of production. That will trigger a member of the [Frame.io](http://frame.io/) team to reach out to set up a training session with your team. Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content (with Roku’s approval). - -#### 3.3.2 Dailies formatting - -Dailies should be posted and organized according to their corresponding shoot day. - -Each take should be uploaded as 1 clip within the overall day’s dailies folder. Please ensure that the camera roll source and scene/take information is available for every clip uploaded, either via burn-in windows or file naming. Source camera timecode should be burned into picture. - -Once dailies have been uploaded to [Frame.io](http://frame.io/), please send a notification email to those reviewing Dailies, per the Distribution List provided by your Roku Originals Post Manager. Please include the following in each email: - -- In the subject line include the show title, episode # and dailies day -- In the body of the email include the link from the address bar to the [Frame.io](http://frame.io/) dailies project - -#### 3.3.3 Dailies memo - -A Dailies Memo should be submitted to the Roku Production and Post Production teams for approval prior to the commencement of principal photography. This document should include the proposed dailies workflow process, from camera capture through dailies distribution. Please include at least the following information: - -CAPTURE - -- Camera(s) utilized - - For each camera model, please provide: - - Video Resolution - - Acquisition Codec - - Frame rate(s) - -- Audio sample rate and bit depth - -- Please confirm that video will be captured log/flat and that no LUT/color grade will be baked into the footage at capture - -OFFLOAD - -- Utility/Process used for offload - -- Checksum Algorithm used - -DAILIES & EDIT PROXY PROCESS - -- Program utilized for creation -- Processing method & workflow utilized, including where in process LUT/color applied -- Edit Proxies codec & frame rate and Dailies codec & frame rate -- Raster/Resolution - -### 3.4 Sizzle - -#### 3.4.1 Sizzle overview - -Roku may request your team create a 30-45 second sizzle for your project to be used for business-to-business purposes. - -Please note that the sizzle does not require formal finishing, i.e. final assembly, conform, color, or mix. As it is for B2B use, it does not require clearances or music licensing. - -Process: - -- Your Roku Production Executive will inform you if a sizzle is needed for your project -- Please include sizzle milestones in overall calendar deliverable once due date has been provided by your Roku Post Manager -- Please account for 2 rounds of notes from Roku Creative -- Please reach out to your Roku Post Manager for the delivery date - -Sizzle should include: - -- two cards for a minimum of two seconds each: - - Roku Presents - - A Roku Original Film / A Roku Original Documentary / A Roku Original -- Temp Main Title treatment -- Clips that represent the story and showcase talent involved -- Please include lower third IDs for any interview footage included -- Sizzle does not need to include full scenes - -Please reach out to your Roku Post Manager if you would like to see an example of a previous sizzle. - -#### 3.4.2 Sizzle deliverables - -An HD primary video deliverable is required as follows: - -- Please do not include any head/tail formatting or slate -- Program should start at 00:00:00:00 -- File Specs: - - (1) H.264 - - 1920 x 1080 - - 23.98 (or native framerate of Production, if different) - - Temp Stereo Mix -- Delivery Destination: Frame.io (Final Archive > Sizzle) - -## 4. Security - -Security is of the utmost importance to Roku. As such, access to all of the exciting content we are creating together must be limited. Please review Roku’s security requirements noted below and reach out to Roku Post Production with any questions. - -### 4.1 Review platform - -Roku’s approved platform for content sharing is [Frame.io](http://frame.io/). Roku and [Frame.io](http://frame.io/) have developed a content review workflow that both ensures security and limits access to all pre-launched content. In this workflow, anyone viewing Roku content will be required to set up a user account within [Frame.io](http://frame.io/) so that their activity can be tracked. - -**No material should be shared on any other platform without written approval from Roku.** - -### 4.2 Download access - -**It is not permitted for anyone to have direct, clean download access to any Roku content without written approval from Roku.** - -For team members who require reference QuickTime's in order to complete their work efficiently (i.e., Composers, Music Editors, Visual Effects Supervisors), please follow the steps below: - -- Submit a written request with the recipient’s name, email, and use case. Upon Roku approval: - - Each file must be watermarked with the recipient’s full name and located in the center of picture. - - Recipients should never be given access to an entire folder’s worth of content; Review links that contain solely the required assets should be sent to the Roku approved recipients. This link must be manually expired as soon as the file has been successfully downloaded. - - Files should always be housed on a vendor’s secure Storage Area Network. Files are never permitted to be stored on anyone’s personal device. - - It is the responsibility of each show's Post team to request vendor deletion of these files at show wrap. - -### 4.3 Content review - -It is never permitted to share rough cuts via Public Links. Review Links require user login and are the only approved method for content review. - -[Frame.io](http://frame.io/)’s Roku Partner Playbook is shared with the Post team at the start of each project. This workflow must be followed for both cuts released to Roku and also cuts released prior (Editor, Director, Producers, etc.). If you have not received this document, please reach out to Roku Post Production. - -All guidelines below must be followed when sharing review links: - -- It is not permitted for any rough cut viewing links to be download-enabled -- All viewing links must include an expiration date that confines access to seven days or less -- **All cuts uploaded for review must be watermarked** - -### 4.4 Non-standard requests - -It is not permitted to send content to anyone who is not a [Frame.io](http://frame.io/) user without written approval from Roku. - -## 5. Rough cuts and viewables - -### 5.1 Post weekly sync - -Once you begin the rough-cut process, your Roku Post Manager will reach out to schedule a weekly call. The call will be an informal sync to determine how the rough cuts are progressing and help address any questions you may have. If you have made any changes to the Post Grid over the week prior, please send a revised version prior to this call. - -### 5.2 Rough cut formatting - -#### 5.2.1 General requirements - -- There may be discussions around pre-roll, mid-roll, or post-roll advertising cue points. Regardless, please deliver each file as a seamless master. -- Roku requires rough versions of graphics starting at the RC1 stage, and near final graphics by the FC stage. See Section 5.6 for a full breakdown of Roku’s graphics milestones (if applicable). -- Blurring un-cleared video content requires Roku Creative approval beforehand. -- Temp ADR must be added to all in-progress cuts where applicable, including all add-lines and alts. - -#### 5.2.2 Timing requirements and ad breaks - -Timing requirements are as follows: - -- Scripted Feature - - Feature content run time should be between 85-89 minutes, unless instructed or permitted otherwise by Roku. - - **Locked Cut** - QT’s must include a slug for the end credits so that the exact timing is locked to match the final master. - - Rough Cut 1 is permitted to be up to 15 min longer than the maximum allowable TRT (89 min.). Rough Cut 2 may be up to 2 min. longer than the maximum allowable TRT. - - Fine Cut and above must be within allowable TRT. - - A minimum of seven ad breaks required. - - Roku’s general preference is that ad breaks be spaced anywhere from 10-14 minutes apart, dependent on the creative. - -- Documentary - - Feature content run time should be between 44-50 minutes, unless instructed or permitted otherwise by Roku. - - **Locked Cut** - QT’s must include a slug for the end credits so that the exact timing is locked to match the final master. - - Rough Cut 1 is permitted to be up to 15 min longer than the maximum allowable TRT assigned. Rough Cut 2 may be up to 2 min. longer than the maximum allowable TRT. - - Fine Cut and above must be within allowable TRT. - - five total ad breaks required. - - All ad breaks should be spaced anywhere from 6-10 minutes apart, dependent on the creative. - -- Alternative Specials - - Feature content run time should be between 65-90 minutes, based on the creative for each project. Your Roku Creative Executive or your Roku Post Manager will convey the appropriate TRT for your project. - - **Locked Cut** - QT’s must include a slug for the end credits so that the exact timing is locked to match the final master. - - Rough Cut 1 is permitted to be up to 15 min longer than the maximum allowable TRT assigned. Rough Cut 2 may be up to 2 min. longer than the maximum allowable TRT. - - Fine Cut and above must be within allowable TRT. - - 65-90 minute specials will require a minimum of 6-7 ad breaks. - - Roku’s general preference is that ad breaks be spaced anywhere from 10-14 minutes apart, dependent on the creative. - -Ad break guidelines for all content types: - -- The ad breaks should not appear until at least five minutes of content have elapsed. -- The final ad break must appear before the last three minutes of the feature, which will remain ad-free. -- Ad breaks should be formatted as 1 second of black (no text permitted). Fade outs/ins are permitted. - -All Fine and Locked cuts sent to Roku must adhere to the specifications above. They will not be deemed acceptable otherwise. Please see the guidelines above for more detail on permissible TRT exceptions on earlier cut releases. - -If your project does not fall within the total run time guidance above, and this has been previously approved by Roku’s Content team, please reach out to Roku Post Production to discuss ad break implications. - -The exact timecode of each ad break, in (HH:MM:SS:FF) format, will be required in both the Segment Rundown and Metadata deliverables. Both templates were provided in the Post Kickoff Deliverables Packet. Please reach out to Roku Post if you did not receive one. - -#### 5.2.3 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -#### 5.2.4 Rating guidelines - -Roku Originals content must fall within a TV-PG or TV-14 rating. Some general ratings guidance has been provided below for you to keep in mind as the creative story progresses in editorial. Please note, however, this is a very subjective process and the rating tiers below are regularly reviewed and may be modified in response to shifts in industry standards. So please be sure to reach out to your Roku Legal contact if you have any questions or clarifications. - -**Rating Tiers** - -| | VIOLENCE | SEX/NUDITY | SUBSTANCE USE/ABUSE | LANGUAGE | -| :-------- | :----------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------: | -| **TV-PG** | **✔** Shootings, brawls, fist fights
**✖** No blood | **✔** Limited to kissing, couples in bed, implied sexual situations
**✖** No nudity at all
**✖** No sexual violence | **✔** Implied drug use (not glorified or must show consequences) | **✔** Limited use of bleeping/dropping strong language. Ass, damn, hell, and bitch | -| **TV-14** | **✔** Brief violence, OK with some blood shown
**✕** No gore | **✔** Covered sex is allowed, brief thrusting, implied sexual abuse OK
**✔** Exposed butt/side breast OK
**✖** No full nudity | **✔** Visuals/use of drug abuse (not glorified, must show consequences)
**✖** No smoking minors | **✔** Shit, asshole, bastard (when used in a pejorative matter), goddamn, bitch, dick and pussy (as an insult) | -| **TV-MA** | **✔** On-screen graphic violence, gore | **✔** Depictions of graphic sexual activity or sexual violence
**✔** Full male or female nudity | **✔** Graphic visuals of substance use/abuse, injection, etc. (both. minors and adults)
**✖** No smoking minors | **✔** Use of fuck, tits, twat, cum, pussy, and cunt
**✖** Racial slurs and hate speech on a case-by-case basis | - -### 5.3 Rough cut review - -#### 5.3.1 Review platform - -Roku’s approved platform for dailies and rough cut release is [Frame.io](http://frame.io/). All content being sent for review by the Roku team will need to be shared via this platform. If you are working with a partner who utilizes a different internal platform, there will not be a need to render out separate files just for use with [Frame.io](http://frame.io/); [Frame.io](http://frame.io/)’s platform is compatible with most commonly used codecs, which allows the same file to be uploaded to both platforms. - -The Roku Post team will initiate onboarding prior to the first day of production. That will trigger a member of the [Frame.io](http://frame.io/) team to reach out to set up a training session with your team. Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content (with Roku’s approval). - -#### 5.3.2 Review process and turnaround timing - -Roku will provide notes within 48-72 business hours after receipt, whether the Production Company is based in the United States or outside the United States. Cuts received by Roku after 6:00 pm PST will be deemed received the following business day. When sending cuts earlier than the scheduled release date, please note that the original notes return timing will need to be honored unless otherwise approved by Roku Creative. - -Locked cuts are approved if no notes have been sent after 48 hours. - -Rounds of Review: - -- RC1 → RC2 → FC1 → FC2 → LC - -Roku Notes Turnaround - -- RC1 notes will be turnaround within 72 hours -- RC2, FC1, FC2, and LC notes will be turned around within 48 hours - -### 5.4 Technical specifications for rough cuts and viewables - -Formatting: - -- Slate before the hour - Please include show title, production number, cut version (RC1, FC, etc.), total run time and release date -- Hour 01 onward should be solely program material, inclusive of production logo card at tail as last frame of picture - -Video Specifications: - -- Dimensions: 1920 x 1080 (horizontal) -- Codec: h264 (preferred) or MPEG file -- Frame Rate: Keep it native to your project (24, 23.976, 25, etc.) -- Bitrate Encoding: Variable Bit Rate, 2 pass -- Target Bitrate: \~ 10mbps -- Aspect: Square Pixels (1.0) -- Visible Timecode Upper Right -- Please mark ad breaks in white text over 1 sec of black as either “Ad Break #” or incoming act number, i.e. “Act 2”. - -Audio Specifications: - -- Audio Codec: AAC -- Sample Rate: 48000 Hz -- Channels: Stereo - -Graphics: - -- Remember to adhere to Broadcast Title Safe Zones when adding any burned-in graphics or text. - -### 5.5 Rough and locked cut delivery - -Roku Post Production will provide a recipient list for all rough cuts prior to the scheduled release of the first cut. The [Frame.io](http://frame.io/) team will walk each project through Roku’s preferred rough cut release workflow, which involves: - -1. An email to the entire distribution list, noting the availability of cuts and when notes are due back. - 1. This email should include a Segment Rundown that relates to the timing of each specific cut being sent. - -2. A notification from [Frame.io](http://frame.io/), which happens automatically after a cut is copied to the Shared Folder on [Frame.io](http://frame.io/). - -For each locked cut, you will be required to deliver the following elements via [Frame.io](http://frame.io/): - -- Locked Cut QuickTime -- Locked Cut EDL -- Locked Cut WAV Files: Mono Dialogue, Mono Music, and Mono Effects - -Cut filenames must follow the proper naming convention below: - -- Show Code (4-digits; Provided by Roku Post) -- Production number (MV100, MV200, etc.) -- Cut version (RC1, FC, etc.) -- Date the cut was released to Roku (YYYYMMDD) - -Example: FLIP_MV100_FC_20260413 - -All rough cut links should be confined to viewing only (i.e. no download access). When sharing cuts, please do not create any folders, or copy any folders into the Roku Review projects. - -### 5.6 Graphics milestones and review process - -For Scripted and Alternative features, the Roku Content & Post Production teams should be involved in key discussions related to graphics, from title treatments to overall episodic graphics packages. - -All graphics work (title treatment, lower thirds, interstitials, etc.) must be completed by a Roku approved graphics company. The use of freelance staff or in-house graphics teams is not permitted. Please reach out to Roku Post to obtain the list of approved vendors. - -The following milestones require Roku notification and review: - -- **Six Weeks Prior to 1st Rough Cut:** A minimum of three graphics vendor options must be sent to Roku for review and approval -- **Four Weeks Prior to 1st Rough Cut:** Due to Roku: Mood board, color palette, title sketches, font, etc. -- **Two Weeks Prior to 1st Rough Cut:** Due to Roku: First round of design and/or animation examples -- **One Week Prior to 1st Rough Cut:** Due to Roku: Second round of design and/or animation examples -- **1st Rough Cut Release** - - Temp graphics implemented into the cut that is distributed to Roku. - - All temp graphics must be based on creative input from Roku. Any changes from the agreed upon look of in-show graphics will need to be outlined in an email to the Roku Content team. -- **1st Fine Cut Release:** Final Graphics must be implemented into the cut that is distributed to Roku - -After Roku has approved all in-show graphics and the first cut is locked, no changes should be made without written approval from the Roku Content team. - -## 6. Final mastering and marketing - -### 6.1 Picture and audio mastering - -#### 6.1.1 Uncompressed masters - -Roku prefers to receive both the un-graded and graded high-resolution master sequences as part of final delivery for wholly-owned Roku projects. These files should be exported in DPX format or TIFF format, at the highest bitrate possible (16-bit preferred). Please package DPX or TIFF image sequence folders into a single .zip file for delivery. - -If your vendor is unable to export these sequences, please reach out to Roku Post Production. - -#### 6.1.2 Harding testing - -Please alert Roku Post Production if any content contains flashing/strobing lights or other image patterns that have the potential to trigger seizures in viewers with Photosensitive Epilepsy. In these instances, you will be required to run a Harding Test and provide the passing report to Roku Post Production as part of Final Delivery. - -Please refer to the [Ofcom ITC Guidelines](https://www.ofcom.org.uk/__data/assets/pdf_file/0021/16248/gn_flash.pdf) for further information. - -#### 6.1.3 HDR10 and Dolby Vision - -Currently, Roku Scripted and Alternative projects are only required to complete an SDR (Rec709) grade. Please keep in mind your final deliverables will need to be in legal video range. - -Roku encourages that all series be graded utilizing the Dolby Vision workflow. Although an HDR deliverable is not yet a requirement for the Roku platform, grading in Dolby Vision will allow for the highest quality visual experience, as well as protect for future inclusion of HDR deliverables. - -For Productions whose budgets and schedules permit HDR 10 or Dolby Vision grading, please reach out to Roku Post Production to determine the necessary workflow and related deliverables associated with either. - -#### 6.1.4 Sound mixing - -Roku requires that all Scripted and Alternative projects mix in 5.1 Surround, and then downmix to create Stereo deliverables as well. - -Roku Policy/Preference is for live, remote playback of the mix for Roku Creative and Roku Post Managers prior to conclusion of the mix. Please include provisions (remote view client/seat licensing, remote view capable stages, etc.) to accommodate when budgeting. - -#### 6.1.5 Promotional assets (images and trailers) - -As each production will differ with regards to promotional assets, please reach out to Roku Marketing to determine the specific asks for your show. - -## 7. Credits - -**All opening and end credits must be submitted to Roku Post for approval with delivery of the first Fine Cut.** - -### 7.1 Opening credits - -For opening credits, Roku will utilize traditional burned-in credits. Full requirements are noted below. Please reach out to Roku Post Production with any questions. - -#### 7.1.1 Disclaimer use - -If your show contains sensitive content, please reach out to your Roku Legal Executive to see if it requires a trigger warning prior to the cold open. - -**For any other opening cards or disclaimers, please reach out to Roku Post Production for approval.** - -#### 7.1.2 Main title card - -During the initial design phase of any title treatments please reach out to your Roku Creative Executives; Roku Production ([production@roku.com](mailto:production@roku.com)); Roku Marketing ([dlrokuoriginalmarketingcreative@roku.com](mailto:dlrokuoriginalmarketingcreative@roku.com)) and Roku Post: ([dlropost@roku.com](mailto:dlropost@roku.com)). - -Please follow the formatting requirements below: - -- The title card will display the show title/logo, burned into picture as part of each final video master. -- The Production Company/Producer will have full creative control over how the title appears, subject to size requirements and provided that it is within the 16x9 title safe zones. - - Duration of this card will be a maximum of five seconds -- Deliverables: Series Logo (Static File) - - Dimensions: - - Scripted: - - 1920x1080px Transparent PNG - - 3840x2160px Transparent PNG - - Documentary - - 1920x1080px - - UHD resolution may also be applicable pending show’s specs - - Project Files (where applicable): - - PSD with hi-res textured layers - - AI Vector File - - Original font file with license receipt (Adobe/Google font link, .tff or .otf - -#### 7.1.3 Opening credits - -Each project, whether scripted or unscripted, is required to include two Roku presentation cards at the top of the program as follows: - -- Series: **Roku Presents / A Roku Original Series** -- Feature: **Roku Presents / A Roku Original Film** -- Documentary: **Roku Presents / A Roku Original Documentary** - - This includes the presentation card for a docu-series. - -In addition please follow the below spec on duration and style of the Roku presentation cards: - -- Duration: Minimum of two seconds per card -- Please utilize the same font and style that is specific to each project -- Roku prefers these be integrated into the opening of each program, rather than added as separate cards over black - -Further opening credits specifications by project type: - -- Scripted: - - Credits may appear over picture at the top of each project, provided the following criteria are met: - - Full duration of these credits does not exceed 1:15 in length - - Up to three names per credit block - - Up to 12 total credits/credit blocks can be utilized - - Credits that are approved to be included within the show opening are outlined below: - - Up to three “Union” credits (i.e., “Created by,” “Written by,” and “Directed by”), as determined by the Production Company/Producer. - - ‘Created By’ and ‘Written By’ credits can be swapped, but ‘Directed By’ must be the last credit. - - Production Companies, Executive Producers, and Producers are permitted. - - The size and style of type for these credits will be determined by the Production Company/Producer, provided that: - - Fonts have to be large enough to be legible. - - Fonts used for names should be the same size. - - The individuals who receive these credits, the order of credits, the size and style of type (subject to the restrictions noted below), and whether 1, 2, or 3 names appear in the credit block will all be determined by the Production Company/Producer and notified to Roku as part of the delivery process. -- Documentaries and Specials: - - No “Presentation”, possessory, or origination credits permitted anywhere on the program. - - Any request to include on-screen credits on the main title card will require approval by the Roku Content and Post Production teams. - - No other credits are permitted in the opening of the show. - -### 7.2 End credit sequence - -Roku feature length content will utilize traditional burned-in credits. All end credits must be submitted to Roku Post Production for approval before picture is locked. - -- End Credits - - End credits can be no longer than five total minutes in length, inclusive of production company logos - - The Roku Originals Logo should be placed last in the end credits - - **Please reach out directly to Roku Post for access to the most current Roku Original Logo at: [dlropost@roku.com](mailto:dlropost@roku.com)** - - The 2025 logo is available in UHD or HD (both at 23.98fps), and with either Stereo or 5.1 Audio or both - - End credits may be formatted as separate end cards or as an end scroll - - Must be within 16x9 Title Safe -- Production Company Logo Card / Studio Credits - Optional - - Up to 3 production company or studio logos/credits can be included in the end credits, in addition to the mandatory Roku Originals end credit logo - - Separate end cards can have a maximum total length of three seconds each - - For shared cards, no more than two logos can be combined onto the same end card - - Animated logos/credits are permitted - - Logos can include audio provided there is no cost to Roku to license such audio - - Audio ring outs from the end of the program are also acceptable - - **The end of the last logo card will signify your LFOP (last frame of picture)** - - No credits may appear after the end logo cards - -### 7.3 Other credit requirements - -- Production Company/Producer shall deliver a complete written statement of all credit obligations in a format to be decided by Roku -- Production Company/Producer shall ensure that all credits conform to applicable third-party requirements -- Roku will have approval over all credits in each program, including all credits accorded to third parties - -**Adherence to the credit requirements in this document will be part of Roku’s Quality Check. If any specifications are not met, the asset will be passed back to the Production Company/Producer to modify. Roku’s Content Operation team can advise on how to upload assets for Roku review.** - -## 8. Final delivery - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and approved by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -The Delivery Phase begins as soon as the feature is ready for Quality Control, after Visual Effects, color, and mix are complete. The following timeline is required to ensure that all assets are received on time for Post, Marketing, and Operations: - -- Due 1 Week Before Delivery to Quality Control Vendor - - Let Roku Post know which vendor you’re proceeding with - - Metadata Ingest Document due to the Hub \[See 8.8.1] - -- Due With Delivery to Quality Control Vendor - - Texted Master - - Textless Master (if applicable) - - Text Spotting List - -### 8.1 Onboarding - -Roku uses an External Deliverables Hub (“Hub”) to receive specific post and production documents. This Hub will also provide information necessary for the naming of each document and file deliverable. If you have not heard from the Roku Post Production team prior to delivery, please reach out to be set up with access to the Hub. - -### 8.2 Quality control (QC) - -Each Production is responsible for covering the cost of and delivering 100% QC approved content. All masters noted below will be required to be submitted to QC **using one of Roku’s approved QC vendors:** - -- Texted Master -- Textless Master - -All required versions should be delivered to the Quality Control facility on the same day. This will ensure the Quality Control operator is able to verify that there is no variation between the texted/textless timings. - -Please be sure to build time into your delivery schedule to account for the Roku Quality Control process. Roku advises that you set aside three weeks to complete the Quality Control on both horizontal masters. Delivery will not be considered ‘Final’ unless all masters have received a passing report from one of Roku’s approved vendors. A list of these vendors will be provided in the Post Kickoff Packet. - -If a file has passed Quality Control but a revision is necessary (incorrect titles, production card modification, etc.) you **must** reach out to Roku Post before any redelivery is made. Please send an email with a detailed and time coded breakdown of what fixes are being requested so that Roku can review and determine the impact it will have on each team and the show premiere itself. - -#### 8.2.1 Text spotting list (TSL) - -You will be required to deliver a Text Spotting List file when the feature is submitted for Quality Control. This list will help Quality Control vendors verify that creatively intended text is included in the final file. A Roku Text Spotting List template was provided in your Post Kickoff zip file. This single file should be updated as episodes are sent to Quality Control so that all information for the series is included in the same master spreadsheet. - -The Text Spotting List should contain any and all text that is burned into picture, and the corresponding timecodes for each. If there is no burned-in text, you will still be required to deliver this file, but will specify the lack of text by checking the box at the top of the template. - -### 8.3 Filename specifications - -#### 8.3.1 Paper deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -- ShowCode_ProdNumber_AirOrder_Version_LangCode_Date_FINAL -- Example: SMSP_MV100_AIR_1_PostVendorList_enUS_20260504_FINAL - -#### 8.3.2 Master video deliverables - -All master\* video files should be labeled as follows: - -ShowCode_ProdNumber_AirOrder_Version**\_**LangCode_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov - -Example: - -ZOEC_MV100_AIR_1_TXTD_enUS_UHD_SDR_FN_2CH_23976p_20190701-v2.mov - -Production Number = As listed on Post Grids (MV100, MV200, SP100, SP200, etc.) - -Air Order = Please list even if the Air Order is the same as the Production Number - -| File Name Segment | File Name Abbreviation | -| ----------------- | ----------------------------------------------------------------------------------------------- | -| Version | TXTD (Texted), TXLS (Textless), or PROXY | -| Language | enUS (American English) | -| Resolution | UHD (scripted) or HD (documentary & alternative special) + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | 2CH (Interleaved) or 8CH (5.1 and Stereo) – 7.1 audio not permitted on any masters at this time | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Revision Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of QC and track the latest version for delivery | - -\*See 8.4.5 for Proxy file naming - -#### 8.3.3 Master audio deliverables - -Audio materials should be named to include all appropriate information: - -ShowCode_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_102_v04_20220919_enUS_PM_Nearfield_2CH_48k_24b_23976_LT.wav - -| **Material Type** | **Abbreviation** | -| --------------------------------------------- | --------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, FFFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | - -| **Channel Type** | **Abbreviation** | -| ---------------- | ---------------- | -| Mono | Mono | -| Stereo | 2CH | -| 5.1 Surround | 6CH | - -| **Track Assignment** | **Abbreviation** | -| -------------------- | -------------------- | -| Mono | N/A | -| Stereo | LT, RT | -| 5.1 Surround | L, R, C, LFE, LS, RS | - -### 8.4 Video deliverables - -All video should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher of the export settings mentioned in 8.4.3, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate and chroma information that was captured (for example, if the camera captured ProRes 422 HQ, then final export should be ProRes 422 HQ or equivalent, instead of 4444 XQ). - -**Roku Best Practices** - -It is important to keep master sequences (VAM/CTM) and final deliverables in alignment with dailies capture specifications (i.e. free of any up-scaling, cross-conversions, or up-conversions). - -#### 8.4.1 Video formatting - -All files should be formatted to start at 00:00:00:00. - -Files should begin with the cold open and end on the last frame of the Roku Originals logo end card. - -All video files **MUST NOT** contain any of the following: bars and tone, bumpers, segment recaps or previews, vertical Interval time code, advertisements, slates, rating cards, FBI warning cards, placards, overlay branding, promotional bugs, informational bugs, watermarks, or website link callouts. - -If promotional bugs or watermarks are required by a 3rd party, Roku Content Legal should be notified. - -#### 8.4.2 Audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 8.4.3 for specifications based on delivery codec. - -**The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all texted and textless masters.** - -- If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered -- Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export - -Mixing Specifications: - -- Target - 24 LKFS +/- 2 (any average between -22 and -26). Based on ITU-R 1170-3 measurement. -- Audio should not peak above -2 dBfs (True Peak) - -#### 8.4.3 Texted video master - -| Video Codec | ProRes | -| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Container | MOV | -| Profile | Scripted Features: 4444 XQ (4444 Ok if exporting from Premiere) if source is 4:4:4; or 422 HQ
Documentaries and Alternative Specials: 422 HQ; or 4444 if source is 4:4:4 | -| Minimum Bitrate | 50 mbit/s or higher | -| Landscape aspect ratio | 16:9 (1.77:1) - (widescreen permitted within this AR)

Scripted: W3840x H2160 (UHD)
Documentary and Alternative Special: W1920xH1080 (HD) | -| Pixel aspect ratio | Square pixels (1:1) | -| Scan type | Progressive scan type | -| Chroma Subsampling | 4:2:2 or None/4:4:4 if acquired at 4:4:4 | -| Color Space | BT.709 Legal Video Range (64 to 940) | -| Bit depth | 10-bit or 12-bit | -| Constant Frame Rate | 23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p | -| Native frame rate | No 3:2 pulldown flags | - -| Audio Code | PCM | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Format | 2 Interleaved Tracks or 8 Mono Tracks | -| Track Layout | Interleaved: Track 1: 5.1, L-R-C-LFE-Ls-Rs Track 2: Stereo, LT/RT
Mono: L, R, C, LFE, Ls, Rs, Stereo LT, Stereo RT

**7.1 audio is not permitted on any masters at this time** | -| Sample Rate/Bit Depth | 48000Hz/24-bit | -| Channel Mapping & Tagging | See 8.4.2 -Verify correct audio channel mapping and tagging. | - -#### 8.4.4 Textless delivery - -If your content includes burned-in on screen text, you will be required to deliver a separate Textless Reel. This reel should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Video Master noted above. - -Audio mapping label verification as noted in 8.4.2 must be verified in textless master. - -Additionally, if foreign language subtitles cover 30% or more of the feature, you will be required to deliver a fully textless version of the entire program. All episodes should be delivered with the same formatting; if one episode requires a textless master, versus a reel, then all remaining episodes should also be delivered as textless masters. - -Examples of what to remove for the Textless Masters: - -| **Forced Narratives** | **Credits** | **Text-Based Graphics** | -| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -| ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-1.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-2.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-3.jpeg) | - -_Roku Best Practices_ - -- Background elements with text, such as street signs, do not need to be included in the Textless Reel -- ‘Forced Narratives’ refers to on-screen text that is used in one of two ways: to translate foreign dialogue into English or to clarify dialogue that may be inaudible - -#### 8.4.5 Final proxy files (clean and visible timecode) - -From each Texted Master created, please export following proxy files (two total per episode + one series opener): - -| **Video Codec** | **H.264** | -| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Container | MOV or MP4 | -| Picture | (1) Clean (1) w/ Vis.TC UR (1) Series Opener Only (where applicable) | -| Bitrate | 5mbit/s (total file size \< 1gb to 2gb) | -| Dimensions | W1920 x H1080 (HD) | -| Scan Type | Progressive scan type | -| Color Space | BT.709 Legal Video Range | -| Bit Depth | 10-bit or 12-bit | -| Constant Frame Rate | Should Match Master | -| Native Frame Rate | Should Match Master | -| Audio | Ch.1 Stereo Left, Ch.2 Stereo Right | -| Filename | ShowCode_ProdNumber_AirOrder_Proxy_Language_HD_
FN(if applicable)\_Audio_Timecode(Clean or VisTC)\_RevisionDate-v#\_(Final or Pre-QC).mov

ASHN_SP100_AIR_1_PROXY_enUS_HD_FN_2CH_CLEAN_20260421-v2_FINAL.mov | - -### 8.5 Audio stem delivery - -Prior to the commencement of principal photography, please reach out to Roku Post Production in order to determine the necessary audio deliverables for your series. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. Please upload to your Archive folder on S3. - -#### 8.5.1 Domestic stems - -Provided below are the stems required for delivery of each episode/project: - -- Mono Dialogue, Music, and Sound Effects stems -- Stereo and 5.1 Printmasters -- Stereo and 5.1 M\&E - Fully Filled (Scripted Projects Only) -- Stereo and 5.1 M\&E -- Stereo and 5.1 Music -- Stereo and 5.1 Dialogue -- Stereo and 5.1 Sound Effects -- Pro Tools Session Files (.ptx) - -Provided below are additional required elements: - -- Stereo and 5.1 Mix minus narration stems (where applicable) -- Original Score or Original Composition provided as a flattened .WAV for each discrete cue -- Mono M\&E Stems - Opticals, Backgrounds, etc - -All audio should be archived as 24-bit, 48kHz WAV files. - -Please see section 8.3.3 for full guidelines on labeling audio files. - -ShowCode_ProdNumber_Vers_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_102_v04_enUS_PM_Nearfield_2CH_48k_24b_23976_LT.wav - -_Roku Best Practices_ - -- Roku requires that all music be cleared for both domestic and international use across all media on all devices -- Optional tracks (foreign language, grunts, breathing, etc.) are preferred, if applicable -- If budget permits, please create Fully Filled Sound Effects stems as part of delivery - -### 8.6 Timed text file delivery - -Roku requires all content to be delivered with all of the following timed-text formats: - -- Subtitles: Language solely (no inclusion of sound descriptors) -- SDH: Language in addition to sound descriptors (no forced narratives) -- FN: Forced Narratives solely - -All files are required in an effort to support customers that are deaf or hard of hearing. - -Roku requires closed captions and subtitles in two formats: SRT and WebVTT. The files have to have the same timecode and frame rate as the video and audio delivered. Character encoding MUST be UTF-8. - -All timed text should be delivered to the show's archival folder on S3 via Aspera. - -**Languages & formats required:** - -English (American, Code: enUS): Subtitles, SDH, and Forced Narrative - -**All files should be labeled as follows:** - -ShowCode-ProdNumber-LanguageCode_Format-RevisionDate.srt - -**Filename Examples:** - -NION-101-enUS_SDH-20190701 - -NION-101-enUS_FN-20190701 - -### 8.7 Breakdown of final locations for media deliverables - -| **Media** | **Final Location** | -| :------------------------------------------------ | :----------------- | -| TXTD Master | S3 | -| TXLS Master | S3 | -| Clean Proxy | Frame.io | -| Vis. TC Proxy | Frame.io | -| Sizzle or Show Opener Proxy | Frame.io | -| Mono Audio Stems | S3 | -| Stereo and 5.1 Printmaster Stems | S3 | -| Stereo and 5.1 Stems (M\&E, Music, Dialogue, SFX) | S3 | -| Pro Tools Session Files (.ptx) | S3 | -| VAM Image Sequence (in .zip container) | S3 | -| CTM Image Sequence (in .zip container) | S3 | -| Timed Text Files (.srt and .vtt) | S3 | -| Paper Deliverables (Credits, Metadata, etc.) | The Hub | - -### 8.8 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Post Manager. - -#### 8.8.1 Roku metadata ingest template - -Metadata allows Roku to ingest and display all series related information for our customers. Marketing and/or the Roku Content Executive may tweak the information to ensure it’s as effective as possible on the Roku platform. - -Please find the most recent Roku metadata templates and guidelines [HERE](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates) - -The required details will include, but are not limited to, the following: - -- Show - Title, Description, Primary Spoken Language, Production Companies -- Season - Title, Description (leave blank if not applicable) -- Episode - Title, Production Number, Air Order, Total Run Time (TRT) -- Exact timecode of ad break insertion, in HH:MM:SS:FF format - -Metadata is the first Final Deliverable due to Roku. It should be delivered between lock and the start of the Quality Control process. Please reach out to your Roku Post Manager to confirm the deadline specific to your project. - -#### 8.8.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. PNG files relating to the Title Logo and any other logos submitted should be uploaded to [Frame.io](http://frame.io/). -2. Roku Scripted Credit Approval Form - This document should include both main title and end credits for Business Affairs Approval. -3. Traditional Rolling/Card Credits List that detail the specific credits for all contributors should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -#### 8.8.3 Segment rundown - -You will be required to deliver a detailed breakdown of the timecodes pertaining to all segments within the feature. Please utilize the Roku Segment Rundown Template provided in your Kick-Off Delivery Packet. - -Roku requires that the timecodes within this document be delivered in HH:MM:SS:FF format. Any spreadsheets submitted without this formatting will not be accepted by Roku. - -#### 8.8.4 As broadcast script (ABS) - -Please deliver one As Broadcast Script to the Hub. ABS files should have a timecode-based breakdown of each line of dialogue. You are approved to submit the ABS’s in any format that a Roku approved vendor utilizes. - -#### 8.8.5 Final font memo - -Please deliver one document that details the font name and size utilized for opening credits, identifiers and/or other on-screen text to the Hub. If applicable, please also note which vendor created the show logo. - -#### 8.8.6 Final vendor list - -Please deliver your final version of the Roku Vendor List that you received in the Kick-Off Delivery Packet to the Hub. - -#### 8.8.7 Final text spotting list - -Please deliver the final version of the Text Spotting List that was used to Quality Control the final Texted Master to the Hub. Please ensure that any changes made during Quality Control are reflected in the final document that is delivered to Roku via The Hub. Please deliver a single excel file, via Roku’s template, with episodes separated onto their own tabs. - -#### 8.8.8 Delivery checklist - -Please deliver the final version of the Roku Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. All of the following must be completed: - -- All applicable file version dates and delivery locations for each asset -- All Quality Control Start and End/Approval dates for Texted and Textless Masters -- Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -- If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 8.8.9 Music cue sheet - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the American Society of Composers, Authors and Publishers (ASCAP) website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. - -For the Roku Originals end logo cue: - -- Masters & Publishing: 100% ASCAP -- Publisher: Roku, Inc - -Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Vosper at [svosper@roku.com](mailto:sgrossberg@roku.com). - -#### 8.8.10 Not applicable form - -In cases where a paper deliverable is non-applicable to the project, please upload the Roku Not Applicable Form to the Hub with a written explanation of why this deliverable does not apply. - -## 9. Archival - -### 9.1 High-resolution masters and source material - -Roku’s platform for archiving projects is to an AWS S3 bucket. This can be accessed via Aspera Shares. Note that this is separate from the Aspera Ingest upload. A Roku Post Manager will request email addresses and names of those who will be uploading archival assets to the designated archival show folder for credentialing. - -When adding video assets to S3 do not create additional sub-folders. Keep all media (proxies, texted/textless masters) only in the folders provided. - -The following are required deliverables that must be uploaded to the Final Archive folder on S3: - -Required: - -- Final Texted Masters -- Final Textless Masters -- Final Audio Stems -- Graphic Elements – Main title card, credit PNGs, end credit PNGs, on-screen graphics, interstitials, etc -- Timed Text Files -- Locked Cuts - -Any and all series that are wholly owned by Roku will require delivery of VAMs, CTMs, and final Visual Effects shots (where applicable) via Aspera upload to S3, or, in some cases, LTO10 or greater. LTOs should be formatted LTFs and include a digital manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. These manifests should be uploaded to The Hub. - -For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -- VAMs – Un-color-corrected, textless, DPX or TIFF (\***_Compress\*_** to .ZIP or .TAR) - - Associated Avid bins or Edit Decision Lists -- CTM – Color-corrected, textless, DPX or TIFF (\***_Compress\*_** to .ZIP or .TAR) - - Associated LUTs or color-grading files -- Final Visual Effects Shots – Un-color-corrected preferred (if applicable) - -#### 9.1.1 Dailies archival - -Any and all series that are wholly owned by Roku will require delivery of dailies/OCF via LTO10 or greater. LTOs should be formatted LTFs and include a manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -### 9.2 Offline editorial masters - -Please be sure that all consolidated avid media is archived and removed from [Frame.io](http://frame.io/) prior to wrap. Once each project’s wrap is complete, all media still contained within the [Frame.io](http://frame.io/) platform will be **deleted** and the series users will be disabled. - -## 10. Change log - -### V4.0 - -- 3.3.3 - Dailies Memo requirements updated. -- 3.4 - Sizzle requirements added for Roku’s main title presentation cards and deliverables. -- 3.4.1 - Sizzle TRT updated to 30-45 seconds. -- 5.2.1 - Temp ADR required in all in-progress cuts. -- 5.2.2 - Runtime Requirements Updated. -- 6.1.1 - Uncompressed masters - packaging DPX and TIFF folders into one .zip file. -- 6.1.4 - Live, remote mix playback preference for Roku Creative and Post Production. -- 7.1.3 - Roku presentation cards, duration and style specifications added. -- 8.6 - Timed Text files will now be delivered to the AWS S3 Archival Bucket. -- 8.7 - Final destination chart for all deliverables. -- 9.1 - Final Archival Media will now be uploaded to AWS S3, rather than Frame.io and for LTO Archive please use LTO10. - -### V3.0 - -- 2.5 - Roku's Localization Team will handle the creation of all Latin Spanish subtitles and Audio Descriptions. -- 3.1 - Capture specifications updated based on content type. -- 5.2.3 - Ad breaks placement. -- 7.1.2 - Presentation credit formatting requirements added. -- 7.2 - Roku Originals end card updated -- 8.3.1 - Paper deliverable labeling revised. -- 8.4.5 - If one episode in a series requires a full textless asset delivery, now all episodes in that series will require a fully textless master. -- 8.7.1 - Link to current metadata templates and guidelines added. -- 8.7.10 - 'Not Applicable' Form added. -- 9.1 - LTO archive updated to LTO9 requirement. - -### V2.1 - -- 5.2.4 – RO Content Rating Guidelines updated -- 5.6 - Graphics guidelines & review process section added for alternative features -- 8.7.1 - Roku Ingest Specs Link added for access most updated Metadata Template - -### V2.0 - -- Multiple Sections - 5.1 & Stereo Mix required. 7.1 mix no longer being requested. -- Multiple Sections - Timecodes of act breaks updated to HH:MM:SS:FF -- 5.2.1 - Total run time must be locked at Locked Cut stage, inclusive of a slug for the end credit bed. -- 5.5 - Locked Cut requirements updated -- 8.3.2 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX) -- 8.4.5 - Final Proxy file size changed to a maximum of 2gb -- 8.5.1 - Audio Deliverables updated -- 8.6 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX); Removed SCC file requirement -- 9.1 - Archival - Use of [Frame.io](http://frame.io/) Transfer App required for all uploads to the app - -(v1.9 intentionally skipped) - -### V1.8 - -- 2.4 – Roku Marketing Team’s involvement in Sizzle Reel and Main Title Treatment clarified -- 2.5 – Localization Introduction -- 3.1 – Approval needed for aspect ratios outside of 16:9; VFX workflow must maintain capture -- 5.3.2 – Cut Review & Turnaround Timing clarified -- 7.1.2 – Main Title Card requires review/approval by Roku Creative Execs, Marketing, Production & Post -- 7.2 – Roku Originals Logo must be placed last in end credits; download link provided -- 8.3.2 – Master Video Deliverables file naming modified -- 8.3.3 – Master Audio Deliverables file naming modified -- 8.4.2 – Audio Channel mapping and tagging of metadata must be verified -- 8.4.3 – Texted Video Masters audio track layout updated -- 8.4.4 – Audio mapping label verification as noted in 8.4.2 must be verified in Textless Master -- 8.5.1 – Revised audio labeling guidelines for stem delivery -- 9.1 – [Frame.io](http://frame.io/) & High Resolution Masters instructions revised - -### V1.7 - -- 3.3.2 – [Frame.io](http://frame.io/) dailies notification email -- 5.2.2 – Segment Rundown deliverable must include milliseconds in its formatting. -- 5.4 – Revised file naming convention on rough cut deliveries. -- 8.2.1 – Text Spotting List updated -- 8.3 – File naming format for both paper and media deliverables modified. -- 8.4.5 – Additional proxy deliverable added. -- 8.6 – Replaced Latin American (LAS) labeling with Mexican Spanish (esMX). -- 8.7 – Further clarification provided across paper deliverables. - -### V1.6 - -- 8.7.2 - Updated to include the “Cast & Crew“ file as a credits document deliverable. -- 9.1.1- Dailies Archival section added. - -### V1.5 - -- 5.5 – Segment Rundowns will be required with delivery of each rough cut -- 8.4.2 – HD Texted Master added as a new deliverable -- 8.5.2 – Audio Description files added as a new deliverable diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/index.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/index.md deleted file mode 100644 index 18adab70..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "Roku Originals" -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, Mexico, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices.  - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Production Guidelines outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-alternative-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-alternative-specs.md deleted file mode 100644 index 9267e608..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-alternative-specs.md +++ /dev/null @@ -1,966 +0,0 @@ ---- -title: Alternative media delivery specifications -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices. - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Post Production Delivery Specifications outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -## 2. Post kick-off - -Post Producer resumes should be sent to Roku for prior approval. One week prior to Production start, please reach out to Roku Post Production to set up a kick-off call. In prep for this call, please review this full specification document so that we can address any follow up questions you may have. - -### 2.1 Startup documents - -Additionally, please make sure to send the preliminary versions of all documents noted below to Roku Post Production prior to the first day of Production. Available templates have been provided in the Post Kickoff zip file. - -1. Post Grid (Please send in excel format, not PDF) -2. Post Production Contact List -3. Preliminary Vendor List -4. Dailies Memo - -#### 2.1.1 Episode numbering and post grid workflow - -Post Grids accuracy must be confirmed weekly, either via revised grid or an email reflecting that no changes have been made. For distribution, Roku requires these grids to be both uploaded to The Hub and emailed to a distribution list that Roku Production will provide prior to Production. - -Please note that the Post Grid template provides columns for multiple types of series, as noted below. If a specific column does not apply to your show, you can disregard it. - -- **Production Number**: 3-digit number that reflects season number and sequencing of shot material (101, 102, etc.) - - One-off Specials should contain the prefix “SP” and begin with 100. (SP100, SP200, etc.). - -- **Air Order**: 1-digit number that reflects the order in which each episode will air. - -### 2.2 Notifications workflow - -- Once in production, any changes to the post schedule/calendar must be communicated to Roku Post Production immediately (within 24 hours) -- **Quality Control Delivery and Final Delivery dates cannot shift without written approval by Roku Post Production** -- At the below milestones please set a call with the Roku Post Production Manager at the email address provided on the contact sheet: - - 1 week prior to Production - - 1 week prior to the first scheduled rough cut release date - - Within 1 week of production wrap - -### 2.3 Misc. - -- Please be sure to include the full name of the show in the subject line of all email correspondence. -- Do not include the Roku name or logo on any documents (including contact sheets, call sheets, PR’s, casting notices etc.) without written permission from Roku Production. -- The Roku Contact sheet is for Studio use and should not be distributed widely - -### 2.4 Roku marketing - -Marketing will be directly involved in the Main Title treatment creative process. - -### 2.5 Roku localization - -Roku’s Localization Team will handle the creation of Latin Spanish subtitles and Audio Description files (AD). - -## 3. Production - -Each production will be required to submit a Dailies Memo prior to the commencement of principal photography. The memo should confirm camera(s) being utilized as well as the workflow for processing all captured video and audio. - -### 3.1 Capture specifications - -- Unless otherwise approved by Roku production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of HD (1920x1080) and an aspect ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. -- All material should be captured, transferred, and mastered in a progressive frame rate. Please do not apply any cross-conversions to content. -- Please do not apply in-camera upscaling or de-squeezing to any camera masters. If your desire is to work with cameras that do not natively capture in HD, please reach out to Roku Post Production to discuss workflow options. - -### 3.2 Dailies selects - -- Roku only requires 5-10 minutes of dailies selects to be posted for each of the first 3 days of production. -- Selects must be uploaded during the first week of production unless b-roll capture is scheduled. If the latter is the case, reach out to your Roku Post Manager to strategize the timing for posting Selects. -- Please choose select takes that confirm production is proceeding as intended. It is not necessary to post all media from each day. -- Dailies should be posted to [Frame.io](http://frame.io/). Roku Post Production will provide a distribution list prior to the first day of dailies. - -### 3.3 Dailies memo - -A Dailies Memo should be submitted to both the Roku Production and Post Production teams for approval prior to the commencement of principal photography. This document should include the proposed dailies workflow process, from camera capture through dailies distribution. Please include at least the following information: - -CAPTURE - -- Camera(s) utilized - - For each camera model, please provide: - - Video Resolution - - Acquisition Codec - - Frame rate(s) -- Audio sample rate and bit depth -- Please confirm that video will be log/flat and that no LUT/color grade will be baked into the footage at capture - -OFFLOAD - -- Utility/Process used for offload -- Checksum Algorithm used - -DAILIES & EDIT PROXY PROCESS - -- Program utilized for creation -- Processing method & workflow utilized, including where in process LUT/color applied -- Edit Proxies Codec and Dailies Codec -- Raster/Resolution - -#### 3.4 Sizzle - -##### 3.4.1 Sizzle overview - -Roku may request your team create a 30-45 second sizzle for your project to be used for business-to-business purposes. - -Please note that the sizzle does not require formal finishing, i.e. final assembly, conform, color, or mix. As it is for B2B use, it does not require clearances or music licensing. - -Process: - -- Please include sizzle milestones in overall calendar deliverable. -- Please account for 2 rounds of notes from Roku Creative, plus an approval review. -- Please reach out to your Roku Post Manager for the delivery date, as the sizzle might be required prior to the end of principal photography for some projects. - -Sizzle should include: - -- 2 cards for a minimum of 2 seconds each - - Roku Presents - - A Roku Original Series -- Temp Main Title treatment -- Clips that represent the story and showcase talent involved -- Please include lower third IDs for any interview footage included -- Sizzle does not need to include full scenes - -Please reach out to your Roku Post Manager if you would like to see an example of a previous sizzle. - -##### 3.4.2 Sizzle deliverables - -An HD primary video deliverable is required as follows: - -- Please do not include any head/tail formatting or slate. -- Program should start at 00:00:00:00. -- File Specs: - - (1) H.264 - - 1920 x 1080 - - 23.98 (or native framerate of Production, if different) - - Temp Stereo Mix -- Delivery Destination: Frame.io (Final Archive > Sizzle) - -## 4. Security - -Security is of the utmost importance to Roku. As such, access to all of the exciting content we are creating together must be limited. Please review Roku’s security requirements noted below and reach out to Roku Post Production with any questions. - -### 4.1 Review platform - -Roku’s approved platform for content sharing is [Frame.io](http://frame.io/). Roku and [Frame.io](http://frame.io/) have developed a content review workflow that both ensures security and limits access to all pre-launched content. In this workflow, anyone viewing Roku content will be required to set up a user account within [Frame.io](http://frame.io/) so that their activity can be tracked. - -**No material should be shared on any other platform without written approval from Roku.** - -### 4.2 Download access - -**It is not permitted for anyone to have direct, clean download access to any Roku content without written approval from Roku.** - -For team members who require reference quicktimes in order to complete their work efficiently (i.e., Composers, Music Editors, Visual Effects Supervisors), please follow the steps below: - -- Submit a written request with the recipient’s name, email, and use case. Upon Roku approval: - - Each file must be watermarked with the recipient’s full name and located in the center of picture. - - Recipients should never be given access to an entire folder’s worth of content; Review links that contain solely the required assets should be sent to the Roku approved recipients. This link must be manually expired as soon as the file has been successfully downloaded. - - Files should always be housed on a vendor’s secure Storage Area Network (SAN). Files are never permitted to be stored on anyone’s personal device. - - It is the responsibility of each show's Post team to request vendor deletion of these files at show wrap. - -### 4.3 Content review - -[Frame.io](http://frame.io/)’s Roku Partner Playbook is shared with the Post team at the start of each project. This workflow must be followed for both cuts released to Roku and also cuts released prior (Editor, Director, Producers, etc.). If you have not received this document, please reach out to Roku Post Production. - -All guidelines below must be followed when sharing review links: - -- It is never permitted to share rough cuts via Public Links. Review Links require user login and are the only approved method for content review. -- It is not permitted for any rough cut viewing links to be download-enabled. -- All viewing links must include an expiration date that confines access to 7 days or less. -- **All cuts uploaded for review must be watermarked.** - -### 4.4 Non-standard requests - -It is not permitted to send content to anyone who is not a [Frame.io](http://frame.io/) user without written approval from Roku. - -## 5. Rough cuts - -### 5.1 Post weekly sync - -Once you begin the rough-cut process, your Roku Post Manager will reach out to schedule a weekly call. The call will be an informal sync to determine how the rough cuts are progressing and help address any questions you may have. If you have made any changes to the Post Grid over the week prior, please send a revised version prior to this call. - -### 5.2 Rough cut formatting - -#### 5.2.1 General requirements - -Below are the basic parameters to keep in mind as you begin the rough cut process: - -- Total Run Times: - - Short form - Each episode should be no longer than 15 minutes in total run time. Each episode’s content and length should be approved by the Roku Content team prior to lock. - - Half hour - Each episode’s run time should be between 22-24 minutes. - - Hour long - Each episode’s run time should be between 44-48 minutes. - - **_\*For All Locked Cuts\*_** - QT's must include a slug for the end credits so that the exact timing is locked to match the final master. -- Roku requires rough versions of graphics starting at the RC1 stage, and near final graphics by the FC stage. See Section 5.6 for a full breakdown of Roku’s graphics milestones. -- _It is not permitted to send rough cuts longer than either formats maximum without prior approval from the Roku Content Team._ -- Episodes should be cut, mastered, and delivered as separate episodes; not a long-play master. -- There may be discussions around pre-roll, mid-roll, or post-roll advertising cue points. Regardless, please deliver each episode as a seamless master. -- The use of blurs on un-cleared video content is not permitted without Roku Creative approval beforehand. - -#### 5.2.2 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -Wholly owned Roku Alternative projects have access to Universal Production Music (UPM) as a music provider. However, each project should confirm UPM availability with Roku Production prior to the commencement of Principal Photography. - -#### 5.2.3 Ad breaks - -All Roku Originals series are required to include ad breaks. Please refer to the parameters below based off your episode run times. - -- Short Form episodes with a total run time of 11-15 minutes will be required to include 1 total ad break into each episode. - - Short Form episodes with a total run time of less than 11 minutes will not need to include any act breaks. -- Episodes with a total run time of 22-24 minutes will be required to build 3 total ad breaks into each episode. -- Episodes with a total run time of 44-48 minutes will be required to build 5 total ad breaks into each episode. -- Formatting across all run times: - - **The ad breaks should not appear until at least 5 minutes of content have elapsed.** - - Ad breaks should be formatted as 1 second of black (no text permitted). Fade outs/ins are permitted. - - The last ad break must appear before the last 3 minutes of an episode, which will remain ad-free. - - All ad breaks should be spaced anywhere from 6 to 10 minutes apart, dependent on the creative. - -All Fine and Locked cuts sent to Roku must adhere to the specifications above. They will not be deemed acceptable otherwise. Please see Section 5.3.2 below for more detail on earlier cut releases. - -If an episode will not meet either run time range, and this has been previously approved by Roku’s Content team, please reach out to Roku Post Production to discuss ad break implications. - -The exact timecode of each ad break, in (HH:MM:SS:FF) format, will be required in both the Segment Rundown and Metadata deliverables. Both templates were provided in the Post Kickoff Deliverables Packet. Please reach out to Roku Post if you did not receive one. - -#### 5.2.4 Rating guidelines - -Roku Originals content must fall within a TV-PG or TV-14 rating. Some general ratings guidance has been provided below for you to keep in mind as the creative story progresses in editorial. Please note, however, this is a very subjective process and the rating tiers below are regularly reviewed and may be modified in response to shifts in industry standards. So please be sure to reach out to your Roku Legal contact if you have any questions or clarifications. - -**Rating tiers** - -| | VIOLENCE | SEX/NUDITY | SUBSTANCE USE/ABUSE | LANGUAGE | -| :-------- | :----------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------: | -| **TV-PG** | **✔** Shootings, brawls, fist fights
**✖** No blood | **✔** Limited to kissing, couples in bed, implied sexual situations
**✖** No nudity at all
**✖** No sexual violence | **✔** Implied drug use (not glorified or must show consequences) | **✔** Limited use of bleeping/dropping strong language. Ass, damn, hell, and bitch | -| **TV-14** | **✔** Brief violence, OK with some blood shown
**✕** No gore | **✔** Covered sex is allowed, brief thrusting, implied sexual abuse OK
**✔** Exposed butt/side breast OK
**✖** No full nudity | **✔** Visuals/use of drug abuse (not glorified, must show consequences)
**✖** No smoking minors | **✔** Shit, asshole, bastard (when used in a pejorative matter), goddamn, bitch, dick and pussy (as an insult) | -| **TV-MA** | **✔** On-screen graphic violence, gore | **✔** Depictions of graphic sexual activity or sexual violence
**✔** Full male or female nudity | **✔** Graphic visuals of substance use/abuse, injection, etc. (both. minors and adults)
**✖** No smoking minors | **✔** Use of fuck, tits, twat, cum, pussy, and cunt
**✖** Racial slurs and hate speech on a case-by-case basis | - -### 5.3 Rough cut review - -#### 5.3.1 Review platform - -Roku’s approved platform for dailies and rough cut release is [Frame.io](http://frame.io/). All content being sent for review by the Roku team will need to be shared via this platform. If you are working with a partner who utilizes a different internal platform, there will not be a need to render out separate files just for use with [Frame.io](http://frame.io/); [Frame.io](http://frame.io/)’s platform is compatible with most commonly used codecs, which allows the same file to be uploaded to both platforms. - -The Roku Post team will initiate onboarding prior to the first day of production. That will trigger a member of the [Frame.io](http://frame.io/) team to reach out to set up a training session with your team. Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content (with Roku’s approval). - -#### 5.3.2 Cut review and turnaround timing - -For each episode, Roku will provide notes within 48 business hours after receipt, whether the Production Company is based in the United States or outside the United States. Cuts received by Roku after 6:00 pm Pacific Standard Time will be deemed received the following business day. When sending cuts earlier than the scheduled release date, please note that the original notes return timing will need to be honored unless otherwise approved by Roku Creative. - -Locked cuts are approved if no notes have been sent after 48 hours. - -Rounds of Review: - -- 101-103\*: Rough Cut 1 → Rough Cut 2 → Fine Cut → Locked Cut -- 104+: Rough Cut 1 → Fine Cut → Locked Cut - -Review Order: - -- **Serialized Series:** Please prioritize RC1s over RC2s and FCs. - - Example - 101 RC1 → 102 RC1 → 103 RC1 → 101 RC2 -- **Formatted Series:** Please prioritize all cuts for 101 over subsequent episodes. - - Example - 101 RC1 → 101 RC2 → 101 FC → 102 RC1 - -\*If sending out of production order, please ensure the first three episodes sent to Roku receive Rough Cut 2’s. - -Please follow turnaround timing parameters below when sending cuts and addressing notes from Roku Creative: - -- Rough Cuts - - Eps. 1-2 Rough Cut 2's must be turned around within 5 business days of receiving notes from Roku - - For half-hour shows: - - Any given Rough Cut 1 will be accepted at up to 5 minutes over the 24-minute max run time per episode - - Any given Rough Cut 2 will be accepted at up to 1 minute over the 24-minute max run time per episode - - For hour-long shows: - - Any given Rough Cut 1 will be accepted at up to 5 minutes over the 48-minute max run time per episode - - Any given Rough Cut 2 will be accepted at up to 1 minute over the 48-minute max run time per episode - - For short form shows: - - Any given Rough Cut 1 will be accepted at up to 5 minutes over the 15-minute max run time per episode - - Any given Rough Cut 2 will be accepted at up to 1 minute over the 15-minute max run time per episode -- Fine Cuts & Locked Cuts - - All Fine & Locked Cuts must be to delivered per Roku’s exact formatting specifications or they will be rejected - - Eps. 1-2 Fine Cuts, Locked Cut cuts must be turned around within 3 business days of receiving notes from Roku - - Eps. 3+ Fine Cuts, Locked Cut cuts must be turned around within 3 business days of receiving notes from Roku - -Up to 2 half-hour episodes (or 1 hour-long episode) can be sent within a 48-hour period. No more than 3 10-minute episodes, per show, should be sent within a 48-hour period. - -For series with one or more story arcs, episodes should be sent for review in the order they will ultimately air on the Roku platform. For anthology series, or series consisting of stand-alone/self-contained episodes, rough cuts may be sent out of air order, if necessary. - -Check with your Content Executive regarding single vs. batch delivery of cuts. - -For any variations to the schedule above, please check with your Post Production or Content Executive for review and approval prior to the release of the first rough cut. - -### 5.4 Technical specifications for rough cuts - -Formatting: - -- Slate before the hour - Please include show title, episode number, cut version (RC1, FC, etc.), total run time and release date -- Hour 01 onward should be solely program material, inclusive of production logo card at tail as last frame of picture - -Video Specifications: - -- Dimensions: 1920 x 1080 -- Codec: h264 (preferred) or MPEG file -- Frame Rate: Keep it native to your project (24, 23.976, 25, etc.) -- Bitrate Encoding: Variable Bit Rate, 2 pass -- Target Bitrate: \~ 10mbps -- Aspect: Square Pixels (1.0) -- Visible Timecode Upper Right -- Please mark ad breaks in white text over one sec of black as either “Ad Break #” or incoming act number, i.e. “Act 2”. - -Audio Specifications: - -- Audio Codec: AAC -- Sample Rate: 48000 Hertz -- Channels: Stereo - -Graphics: - -- Remember to adhere to Broadcast Title Safe Zones when adding any burned-in graphics or text. - -### 5.5 Rough and locked cut delivery - -Roku Post Production will provide a recipient list for all rough cuts prior to the scheduled release of the first episode. The [Frame.io](http://frame.io/) team will walk each project through Roku’s preferred rough cut release workflow, which involves 2 notifications: - -1. An email to the entire distribution list, noting the availability of cuts and when notes are due back. - 1. This email should include a Segment Rundown that relates to the timing of each specific cut being sent. - -2. A notification from [Frame.io](http://frame.io/), which happens automatically after a cut is copied to the Shared Folder on [Frame.io](http://frame.io/). - -For each locked cut, you will be required to deliver the following elements via [Frame.io](http://frame.io/): - -- Locked Cut QuickTime -- Locked Cut EDL -- Locked Cut WAV Files: Mono Dialogue, Mono Music, and Mono Effects - -Cut filenames must follow the proper naming convention below: - -- Show Code (4-digits; Provided by Roku Post) -- Production number (3-digits: 101, 102, 103, etc.) -- Air Sequence (If available; 1-digit: 1, 2, 3, etc.) -- Cut version (Rough Cut 1, FC, etc.) -- Date the cut was released to Roku (YYYYMMDD) - -Example: FLIP_102_AIR_2_FC_20260513 - -All rough cut links should be confined to viewing only (i.e. no download access). When sharing cuts, please do not create any folders, or copy any folders into the Roku Review projects. - -### 5.6 Graphics milestones and review process - -The Roku Content & Post Production teams should be involved in key discussions related to graphics, from title treatments to overall episodic graphics packages. - -All graphics work (title treatment, lower thirds, interstitials, etc.) must be completed by a Roku approved graphics company. The use of freelance staff or in-house graphics teams is not permitted. Please reach out to Roku Post to obtain the list of approved vendors. - -The following milestones require Roku notification and review: - -- **6 weeks prior to 1st rough cut:** A minimum of 3 graphics vendor options must be sent to Roku for review and approval -- **4 weeks prior to 1st rough cut:** Due to Roku: Mood board, color palette, title sketches, font, etc. -- **2 weeks prior to 1st rough cut:** Due to Roku: First round of design and/or animation examples -- **1 week prior to 1st rough cut:** Due to Roku: Second round of design and/or animation examples -- **1st Rough Cut Release** - - Temp graphics implemented into the cut that is distributed to Roku. - - All temp graphics must be based on creative input from Roku. Any changes from the agreed upon look of in-show graphics will need to be outlined in an email to the Roku Content team. -- **1st Fine Cut Release:** Final Graphics must be implemented into the cut that is distributed to Roku - -After Roku has approved all in-show graphics and the first cut is locked, no changes should be made without written approval from the Roku Content team. - -## 6. Final mastering and marketing - -### 6.1 Picture and audio mastering - -#### 6.1.1 Uncompressed masters - -For wholly-owned Roku projects, Roku requires both the un-graded and graded high-resolution master sequences as part of final delivery. These files should be exported in DPX format or TIFF format, at the highest bitrate possible (16-bit preferred). Package DPX or TIFF image sequence folders into a single .zip file per episode for delivery. - -If your vendor is unable to export these sequences, please reach out to Roku Post Production. - -#### 6.1.2 Harding testing - -Please alert Roku Post Production if any episodic content contains flashing/strobing lights or other image patterns that have the potential to trigger seizures in viewers with Photosensitive Epilepsy. In these instances, you will be required to run a Harding Test and provide the passing report to Roku Post Production as part of Final Delivery. - -Please refer to the [Ofcom ITC Guidelines](https://www.ofcom.org.uk/__data/assets/pdf_file/0021/16248/gn_flash.pdf) for further information. - -#### 6.1.3 HDR10 and Dolby Vision - -Currently, Roku Alternative projects are only required to complete a SDR (Rec709) grade. Please keep in mind your final deliverables will need to be in legal video range. - -Roku encourages that all series be graded utilizing the Dolby Vision workflow. Although a HDR deliverable is not yet a requirement for the Roku platform, grading in Dolby Vision will allow for the highest quality visual experience, as well as protect for future inclusion of HDR deliverables. - -For Productions whose budgets and schedules permit HDR10 or Dolby Vision grading, please reach out to Roku Post Production to determine the necessary workflow and related deliverables associated with either. - -#### 6.1.4 Sound mixing - -Roku Alternative projects are required to mix in 5.1 Surround, and then downmix to create Stereo deliverables as well. - -#### 6.1.5 Promotional assets (images and trailers) - -As each production will differ with regards to promotional assets, please reach out to Roku Marketing to determine the specific asks for your show. - -## 7. Credits - -**The first draft of credits (opening title card + end credits) must be submitted to Roku Post for approval with delivery of the first Fine Cut.** - -### 7.1 Opening credits - -For opening credits, Roku will utilize traditional burned-in credits. Full requirements are noted below. Please reach out to Roku Post Production with any questions. - -#### 7.1.1 Disclaimer use - -If your show contains sensitive content, please reach out to your Roku Legal Executive to see if your episode requires a trigger warning prior to the cold open. - -**For any other opening cards or disclaimers, please reach out to Roku Post Production for approval.** - -#### 7.1.2 Presentation cards - -Each project is required to include (2) Roku presentation cards at the top of each program, as follows: - -- 1st card: ‘Roku Presents’ -- 2nd card: ‘A Roku Original’ ‘A Roku Original Series’ (Please confirm with Roku Post) -- Duration: Minimum of 2 seconds per card -- Please utilize the same font and style that is specific to each project. -- Roku prefers these be integrated over picture, during the opening of each program, rather than added as separate cards over black. - -#### 7.1.3 Main title option 1: main title card - -During the initial design phase of any title treatments please reach out to your Roku Creative Executives; Roku Production (production[@roku.com);](mailto:production@roku.com) Roku Marketing ([dlrokuoriginalmarketingcreative@roku.com](mailto:dlrokuoriginalmarketingcreative@roku.com)) and Roku Post: ([dlropost@roku.com](mailto:dlropost@roku.com)). - -For shows that choose to utilize a main title card, please follow the formatting requirements below: - -- Duration of this card will be a maximum of 5 seconds. -- The title card will display the show title/logo, burned into picture as part of each final video master. -- The Production Company/Producer will have full creative control over how the title appears, subject to size requirements and provided that it is within the 16x9 title safe zone. -- No other “Presentation”, possessory, or origination credits permitted anywhere on the program. -- Any request to include on-screen credits on this card will require approval by the Roku Content and Post Production teams. - -#### 7.1.4 Main title option 2: main title sequence - -For shows that choose to utilize a main title sequence, please follow the formatting requirements below: - -- Duration of this sequence will be a maximum of 15 seconds. - -- The main title sequence must include the title card or title logo. - - Title card or logo must be burned into picture as part of each final video master. - -- No other “Presentation”, possessory, or origination credits permitted anywhere on the program. - -- Any request to include on-screen credits within this sequence will require approval by the Roku Content and Post Production teams. - -### 7.2 End credit sequence - -For end credits, Roku will utilize traditional burned-in credits. Please follow the formatting requirements below: - -- For half-hour shows, duration of the End Credits should be a maximum of 30 seconds, inclusive of logo cards - - For hour-long shows, duration of the End Credits will be a maximum of 90 seconds, inclusive of logo cards. 
 - - For short form shows, end credits can have up to 3 production company logos/credits, not inclusive of the Roku Originals Logo -- The Roku Originals Logo should be placed last in the end credits - - **Please reach out directly to Roku Post for access to the most current Roku Original Logo at: [dlropost@roku.com](mailto:dlropost@roku.com)** - - The 2025 logo is available in UHD or HD (both at 23.98fps), and with either Stereo or 5.1 Audio -- End Credits must be white text on a black background -- End Credits must be formatted as separate cards, not as a rolling sequence -- Placing the show title logo or title card at the end of any episode is not permitted without prior approval from the Roku Content and Post Production teams -- Production Company Logo Card / Studio Credits - Optional - - Up to 3 production company or studio logos/credits can be included in the end credits, in addition to the mandatory Roku Originals end credit logo - - Separate end cards can have a maximum total length of 3 seconds each - - For shared cards, no more than 2 logos can be combined onto the same end card - - Animated logos/credits are permitted - - Logos can include audio provided there is no cost to Roku to license such audio - - Audio ring outs from the end of the episode are also acceptable - - **_\*The end of the last logo card will signify your last frame of picture.\*_** - - No credits may appear after the end logo cards. 
 - -### 7.3 Other credit requirements - -- Production Company/Producer shall deliver a complete written statement of all credit obligations in a format to be decided by Roku -- Production Company/Producer shall ensure that all credits conform to applicable third-party requirements -- Roku will have approval over all credits in each program, including all credits accorded to third parties - -**Adherence to the credit requirements in this document will be part of Roku’s Quality Check. If any specifications are not met, the asset will be passed back to the Production Company/Producer to modify. Roku’s Content Operation team can advise on how to upload assets for Roku review.** - -## 8. Final delivery - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and approved by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -The Delivery Phase begins as soon as your episodes are ready for Quality Control, after visual effects, color, and mix are complete. The following timeline is required to ensure that all pertinent assets are received on time for Post, Marketing, and Operations: - -- Due 1 Week Before First Episode Delivered to Quality Control Vendor - - Let Roku Post know which vendor you’re proceeding with - - Metadata Ingest Document due to the Hub \[See 8.7.1] - -- Due With Delivery to Quality Control Vendor - - Texted Masters - - Textless Masters (if applicable) - - Text Spotting List - -### 8.1 Onboarding - -Roku uses an External Deliverables Hub (“Hub”) to receive specific production documents. This Hub will also provide information necessary for the naming of each document and file deliverable. If you have not heard from the Roku Post Production team prior to delivery, please reach out to be set up with access to the Hub. - -### 8.2 Quality control (QC) - -Each Production is responsible for covering the cost of and delivering 100% QC approved content. All masters noted below will be required to be submitted to QC **using one of Roku’s approved QC vendors:** - -- Texted Master -- Textless Master - -All required versions for each episode should be delivered to the Quality Control facility on the same day. This will ensure the Quality Control operator is able to verify that there is no variation between the texted/textless timings. - -Please be sure to build time into your delivery schedule to account for the Roku Quality Control process. Roku advises that you set aside 2 weeks for each episode to complete the Quality Control of all masters. Delivery will not be considered ‘Final’ unless all masters have received a passing report from one of Roku’s approved vendors. A list of these vendors will be provided in the Post Kickoff Packet. - -If an episode has passed Quality Control but a revision is necessary (incorrect titles, production card modification, etc.) you **must** reach out to Roku Post before any redelivery is made. Please send an email with a detailed and time coded breakdown of what fixes are being requested so that Roku can review and determine the impact it will have on each team and the show premiere itself. - -#### 8.2.1 Texted spotting list (TSL) - -You will be required to deliver a Texted Spotting List file for each episode when it is submitted for Quality Control. This list will help Quality Control vendors verify that creatively intended text is included in the final file. A Roku Texted Spotting List template was provided in your Post Kickoff zip file. This single file should be updated as episodes are sent to Quality Control so that all information for the series is included in the same master spreadsheet. - -The Texted Spotting List should contain any and all text that is burned into picture, and the corresponding timecodes for each. If an episode has no burned-in text, you will still be required to deliver this file, but will specify the lack of text by checking the box at the top of the template. - -### 8.3 Filename specifications - -#### 8.3.1 Paper deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -- ShowCode _ProdNumber_AirOrder_Version_LangCode_Date_FINAL -- Example: GABH _301_Air_1_PostVendorList_enUS_20250303_FINAL - -#### 8.3.2 Master video deliverables - -All master\* video files should be labeled as follows: - -- ShowCode_ProdNumber_AirOrder_Version_LangCode_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov - -Example: - -NION_101_AIR_1_TXTD_enUS_UHD_SDR_FN_2CH_23976p_20190701-v2.mov - -Production Number = As listed on Post Grids - -Air Order = Please list even if the Air Order is the same as the Production Number - -| **File Name Segment** | **File Name Abbreviation** | -| --------------------- | ------------------------------------------------------------------------------------------------------- | -| Version | TXTD (Texted), TXLS (Textless), or PROXY | -| Language | enUS (American English) | -| Resolution | UHD or HD + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | 2CH (Interleaved) or 8CH (5.1 and Stereo) - 7.1 audio not permitted on any masters at this time | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of Quality Control and track the latest version for delivery | - -\*See 8.5.5 for Proxy file naming. - -#### 8.3.3 Master audio deliverables - -Audio materials should be named to include all appropriate information: - -ShowCode_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Example:** - -MAMA_102_v04_20220919_enUS_PM_Nearfield_2ch_48k_24b_23976_LT.wav - -| **Material Type** | **Abbreviation** | -| --------------------------------------------- | --------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, FFFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | - -| **Channel Type** | **Abbreviation** | -| ---------------- | ---------------- | -| Mono | Mono | -| Stereo | 2CH | -| 5.1 Surround | 6CH | - -| Track Assignment | Abbreviation | -| ---------------- | -------------------- | -| Mono | N/A | -| Stereo | LT, RT | -| 5.1 Surround | L, R, C, LFE, LS, RS | - -### 8.4 Breakdown of final locations for deliverables - -| **Media** | **Final Location** | -| :---------------------------------------------- | :----------------- | -| TXTD Master | S3 | -| TXLS Master | S3 | -| Clean Proxy | Frame.io | -| Vis. TC Proxy | Frame.io | -| Mono Audio Stems | S3 | -| Stereo & 5.1 Printmaster Stems | S3 | -| Stereo & 5.1 Stems (M\&E, Music, Dialogue, SFX) | S3 | -| Pro Tools Session Files (.ptx) | S3 | -| VAM Image Sequence (in .zip container) | S3 | -| CTM Image Sequence (in .zip container) | S3 | -| Timed Text Files (.srt and .vtt) | S3 | -| Paperwork (Metadata, Credits, etc.) | The Hub | - -### 8.5 Video deliverables - -All video should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher of the export settings mentioned in 8.5.3, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate that was captured (for example, if the camera captured ProRes 422, then final export should be ProRes 422 or equivalent instead of 4444 XQ). - -**_Roku Best Practices_** - -It is important to keep master sequences (Video Asset Management/Color Timed Master) and final deliverables in alignment with dailies capture specifications (i.e. free of any up-scaling, cross-conversions, or up-conversions). - -#### 8.5.1 Video formatting - -All files should be formatted to start at 00:00:00:00. - -Files should begin with the cold open and end on the last frame of the Roku Originals logo end card. - -All video files **MUST NOT** contain any of the following: bars and tone, bumpers, segment recaps or previews, Vertical Interval time code, advertisements, slates, rating cards, FBI warning cards, placards, overlay branding, promotional bugs, informational bugs, watermarks, or website link callouts. - -If promotional bugs or watermarks are required by a 3rd party, Roku Content Legal should be notified. - -#### 8.5.2 Audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 8.5.3 for specifications based on delivery codec. - -**The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all Texted and Textless Masters.** - -- If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered. -- Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export. - -Mixing Specifications: - -- Target - 24 LKFS +/- 2 (any average between -22 & -26). Based on ITU-R 1170-3 measurement. -- Audio should not peak above -2 dBfs (True Peak) - -#### 8.5.3 Texted video masters - -| **Video Codec** | **ProRes** | -| ---------------------- | ------------------------------------------------------- | -| Container | MOV | -| ­­­Profile | 422 HQ | -| Minimum Bitrate | 175 mbits or higher | -| Landscape aspect ratio | 16:9 (1.77:1) - (no black bars)
W1920 x H1080 (HD) | -| Pixel aspect ratio | Square pixels (1:1) | -| Scan type | Progressive scan type | -| Chroma Subsampling | 4:2:2 | -| Color Space | BT.709 Legal Video Range (16 to 940) | -| Bit depth | 10-bit or 12-bit | -| Constant Frame Rate | 23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p | -| Native frame rate | No 3:2 pulldown flags | - -
- -| **Audio Codec** | **PCM** | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Format | 2 Interleaved Tracks or 8 Mono Tracks | -| Track Layout | Interleaved: Track 1: 5.1, L-R-C-LFE-Ls-Rs Track 2: Stereo, LT/RT
Mono: L, R, C, LFE, Ls, Rs, Stereo LT, Stereo RT

**7.1 audio is not permitted on any masters at this time** | -| Sample Rate/Bit Depth | 48000Hz/24-bit | -| Channel Mapping & Metadata Tagging | See 8.5.2 - Verify correct audio channel mapping and metadata tagging. | - -#### 8.5.4 Textless delivery - -If your content includes burned-in on screen text, you will be required to deliver a separate Textless Reel or Full Episode. This reel should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Masters noted above. - -Audio mapping label verification as noted in 8.5.2 must be verified in textless master. - -Additionally, if foreign language subtitles cover 30% or more of a given episode, you will be required to deliver a completely textless master of that episode. All episodes should be delivered with the same formatting; if one episode requires a textless master, versus a reel, then all remaining episodes should also be delivered as textless masters. - -Examples of what to remove for the Textless Masters: - -| Forced Narratives | Credits | Text-Based Graphics | -| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -| ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-1.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-2.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-3.jpeg) | - -_Roku Best Practices_ - -- Background elements with text, such as street signs, do not need to be included in the Textless Reel. -- ‘Forced Narratives’ refers to on-screen text that is used in one of two ways: to translate foreign dialogue into English or to clarify dialogue that may be inaudible. - -#### 8.5.5 Final proxy files (clean and visible timecode) - -From each Texted Master created, please export the following proxy files: - -| **Video Codec** | **H.264** | -| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Container | MOV or MP4 | -| Picture | (1) Clean & (1) w/ Vis.TC UR (1) Series Opener Only | -| Bitrate | 5mbit/s (total file size \< 1gb to 2gb) | -| Dimensions | W1920 x H1080 (HD) | -| Scan Type | Progressive scan type | -| Color Space | BT.709 Legal Video Range | -| Bit Depth | 10-bit or 12-bit | -| Constant Frame Rate | Should Match Master | -| Native Frame Rate | Should Match Master | -| Audio | Ch.1 Stereo Left, Ch.2 Stereo Right | -| Filename | ShowCode_ProdNumber_AirOrder_Language_Proxy_HD_FN(if applicable)\_Audio_Timecode(Clean or VisTC)\_RevisionDate-v#\_(Final or Pre-QC).mov THAM_101_AIR_1_PROXY_enUS_HD_FN_2CH_CLEAN_20200916_V4_FINAL.mov | - -### 8.6 Audio delivery - -Prior to the commencement of principal photography, please reach out to Roku Post Production in order to determine the necessary audio deliverables for your series. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. Please upload to your Archive folder on [Frame.io](https://frame.io/home). - -#### 8.6.1 Domestic episodic stems - -Provided below are the stems required for delivery of each episode/project: - -- Mono Dialogue, Music, and Sound Effects stems -- Stereo & 5.1 Printmasters -- Stereo & 5.1 M\&E - Fully Filled -- Stereo & 5.1 Music -- Stereo & 5.1 Dialogue -- Stereo & 5.1 Sound Effects -- Pro Tools Session Files (.ptx) - -Provided below are the stems Roku would like to receive, if available (and applicable): - -- Stereo & 5.1 Mix minus narration -- Score or Original Composition (pending rights) -- Mono M\&E Stems - Opticals, Backgrounds, etc. - -All audio should be archived as 24-bit, 48kHz WAV files. - -Please see section 8.3.3 for full guidelines on labeling audio files. - -ShowCode_ProdNumber_Vers__DateLangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Example:** - -MAMA_102_v04_enUS_PM_Nearfield_2ch_48k_24b_23976_LT.wav - -_Roku Best Practices_ - -- Roku requires that all music be cleared for both domestic and international use across all media on all devices -- Optional tracks (foreign language, grunts, breathing, etc.) are preferred, if applicable -- If budget permits, please create Fully Filled FX stems as part of delivery - -### 8.7 Timed text file delivery - -Roku requires timed-text files to be delivered in all of the following formats: - -- Subtitles: Language solely (no inclusion of sound descriptors) -- SDH: Language in addition to sound descriptors (no forced narratives) -- FN: Forced Narratives solely - -All files are required in an effort to support customers that are deaf or hard of hearing. - -Roku requires closed captions and subtitles in **2** formats: SRT and WebVTT. The files have to have the same timecode and frame rate as the video and audio delivered. Character encoding MUST be UTF-8. - -**Languages & formats required:** - -English (American, Code: enUS): Subtitles, SDH, & Forced Narrative - -**All files should be labeled as follows:** - -ShowCode-ProdNumber-LanguageCode_Format-RevisionDate.srt - -**Filename examples:** - -NION-101-enUS_SDH-20190701 - -NION-101-enUS_FN-20190701 - -### 8.8 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Post Manager. - -#### 8.8.1 Roku metadata template - -Metadata allows Roku to ingest and display all series related information for our customers. Please do not alter the formatting of this spreadsheet as it will break the coding required for ingest. - -Please find the most recent Roku metadata templates and guidelines [HERE](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates). - -The required details will include, but are not limited to, the following: - -- Show - Title, Description, Primary Spoken Language, Production Companies -- Season - Title, Description (leave blank if not applicable) -- Episode - Title, Production Number, Air Order, Total Run Time (TRT) -- Exact timecode of ad break insertion, in (HH:MM:SS:FF) format - -Please note that Air Order and Episode Titles must be a decision made with your Content Executive. The Episode Titles must be creative (no “Episode 1”) and should be written with the show writers or receive writer approval. - -#### 8.8.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. Portable Network Graphics (PNG) files relating to the Title Logo and any other logos submitted should be uploaded to [Frame.io](http://frame.io/). -2. Roku Alternative Credit Approval Form - This document should include both main title and end credits for Business Affairs Approval. -3. Traditional Episodic Credits Lists that detail the specific credits tied to each episode should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -#### 8.8.3 Segment rundowns - -You will be required to deliver a detailed breakdown of the timecodes pertaining to all segments in each episode. Please utilize the Roku Segment Rundown Template provided in your Kick-Off Delivery Packet. - -Roku requires that the timecodes within this document be delivered in HH:MM:SS:FF format. Any spreadsheets submitted without this formatting will not be accepted by Roku. - -#### 8.8.4 As broadcast scripts (ABS) - -Please deliver one set of As Broadcast Scripts for each series to the Hub. As Broadcast Script files should have a timecode-based breakdown of each line of dialogue. You are approved to submit the As Broadcast Script’s in any format that a Roku approved vendor utilizes. - -#### 8.8.5 Final font memo - -Please deliver one document that details the font name and size utilized for opening credits, identifiers and/or other on-screen text added to each episode (where applicable) to the Hub. If applicable, please also note which vendor created the show logo. - -#### 8.8.6 Final vendor list - -Please deliver your final version of the Roku Vendor List that you received in the Kick-Off Delivery Packet to the Hub. - -#### 8.8.7 Final text spotting list - -Please deliver the Text Spotting List that was used to Quality Control the final episodes to the Hub. Please ensure that any changes made during Quality Control are reflected in the final document that is delivered to Roku via The Hub. Please deliver a single excel file, via Roku’s template, with episodes separated onto their own tabs. - -#### 8.8.8 Episodic delivery checklist - -Please deliver the final version of the Roku Episodic Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. Please fill in all applicable delivery dates of assets and indicate when Archival will be completed. - -- All applicable file version dates and delivery locations for each asset -- All Quality Control Start and End/Approval dates for Texted and Textless Masters -- Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -- If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 8.8.9 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the American Society of Composers, Authors and Publishers (ASCAP) website linked [HERE](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP is also available via the Hub in the Production Legal – Scripted folder. - -Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Vosper at [svosper@roku.com](mailto:sgrossberg@roku.com). - -#### 8.8.10 Not applicable form - -In cases where a paper deliverable is non-applicable to the project, please upload the Roku Not Applicable Form to the Hub with a written explanation of why this deliverable does not apply. - -## 9. Archival - -### 9.1 High resolution masters and source material - -AWS is Roku’s platform for archiving projects. Roku’s S3 bucket can be accessed via Aspera Shares. Note that this is separate destination from the Aspera Ingest upload. A Roku Post Manager will request email addresses and names of those who will be uploading archival assets to the the designated archival show folder. - -Reach out to Roku Post if you have not received access to Aspera credentials. - -When adding video assets to S3 do not create additional sub-folders. Keep all media (proxies, texted/textless masters) only in the folders provided. Audio files should be grouped by episode (where applicable). - -The following are required deliverables that must be uploaded to the Final Archive folder on S3: - -Required: - -- Final Texted Masters -- Final Textless Masters -- Final Audio Stems -- Graphic Elements – Main title card, credit PNGs, end credit PNGs, on-screen graphics, interstitials, etc. -- Timed Text Files -- Locked Cuts - -Any and all series that are wholly owned by Roku will require delivery of VAMs, CTMs, and final Visual Effects shots (where applicable) via LTO10 or greater. LTOs should be formatted LTFS and include a digital manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. These manifests should be uploaded to The Hub. - -For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -- VAMs – Un-color-corrected, textless, DPX or TIFF (\***_Compress\*_** to .ZIP or .TAR) - - Associated Avid bins or Edit Decision Lists -- CTM – Color-corrected, textless, DPX or TIFF (\***_Compress\*_** to .ZIP or .TAR) - - Associated LUTs or color-grading files -- Final Visual Effects Shots – Un-color-corrected preferred (if applicable) - -#### 9.1.1 Dailies archival - -Any and all series that are wholly owned by Roku will require delivery of dailies/OCF via LTO9 or greater. LTOs should be formatted LTFS and include a digital manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -### 9.2 Offline editorial masters - -Please be sure that all consolidated avid media is archived and removed from [Frame.io](http://frame.io/) prior to wrap. Once each project’s wrap is complete, all media still contained within the [Frame.io](http://frame.io/) platform will be **deleted** and the series users will be disabled. - -## 10. Change log - -### V4.0 - -- 3.3 - Dailies Memo requirements updated. -- 3.4 - Sizzle requirements - Roku's main title presentation cards and deliverables added. -- 3.4.1 - Sizzle TRT updated to 30-45 seconds -- 5.2.2 - Wholly-owned Roku unscripted projects now have access Universal Production Music. -- 6.1.1 - Uncompressed masters - packaging DPX and TIFF folders into one .zip file. -- 7.1.2 - Roku presentation cards, duration and style specifications added. -- 8.4 - Final destination chart for all deliverables. -- 8.7 - Timed Text files will now be delivered to the AWS S3 Archival Bucket. -- 9.1 - Final Archival Media will now be uploaded to AWS S3, rather than Frame.io and for LTO Archive please use LTO10. - -### V3.0 - -- 2.5 - Roku's Localization Team will handle the creation of all Latin Spanish subtitles and Audio Descriptions -- 5.2.3 - Ad breaks placement. -- 7.1.2 - Presentation credit requirement added -- 7.2 - Roku Originals end card updated -- 8.3.1 - Paper deliverable labeling revised -- 8.4.4 - If one episode in a series requires a fully textless master delivery, now all episodes in that series will require a fully textless master -- 8.7.1 - Link to current metadata templates and guidelines added -- 8.7.10 - 'Not Applicable' Form added -- 9.1 - LTO9 is the newest version of the Linear Tape-Open and this is the version that should always be used - -### V2.1 - -- 5.2.4 – RO Content Rating Guidelines updated -- 5.6 - Graphics vendors guidelines updated -- 8.7.1 - Roku Ingest Specs Link added for access most updated Metadata Template - -### V2.0 - -- Multiple Sections - 7.1 Mix preferred but Texted Masters and stem delivery must be in 5.1 and Stereo only. 7.1 master files should be archived for future use. -- Multiple Sections - Timecodes of act breaks updated to HH:MM:SS:FF -- 5.2.1 - Blurring video not permitted without Roku approval -- 5.5 - Locked Cut requirements updated -- 8.3.2 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX) -- 8.4.5 - Final Proxy file size changed to a maximum of 2gb -- 8.6 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX); Removed SCC file requirement -- 9.1 - Archival - Use of Frame.io Transfer App required for all uploads to the app - -(v1.9 intentionally skipped) - -### V1.8 - -- 2.4 – Roku Marketing Team’s involvement in Sizzle Reel and Main Title Treatment clarified -- 2.5 – Localization Introduction -- 3.1 – Capture requirements adjusted to HD (1920x1080); Approval needed for aspect ratios outside of 16:9 -- 3.2 – Dailies Selects requirements further clarified -- 5.3.3 – Runtime requirements, cut review, and turnaround timing clarified -- 7.1.2 – Main Title Card requires review/approval by Roku Creative Execs, Marketing, Production & Post -- 7.2 – Roku Originals Logo must be placed last in end credits; download link provided -- 8.3.2 – Master Video Deliverables file naming modified -- 8.3.3 – Master Audio Deliverables file naming modified -- 8.4.2 – Audio Channel mapping and tagging of metadata must be verified -- 8.4.3 – Texted Video Masters audio track layout updated and resolution adjusted to HD -- 8.4.4 – Audio mapping label verification as noted in 8.4.2 must be verified in Textless Master -- 8.5.1 – Revised audio labeling guidelines for stem delivery -- 9.1 – [Frame.io](http://frame.io/) & High Resolution Masters instructions revised - -### V1.7 - -- 5.2.2 – Segment Rundown deliverable must include milliseconds in its formatting -- 5.4 – Revised file naming convention on rough cut deliveries. -- 8.2.1 – Text Spotting List updated -- 8.3 – File naming format for both paper and media deliverables modified -- 8.4.5 – Additional proxy deliverable added. -- 8.6 – Replaced Latin American (LAS) labeling with Neutral Latin American Spanish (esMX) -- 8.7 – Further clarification provided across paper deliverables - -### V1.6 - -- 8.7.2 - Updated to include the “Cast & Crew“ file as a credits document deliverable -- 9.1.1- Dailies Archival section added - -### V1.5 - -- 5.5 – Segment Rundowns will be required with delivery of each rough cut -- 8.5.2 – Audio Description files added as a new deliverable - -### V1.4 - -- 5.2.2 – Clarified that cuts will not be accepted if they do not adhere to Ad Break duration specifications -- 6.1.2 – Added Harding Test section for content with flashing/strobing lights and other image patterns -- 7.2 – End Production Logos may include audio provided there is no additional cost to Roku - -### V1.3 - -- 5.2.2 – Clarified that Ad Breaks should have no text -- 7.2 – Updated End Credits section with more detail -- 8.7.9 – Updated Music Cue Sheet information and point of contact for questions diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-branded-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-branded-specs.md deleted file mode 100644 index d1c16824..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-branded-specs.md +++ /dev/null @@ -1,883 +0,0 @@ ---- -title: Branded delivery specifications -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -_Version 3.0_ - _May 2026_ - -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices.   - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Post Production Delivery Specifications outline the best practices for the Partner at this time. - -This document covers the guidelines and protocol throughout the entirety of the Post Production process of a Roku Brand Studio Custom Series project. If you have any questions or do not think the needs of your project fit these guidelines, please contact [dlropost@roku.com](http://dlropost@roku.com/). These requirements are subject to change at Roku’s sole discretion.  - -## 2. Post kick-off - -Post Producer resumés should be sent to Roku for approval. One week prior to Production start, please reach out to Roku Post Production to set up a kick-off call. In preparation for this call, please review this full specification document so that we can address any follow-up questions you may have. - -During the kick-off call, ensure the following topics have been discussed: - -- Final deliverables list, including cutdowns -- Brand guidelines and assets - -### 2.1 Startup documents - -Additionally, please make sure to send the preliminary versions of all documents noted below to Roku Post Production prior to the first day of Production. Available templates have been provided in the Post Kick-off zip file. - -1. Post Grid (Please send in excel format, not PDF) -2. Post Production Contact List -3. Preliminary Vendor List -4. Dailies Memo - -#### 2.1.1 Episode numbering & post grid workflow - -Post Grids accuracy must be confirmed weekly either via revised grid or an email reflecting that no changes have been made. For distribution, Roku requires these grids to be both uploaded to The Hub and emailed to a distribution list that Roku Post Production will provide prior to Production. - -Please note that the Post Grid template provides columns for multiple types of series, as noted below. If a specific column does not apply to your show, you can disregard it. - -- **Production Number**: 3-digit number that reflects season number and sequencing of shot material (101, 102, etc.) -- **Air Order**: 1-digit number that reflects the order in which each episode will air. - -### 2.2 Notifications workflow - -- Any changes to the post schedule/ calendar must be communicated and approved by Roku Post Production and Roku Brand Studio. -- **Client Review, QC Delivery and Final Delivery dates cannot shift without written approval by Roku Post Production and Roku Brand Studio.** -- At the below milestones please set a call with the Roku Post Production Manager at the email address provided on the contact sheet: - - 1 week prior to Production - - 1 week prior to the first scheduled rough cut release date - - 2 days before review cuts go to client - - Within one week of production wrap - -### 2.3 Misc. - -- Please be sure to include the brand and full name of the show in the subject line of all email correspondence. Do not use acronyms for the title of the show. -- Do not include the Roku name or logo on any documents (including contact sheets, call sheets, PR’s, casting notices etc.) without written permission from Roku Production. -- The Roku Contact sheet is for Studio use and should not be distributed widely. - -### 2.4 Roku localization - -Roku’s Localization Team will handle the creation of Latin Spanish subtitles and Audio Descriptions (AD) files. - -## 3. Production - -Each production will be required to submit a Dailies Memo prior to the commencement of principal photography. The memo should confirm camera(s) being utilized as well as the workflow for processing all captured video and audio. - -### 3.1 Capture specifications - -- Unless otherwise approved by Roku Production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of HD (1920x1080) and an aspect ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. -- All material should be captured, transferred, and mastered in a progressive frame rate, 23.976 being preferred. Please do not apply any cross-conversions to content. -- Please reach out to Roku Post to confirm capture frame rate. -- Please do not apply in-camera upscaling or de-squeezing to any camera masters. If your desire is to work with cameras that do not natively capture in 4K, please reach out to Roku Post Production to discuss workflow options. - -### 3.2 Dailies selects - -Confirm with Roku Brand Studio if there are brand or product-specific dailies that need to be reviewed after production wrap. - -When Dailies Selects are requested, please follow the guidelines below: - -- Selects must be uploaded during the first week of production unless b-roll capture is scheduled. If the latter is the case, reach out to your Roku Post Manager to strategize the timing for posting Selects. -- Please choose select takes that confirm production is proceeding as intended. It is not necessary to post all media from each day. -- Dailies should be posted to [Frame.io](http://frame.io/). Roku Post Production will provide a distribution list prior to the first day of dailies. - -## 4. Security - -Security is of the utmost importance to Roku. As such, access to all of the exciting content we are creating together must be limited. Please review Roku’s security requirements noted below and reach out to Roku Post Production with any questions. - -### 4.1 Review platform - -Roku’s approved platform for content sharing is [Frame.io.](https://frame.io/) Roku and [Frame.io](https://frame.io/) have developed a content review workflow that both ensures security and limits access to all pre-launched content. In this workflow, anyone viewing Roku content will be required to set up a user account with [Frame.io](https://frame.io/) so that their activity can be tracked. - -**_No material should be shared on any other platform without written approval from Roku._** - -### 4.2 Download access - -**It is not permitted for anyone to have direct, clean download access to any Roku content without written approval from Roku.** - -For team members who require reference Quicktimes in order to complete their work efficiently (i.e., Composers, Music Editors, Graphic Designers, VFX Supervisors) , please follow the steps below: - -- Submit a written request with the recipient’s name, email, and use case: - - Each file must be watermarked with the recipient’s full name and located in the center of the picture. - - Recipients should never be given access to an entire folder’s worth of content; Review links that contain solely the required assets should be sent to the Roku approved recipients. This link must be manually expired as soon as the file has been successfully downloaded. - - Files should always be housed on a vendor’s secure SAN. Files are never permitted to be stored on anyone’s personal device. - - It is the responsibility of each show's Post team to request vendor deletion of these files at show wrap. - -### 4.3 Content review - -[Frame.io's](http://frame.io/) Roku Partner Playbook is shared with the Post team at the start of each project. This workflow must be followed for both cuts released to Roku and cuts released prior (Editor, Director, Producers, etc). If you have not received this document, please reach out to Roku Post Production. - -All guidelines below must be followed when sharing review links: - -- It is never permitted to share rough cuts externally via Public Links. Review Links require user login and are the only approved method for content review. -- It is not permitted for any rough cut viewing links to be download-enabled. -- All viewing links must include an expiration date that confines access to seven days or less. -- **All cuts uploaded for review must be watermarked.** -- If making a link for client review, use a password-protected presentation link with download disabled. - -### 4.4 Non-Standard requests - -It is not permitted to send content to anyone who is not a [Frame.io](http://frame.io/) user without written approval from Roku. - -## 5. Rough cuts - -### 5.1 Post weekly sync - -Before Post Production, your Roku Post Manager will reach out to schedule a weekly call. The call will be an informal sync to determine how the rough cuts are progressing and help address any questions you may have. If you have made any changes to the Post Grid over the week prior, please send a revised version prior to this call. - -### 5.2 Rough cut formatting - -#### 5.2.1 General requirements - -Below are the basic parameters to keep in mind as you begin the rough cut process: - -- Total Run Times: - - Ad Length – 00:15 or 00:30 TRT - - Marquee Ad Video (MAV) - Between 00:06 and 00:15 TRT - - Custom Vignette - Exactly 00:30 TRT - - Micro Series - A branded series of typically 3 episodes, each episode roughly between 2:00 and 4:00 TRT - - Short form - Each episode should be no longer than 15 minutes in total run time. Each episode’s content and length should be approved by the Roku Content team prior to lock. - - Half hour - Each episode’s run time should be between 22-24 minutes. - - Hour long - Each episode’s run time should be between 44-48 minutes. - -- Roku requires approved versions of graphics starting at the RC1 stage. See sections 5.2.4 for a full breakdown of Roku’s graphics milestones. - -- Each episode’s content should be approved by the Roku Brand Studio team prior to lock. - -- Episodes should be cut, mastered, and delivered as separate episodes; not a long-play master. - -- The use of blurs on un-cleared video content is not permitted without Roku Creative approval beforehand. - -#### 5.2.2 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -For branded content, Roku uses DeWolfe Music as a music provider. Please contact your Roku Post Production Manager to be granted a login and password to access DeWolfe’s library. - -#### 5.2.3 Rating guidelines - -Roku Originals content must fall within a TV-14 or TV-PG rating. Some general ratings guidance has been provided below for you to keep in mind as the creative story progresses in editorial. Please note, however, this is a very subjective process and the rating tiers below are regularly reviewed and may be modified in response to shifts in industry standards. So please be sure to reach out to your Roku Legal contact if you have any questions or clarifications. - -**Rating Tiers** - -| | VIOLENCE | SEX/NUDITY | SUBSTANCE USE/ABUSE | LANGUAGE | -| ---------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| TV-PG | ✔ Shootings, brawls, fist fights
✖ No blood | ✔ Limited to kissing, couples in bed, implied sexual situations
✖ No nudity at all
✖ No sexual violence | ✔ Implied drug use (not glorified or must show consequences) | ✔ Limited use of bleeping/dropping strong language. Ass, damn, hell, and bitch | -| TV-14 | ✔ Brief violence, OK with some blood shown
✕ No gore | ✔ Covered sex is allowed, brief thrusting, implied sexual abuse OK
✔ Exposed butt/side breast OK
✖ No full nudity | ✔ Visuals/use of drug abuse (not glorified, must show consequences)
✖ No smoking minors | ✔ Shit, asshole, bastard (when used in a pejorative matter), goddamn, bitch, dick and pussy (as an insult) | -| TV-MA | ✔ On-screen graphic violence, gore | ✔ Depictions of graphic sexual activity or sexual violence
✔ Full male or female nudity | ✔ Graphic visuals of substance use/abuse, injection, etc. (both. minors and adults)
✖ No smoking minors | ✔ Use of fuck, tits, twat, cum, pussy, and cunt
✖ Racial slurs and hate speech on a case-by-case basis | - -#### 5.2.4 Graphics milestones and review process - -Roku should be involved in key discussions related to graphics from title treatments to episodic graphics packages. All graphics work (title treatment, lower thirds, interstitials, etc.) must be completed by a Roku approved graphics vendor. These vendors are listed in the Roku Approved Graphics Vendor List in the Branded Content Series Kick-off Packet. This is to ensure brand safety and so graphics can have a streamlined approval before review of RC1 is underway. Roku Brand Studio requires final versions of graphics to be included for approval starting at the RC1 stage. This most importantly includes the title treatment. An RBS project will always have a graphics review timeline with the below milestones: - -1. A minimum of three graphics vendor options must be sent to Roku for review and approval - -2. Style frames that include 3-4 different creative directions (initial designs, mood board, color palette, fonts) - 1. Each creative direction should include static drafts of title treatment, lower thirds, segment name cards, informational graphics template, etc... - -3. RBS selection of approach to graphics from style frames along with some further notes - -4. 1st round of animated drafts to RBS - -5. RBS Notes of first round - -6. 2nd round of animated draft(s) to RBS - -7. RBS approval of graphics - -8. Delivery of title treatment to Roku Post and implementation of graphics into RC1 - -Once it is approved, the title treatment should be delivered to the Roku Brand Studio in PNG or MOV with transparency layers along with a consolidated After Effects Project, PSD, or Adobe Illustrator project file. - -After Roku has approved all in-show graphics and the first cut is locked, no changes should be made without written approval from RBS. - -### 5.3 Rough cut review - -#### 5.3.1 Review platform - -Roku’s approved platform for dailies and rough cut release is [Frame.io](https://frame.io/). All content being sent for review by the Roku team will need to be shared via this platform. If you are working with a partner who utilizes a different internal platform, there will not be a need to render out separate files just for use with [Frame.io](https://frame.io/); Frame.io’s platform is compatible with most commonly used codecs, which allows the same file to be uploaded to both platforms. - -The Roku Post team will initiate onboarding prior to the first day of production. That will trigger a member of the [Frame.io](http://frame.io/) team to reach out to set up a training session with your team. Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content (with Roku’s approval). - -#### **5.3.2 Cut review & turnaround timing** - -For each episode, Roku will provide notes listed within the Post Grid, but this is usually within 48 business hours after receipt, whether the Production Company is based in the United States or outside the United States. For cuts submitted earlier than the scheduled date, please note that the original notes return timing will need to be honored unless otherwise approved by Roku. - -Release Workflow: - -- All episode rough cuts should be sent for review at the same time. - - Split release schedules must be approved by RBS before production begins. -- Timing: - - If a cut is sent to Roku after 6:00 PM PST, then it will be deemed received the following business day. - - If a cut is scheduled to go to client for review, then all deadlines for materials should be sent to Roku by 4:00 PM PST. - - Note that this is for Roku’s own internal review before client. Roku will still have to approve the cut before sending to client. Additional edit requests may be sent back to the Production Company before the end of that day. -- Review Links: - - For review cuts to Roku, send [Frame.io](https://frame.io/) links to the review folder with NO passwords. Viewers will be required to sign into Frame.io. - - For review cuts to client, send public presentation links with a simple, show-specific password. Viewers will not be required to sign into [Frame.io](https://frame.io/). -- All Fine & Locked Cuts must be delivered per Roku’s exact formatting specifications or they will be rejected. -- Locked cuts are approved once RBS has received written approval from client. - -**Rounds of Review:** - -Please consult with RBS to determine the amount of Roku internal reviews and client reviews needed for a project. A typical RBS project will have a cut review similar to below: - -- Roku Rough Cut 1 → Client Rough Cut 2 → Roku Fine Cut 1 → Client Fine Cut 2 → Roku Locked Cut Review → Client Locked Cut Approval - -Up to three short-form episodes, two half-hour episodes, or one hour-long episode can be sent within a 48-hour period. For any variations to the schedule above, please check with your Post Production or Content executive for review and approval prior to the release of the first rough cut. - -For any variations to the schedule above, please check with your Post Production and RBS Contact for review and approval prior to the release of the first rough cut. - -### 5.4 Technical specifications for rough cuts - -#### 5.4.1 General technical requirements - -Formatting: - -- Roku Brand Studio Slate can be found [here](https://f.io/V0ADY-Vh). -- [Slate](https://f.io/V0ADY-Vh) before the Hour 01 timecode mark - Please include the brand, show title, episode number, TRT and cut date. -- Hour 01 onward should be solely program material. - -Video Specifications: - -- Dimensions: 1920 x 1080 (horizontal) -- Codec: h264 (preferred) or MPEG -- Frame Rate: Native (24, 23.976, 25, etc...) -- Bitrate Encoding: VBR, 2 pass -- Target Bitrate: \~ 10mbps -- Aspect: Square Pixels (1.0) -- Visible Timecode Upper Right - -Audio Specifications: - -- Audio Codec: AAC -- Sample Rate: 48000 Hz -- Channels: Stereo - -Graphics: - -- Remember to adhere to Broadcast Title Safe Zones when adding any burned-in graphics or text. - -### 5.4.2 Technical specifications for Marquee Ad Video (MAV) rough cuts - -A Marquee Ad Video (MAV) is a vertical video that displays in the Marquee of the Roku Home Screen on the right-hand side of frame. Follow the rough technical specifications below for MAV rough cuts: - -- Video Specifications: - - Dimensions: 525 x 735 (vertical orientation) - - Codec: h264 (preferred) or MPEG - - Frame Rate: Native (24, 23.976, 25, etc...) - - Bitrate Encoding: VBR, 2 pass - - Target Bitrate: \~ 10mbps - - Aspect: Square Pixels (1.0) - - Visible Timecode Upper Right - - TRT: 6 – 15 seconds - -- Audio Specifications: - - Audio Codec: AAC - - Sample Rate: 48000 Hz - - Channels: Stereo - -- Graphics: - - Remember to adhere to reference the Marquee Billboard GFX template [here](https://f.io/n-Ne2iKl) when adding any burned-in graphics or text. In-content GFX cannot intersect with GFX added on the Roku platform - -### 5.5 Rough & locked cut delivery - -Roku Post Production will provide a recipient list for all rough cuts prior to the scheduled release of the first episode. The [Frame.io](https://frame.io/) team will walk each project through Roku’s preferred rough cut release workflow, which involves two notifications: - -1. An email from the show team to the entire distribution list, noting the availability of cuts and when notes should be sent back to the show team, as well as any editorial caveats if applicable. -2. A notification from [Frame.io ](https://frame.io/)directly, which happens automatically as each cut is copied into the Shared Folders on [Frame.io](https://frame.io/). - -For each locked cut, you will be required to deliver the following elements via [Frame.io](https://frame.io/): - -- Locked Cut QuickTime -- Locked Cut EDL -- Locked Cut WAV Files: Mono Dialogue, Mono Music, Mono Effects - -Cut file names must follow the proper naming convention below: - -- Show Code (4-digits; Provided by Roku Post) -- Brand = Associated Brand -- Production number (3-digits: 101, 102, 103, etc.) -- Air Sequence (If available; 1-digit: 1, 2, 3, etc.) -- Cut version (Rough Cut 1, FC, etc.) -- Date the cut was released to Roku (YYYYMMDD) - -Example: FLIP_Nike_102_AIR_2_FC_20260513 - -For an initial internal review round, the cut should be labeled “Rough Cut 1,” and the proceeding cut to client as “Rough Cut 2” in the “CutVersion#” field. - -All rough cut links should be confined to viewing only (i.e. no download access). When sharing cuts, please do not create any folders, or copy any folders into the Roku Review projects. - -### 5.6 Color correction and sound mix review - -All locked cuts should have client approval before moving into Color Correction and Sound Mix. RBS will require review and approval of both preliminary stills and proposed final color. - -NOTE: RBS will need to review color and mix before moving into final finishing. Confirm with Roku to determine the amount of Roku internal finishing reviews and if client reviews are needed for sound and color finishing. - -Timing and review links procedures for reviews of Color Correction and Sound Mix should be identical to rough cut reviews mentioned in Section 5.3.2. Specifications should be identical to rough cut reviews mentioned in Section. 5.4. All color corrected and sound mixed files should be submitted as a single video file for review. - -For any variations to the schedule above, please check with your Post Production and RBS Contact for review and approval prior to commencement of Sound Mix and Color Correction. - -## 6. Credits - -Please discuss with Roku Brand Studio if there should be any opening or closing credits. - -During the initial design phase of any title treatments, please reach out to your Roku Brand Studio contacts. You should discuss the following: - -- The branding and language required to accompany the title treatment of the show. -- The length of time any branding is required to be on screen. -- Any branded fine print disclaimer information / copy that needs to be present on screen. - -### 6.1 Opening credits - -**The first draft of series credits (where applicable) must be submitted to Roku Post for approval with delivery of the first Fine Cut.** - -#### 6.1.1 Disclaimer use - -If your show contains sensitive content, please reach out to your Roku Legal Executive to see if your episode requires a trigger warning prior to the cold open. - -**For any other opening cards or disclaimers, please reach out to Roku Post Production for approval.** - -#### 6.1.2 Main title card - -For shows that choose to utilize a main title card, please follow the formatting requirements below: - -- Duration of this card will be a maximum of 5 seconds. -- The title card will display the show title/logo, burned into picture as part of each final video master. -- Title must be within the 16x9 title safe zone. -- No possessory, or origination credits permitted anywhere on the program. -- Any request to include on-screen credits on this card will require approval by the Roku Content and Post Production teams. - - No other credits are permitted in the opening of the show. - -### 6.2 End credit sequence - -Please discuss with RBS if any credits, logos, disclaimers or branded cards need to go at the end of the program. - -- The end of the last logo card will signify your last frame of picture. -- No credits may appear after the end logo cards. - -### 6.3 Other credit requirements - -- Production Company/Producer shall deliver a complete written statement of all credit obligations in a format to be decided by Roku. -- Production Company/Producer shall ensure that all credits conform to applicable third-party requirements. -- Roku will have approval over all credits in each program, including all credits accorded to third parties. - -**Adherence to the credit requirements in this document will be part of Roku’s Quality Check. If any specifications are not met, the asset will be passed back to the Production Company/Producer to modify. Roku’s Content Operation team can advise on how to upload assets for Roku review.** - -## 7. Final delivery - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and approved by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -The Delivery Phase begins as soon as your episodes are ready for Quality Control, after VFX, color, and mix are complete. Once the Production Company’s QC has been complete, please send to Roku for a brand safety and creative QC as well. - -The assets listed below are considered “Launch Critical.” This means they are required for ingest and launch on the Roku platform. - -- Still Photographs (Listed in 7.4) -- Key Art (Listed in 7.5) -- Video Deliverables (Listed in 7.6) -- Marquee Ad Videos (MAV) Deliverables (Listed in 7.6.5) -- Audio Deliverables (Listed in 7.7) -- Time Text Delivery (Listed in 7.8) -- Paper Deliverables (Listed in 7.10) - -### 7.1 Onboarding - -Roku uses an External Deliverables Hub (“Hub”) to receive specific production documents. This Hub will also provide information necessary for the naming of each document and file deliverable. If you have not heard from the Roku Post Production team prior to delivery, please reach out to be set up with access to the Hub. - -### 7.2 Quality control (QC) - -If there is an extremely tight turnaround on the delivery of a master, in lieu of a standard QC vendor, the production partner will be required to complete a full review of each master prior to delivery via Aspera. Once complete, the partner will be required to send an email confirmation to RBS to confirm video, audio, technical and brand specifications have been met, as well as confirming the final file name. - -Partners undergoing QC are responsible for covering the cost of and delivering 100% QC approved content. Partners will be required to send all masters noted below to **one of Roku’s approved QC vendors:** - -- Texted Master -- Textless Master - -All required versions for each episode should be delivered to the QC facility on the same day. This will ensure the QC operator can verify there is no variation between the texted / textless timings. - -Please be sure to build time into your delivery schedule to account for the Roku QC of each episodes’ masters. Delivery will not be considered ‘Final’ unless all masters have been given a QC by either a vendor or a production partner. A list of suggested vendors will be provided in the Post Kick-off Packet. - -If an episode has passed QC but a revision is necessary (incorrect titles, production card modification, etc.) you **must** reach out to Roku Post before any redelivery is made. Please send an email with a detailed and time coded breakdown of what fixes are being requested so that Roku can review and determine the impact it will have on each team and the show premiere itself. - -**7.2.1 Texted spotting list (TSL)** - -For series undergoing QC, you will be required to deliver a TSL file for each episode when it is submitted for QC. This list will help QC vendors verify that creatively intended text is included in the final file. Roku Post will provide a TSL template to each series. - -The TSL should contain any and all text that is burned into picture, and the corresponding timecodes for each. If an episode has no burnt-in text, you will still be required to deliver this file, but will specify the lack of text by checking the box at the top of the template. - -**7.2.2** **Harding testing** - -Please alert Roku Post Production if any episodic content contains flashing/strobing lights or other image patterns that have the potential to trigger seizures in viewers with Photosensitive Epilepsy. In these instances, you will be required to run a Harding Test and provide the passing report to Roku Post Production as part of Final Delivery. - -Please refer to the [Ofcom ITC Guidelines](https://www.ofcom.org.uk/__data/assets/pdf_file/0021/16248/gn_flash.pdf) for further information. - -### 7.3 Aspera delivery for ingest - -Roku accepts delivery content for ingest to The Roku Channel via Aspera which can be configured as either an Aspera Shares (using the IBM Aspera for desktop) or as an Aspera P2P/Enterprise connection (using Aspera Client or Console). To configure for Aspera Shares delivery: - -- Provide the name(s) and email address(es) for users that will be transmitting content to Roku for The Roku Channel. -- Roku’s Aspera Shares URL: [https://aspera.sr.roku.com](https://aspera.sr.roku.com/) -- For the review of the RBS team, screeners of the master files and key art should be put on Frame.io as well. -- Launch Critical Deliveries must be delivered to the **/prod** folder on Aspera. **Do not separate deliverables into separate subfolders. All assets should be under a single folder.** -- Test files may be delivered to the **/testing** folder. -- Video, closed captions, and key art files must be delivered in one folder. Video, closed captions, and key art files must also be completely delivered prior to the delivery of the metadata sheet. More regarding the Metadata Sheet in Section 7.10.1. - -#### 7.4 Still photographs - -A timeline for stills capture, review and delivery should be included in every production calendar, with final delivery of photos happening before the delivery of a project’s first rough cut. Please discuss with the RBS Team how stills should be captured, how many final photos will need to be delivered, and a timeline for creative, selects review, final selection, and delivery. - -An example of a stills calendar should look like this: - -- Production Wrap -- 2 business days later – first round of .jpg selects sent to RBS -- 2 business days later – Select feedback from RBS due -- 2 business days later – Final delivery of RAW stills - -Capture Requirements: - -- Stills should be captured at the maximum resolution of a camera and in the camera manufacturer's RAW format. -- Photos should be a mixture of vertically and horizontally oriented, posed talent photography is suggested. -- Photos should not be candid or BTS in style. -- In addition to talent stills, photos of sets and locations clear of talent are also required. - -Selects Requirements: - -- First-round selects delivered should equate to 20% of the total number of stills taken. - - First-round selects of stills should be delivered to RBS within 2 business days of production wrap. - - For ease of review, send same-as-source resolution .jpg versions of stills. -- In addition to talent stills, photos of sets and locations clear of talent are also required. - -Final Delivery Requirements: - -- Stills should be delivered at the maximum resolution of a camera and in the camera manufacturer's RAW format. -- The minimum number of total stills required is 15. - - The minimum number of stills per on-screen talent is five. - - The minimum number of stills per sets/locations is five. -- Once final, approved still photos have been selected, they should be uploaded to a designated Frame.io folder as part of Final Delivery. -- Approved final still file names should follow this format: - - Brand_ShowName_ProductionNumber_FinalStill_Resolution_DateYYYYMMDD_version# - - Example: Nike_ShoeShow_101_FinalStill_1920x1080_20260325_V1.jpg - -### 7.5 Key art - -For a Custom Series, please discuss with Roku Brand Studio. If it is the Production Company’s responsibility to create key art, please refer to the below assets: - -- 16x9 Series Key Art (Suggested resolution 1920x1080) - -- 16x9 Episode Background Image (Suggested resolution 1920x1080) - - Should not have any text. - - Can have episode-specific talent in frame. - -- Vertical Box Cover Key Art (Suggested resolution 532x800) - -- Series Background Image (Suggested resolution 1920x1080) - - Should not have any text. - - Most likely will be a talent-free “plate shot” taken of the set. - -- Series Title Treatment - - Please provide PSD with transparent layer, Adobe Illustrator, or consolidated After Effects Project. - - If the treatment has moving / animated elements, also provide a ProRes4444 file with an alpha layer. - -### 7.6 Video deliverables - -All videos should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher as the export settings, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate that was captured (for example, if the camera captured ProRes 422, then final export should be ProRes 422 or equivalent instead of 4444 XQ). - -If your capture workflow is different than specified above, please contact Roku Post Production before final mastering begins. It is important to keep master sequences and final deliverables in alignment with dailies capture specifications (i.e. free of any up-scaling, cross-conversions, or up-conversions). - -#### 7.6.1 Video formatting - -All delivery files should be formatted to start at 00:00:00:00. - -All video files \*\*MUST NOT \*\*contain any of the following: bars and tone, bumpers, segment recaps or previews, VITC time code, slates, rating cards, FBI warning cards, placards, or watermarks. - -Master files should be expected to be the files that will stream on The Roku Channel as is. - -#### 7.6.2 Audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 7.6.3 for specifications based on delivery codec. - -**The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all texted and textless masters.** - -- If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered. -- Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export. - -Mixing Specifications: - -- Target -24LKFS +/- 2 (any average between -22 & -26). Based on ITU-R 1170-3 measurement. -- Audio should not peak above -2 dBfs (True Peak) - -#### 7.6.3 Texted video masters - -| Video Codec | ProRes | -| ---------------------------- | ------------------------------------------------------- | -| Container | MOV | -| Profile | 422 HQ | -| Minimum Bitrate | 175 mbits or higher | -| Landscape aspect ratio | 16:9 (1.77:1) - (no black bars)
W1920 x H1080 (HD) | -| Pixel aspect ratio | Square pixels (1:1) | -| Scan type | Progressive scan type | -| Chroma Subsampling | 4:2:2 | -| Color Space | BT.709 Legal Video Range (16 to 940) | -| Bit depth | 10-bit or 12-bit | -| Constant Frame Rate | 23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p | -| Native frame rate | No 3:2 pulldown flags | -| Audio Codec | PCM | -| Format | Stereo | -| Track Layout | Interleaved: Track 1: Stereo, LT/RT | -| Sample Rate | 48000Hz | -| Bit Depth | 24-bit | - -#### 7.6.4 Textless delivery - -If your content includes burned-in on screen text, you will be required to deliver a Full Episode. This file should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Masters noted above. - -Audio mapping label verification as noted in 7.6.2 must be verified in textless master. - -Additionally, all episodes should be delivered with the same formatting; if one episode requires a textless master then all remaining episodes should also be delivered as textless masters. - -Examples of what to remove for the Textless Masters: - -| Forced Narratives | Credits | Text-Based Graphics | -| ------------------------------------------------------------- | ------------------------------------------------------------- | -------------------------------------------------------------- | -| ![](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-1.png) | ![](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-2.png) | ![](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-3.jpeg) | - -Roku Best Practices - -- Background elements with text, such as street signs, do not need to be included in a Textless version. -- ‘Forced Narratives’ refers to on-screen text that is used in one of two ways: to translate foreign dialogue into English or to clarify dialogue that may be inaudible. - -#### 7.6.5 Marquee Ad Video (MAV) delivery - -Note that the TXLS video master is the deliverable that is ingested into the Roku Channel. The TXTD MAV video masters will be used as a reference for Roku Design. Follow the below technical specifications for both TXTD and TXLS MAV Master delivery: - -
- -| Video Codec | ProRes | -| ---------------------------- | ------------------------------------------------ | -| Container | MOV | -| Profile | 422 HQ | -| Minimum Bitrate | 175 mbits or higher | -| Vertical aspect ratio | W525 x H735 | -| Pixel aspect ratio | Square pixels (1:1) | -| Scan type | Progressive scan type | -| Chroma Subsampling | 4:2:2 | -| Color Space | BT.709 Legal Video Range (16 to 940) | -| Bit depth | 10-bit or 12-bit | -| Constant Frame Rate | 23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p | -| Native frame rate | No 3:2 pulldown flags | -| Audio Codec | PCM | -| Format | Stereo | -| Track Layout | Interleaved: Track 1: Stereo, LT/RT | -| Sample Rate | 48000Hz | -| Bit Depth | 24-bit | - -#### 7.6.6 Branded Stitched Interstitial delivery workflow - -If a piece of branded content is being stitched into Roku Originals (RO) content, Visual Data Media Services (VDMS) is Roku's branded content delivery partner. Once final deliverables have been approved, the production company must reach out to [RokuOriginals@visualdatamedia.com](mailto:RokuOriginals@visualdatamedia.com) to organize the stitch and delivery of launch critical materials to be put on Roku's Aspera Shares for final content ingest. - -Confirm the exact technical specifications of the Roku Original Program that the stitched content will be attached to. The stitched content must match the Roku Original Program exactly. - -Stitched Content Delivery requires: - -- Confirmed timecodes in the Roku Originals content where the branded material will be inserted. -- The audio for the branded material matches the RO content exactly. -- Revised Timed Text files to accommodate timing shift of stitched material. -- At least one QC pass is done by VDMS after stitching has been completed. -- Revised As Broadcast Script (ABS) to accommodate timing shift of stitched material. -- TXLS Master files are treated identically. -- Segment Rundown and Ingest Metadata template have been modified to accommodate timing shift of stitched material. - -#### 7.6.7 Final proxy files (clean & visible timecode) - -From each Texted Master created, please export the following proxy files: - -| Video Codec | H.264 | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Container | MOV or MP4 | -| Picture | (1) Clean & (1) w/ visible timecode | -| Bitrate | 5mbit/s (total file size \< 1gb) | -| Dimensions | W1920 x H1080 (HD) | -| Scan Type | Progressive scan type | -| Color Space | BT.709 Legal Video Range | -| Bit Depth | 10-bit or 12-bit | -| Constant Frame Rate | Should Match Master | -| Native Frame Rate | Should Match Master | -| Audio | Ch.1 Stereo Left, Ch.2 Stereo Right | -| Filename | Brand_ShowName_AirOrder_PROXY_TextVersion_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov.
Ex: Nike_ShowName_101_Proxy_TXTD_HD_SDR_ Stereo_23976p_20240701-v2.mov | - -Note: Textless versions of final proxies are not required: only a texted version. - -### 7.7 Audio delivery - -Prior to the commencement of principal photography, please reach out to Roku Post Production in order to determine the necessary audio deliverables for your series. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. Please upload to your Final Archive folder via Aspera Shares. - -#### **7.7.1 Domestic episodic stems** - -Provided below are the stems required for delivery of each episode / project: - -- Mono Dialogue, Music, and SFX stems. - -- Stereo Printmasters - -- Stereo M\&E (if available) - -- Stereo Mix minus narration - -- Stereo Music - -- Stereo Dialogue - -- Stereo Sound Effects - -- Pro Tools Session Files (.ptx) - -Provided below are the stems Roku would like to receive, if available (and applicable): - -- Score or Original Composition (pending rights) -- Mono M\&E Stems - Opticals, Backgrounds, etc. - -All audio should be archived as 24-bit, 48kHz WAV files. Stereo ONLY. - -Please see section 7.9.3 Master Audio Deliverables for full guidelines on labeling audio files. - -ShowCode_ProdNumber_Vers_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_102_v04_enUS_PM_Nearfield_2ch_48k_24b_23976_LT.wav - -_Roku Best Practices_ - -- Roku requires that all music be cleared for both domestic and international use across all media on all devices. -- Optional tracks (foreign language, grunts, breathing, etc.) are preferred, if applicable. -- If budget permits, please create Fully Filled FX stems as part of delivery. - -### 7.8 Timed text file delivery - -Roku requires all content to be delivered with all the following timed-text formats: - -- Subtitles: Language solely (no inclusion of sound descriptors) -- SDH: Language in addition to sound descriptors (no forced narratives) - - These caption files should assume the viewer cannot hear dialogue or important, non-verbal narrative actions such as audio cues, music, sound effects and speaker identification. -- FN: Forced Narratives solely. - -All files are required in an effort to support customers that are deaf or hard of hearing. - -Roku requires closed captions and subtitles in **2** formats: SRT, and WebVTT. The files must have the same timecode and frame rate as the video and audio delivered. Character encoding MUST be UTF-8. - -**Languages & formats required:** - -English (American, Code: enUS): Subtitles, SDH, & FN - -**All files should be labeled as follows:** - -ShowCode-Brand-ProdNumber-LanguageCode_Format_RevisionDate.srt - -**Filename Examples:** - -NION-Nike-101-enUS_SDH_20190701.srt - -NION-Nike-101-enUS_FN_20190701.srt - -### 7.9 Filename specifications - -#### 7.9.1 Paper deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -- ShowCode _ProdNumber_AirOrder_Version_LangCode_Date_FINAL. -- Example: GABH _301_Air_1_PostVendorList_enUS_20250303_FINAL - -\*For any redeliveries of post deliverables, please include the date in addition to “FINAL”. - -#### 7.9.2 Master video deliverables - -All master video files should be labeled as follows: - -ShowCode_Brand_ProductionNumber_AirOrder_TextVersion_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov. - -Example: TCRE_Nike_101_1_Master_TXTD_HD_SDR_ Stereo_23976p_20240701-v2.mov - -Example for MAV Master: TCRE_Nike_MAV_MASTER_TXLS_HD_SDR_ Stereo_23976p_20240701-v2.mov - -Production Number = As listed on Post Grids - -Air Order = Please list even if the Air Order is the same as the Production Number - -| File Name Segment | File Name Abbreviation | -| ----------------- | ------------------------------------------------------------------------------------------ | -| Text Version | TXTD (Texted), TXLS (Textless), PROXY, or MAV | -| Language | enUS (American English) or esMX (Mexican Spanish) | -| Resolution | UHD or HD + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | Stereo 2CH (Interleaved) | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of QC and track the latest version for delivery | - -\*See 7.6.7 for Proxy file naming. - -**7.9.3 Master audio deliverables** - -Audio materials should be named to include all appropriate information: - -ShowCode_Brand_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_Nike_102_v04_20220919_enUS_PM_Nearfield_2ch_48k_24b_23976_L.wav - -MAMA_Nike_102_v03_20220919_esMX_FXSTEM_6ch_48k_24b_23976_R.wav - -MAMA_Nike_102_v02_20220919_esMX_ME_Nearfield_6ch_48k_24b_23976_C.wav - -| Material Type | Abbreviation | -| --------------------------------------------- | -------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, SFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | -| **Channel Type** | **Abbreviation** | -| Mono | Mono | -| Stereo | 2CH | -| **Track Assignment** | **Abbreviation** | -| Mono | N/A | -| Stereo | LT, RT | - -#### 7.9.4 File naming limitations - -Source video, closed captions, and artwork files delivered for ingest must adhere to the following guidelines: - -- File names must not exceed 64 characters in length. -- File names must match the reference to the file name in the metadata supplied for the title delivered. -- Whitespace and special characters `(!@#$%^&*(){}|[];:'"?/><)` must not be included in any file name. - -### 7.10 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Roku Post Manager. - -#### 7.10.1 Roku metadata template - -Metadata allows Roku to ingest and display all series related information for our customers. Please do not alter the formatting of this spreadsheet as it will break the coding required for ingest. - -Please find the most recent Roku metadata templates and guidelines [here](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates). - -The required details will include, but are not limited to, the following: - -- Show - Title, Description, Primary Spoken Language, Production Companies -- Season - Title, Description (leave blank if not applicable) -- Episode - Title, Production Number, Air Order, Total Run Time (TRT) - -Please note that Air Order and Episode Titles must be a decision made with and approved by RBS. The Episode Titles must be creative (no “Episode 1”) and should be written with the show writers or receive writer approval. - -The metadata sheet should only be submitted after all other Launch Critical materials have been approved. - -The metadata sheet must be delivered to the same folder as all other launch critical delivery material. Failure to do so will result in content processing delays. Reach out to the RBS Producer or Post Manager for any needed information for the Metadata Sheet. - -#### 7.10.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. Portable Network Graphics (PNG) files relating to the Title Logo and any other logos submitted should be uploaded to S3 via Aspera Shares. -2. Roku Branded Credit Approval Form - This document should include both main title and end credits for Business Affairs Approval. -3. Traditional Episodic Credits Lists that detail the specific credits tied to each episode should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -#### 7.10.3 As broadcast scripts (ABS) - -Please deliver one set of As Broadcast Scripts for each series to the Hub. As Broadcast Script files should have a timecode-based breakdown of each line of dialogue. You are approved to submit the As Broadcast Scripts in any format that a Roku approved vendor utilizes. - -#### 7.10.4 Final font memo - -Please deliver one document that details the font name and size utilized for identifiers and/or other on-screen text added to each episode (where applicable) to the Hub. If applicable, please also note which vendor created the show logo. - -#### 7.10.5 Final vendor list - -Please deliver your final version of the Roku Vendor List that you received in the Kick-Off Delivery Packet to the Hub. - -#### 7.10.6 Final text spotting list - -If an approved QC vendor was used, please deliver the Text Spotting List used to QC the final episodes to the Hub. Please ensure that any changes made during QC are reflected in the final document that is delivered to Roku via The Hub. Please deliver a single excel file, via Roku’s template, with episodes separated onto their own tabs. - -If a QC vendor was not used, still submit a final TSL to document all text information for a project. - -#### 7.10.7 Episodic delivery checklist - -Please deliver the final version of the Roku Episodic Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. Please fill in all applicable delivery dates of assets and indicate when Archival will be completed. - -- All applicable file version dates and delivery locations for each asset -- All QC Start and End/Approval dates for Texted and Textless Masters -- Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -- If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 7.10.8 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the ASCAP website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. - -Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Vosper at [svosper@roku.com](mailto:svosper@roku.com). - -#### 7.10.9 Not applicable form - -In cases where a paper deliverable is non-applicable to the project, please upload the Roku Not Applicable Form to the Hub with a written explanation of why this deliverable does not apply. - -## 8. Archival - -### 8.1 High resolution masters & source material - -AWS is Roku's platform for archiving projects. Roku's S3 bucket can be accessed via Aspera Shares. Note that this is a separate destination from the Aspera Ingest upload. A Roku Post Manager will request email addresses and names of those who will be uploading archival assets to the designated archival show folder. - -Reach out to Roku Post if you have not received access to Aspera credentials. - -When adding video assets to S3, do not create additional sub-folders. Keep all media (proxies, texted/textless masters) only in the folders provided. Audio files should be grouped by episode (where applicable). - -The following are required deliverables that must be uploaded to the Final Archive folder on S3: - -Required: - -- Final Texted Masters -- Final Textless Masters -- Final Audio Stems -- Graphic Elements – Main title card, MOV files with an alpha channel. After Effects graphics package on-screen with graphics, interstitials, etc. -- Timed Text Files - -#### 8.1.1 Dailies archival - -Dailies and all production assets should be kept for a minimum of 30 days after the receipt of all deliverables to Roku. - -### **8.2 Offline editorial masters** - -Please be sure that all consolidated edit media is archived and removed from [Frame.io](https://frame.io/) prior to wrap. Once each project’s wrap is complete, all media still contained within the [Frame.io ](https://frame.io/)platform will be **deleted** and the series users will be disabled. - -## 9. Change log - -### V3.0 - -- 5.2.1 - Approved runtimes for Custom Vignettes and Micro Series -- 5.4.2 - Technical spec requirements for the Marquee Ad Video (MAV) -- 7.4 - File naming convention for final still photos -- 7.6.5 - MAV Textless master delivery -- 7.6.6 - Branded Stitched Interstitial delivery workflow updated -- 8.1 - Final Archival Media will now be uploaded to AWS S3, rather than Frame.io. - -### V2.0 - -- 2.4 - Roku's Localization Team will handle the creation of all Latin Spanish subtitles and Audio descriptions. -- 5.2.1 - New run times for Ad Length and Marquee Ad Video (MAV). -- 5.2.2 - DeWolfe Music is RBS's music provider. -- 5.3.2 - Clarification on cut deadlines and reviews prior to distribution to the Client. -- 5.4.1 - Specific technical specifications for Marquee Ad Video (MAV) (if applicable). -- 7.5 - For a Custom Series, please discuss with Roku Brand Studio if the partner must create key art. -- 7.6.4 - Textless delivery requirements updated. -- 7.7.2 - Workflow update for all “Stitched Branded Content”, using Visual Data Media Services (VDMS). -- 7.10.1 - Link to current metadata templates and guidelines added. -- 7.10.9 - 'Not Applicable' Form added. -- 8.1 - Archival Graphic Elements should also include MOV files with an alpha channel. -- 8.1.1 - Dailies and all production assets should be kept for a minimum of 30 days before deleting. diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-live-event-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-live-event-specs.md deleted file mode 100644 index 44fbdb29..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-live-event-specs.md +++ /dev/null @@ -1,476 +0,0 @@ ---- -title: Live event VOD delivery specifications -excerpt: '' -deprecated: false -hidden: true -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -_Version 2.0 - September 2023_ - -## 1. General overview - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Originals Post Production Delivery Specifications outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -The specifications below encompass deliverables for Roku Originals Post Production, as they relate to VOD delivery of Live Events/Series. It is not comprehensive of all deliverables that may be required as part of your agreement. Please continue to utilize the [The Roku Channel Ingest Specifications](https://go.roku.com/rokuchannel-ingest-vod) document for all other areas noted below: - -* Ad Policy -* Kids Directed Content Policy -* External Branding and Calls to Action -* Artwork and Marketing Deliverables -* File Delivery Setup - -## 2. Post kick-off - -Post Producer resumes should be sent to Roku for prior approval. One week prior to Production start, please reach out to Roku Post Production to set up a kick-off call. In prep for this call, please review this full specification document so that we can address any follow up questions you may have. - -### 2.1 Startup documents - -Additionally, please make sure to send the preliminary versions of all documents noted below to Roku Post Production prior to the first day of Production. Available templates have been provided in the Post Kickoff zip file. - -1. Post Production Contact List -2. Preliminary Vendor List - -#### 2.1.1 Episode numbering - -* **Production Number**: 3-digit number that reflects season number and sequencing of shot material (101, 102, etc.) - * One-off Specials should contain the prefix “SP” and begin with 100. (SP100, SP200, etc.). -* **Air Order**: 1-digit number that reflects the order in which each episode will air. - -### 2.2 Notifications workflow - -* Once in production, any changes to the post schedule/calendar must be communicated to Roku Post Production immediately (within 24 hours) -* **QC Delivery and Final Delivery dates cannot shift without written approval by Roku Post Production** - -### 2.3 Misc - -* Please be sure to include the full name of the show in the subject line of all email correspondence. -* Do not include the Roku name or logo on any documents (including contact sheets, call sheets, PR’s, casting notices etc.) without written permission from Roku Production. -* The Roku Contact sheet is for Studio use and should not be distributed widely - -### 2.4 Roku marketing - -Please reach out to the Roku Creative Studio ([dlrokuoriginalmarketingcreative@roku.com](mailto:dlrokuoriginalmarketingcreative@roku.com)) to determine what marketing deliverables will be required for your show. Marketing will be directly involved in the Main Title treatment creative process. - -### 2.5 Roku localization - -Roku’s Localization Team may handle the creation of foreign language subtitles and audio descriptions, dependent on the series. At the beginning of production, please reach out to Localization ([Localizationoperations@roku.com](mailto:Localizationoperations@roku.com)) to verify what deliverables will be required for your project. - -## 3. Production - -Each production will be required to submit a Dailies Memo prior to the commencement of principal photography. The memo should confirm camera(s) being utilized as well as the workflow for processing all captured video and audio. - -### 3.1 Capture specifications - -* Unless otherwise approved by Roku production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of HD (1920x1080) and an aspect ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. -* All material should be captured, transferred, and mastered in a progressive frame rate. Please do not apply any cross-conversions to content. -* Please do not apply in-camera upscaling or de-squeezing to any camera masters. If your desire is to work with cameras that do not natively capture in HD, please reach out to Roku Post Production to discuss workflow options. - -## 4. Deliverables - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and confirmed by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -### 4.1 Roku originals logo - -All content that will be branded as a Roku Original series will be required to add the Roku Originals logo to their end credits. The Roku Originals Logo should be placed last in the end credits. The Roku Originals end logo is available [HERE.](https://f.io/jr_v0Z3C) - -### 4.2 Filename specifications - -#### 4.2.1 Papers deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -* ShowTitle_PTID_DocumentName_aoDate - -Your PTID (Provider Title ID) will be found on the Hub in the name of your Show Deliverables Folder. If the document is a final document, it should be labeled with ‘Final’ instead of the date. - -* Example: TheBestRokuShow_SC00000_PostVendorList_FINAL - -*For any redeliveries of post deliverables, please include the date in addition to “FINAL” - -#### 4.2.2 Master video deliverables - -All master* video files should be labeled as follows: - -ShowCode_ProdNumber_AirOrder_Version_LangCode_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov - -Example: - -NION_101_AIR_1_TXTD_enUS_UHD_SDR_FN_2CH_23976p_20190701-v2.mov - -Production Number = As listed on Post Grids - -Air Order = Please list even if the Air Order is the same as the Production Number - -| **File Name Segment** | **File Name Abbreviation** | -| --------------------- | --------------------------------------------------------------------------------------------------- | -| Version | TXTD (Texted), TXLS (Textless), or PROXY | -| Language | enUS (American English) or esMX (Mexican Spanish) | -| Resolution | UHD or HD + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | 2CH (Interleaved) or 8CH (5.1 and Stereo) - **7.1 audio not permitted on any masters at this time** | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Revision Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of QC and track the latest version for delivery | - -*See 4.3.6 for Proxy file naming. - -#### 4.2.3 Master audio deliverables - -Audio materials should be named to include all appropriate information: - -ShowCode_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#_SampleRate_BitRate_TC_Channel.mov - -**Examples:** - -MAMA_102_v04_20220919_enUS_PM_Nearfield_2ch_48k_24b_23976.L.wav - -MAMA_102_v03_20220919_esMX_FXSTEM_6ch_48k_24b_23976.R.wav - -MAMA_102_v02_20220919_esMX_ME_Nearfield_6ch_48k_24b_23976.C.wav - -| **Material Type** | **Abbreviation** | -| --------------------------------------------- | --------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, FFFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | -| | | -| **Channel Type** | **Abbreviation** | -| Mono | Mono | -| Stereo | 2CH | -| 5.1 Surround | 6CH | -| 7.1 Surround | 8CH | -| Atmos | Atmos | -| | | -| **Track Assignment** | **Abbreviation** | -| Mono | N/A | -| Stereo | LT, RT | -| 5.1 Surround | L, R, C, LFE, LS, RS | - -### 4.3 VOD video deliverables - -All video masters should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher of the export settings mentioned in 8.4.3, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate that was captured (for example, if the camera captured ProRes 422, then final export should be ProRes 422 or equivalent). - -#### 4.3.1 VOD video formatting - -All files should be formatted to start at 00:00:00:00. - -Files should begin with program and end on the last frame of the Roku Originals logo end card. - -All video files **MUST NOT** contain any of the following: bars and tone, bumpers, segment recaps or previews, VITC time code, advertisements, slates, rating cards, FBI warning cards, placards, overlay branding, promotional bugs, informational bugs, watermarks, or website link callouts. - -If promotional bugs or watermarks are required by a 3rd party, Roku Content Legal should be notified. - -#### 4.3.2 VOD ad breaks - -Each project will be required to deliver the VOD video master follows: - -* All ads should be removed from the program. - -* Ad breaks should be formatted as one second of black (no text permitted). Fade outs/ins are permitted. - -The exact timecode of each ad break, in HH:MM:SS:FF format, will be required in both the Segment Rundown and Metadata deliverables. Both templates were provided in the Post Kickoff Deliverables Packet. Please reach out to Roku Post if you did not receive one. - -#### 4.3.3 VOD audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 2.3.4 for specifications based on delivery codec. - -The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all texted and textless masters. - -* If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered. -* Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export. - -Mixing Specifications: - -* Target - 24 LKFS +/- 2 (any average between -22 & -26). Based on ITU-R 1170-3 measurement. -* Audio should not peak above -2 dBfs (True Peak) - -#### 4.3.4 VOD texted video masters - -The formatting requested below is a subset of [The Roku Channel Ingest Specifications](https://go.roku.com/rokuchannel-ingest-vod). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Video CodecProRes
ContainerMOV
Profile422 HQ
Minimum Bitrate175 mbit/s or higher
Landscape aspect ratio16:9 (1.77:1) - (no black bars)
W1920 x H1080 (HD)
Pixel aspect ratioSquare pixels (1:1)
Scan typeProgressive scan type
Chroma Subsampling4:2:2
Color SpaceBT.709 Legal Video Range (16 to 940)
Bit depth10-bit or 12-bit
Constant Frame Rate23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p
Native frame rateNo 3:2 pulldown flags
Audio CodecPCM
Format1 Interleaved Track or 2 Mono Tracks
Track LayoutInterleaved: Track 1: Stereo, LT/RT
Mono: Track 1: Stereo LT, Track 2: Stereo RT
7.1 audio is not permitted on any masters at this time
Sample Rate/Bit Depth48000Hz/24-bit
Channel Mapping & Metadata TaggingSee 2.4.2 -Verify correct audio channel mapping and metadata tagging.
- -#### 4.3.5 Textless delivery - -Textless Reels/Masters are a Roku Original-specific deliverable. They provide our Marketing team with clean assets to use in preparation for the VOD launch (where applicable). - -If your content includes burned-in on screen text, you will be required to deliver a separate Textless Reel or Full Episode. This reel should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Masters noted above. - -Audio mapping label verification as noted in 2.4.2 must be verified in textless master. - -Additionally, if foreign language subtitles cover 30% or more of a given episode, you will be required to deliver a fully textless version of that episode. - -#### 4.3.6 VOD final proxy files (clean & visible timecode) - -Proxy files are a Roku Original-specific deliverable. They are utilized by multiple internal teams both pre and post launch. - -From each Texted Master created, please export following proxy files: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Video CodecH.264
ContainerMOV or MP4
Picture(1) Clean & (1) w/Vis.TC UR
Bitrate5mbit/s (total file size \< 1gb to 2gb)
DimensionsW1920 x H1080 (HD)
Scan TypeProgressive scan type
Color SpaceBT.709 Legal Video Range
Bit Depth10-bit or 12-bit
Constant Frame RateShould Match Master
Native Frame RateShould Match Master
AudioCh.1 Stereo Left, Ch.2 Stereo Right
FilenameShowCode\_ProdNumber\_AirOrder\_Language\_Proxy\_HD\_ FN(if applicable)\_Audio\_Timecode(Clean or VisTC)*RevisionDate-v#*(Final or Pre-QC).mov

THAM\_101\_AIR\_1\_PROXY\_enUS\_HD\_FN\_2CH\_CLEAN\_20200916\_V4\_FINAL.mov
- -### 4.4 VOD audio delivery - -Audio stems are a Roku Original-specific deliverable. Full audio stem delivery may not be required for each series. Please reach out to Roku Post Production to determine if your series will be required to delivery these materials. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. - -#### 4.4.1 Domestic episode stems - -Provided below are the stems Roku would like to receive, if available (and applicable): - -* Mono Dialogue, Music, and SFX stems -* Stereo Printmasters -* Stereo Music & Effects -* Stereo Music -* Stereo Dialogue -* Stereo Sound Effects - -All audio should be archived as 24-bit, 48kHz WAV files. If Final Mix was 7.1, stems should be delivered as 7.1 as well. However, stem and master delivery to Roku must be in 5.1 and/or Stereo ONLY. - -Please see section 4.2.3 for full guidelines on labeling audio files. - -ShowCode_ProdNumber_Vers_LangCode_MaterialType_Channel#_SampleRate_BitRate_TC_Channel.mov - -**Examples:** - -MAMA_102_v04_enUS_PM_Nearfield_2ch_48k_24b_23976.L.wav - -_Roku Best Practices_ - -* Roku requires that all music be cleared for both domestic and international use across all media on all devices. - -### 4.5 VOD timed text file delivery - -Roku Originals Live Event content should be delivered in each of the following timed-text formats in order to support the hearing impaired: - -* Subtitles: Language solely (no inclusion of sound descriptors) - * Foreign subtitle files should also include any translated forced narratives that are currently burned into picture in English - -* SDH: Language in addition to sound descriptors (no forced narratives) - -All timed-text files should be formatted to match the final VOD Video Master, not the live broadcast master. The files must have the same timecode and frame rate as the video and audio delivered. - -Roku requires closed captions and subtitles in **SRT** formats. Character encoding MUST be UTF-8. - -**Languages & Formats Required:** - -English (American, Code: enUS): Subtitles, SDH, & FN - -Spanish* (Neutral Latin American Spanish, Code: esMX): Subtitles (no SDH or FN necessary) - -*If applicable, and dependent on Roku’s distribution rights - -**All files should be labeled as follows:** - -ShowCode-ProdNumber-LanguageCode_Format-RevisionDate - -**Filename Examples:** - -NION-101-esMX_SUB-20190701 - -NION-101-enUS_SDH-20190701 - -NION-101-enUS_FN-20190701 - -### 4.6 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Post Manager. - -#### 4.6.1 Roku metadata ingest template - -Metadata allows Roku to ingest and display all series related information for our customers. Marketing and/or the Roku Content Executive may tweak the information to ensure it’s as effective as possible on the Roku platform. - -The required details will include, but are not limited to, the following: - -* Show - Title, Description, Primary Spoken Language, Production Companies -* Season - Title, Description (leave blank if not applicable) -* Episode - Title, Production Number, Air Order, Total Run Time (TRT) - -Please note that air order and episode titles must be a decision made with your Content Executive. The episode titles must be creatively driven (e.g. not “Episode 1”) and should be written with the show writers or receive writer approval. Episode Titles should be locked after Rough Cut 1s. - -Please ensure you have the most up to date template for Metadata which can be found here within the [Roku Ingest Specs site](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates). - -#### 4.6.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. PNG files relating to the Title Logo and any other logos submitted should be uploaded to [Frame.io](http://frame.io/). -2. Traditional Episodic Credits Lists that detail the specific credits tied to each episode should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -#### 4.6.3 Segment rundowns - -You will be required to deliver a detailed breakdown of the timecodes pertaining to all segments in each episode. Please utilize the Roku Segment Rundown Template provided in your Kick-Off Delivery Packet. - -Roku requires that the timecodes within this document be delivered in HH:MM:SS:FF format. Any spreadsheets submitted without this formatting will not be accepted by Roku.  - -#### 4.6.4 As broadcast scripts - -Please deliver one set of As Broadcast Scripts for each series to the Hub. ABS files should reflect all changes made during the live broadcast, but do not need to be created by an outside vendor. - -#### 4.6.5 Final font memo - -Please deliver one document that details the font name and size utilized for opening credits, identifiers and/or other on-screen text added to each episode (where applicable) to the Hub. If applicable, please also note which vendor created the show logo. - -#### 4.6.6 Episodic delivery checklist - -Please deliver the final version of the Roku Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. All of the following must be completed: - -* All applicable file version dates and delivery locations for each asset -* Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -* If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 4.6.7 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the ASCAP website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Grossberg at [sgrossberg@roku.com](mailto:sgrossberg@roku.com). - -## 5. Archival - -Archival delivery is not required for all Live Event content. Please reach out to Roku Post Production to determine if your series will be required to deliver these materials. - -### 5.1 High resolution masters & source material - -Any and all series that are wholly owned by Roku will require delivery of archival media (where applicable) via LTO7 or greater. LTOs should be formatted LTFs and include a digital manifest for each tape. - -When adding assets to [Frame.io](http://frame.io/) folders, do not create additional sub-folders for episodes. Keep all media (proxies, texted/textless masters) only in the specified folder. - -The following are required deliverables that must be uploaded to the Final Archive folder on [frame.io](http://frame.io/): - -Required: - -* Final Texted Masters -* Final Textless Masters/Reels -* Final Audio Stems -* Graphic Elements – Main title card, credit PNGs, end credit PNGs, on-screen graphics, interstitials, etc. \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-scripted-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-scripted-specs.md deleted file mode 100644 index fb84dde2..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-scripted-specs.md +++ /dev/null @@ -1,997 +0,0 @@ ---- -title: Scripted media delivery specifications -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices. - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Post Production Delivery Specifications outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -## 2. Post kick-off - -Post Producer resumes should be sent to Roku for prior approval. One week prior to Production start, please reach out to Roku Post Production to set up a kick-off call. In prep for this call, please review this full specification document so that we can address any follow up questions you may have. - -### 2.1 Startup documents - -Additionally, please make sure to send the preliminary versions of all documents noted below to Roku Post Production prior to the first day of Production. Available templates have been provided in the Post Kickoff zip file. - -1. Post Grid (Please send in excel format, not PDF) -2. Post Production Contact List -3. Preliminary Vendor List -4. Dailies Memo - -#### 2.1.1 Episode numbering & post grid workflow - -Post Grids accuracy must be confirmed weekly, either via revised grid or an email reflecting that no changes have been made. For distribution, Roku requires these grids to be both uploaded to The Hub and emailed to a distribution list that Roku Post Production will provide prior to Production. - -Please note that the Post Grid template provides columns for multiple types of series, as noted below. If a specific column does not apply to your show, you can disregard it. - -- **Production Number:** 3-digit number that reflects season number and sequencing of shot material (101, 102, etc.) - - One-off Specials should contain the prefix “SP” and begin with 100. (SP100, SP200, etc.) - -- **Air Order:** 1-digit number that reflects the order in which each episode will air - -### 2.2 Notifications workflow - -- Once in production, any changes to the post schedule/calendar must be communicated to Roku Post Production immediately (within 24 hours) -- **Quality Control Delivery and Final Delivery dates cannot shift without written approval by Roku Post Production** -- At the below milestones please set a call with the Roku Post Production Manager at the email address provided on the contact sheet: - - 1 week prior to Production - - 1 week prior to the first scheduled rough cut release date - - Within one week of production wrap - -### 2.3 Misc. - -- Please be sure to include the full name of the show in the subject line of all email correspondence -- Do not include the Roku name or logo on any documents (including contact sheets, call sheets, PR’s, casting notices etc.) without written permission from Roku Production -- The Roku Contact sheet is for Studio use and should not be distributed widely - -### 2.4 Roku marketing - -Marketing will be directly involved in the Main Title treatment creative process. - -### 2.5 Roku localization - -Roku’s Localization Team will handle the creation of Latin Spanish subtitles and Audio Descriptions (AD) files. - -## 3. Production - -### 3.1 Capture specifications - -- Content Type - - Scripted - - Unless otherwise approved by Roku Production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of UHD (3840x2160) and an Aspect Ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. - - Unscripted - - Unless otherwise approved by Roku Production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of HD (1920x1080) and an Aspect Ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. -- All material should be captured, transferred, and mastered in a progressive frame rate. Please do not apply any cross-conversions to content. -- Please do not apply in-camera upscaling or de-squeezing to any camera masters. If your desire is to work with cameras that do not natively capture in 4k, please reach out to Roku Post Production to discuss workflow options. -- Any material that is being shot or used for Visual Effects must match capture resolution. This resolution must remain consistent throughout the Visual Effects creation and final delivery process. - -### 3.2 Camera tests - -- Prior to principal photography, please plan to shoot camera tests and post to [Frame.io](http://frame.io/) (Rough Cut 1 folder) for Roku review. -- These do not need to contain talent, final lighting, or even audio. They will solely be utilized to confirm the efficacy of camera capture and dailies workflows. -- Camera test material can be a quick compilation of various shots and angles; it is not necessary to cut a full scene together. -- Roku Post Production will provide a distribution list for all camera test material. If you have not received it, please reach out to your Roku Post Manager. - -### 3.3 Dailies - -#### 3.3.1 Dailies distribution - -Dailies are requested for visibility and early Marketing preparation. Roku Post will provide a user list for Dailies prior to production. - -- Scripted projects: Allow for dailies across all days of production. - -Roku’s approved platform for dailies, rough cut release, and final archive is Frame.io. All content being sent for review by the Roku team will need to be shared via this platform. Frame.io’s platform is compatible with most commonly used codecs, so if you are working with a partner who utilizes a different review platform, this may not require an extra render (pending specifications for each). - -The Roku Post team will initiate onboarding prior to the first day of production. That will trigger a member of the Frame.io team to reach out to set up a training session with your team. Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content (with Roku’s approval). - -#### 3.3.2 Dailies formatting - -Dailies should be posted and organized according to their corresponding shoot day. For Productions who are cross-boarding, further organization per episode within the master folder is permitted but not required. - -Each take should be uploaded as one clip within the overall day’s dailies folder. Please ensure that the camera roll source and scene/take information is available for every clip uploaded, either via burn-in windows or file naming. Source camera timecode should be burned into picture. - -Once dailies have been uploaded to [Frame.io](http://frame.io/), please send a notification email to those reviewing Dailies, per the Distribution List provided by your Roku Originals Post Manager. Please include the following in each email: - -- In the subject line include the show title, episode # and dailies day -- In the body of the email the include the link from the address bar to the [Frame.io](http://frame.io/) dailies project - -#### 3.3.3 Dailies memo - -A Dailies Memo should be submitted to the Roku Production and Post Production teams for approval prior to the commencement of principal photography. This document should include the proposed dailies workflow process, from camera capture through dailies distribution. Please include at least the following information: - -CAPTURE - -- Camera(s) utilized - - For each camera model, please provide: - - Video Resolution - - Acquisition Codec - - Frame rate(s) - -- Audio sample rate and bit depth - -- Please confirm that video will be captured log/flat and that no LUT/color grade will be baked into the footage at capture - -OFFLOAD - -- Utility/Process used for offload -- Checksum Algorithm used - -DAILIES & EDIT PROXY PROCESS - -- Program utilized for creation -- Processing method & workflow utilized, including where in process LUT/color applied -- Edit Proxies codec & frame rate and Dailies codec & frame rate -- Raster/Resolution - -### 3.4 Sizzle - -#### 3.4.1 Sizzle overview - -Roku may request your team create a 30-45 second sizzle for your project to be used for business-to-business purposes. - -Please note that the sizzle does not require formal finishing, i.e. final assembly, conform, color, or mix. As it is for B2B use, it does not require clearances or music licensing. - -Process: - -- Your Roku Production Executive will inform you if a sizzle is needed for your project. -- Please include sizzle milestones in overall calendar deliverable once due date has been provided by your Roku Post Manager. -- Please account for 2 rounds of notes from Roku Creative. -- Please reach out to your Roku Post Manager for the delivery date. - -Sizzle should include: - -- 2 cards for a minimum of 2 seconds each: - - Roku Presents - - A Roku Original Series -- Temp Main Title treatment -- Clips that represent the story and showcase talent involved -- Sizzle does not need to include full scenes. - -Please reach out to your Roku Post Manager if you would like to see an example of a previous sizzle. - -#### 3.4.2 Sizzle deliverables - -An HD primary video deliverable is required as follows: - -- Please do not include any head/tail formatting or slate. -- Program should start at 00:00:00:00. -- File Specs: - - (1) H.264 - - 1920 x 1080 - - 23.98 (or native framerate of Production, if different) - - Temp Stereo Mix -- Delivery Destination: Frame.io (Final Archive > Sizzle) - -## 4. Security - -Security is of the utmost importance to Roku. As such, access to all of the exciting content we are creating together must be limited. Please review Roku’s security requirements noted below and reach out to Roku Post Production with any questions. - -### 4.1 Review platform - -Roku’s approved platform for content sharing and final archive is [Frame.io](http://frame.io/). Roku and [Frame.io](http://frame.io/) have developed a content review workflow that both ensures security and limits access to all pre-launched content. In this workflow, anyone viewing Roku content will be required to set up a user account within [Frame.io](http://frame.io/) so that their activity can be tracked. **No material should be shared on any other platform without written approval from Roku.** - -### 4.2 Download access - -**It is not permitted for anyone to have direct, clean download access to any Roku content without written approval from Roku.** - -For team members who require reference QuickTimes in order to complete their work efficiently (i.e., Composers, Music Editors, Visual Effects Supervisors), please follow the steps below: - -- Submit a written request with the recipient’s name, email, and use case. Upon Roku approval: - - Each file must be watermarked with the recipient’s full name and located in the center of picture. - - Recipients should never be given access to an entire folder’s worth of content; Review links that contain solely the required assets should be sent to the Roku approved recipients. This link must be manually expired as soon as the file has been successfully downloaded. - - Files should always be housed on a vendor’s secure Storage Area Network. Files are never permitted to be stored on anyone’s personal device. - - It is the responsibility of each show's Post team to request vendor deletion of these files at show wrap. - -### 4.3 Content review - -It is never permitted to share rough cuts via Public Links. Review Links require user login and are the only approved method for content review. - -[Frame.io](http://frame.io/)’s Roku Partner Playbook is shared with the Post team at the start of each project. This workflow must be followed for both cuts released to Roku and also cuts released prior (Editor, Director, Producers, etc.). If you have not received this document, please reach out to Roku Post Production. - -All guidelines below must be followed when sharing review links: - -- It is never permitted to share rough cuts via Public Links. Review Links require user login and are the only approved method for content review. -- It is not permitted for any rough cut viewing links to be download-enabled. -- All viewing links must include an expiration date that confines access to seven days or less. -- **_\*All cuts uploaded for review must be watermarked.\*_** - -### 4.4 Non-standard requests - -It is not permitted to send content to anyone who is not a [Frame.io](http://frame.io/) user without written approval from Roku. - -## 5. Rough cuts and viewables - -### 5.1 Post weekly sync - -Once you begin the rough-cut process, your Roku Post Manager will reach out to schedule a weekly call. The call will be an informal sync to determine how the rough cuts are progressing and help address any questions you may have. If you have made any changes to the Post Grid over the week prior, please send a revised version prior to this call. - -### 5.2 Rough cut formatting - -#### 5.2.1 General requirements - -Below are the basic parameters to keep in mind as you begin the rough cut process: - -- Total Run Times: - - Short Form - Each episode should be no longer than 15 minutes in total run time. Each episode’s content and length should be approved by the Roku Content team prior to lock. - - Half Hour - Each episode's run time should be between 22-24 minutes. - - For Hour Long shows - Each episode’s run time should be between 44-48 minutes. - - **_\*For All Locked Cuts\*_** - QT's must include a slug for the end credits so that the exact timing is locked to match the final master. -- Each episode of content should commence with a “cold open” prior to any logos, credits or title sequence in order to immediately engage the viewer. -- There may be discussions around pre-roll, mid-roll, or post-roll advertising cue points. Regardless, please deliver each episode as a seamless master. -- Roku requires rough versions of graphics starting at the RC1 stage, and near final graphics by the FC stage. See Section 5.6 for a full breakdown of Roku’s graphics milestones (if applicable). -- Blurring un-cleared video content requires Roku Creative approval beforehand. -- Temp ADR must be added to all in-progress cuts where applicable, including all add-lines and alts. - -#### 5.2.2 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -#### 5.2.3 Ad breaks - -All Roku Originals series are required to include ad breaks. Please refer to the parameters below based off your episode run times. - -- Short Form episodes with a total run time of 11-15 minutes will be required to include 1 ad break in each episode. - - Short Form episodes with a total run time of less than 11 minutes will not need to include any act breaks - - The first ad break should not appear until at least 6 minutes of content have elapsed -- Each half-hour episode of content, with a total run time of 22-24 minutes, will be required to include 3 total ad breaks in each episode -- Each hour-long episode of content, with a total run time of 44-48 minutes, will be required to include 4 total ad breaks in each episode -- Formatting across all run times: - - **The ad breaks should not appear until at least 5 minutes of content have elapsed.** - - Ad breaks should be formatted as 1 second of black (no text permitted). Fade outs/ins are permitted. - - The final ad break must appear before the last 3 minutes of an episode, which will remain ad-free. - - All ad breaks should be spaced anywhere from 6 to 10 minutes apart, dependent on the creative. - -**All best efforts should be made to abide by the parameters noted above. Creatively, if a rough cut cannot meet these requirements, you will need to flag the variations within the rough cut release email to Roku.** - -If an episode will not meet the maximum run time, and this has been previously approved by Roku’s Content team, please reach out to Roku Post Production to discuss ad break implications. - -The exact timecode of the ad break, in (HH:MM:SS:FF) format, will be required in both the Segment Rundown and Metadata deliverables. Both templates were provided in the Post Kickoff Deliverables Packet. Please reach out to Roku Post if you did not receive one. - -#### 5.2.4 Rating guidelines - -Roku Originals content must fall within a TV-14 or TV-PG rating. Some general ratings guidance has been provided below for you to keep in mind as the creative story progresses in editorial. Please note, however, this is a very subjective process and the rating tiers below are regularly reviewed and may be modified in response to shifts in industry standards. So please be sure to reach out to your Roku Legal contact if you have any questions or clarifications. - -**Rating Tiers** - -| | VIOLENCE | SEX/NUDITY | SUBSTANCE USE/ABUSE | LANGUAGE | -| :-------- | :----------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------: | -| **TV-PG** | **✔** Shootings, brawls, fist fights
**✖** No blood | **✔** Limited to kissing, couples in bed, implied sexual situations
**✖** No nudity at all
**✖** No sexual violence | **✔** Implied drug use (not glorified or must show consequences) | **✔** Limited use of bleeping/dropping strong language. Ass, damn, hell, and bitch | -| **TV-14** | **✔** Brief violence, OK with some blood shown
**✕** No gore | **✔** Covered sex is allowed, brief thrusting, implied sexual abuse OK
**✔** Exposed butt/side breast OK
**✖** No full nudity | **✔** Visuals/use of drug abuse (not glorified, must show consequences)
**✖** No smoking minors | **✔** Shit, asshole, bastard (when used in a pejorative matter), goddamn, bitch, dick and pussy (as an insult) | -| **TV-MA** | **✔** On-screen graphic violence, gore | **✔** Depictions of graphic sexual activity or sexual violence
**✔** Full male or female nudity | **✔** Graphic visuals of substance use/abuse, injection, etc. (both. minors and adults)
**✖** No smoking minors | **✔** Use of fuck, tits, twat, cum, pussy, and cunt
**✖** Racial slurs and hate speech on a case-by-case basis | - -### 5.3 Rough cut review - -#### 5.3.1 Review platform - -Roku’s approved platform for dailies and rough cut release is [Frame.io](http://frame.io/). All content being sent for review by the Roku team will need to be shared via this platform. If you are working with a partner who utilizes a different internal platform, there will not be a need to render out separate files just for use with [Frame.io](http://frame.io/); [Frame.io](http://frame.io/)’s platform is compatible with most commonly used codecs, which allows the same file to be uploaded to both platforms. - -Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content within their own workspace (with Roku’s approval). Roku Post will handle user management for their space, which contains ‘Shared’ projects that are access by both partner and Roku teams . For any questions about this process, please reach out to your Post Manager. - -#### 5.3.2 Review process & turnaround timing - -For each episode, Roku will provide notes within 48 business hours after receipt, whether the Production Company is based in the United States or outside the United States. Cuts received by Roku after 6:00 pm PST will be deemed received the following business day. When sending cuts earlier than the scheduled release date, please note that the original notes return timing will need to be honored unless otherwise approved by Roku Creative. - -Locked cuts are approved if no notes have been sent after 48 hours. - -Rounds of Review: - -- RC → FC → LC - -Please follow turnaround timing parameters below when addressing notes from the Roku Content Team: - -- Eps. 1-3 cuts must be turnaround within 5 business days of receiving notes from Roku -- Eps. 4+ cuts must all be turned around within 3 business days of receiving notes from Roku - -Up to 2 half-hour episodes (or 1 hour-long episode) can be sent within a 48-hour period. No more than 3 10-minute episodes, per show, should be sent within a 48-hour period. - -For series with one or more story arcs, episodes should be sent for review in the order they will ultimately air on the Roku platform. For anthology series, or series consisting of stand-alone/self-contained episodes, rough cuts may be sent out of air order, if necessary. - -Check with your Content Executive regarding single vs. batch delivery of cuts. - -For any variations to the schedule above, please check with your Post Production or Content executive for review and approval prior to the release of the first rough cut. - -### 5.4 Technical specifications for rough cuts and viewables - -Formatting: - -- Slate before the hour - Please include show title, episode number, cut version (RC1, FC, etc.), total run time and release date -- Hour 01 onward should be solely program material, inclusive of production logo card at tail as las frame of picture - -Video Specifications: - -- Dimensions: 1920 x 1080 -- Codec: h264 (preferred) or MPEG -- Frame Rate: Keep it native to your project (24, 23.976, 25, etc.) -- Bitrate Encoding: Variable Bit Rate, 2 pass -- Target Bitrate: \~ 10mbps -- Aspect: Square Pixels (1.0) -- Visible Timecode Upper Right -- Please mark ad breaks in white text over one sec of black as either “Ad Break #” or incoming act number, i.e. “Act 2”. - -Audio Specifications: - -- Audio Codec: AAC -- Sample Rate: 48000 Hz -- Channels: Stereo - -Graphics: - -- Remember to adhere to Broadcast Title Safe Zones when adding any burned-in graphics or text. - -### 5.5 Rough & locked cut delivery - -Roku Production will provide a recipient list for all rough cuts prior to the scheduled release of the first episode. The [Frame.io](http://frame.io/) team will walk each project through Roku’s preferred rough cut release workflow, which involves: - -1. An email to the entire distribution list, noting the availability of cuts and when notes are due back. - - This email should include a Segment Rundown that relates to the timing of each specific cut being sent. -2. A notification from [Frame.io](http://frame.io/), which happens automatically after a cut is copied to the Shared Folder on [Frame.io](http://frame.io/). - -For each locked cut, you will be required to deliver the following elements via [Frame.io](http://frame.io/): - -- Locked Cut QuickTime -- Locked Cut EDL -- Locked Cut WAV Files: Mono Dialogue, Mono Music, and Mono Effects - -Cut filenames must follow the proper naming convention below: - -- Show Code (4-digits; Provided by Roku Post) -- Production number (3-digits: 101, 102, 103, etc.) -- Air Sequence (If available; 1-digit: 1, 2, 3, etc.) -- Cut version (RC1, FC, etc.) -- Date the cut was released to Roku (YYYYMMDD) - -Example: FLIP_102_AIR_2_FC_20260513 - -All rough cut links should be confined to viewing only (i.e. no download access). When sharing cuts, please do not create any folders, or copy any folders into the Roku Review projects. - -### 5.6 Graphics milestones & review process - -For Scripted and Alternative features, the Roku Content & Post Production teams should be involved in key discussions related to graphics, from title treatments to overall episodic graphics packages. - -All graphics work (title treatment, lower thirds, interstitials, etc.) must be completed by a Roku approved graphics company. The use of freelance staff or in-house graphics teams is not permitted. Please reach out to Roku Post to obtain the list of approved vendors. - -The following milestones require Roku notification and review: - -- **Six Weeks Prior to 1st Rough Cut:** A minimum of three graphics vendor options must be sent to Roku for review and approval -- **Four Weeks Prior to 1st Rough Cut:** Due to Roku: Mood board, color palette, title sketches, font, etc. -- **Two Weeks Prior to 1st Rough Cut:** Due to Roku: First round of design and/or animation examples -- **One Week Prior to 1st Rough Cut:** Due to Roku: Second round of design and/or animation examples -- **1st Rough Cut Release** - - Temp graphics implemented into the cut that is distributed to Roku. - - All temp graphics must be based on creative input from Roku. Any changes from the agreed upon look of in-show graphics will need to be outlined in an email to the Roku Content team. -- **1st Fine Cut Release:** Final Graphics must be implemented into the cut that is distributed to Roku - -After Roku has approved all in-show graphics and the first cut is locked, no changes should be made without written approval from the Roku Content team. - -## 6. Final mastering & marketing - -### 6.1 Picture & audio mastering - -#### 6.1.1 Uncompressed masters - -Roku prefers to receive both the un-graded and graded high-resolution master sequences as part of final delivery for wholly-owned. These files should be exported in DPX or TIFF, at the highest bitrate possible (16-bit preferred). Please package DPX or TIFF image sequence folders into a single .zip file for delivery. - -If your vendor is unable to export these sequences, please reach out to Roku Post Production. - -#### 6.1.2 Harding testing - -Please alert Roku Post Production if any episodic content contains flashing/strobing lights or other image patterns that have the potential to trigger seizures in viewers with Photosensitive Epilepsy. In these instances, you will be required to run a Harding Test and provide the passing report to Roku Post Production as part of Final Delivery. - -Please refer to the [Ofcom ITC Guidelines](https://www.ofcom.org.uk/__data/assets/pdf_file/0021/16248/gn_flash.pdf) for further information. - -#### 6.1.3 HDR10 & dolby vision - -Currently, Roku Scripted projects are only required to complete an SDR (Rec709) grade. Please keep in mind your final deliverables will need to be in legal video range. - -Roku encourages that all series be graded utilizing the Dolby Vision workflow. Although a HDR deliverable is not yet a requirement for the Roku platform, grading in Dolby Vision will allow for the highest quality visual experience, as well as protect for future inclusion of HDR deliverables. - -For Productions whose budgets and schedules permit HDR10 or Dolby Vision grading, please reach out to Roku Post Production to determine the necessary workflow and related deliverables associated with either. - -#### 6.1.4 Sound mixing - -Roku requires that all Scripted series mix in 5.1 Surround, and then downmix to create Stereo deliverables as well. - -Roku Policy/Preference is for live, remote playback of the mix for Roku Creative and Roku Post Managers prior to conclusion of the mix. Please include provisions (remote view client/seat licensing, remote view capable stages, etc.) to accommodate when budgeting. - -#### 6.1.5 Promotional assets (images and trailers) - -As each production will differ with regards to promotional assets, please reach out to determine the specific asks for your show. - -## 7. Credits - -**The first draft of credits (opening title card + end credits) must be submitted to Roku Post for approval with delivery of the first Fine Cut.** - -### 7.1 Opening credits - -For opening credits, Roku will utilize traditional burned-in credits. Full requirements are noted below. Please reach out to Roku Post Production with any questions. - -#### 7.1.1 Disclaimer use - -If your show contains sensitive content, please reach out to your Roku Legal Executive to see if your episode requires a trigger warning prior to the cold open. - -**For any other opening cards or disclaimers, please reach out to Roku Post Production for approval.** - -#### 7.1.2 Main title card - -During the initial design phase of any title treatments please reach out to your Roku Creative Executives; Roku Production (production[@roku.com);](mailto:altprod@roku.com) Roku Marketing ([dlrokuoriginalmarketingcreative@roku.com](mailto:dlrokuoriginalmarketingcreative@roku.com)) and Roku Post: ([dlropost@roku.com](mailto:dlropost@roku.com)). - -Please follow the formatting requirements below: - -- The title card will display the show title/logo, burned into picture as part of each final video master -- The Production Company/Producer will have full creative control over how the title appears, subject to size requirements and provided that it is within the 16x9 title safe zones - - Duration of this card will be a maximum of 5 seconds -- Deliverables: Series Logo (Static File) - - Dimensions: - - Scripted: - - 1920x1080px Transparent PNG - - 3840x2160px Transparent PNG - - Documentary - - 1920x1080px - - UHD resolution may also be applicable pending show’s specs - - Project Files (where applicable): - - PSD with hi-res textured layers - - AI Vector File - - Original font file with license receipt (Adobe/Google font link, .tff or .otf - -#### 7.1.3 Opening credits - -Each project, whether scripted or documentary, is required to include (2) Roku presentation cards at the top of the program as follows: - -- ‘Roku Presents’, followed by a subsequent card reading ‘A Roku Original’ or ‘A Roku Original Series’ (Please confirm with Roku Post). -- Duration: Minimum of 2 seconds per card -- Please utilize the same font and style that is specific to each project -- Roku prefers these be integrated into the opening of each program, rather than added as separate cards - -Further opening credits specifications by project type: - -- Scripted: - - Credits may appear over picture at the top of each project, provided the following criteria are met: - - Full duration of these credits does not exceed 1:15 in length - - Up to 3 names per credit block - - Up to 12 total credits/credit blocks can be utilized - - Credits that are approved to be included within the show opening are outlined below: - - Up to 3 “Union” credits (i.e., “Created by,” “Written by,” and “Directed by”), as determined by the Production Company/Producer - - ‘Created By’ and ‘Written By’ credits can be swapped, but ‘Directed By’ must be the last credit - - Production Companies, Executive Producers, and Producers are permitted - - The size and style of type for these credits will be determined by the Production Company/Producer, provided that: - - Fonts have to be large enough to be legible - - Fonts used for names should be the same size - - The individuals who receive these credits, the order of credits, the size and style of type (subject to the restrictions noted below), and whether 1, 2, or 3 names appear in the credit block will all be determined by the Production Company/Producer and notified to Roku as part of the delivery process - -### 7.2 End credit sequence - -Roku content will utilize traditional burned-in credits. All end credits must be submitted to Roku Post Production for approval before each episode is locked - -- End Credits - - For half-hour shows, end credits can be no longer than 30 total seconds, inclusive of production company logos - - For hour-long shows, end credits can be no longer than 90 total seconds, inclusive of production company logos - - For short form shows, end credits can have up to 3 production company logos/credits, not inclusive of the Roku Originals logo - - The Roku Originals Logo should be placed last in the end credits - - **Please reach out directly to Roku Post for access to the most current Roku Original Logo at: [dlropost@roku.com](mailto:dlropost@roku.com)** - - The 2025 logo is available in UHD or HD (both at 23.98fps), and with either Stereo or 5.1 Audio - - End credits must be formatted as separate end cards, not a scroll - - Must be within 16x9 Title Safe - - Placing the show title logo or title card at the end of any episode is not permitted without prior approval from the Roku Content and Post Production teams - -- Production Company Logo Card / Studio Credits - Optional - - - Up to 3 production company or studio logos/credits can be included in the end credits, in addition to the mandatory Roku Originals end credit logo - - Separate end cards can have a maximum total length of 3 seconds each - - For shared cards, no more than 2 logos can be combined onto the same end card - - Animated logos/credits are permitted - - Logos can include audio provided there is no cost to Roku to license such audio - - Audio ring outs from the end of the episode are also acceptable - - **The end of the last logo card will signify your LFOP (last frame of picture)** - - No credits may appear after the end logo cards - -### 7.3 Other credit requirements - -- Production Company/Producer shall deliver a complete written statement of all credit obligations in a format to be decided by Roku -- Production Company/Producer shall ensure that all credits conform to applicable third-party requirements -- Roku will have approval over all credits in each program, including all credits accorded to third parties - -**Adherence to the credit requirements in this document will be part of Roku’s Quality Check. If any specifications are not met, the asset will be passed back to the Production Company/Producer to modify. Roku’s Content Operation team can advise on how to upload assets for Roku review.** - -## 8. Final delivery - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and approved by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -The Delivery Phase begins as soon as your episodes are ready for Quality Control, after visual effects, color, and mix are complete. The following timeline is required to ensure that all assets are received on time for Post, Marketing, and Operations: - -- Due 1 Week Before First Episode Delivered to Quality Control Vendor - - Let Roku Post know which vendor you’re proceeding with - - Metadata Ingest Document due to the Hub \[See 8.7.1] - -- Due With Delivery to Quality Control Vendor - - Texted Masters - - Textless Masters (if applicable) - - Text Spotting List - -### 8.1 Onboarding - -Roku uses an External Deliverables Hub (“Hub”) to receive specific production documents. This Hub will also provide information necessary for the naming of each document and file deliverable. If you have not heard from the Roku Post Production team prior to delivery, please reach out to be set up with access to the Hub. - -### 8.2 Quality control (QC) - -Each Production is responsible for covering the cost of and delivering 100% QC approved content. All masters noted below will be required to be submitted to QC **using one of Roku’s approved QC vendors:** - -- Texted Master -- Textless Master - -All required versions for each episode should be delivered to the Quality Control facility on the same day. This will ensure the Quality Control operator is able to verify that there is no variation between the texted/textless timings. - -Please be sure to build time into your delivery schedule to account for the Roku Quality Control process. Roku advises that you set aside 3 weeks for each episode to complete the Quality Control of all masters. Delivery will not be considered ‘Final’ unless all masters have received a passing report from one of Roku’s approved vendors. A list of these vendors will be provided in the Post Kickoff Packet. - -If an episode has passed Quality Control but a revision is necessary (incorrect titles, production card modification, etc.) you **must** reach out to Roku Post before any redelivery is made. Please send an email with a detailed and time coded breakdown of what fixes are being requested so that Roku can review and determine the impact it will have on each team and the show premiere itself. - -#### 8.2.1 Text spotting list (TSL) - -You will be required to deliver a Text Spotting List file for each episode when it is submitted for Quality Control. This list will help Quality Control vendors verify that creatively intended text is included in the final file. A Roku Text Spotting list template was provided in your Post Kickoff zip file. This single file should be updated as episodes are sent to Quality Control so that all information for the series is included in the same master spreadsheet. - -The Text Spotting List should contain any and all text that is burned into picture, and the corresponding timecodes for each. If an episode has no burned-in text, you will still be required to deliver this file, but will specify the lack of text by checking the box at the top of the template. - -### 8.3 Filename specifications - -#### 8.3.1 Paper deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -- ShowCode _ProdNumber_AirOrder_Version_LangCode_Date_FINAL -- Example: GABH _301_Air_1_PostVendorList_enUS_20250303_FINAL - -#### 8.3.2 Master video deliverables - -All master\* video files should be labeled as follows: - -ShowCode_ProdNumber_AirOrder_Version_LangCode_Resolution_ColorSpace_FN_Audio_FrameRate_Date-v#.mov - -Example: - -NION_101_AIR_1_TXTD_enUS_UHD_SDR_FN_2CH_23976p_20190701-v2.mov - -Production Number = As listed on Post Grids (MV100, MV200, etc.) - -Air Order = Please list even if the Air Order is the same as the Production Number - -| **File Name Segment** | **File Name Abbreviation** | -| --------------------- | ------------------------------------------------------------------------------------------------------- | -| Version | TXTD (Texted), TXLS (Textless), or PROXY | -| Language | enUS (American English) | -| Resolution | UHD (scripted) + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | 2CH (Interleaved) or 8CH (5.1 and Stereo) – 7.1 audio not permitted on any masters at this time | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Revision Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of Quality Control and track the latest version for delivery | - -\*See 8.4.5 for Proxy file naming. - -#### 8.3.3 Master audio deliverables - -Audio materials should be named to include all appropriate information: - -ShowCode_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -Examples: - -MAMA_102_v04_20220919_enUS_PM_Nearfield_2ch_48k_24b_23976_L.wav - -MAMA_102_v03_20220919_esMX_FXSTEM_6ch_48k_24b_23976_R.wav - -MAMA_102_v02_20220919_esMX_ME_Nearfield_6ch_48k_24b_23976_C.wav - -
- -| **Material Type** | **Abbreviation** | -| --------------------------------------------- | --------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, FFFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | - -
- -| **Channel Type** | **Abbreviation** | -| ---------------- | ---------------- | -| Mono | Mono | -| Stereo | 2CH | -| 5.1 Surround | 6CH | - -| **Track Assignment** | **Abbreviation** | -| -------------------- | -------------------- | -| Mono | N/A | -| Stereo | LT, RT | -| 5.1 Surround | L, R, C, LFE, LS, RS | - -### 8.4 Video deliverables - -All video should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher of the export settings mentioned in 8.4.3, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate chroma information that was captured (for example, if the camera captured ProRes 422, then final export should be ProRes 422 or equivalent instead of 4444 XQ). - -**_Roku Best Practices_** - -It is important to keep master sequences (VAM/CTM) and final deliverables in alignment with dailies capture specifications (i.e. free of any up-scaling, cross-conversions, or up-conversions). - -#### 8.4.1 Video formatting - -All files should be formatted to start at 00:00:00:00. - -Files should begin with the cold open and end on the last frame of the Roku Originals logo end card. - -All video files MUST NOT contain any of the following: bars and tone, bumpers, segment recaps or previews, Vertical Interval time code time code, advertisements, slates, rating cards, FBI warning cards, placards, overlay branding, promotional bugs, informational bugs, watermarks, or website link callouts. - -If promotional bugs or watermarks are required by a 3rd party, Roku Content Legal should be notified. - -#### 8.4.2 Audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 8.4.3 for specifications based on delivery codec. - -**The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all texted and textless masters.** - -- If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered. -- Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export. - -Mixing Specifications: - -- Target - 24 LKFS +/- 2 (any average between -22 & -26). Based on ITU-R 1170-3 measurement. -- Audio should not peak above -2 dBfs (True Peak) - -#### 8.4.3 Texted video masters - -| Video Codec | ProRes | -| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| Container | MOV | -| Profile | 4444XQ (4444 okay if exporting from Premiere)

Scripted : 4444 XQ (4444 Ok if exporting from Premiere) if source is 4:4:4; or 422 H | -| Minimum Bitrate | 50 mbit/s or higher | -| Landscape aspect ratio | 16:9 (1.77:1) - (no black bars)
Scripted Series: W3840 x H2160 (UHD) | -| Pixel aspect ratio | Square pixels (1:1) | -| Scan type | Progressive scan type | -| Chroma Subsampling | 4:4:4 or 4.2.2 | -| Color Space | BT.709 Legal Video Range (64 to 940) | -| Bit depth | 10-bit or 12-bit | -| Constant Frame Rate | 23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p | -| Native frame rate | No 3:2 pulldown flags | - -| Audio Codec | PCM | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Format | 2 Interleaved Tracks or 8 Mono Tracks | -| Track Layout | Interleaved: Track 1: 5.1, L-R-C-LFE-Ls-Rs Track 2: Stereo, LT/RT
Mono: 5.1, L, R, C, LFE, Ls, Rs, Stereo LT, Stereo RT
**7.1 audio is not permitted on any masters at this time** | -| Sample Rate/Bit Depth | 48000Hz/24-bit | -| Channel Mapping & Metadata Tagging | See 8.4.2 -Verify correct audio channel mapping and metadata tagging. | - -#### 8.4.4 Textless delivery - -If your content includes burned-in on screen text, you will be required to deliver a separate Textless Reel or Full Episode. This reel should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Masters noted above. - -Audio mapping label verification as noted in 8.4.2 must be verified in textless master. - -Additionally, if foreign language subtitles cover 30% or more of a given episode, you will be required to deliver a fully textless version of that episode. All episodes should be delivered with the same formatting; if one episode requires a textless master, versus a reel, then all remaining episodes should also be delivered as textless masters. - -Examples of what to remove for the Textless Masters: - -| **Forced Narratives** | **Credits** | **Text-Based Graphics** | -| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -| ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-1.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-2.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-3.jpeg) | - -
- -_Roku Best Practices_ - -- Background elements with text, such as street signs, do not need to be included in the Textless Reel. -- ‘Forced Narratives’ refers to on-screen text that is used in one of two ways: to translate foreign dialogue into English or to clarify dialogue that may be inaudible. - -#### 8.4.5 Final proxy files (clean & visible timecode) - -From each Texted Master created, please export following proxy files: - -| **Video Codec** | **H.264** | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Container | MOV or MP4 | -| Picture | (1) Clean & (1) w/ Vis.TC UR (1) Series Opener Only | -| Bitrate | 5mbit/s (total file size \< 1gb to 2gb) | -| Dimensions | W1920 x H1080 (HD) | -| Scan Type | Progressive scan type | -| Color Space | BT.709 Legal Video Range | -| Bit Depth | 10-bit or 12-bit | -| Constant Frame Rate | Should Match Master | -| Native Frame Rate | Should Match Master | -| Audio | Ch.1 Stereo Left, Ch.2 Stereo Right | -| Filename | ShowCode_ProdNumber_AirOrder_Language_Proxy_HD_ FN(if applicable)\_Audio_Timecode(Clean or VisTC)\_RevisionDate-v#\_(Final or Pre-QC).mov
THAM_101_AIR_1_PROXY_enUS_HD_FN_2CH_CLEAN_20200916_V4_FINAL.mov | - -### 8.5 Audio delivery - -Prior to the commencement of principal photography, please reach out to Roku Post Production in order to determine the necessary audio deliverables for your series. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. Please upload to your Archive folder on [Frame.io](http://frame.io/). - -#### 8.5.1 Domestic episodic stems - -Provided below are the stems required for delivery of each episode/project: - -- Mono Dialogue, Music, and Sound Effects stems -- Stereo & 5.1 Printmasters -- Stereo & 5.1 M\&E - Fully Filled -- Stereo & 5.1 Music -- Stereo & 5.1 Dialogue -- Stereo & 5.1 Sound Effects -- Pro Tools Session Files (.ptx) - -Provided below are the stems Roku would like to receive, if available (and applicable): - -- Stereo & 5.1 Mix minus narration -- Score or Original Composition (pending rights) -- Mono M\&E Stems - Opticals, Backgrounds, etc. - -All audio should be archived as 24-bit, 48kHz WAV files. - -Please see section 8.3.3 for full guidelines on labeling audio files. - -ShowCode_ProdNumber_Vers_Date_LangCode_MaterialType_Channel#\_SampleRate_BitRate_TC_Channel.wav - -**Examples:** - -MAMA_102_v04_20220919_enUS_PM_Nearfield_2ch_48k_24b_23976_LT.wav - -_Roku Best Practices_ - -- Roku requires that all music be cleared for both domestic and international use across all media on all devices -- Optional tracks (foreign language, grunts, breathing, etc.) are preferred, if applicable -- If budget permits, please create Fully Filled FX stems as part of delivery - -### 8.6 Timed text file delivery - -Roku requires all content to be delivered with all of the following timed-text formats: - -- Subtitles: Language solely (no inclusion of sound descriptors) -- SDH: Language in addition to sound descriptors (no forced narratives) -- FN: Forced Narratives solely - -All files are required in an effort to support customers that are deaf or hard of hearing. - -Roku requires closed captions and subtitles in **2** formats: SRT and WebVTT. The files have to have the same timecode and frame rate as the video and audio delivered. Character encoding MUST be UTF-8. - -All timed text should be delivered to the show's archival folder on S3 via Aspera. - -**Languages & Formats Required:** - -English (American, Code: enUS): Subtitles, SDH, & FN - -**All files should be labeled as follows:** - -ShowCode-ProdNumber-LanguageCode_Format-RevisionDate.srt - -**Filename Examples:** - -NION-101-enUS_SDH-20190701 - -NION-101-enUS_FN-20190701 - -### 8.7 Breakdown of final locations for media deliverables - -| **Media** | **Final Location** | -| :---------------------------------------------- | :----------------- | -| TXTD Master | S3 | -| TXLS Master | S3 | -| Clean Proxy | Frame.io | -| Vis. TC Proxy | Frame.io | -| Sizzle Screener | Frame.io | -| Mono Audio Stems | S3 | -| Stereo & 5.1 Printmaster Stems | S3 | -| Stereo & 5.1 Stems (M\&E, Music, Dialogue, SFX) | S3 | -| Pro Tools Session Files (.ptx) | S3 | -| VAM Image Sequence (in .zip container) | S3 | -| CTM Image Sequence (in .zip container) | S3 | -| Timed Text Files (.srt and .vtt) | S3 | -| Paper Deliverables (Credits, Metadata, etc.) | The Hub | - -### 8.8 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Post Manager. - -#### 8.8.1 Roku metadata ingest template - -Metadata allows Roku to ingest and display all series related information for our customers. Marketing and/or the Roku Content Executive may tweak the information to ensure it’s as effective as possible on the Roku platform. - -Please find the most recent Roku metadata templates and guidelines [HERE](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates). - -The required details will include, but are not limited to, the following: - -- Show - Title, Description, Primary Spoken Language, Production Companies -- Season - Title, Description (leave blank if not applicable) -- Episode - Title, Production Number, Air Order, Total Run Time (TRT) -- Exact timecode of ad break insertion, in millisecond (HH:MM:SS:FF) format - -Please note that air order and episode titles must be a decision made with your Content Executive. The episode titles must be creatively driven (e.g. not “Episode 1”) and should be written with the show writers or receive writer approval. Episode Titles should be locked after Rough Cut 1s. - -#### 8.8.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. PNG files relating to the Title Logo and any other logos submitted should be uploaded to [Frame.io](http://frame.io/). -2. Roku Scripted Credit Approval Form - This document should include both main title and end credits for Business Affairs Approval. -3. Traditional Episodic Credits Lists that detail the specific credits tied to each episode should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -Short form shows may require an additional Credits template, so please reach out to Roku to determine if this is necessary. - -#### 8.8.3 Segment rundowns - -You will be required to deliver a detailed breakdown of the timecodes pertaining to all segments in each episode. Please utilize the Roku Segment Rundown Template provided in your Kick-Off Delivery Packet. - -Roku requires that the timecodes within this document be delivered in HH:MM:SS:FF format. Any spreadsheets submitted without this formatting will not be accepted by Roku. - -#### 8.8.4 As broadcast scripts - -Please deliver one set of As Broadcast Scripts for each series to the Hub. As Broadcast Script files should have a timecode-based breakdown of each line of dialogue. You are approved to submit the As Broadcast Script’s in any format that a Roku approved vendor utilizes. - -#### 8.8.5 Final font memo - -Please deliver one document that details the font name and size utilized for opening credits, identifiers and/or other on-screen text added to each episode (where applicable) to the Hub. If applicable, please also note which vendor created the show logo. - -#### 8.8.6 Final vendor list - -Please deliver your final version of the Roku Vendor List that you received in the Kick-Off Delivery Packet to the Hub. - -#### 8.8.7 Final text spotting list - -Please deliver the Text Spotting List that was used to Quality Control the final episodes to the Hub. Please ensure that any changes made during Quality Control are reflected in the final document that is delivered to Roku via The Hub. Please deliver a single excel file, via Roku’s template, with episodes separated onto their own tabs. - -#### 8.8.8 Episodic delivery checklist - -Please deliver the final version of the Roku Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. All of the following must be completed: - -- All applicable file version dates and delivery locations for each asset -- All Quality Control Start and End/Approval dates for Texted and Textless Masters -- Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -- If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 8.8.9 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the American Society of Composers, Authors and Publishers (ASCAP) website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. - -Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Vosper at [svosper@roku.com](mailto:sgrossberg@roku.com). - -#### 8.8.10 Not applicable form - -In cases where a paper deliverable is non-applicable to the project, please upload the Roku Not Applicable Form to the Hub with a written explanation of why this deliverable does not apply. - -## 9. Archival - -### 9.1 High resolution masters & source material - -Roku’s platform for archiving projects is to an AWS S3 bucket. This can be accessed via Aspera Shares. Note that this is separate from the Aspera Ingest upload. A Roku Post Manager will request email addresses and names of those who will be uploading archival assets to the designated archival show folder for credentialing. - -When adding video assets to S3 do not create additional sub-folders. Keep all media (proxies, texted/textless masters) only in the folders provided. Audio files should be grouped by episode (where applicable). - -The following are required deliverables that must be uploaded to the Final Archive folder on S3: - -Required: - -- Final Texted Masters -- Final Textless Masters -- Final Audio Stems -- Pro Tools Sessions -- Graphic Elements – Main title card, credit PNGs, end credit PNGs, on-screen graphics, interstitials, etc. -- Timed Text Files -- Locked Cuts - -Any and all series that are wholly owned by Roku will require delivery of VAMS, CTMS, and final Visual Effects shots (where applicable) via Aspera upload to S3, or, in some cases, LTO10 or greater. LTOs should be formatted LTFs and include a digital manifest for each tape. These manifests should be uploaded to The Hub. - -For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -- VAMs – Un-color-corrected, textless, DPX or TIFF format (\***_Compress\*_** to .ZIP or .TAR) - - Associated Avid bins or EDLs -- CTM – Color-corrected, textless, DPX or TIFF format (\***_Compress\*_** to .ZIP or .TAR) - - Associated Look-up Tables or color-grading files -- Final Visual Effects Shots – Un-color-corrected preferred (if applicable) - -#### 9.1.1 Dailies archival - -Any and all series that are wholly owned by Roku will require delivery of dailies/OCF via LTO10 or greater. LTOs should be formatted LTFs and include a manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -### 9.2 Offline editorial masters - -Please be sure that all consolidated avid media is archived and removed from [Frame.io](http://frame.io/) prior to wrap. Once each project’s wrap is complete, all media still contained within the [Frame.io](http://frame.io/) platform will be **deleted** and the series users will be disabled. - -## 10. Change log - -### V4.0 - -- 3.3.3 - Dailies Memo requirements updated. -- 3.4 - Sizzle requirements added for Roku’s main title presentation cards and deliverables. -- 3.4.1 - Sizzle TRT updated to 30-45 seconds -- 5.2.1 - Temp ADR required in all in-progress cuts. -- 6.1.1 - Uncompressed masters - packaging DPX and TIFF folders into one .zip file. -- 6.1.4 - Live, remote mix playback policy for Roku Creative and Post Production. -- 7.1.3 **-** Roku Presentation Card requirements added. -- 8.6 - Timed Text files will now be delivered to the AWS S3 Archival Bucket. -- 8.7 - Final destination chart for all deliverables. -- 9.1 - Final Archival Media will now be uploaded to AWS S3, rather than Frame.io and for LTO Archive please use LTO10. - -### V3.0 - -- 2.5 - Roku's Localization Team will handle the creation of all Latin Spanish subtitles and Audio Descriptions -- 5.2.3 - Ad breaks placement -- 7.1.2 - Presentation credit requirement added -- 7.2 - Roku Originals end card updated -- 8.3.1 - Paper deliverable labeling revised -- 8.4.4 - If one episode in a series requires a fully textless master delivery, now all episodes in that series will require a fully textless master -- 8.7.1 - Link to current metadata templates and guidelines added -- 8.7.10 - 'Not Applicable' Form added -- 9.1 - LTO9 is the newest version of the Linear Tape-Open and this is the version that should always be used - -### V2.1 - -- 5.2.4 – RO Content Rating Guidelines updated -- 8.7.1 - Roku Ingest Specs Link added for access most updated Metadata Template - -### V2.0 - -- Multiple Sections - 5.1 & Stereo Mix required. 7.1 mix no longer being requested. -- Multiple Sections - Timecodes of act breaks updated to HH:MM:SS:FF -- 5.5 - Locked Cut requirements updated -- 8.3.2 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX) -- 8.4.5 - Final Proxy file size changed to a maximum of 2gb -- 8.5.1 - Audio Deliverables updated -- 8.6 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX); Removed SCC file requirement -- 9.1 - Archival - Use of [Frame.io](http://frame.io/) Transfer App required for all uploads to the app - -(v1.9 intentionally skipped) - -### V1.8 - -- 2.4 – Roku Marketing Team’s involvement in Sizzle Reel and Main Title Treatment clarified -- 2.5 – Localization Introduction -- 3.1 – Approval needed for aspect ratios outside of 16:9; Visual Effects workflow must maintain capture resolution -- 5.3.2 – Cut Review & Turnaround Timing clarified -- 7.1.2 – Main Title Card requires review/approval by Roku Creative Execs, Marketing, Production & Post -- 7.2 – Roku Originals Logo must be placed last in end credits; download link provided -- 8.3.2 – Master Video Deliverables file naming modified -- 8.3.3 – Master Audio Deliverables file naming modified -- 8.4.2 – Audio Channel mapping and tagging of metadata must be verified -- 8.4.3 – Texted Video Masters audio track layout updated -- 8.4.4 – Audio mapping label verification as noted in 8.4.2 must be verified in Textless Master -- 8.5.1 – Revised audio labeling guidelines for stem delivery -- 9.1 – [Frame.io](http://frame.io/) & High Resolution Masters instructions revised - -### V1.7 - -- 3.3.2 – [Frame.io](http://frame.io/) dailies notification email -- 5.2.2 – Now states that the Segment Rundown deliverable must include milliseconds in its formatting. -- 5.4 – Revised file naming convention on rough cut deliveries. -- 8.2.1 – Text Spotting List updated -- 8.3 – File naming format for both paper and media deliverables modified. -- 8.4.5 – Additional proxy deliverable added. -- 8.6 – Replaced Latin American subs (LAS) with Mexican Spanish (esMX). -- 8.7 – Further clarification provided across paper deliverables. - -### V1.6 - -- 8.7.2 – Updated to include the “Cast & Crew“ file as a credits document deliverable. -- 9.1.1 – Dailies Archival section added. - -### V1.5 - -- 5.5 – Segment Rundowns will be required with delivery of each rough cut -- 8.5.2 – Audio Description files added as a new deliverable - -### V1.4 - -- 6.1.2 – Added Harding Test section for content with flashing/strobing lights and other image patterns -- 7.2 – End Production Logos may include audio provided there is no additional cost to Roku - -### V1.3 - -- 5.2.2 – Clarified that Ad Breaks should have no text -- 7.2 – Updated End Credits section with more detail -- 8.7.9 – Updated Music Cue Sheet information and point of contact for questions diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-spanish-specs.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-spanish-specs.md deleted file mode 100644 index 3f97ee45..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/post-spanish-specs.md +++ /dev/null @@ -1,992 +0,0 @@ ---- -title: Spanish language - alternative media delivery specifications -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices. - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Post Production Delivery Specifications outline the best practices for the Partner at this time. This document and the requirements are subject to change at Roku’s sole discretion. - -## 2. Post kick-off - -Post Producer resumes should be sent to Roku for prior approval. One week prior to Production start, please reach out to Roku Post Production to set up a kick-off call. In prep for this call, please review this full specification document so that we can address any follow up questions you may have. - -### 2.1 Startup documents - -Additionally, please make sure to send the preliminary versions of all documents noted below to Roku Post Production prior to the first day of Production. Available templates have been provided in the Post Kickoff zip file. - -1. Post Grid (Please send in excel format, not PDF) -2. Post Production Contact List -3. Preliminary Vendor List -4. Dailies Memo - -#### 2.1.1 Episode numbering & post grid workflow - -Post Grids accuracy must be confirmed weekly, either via revised grid or an email reflecting that no changes have been made. For distribution, Roku requires these grids to be both uploaded to The Hub and emailed to a distribution list that Roku Post Production will provide prior to Production. - -Please note that the Post Grid template provides columns for multiple types of series, as noted below. If a specific column does not apply to your show, you can disregard it. - -- **Production Number**: 3-digit number that reflects season number and sequencing of shot material (101, 102, etc.) - - One-off Specials should contain the prefix “SP” and begin with 100. (SP100, SP200, etc.). - -- **Air Order**: 1-digit number that reflects the order in which each episode will air. - -- **Story Number**: 1-digit number that relates to multiple episodes tied together by one story arc. - -### 2.2 Notifications workflow - -- Once in production, any changes to the post schedule/calendar must be communicated to Roku Post Production immediately (within 24 hours) -- **QC Delivery and Final Delivery dates cannot shift without written approval by Roku Post Production** -- At the below milestones please set a call with the Roku Post Production Manager at the email address provided on the contact sheet: - - 1 week prior to Production - - 1 week prior to the first scheduled rough cut release date - - Within one week of production wrap - -### 2.3 Misc. - -- Please be sure to include the full name of the show in the subject line of all email correspondence -- Do not include the Roku name or logo on any documents (including contact sheets, call sheets, PR’s, casting notices etc.) without written permission from Roku Production -- The Roku Contact sheet is for Studio use and should not be distributed widely - -### 2.4 Roku marketing - -Marketing will be directly involved in the Main Title treatment creative process. - -### 2.5 Roku localization - -Roku’s Localization Team will handle the creation of English subtitles and Audio Descriptions (AD) files. - -## 3. Production - -Each production will be required to submit a Dailies Memo prior to the commencement of principal photography. The memo should confirm camera(s) being utilized as well as the workflow for processing all captured video and audio. - -### 3.1 Capture specifications - -- Unless otherwise approved by Roku Production prior to the commencement of principal photography, you will be required to capture at a minimum resolution of HD (1920x1080) and an aspect ratio of 16:9 to match final deliverables specs. Any changes to the required resolution or aspect ratio must be approved by Roku. -- All material should be captured, transferred, and mastered in a progressive frame rate, 23.976 being preferred. Please do not apply any cross-conversions to content. -- Please do not apply in-camera upscaling or de-squeezing to any camera masters. If your desire is to work with cameras that do not natively capture in 4K, please reach out to Roku Post Production to discuss workflow options. - -### 3.2 Dailies selects - -- Roku only requires 5-10 minutes of dailies selects to be posted for each of the first three days of production. -- Selects must be uploaded during the first week of production unless b-roll capture is scheduled. If the latter is the case, reach out to your Roku Post Manager to strategize the timing for posting Selects. -- Please choose select takes that confirm production is proceeding as intended. It is not necessary to post all media from each day. -- Dailies should be posted to [Frame.io](http://frame.io/). Roku Post Production will provide a distribution list prior to the first day of dailies. - -### 3.3 Dailies memo - -A Dailies Memo should be submitted to both the Roku Production and Post Production teams for approval prior to the commencement of principal photography. This document should include the proposed dailies workflow process, from camera capture through dailies distribution. Please include at least the following information: - -CAPTURE - -- Camera(s) utilized - - For each camera model, please provide: - - Video Resolution - - Acquisition Codec - - Frame rate(s) -- Audio sample rate and bit depth -- Please confirm that video will be log/flat and that no LUT/color grade will be baked into the footage at capture - -OFFLOAD - -- Utility/Process used for offload -- Checksum Algorithm used - -DAILIES & EDIT PROXY PROCESS - -- Program utilized for creation -- Processing method & workflow utilized, including where in process LUT/color applied -- Edit Proxies Codec and Dailies Codec -- Raster/Resolution - -### 3.4 Sizzle - -Roku may request your team create a 30-45 second sizzle for your project to be used for business-to-business purposes. - -Please note that the sizzle does not require formal finishing, i.e. final assembly, conform, color, or mix. As it is for B2B use, it does not require clearances or music licensing. - -Process: - -- Please include sizzle milestones in overall calendar deliverable. -- Please account for 2 rounds of notes from Roku Creative, plus an approval review. -- Please reach out to your Roku Post Manager for the delivery date, as the sizzle might be required prior to the end of principal photography for some projects. - -Sizzle should include: - -- 2 cards for a minimum of 2 seconds each - - Roku Presents - - A Roku Original Series -- Temp Main Title treatment -- Clips that represent the story and showcase talent involved -- Sizzle does not need to include full scenes - -Technical Specs for Either Deliverable: - -- (1) H.264 -- No head or tail formatting -- 1920 x 1080 -- 23.98 (or native framerate of Production, if different) -- Temp Stereo Mix - -Please reach out to your Roku Post Manager if you would like to see an example of a previous sizzle. - -#### 3.4.2 Sizzle deliverables - -An HD primary video deliverable is required as follows: - -- Please do not include any head/tail formatting or slate. -- Program should start at 00:00:00:00. -- File Specs: - - (1) H.264 - - 1920 x 1080 - - 23.98 (or native framerate of Production, if different) - - Temp Stereo Mix -- Delivery Destination: Frame.io (Final Archive > Sizzle) - -## 4. Security - -Security is of the utmost importance to Roku. As such, access to all of the exciting content we are creating together must be limited. Please review Roku’s security requirements noted below and reach out to Roku Post Production with any questions. - -### 4.1 Review platform - -Roku’s approved platform for content sharing and final archive is [Frame.io](http://frame.io/). Roku and [Frame.io](http://frame.io/) have developed a content review workflow that both ensures security and limits access to all pre-launched content. In this workflow, anyone viewing Roku content will be required to set up a user account within [Frame.io](http://frame.io/) so that their activity can be tracked. - -**No material should be shared on any other platform without written approval from Roku.** - -### 4.2 Download access - -**It is not permitted for anyone to have direct, clean download access to any Roku content without written approval from Roku.** - -For team members who require reference quicktimes in order to complete their work efficiently (i.e., Composers, Music Editors, Visual Effects Supervisors), please follow the steps below: - -- Submit a written request with the recipient’s name, email, and use case. Upon Roku approval: - - Each file must be watermarked with the recipient’s full name and located in the center of picture. - - Recipients should never be given access to an entire folder’s worth of content; Review links that contain solely the required assets should be sent to the Roku approved recipients. This link must be manually expired as soon as the file has been successfully downloaded. - - Files should always be housed on a vendor’s secure SAN. Files are never permitted to be stored on anyone’s personal device. - - It is the responsibility of each show's Post team to request vendor deletion of these files at show wrap. - -### 4.3 Content review - -[Frame.io](http://frame.io/)’s Roku Partner Playbook is shared with the Post team at the start of each project. This workflow must be followed for both cuts released to Roku and also cuts released prior (Editor, Director, Producers, etc.). If you have not received this document, please reach out to Roku Post Production. - -All guidelines below must be followed when sharing review links - -- It is never permitted to share rough cuts via Public Links. Review Links require user login and are the only approved method for content review. -- It is not permitted for any rough cut viewing links to be download-enabled. -- All viewing links must include an expiration date that confines access to seven days or less. -- **All cuts uploaded for review must be watermarked.** - -### 4.4 Non-Standard requests - -It is not permitted to send content to anyone who is not a [Frame.io](http://frame.io/) user without written approval from Roku. - -## 5. Rough cuts - -### 5.1 Post weekly sync - -Once you begin the rough-cut process, your Roku Post Manager will reach out to schedule a weekly call. The call will be an informal sync to determine how the rough cuts are progressing and help address any questions you may have. If you have made any changes to the Post Grid over the week prior, please send a revised version prior to this call. - -### 5.2 Rough cut formatting - -#### 5.2.1 General requirements - -Below are the basic parameters to keep in mind as you begin the rough cut process: - -- Total Run Times: - - Short form - Each episode should be no longer than 15 minutes in total run time. Each episode’s content and length should be approved by the Roku Content team prior to lock. - - Run time for half-hour series should be between 22-24 minutes. - - Run time for hour-long series should be between 44-48 minutes. - - **For All Locked Cuts** - QT’s must include a slug for the end credits so that the exact timing is locked to match the final master. -- Roku requires a rough versions of graphics starting at the RC1 stage, and near final graphics by the FC stage. See Section 5.6 for a full breakdown of Roku’s graphics milestones. -- It is not permitted to send rough cuts longer than either formats maximum without prior approval from the Roku Content Team. -- Episodes should be cut, mastered, and delivered as separate episodes; not a long-play master. -- There may be discussions around pre-roll, mid-roll, or post-roll advertising cue points. Regardless, please deliver each episode as a seamless master. -- The use of blurs on un-cleared video content is not permitted without Roku Creative approval beforehand. - -#### 5.2.2 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -Wholly owned Roku Alternative projects have access to Universal Production Music (UPM) as a music provider. However, each project should confirm UPM availability with Roku Production prior to the commencement of Principal Photography. - -#### 5.2.3 Ad breaks - -All Roku Originals series are required to include ad breaks. Please refer to the parameters below based off your episode run times. - -- Short Form episodes with a total run time of 11-15 minutes will be required to include 1 total ad break into each episode. - - Short Form episodes with a total run time of less than 11 minutes will not need to include any act breaks. -- Episodes with a total run time of 22-24 minutes will be required to build 3 total ad breaks into each episode. -- Episodes with a total run time of 44-48 minutes will be required to build 5 total ad breaks into each episode. -- Formatting across all run times: - - **The ad breaks should not appear until at least 5 minutes of content have elapsed.** - - Ad breaks should be formatted as 1 second of black (no text permitted). Fade outs/ins are permitted. - - The last ad break must appear before the last 3 minutes of an episode, which will remain ad-free. - - All ad breaks should be spaced anywhere from 6 to 10 minutes apart, dependent on the creative. - -All Fine and Locked cuts sent to Roku must adhere to the specifications above. They will not be deemed acceptable otherwise. Please see Section 5.3.2 below for more detail on earlier cut releases. - -If an episode will not meet either run time range, and this has been previously approved by Roku’s Content team, please reach out to Roku Post Production to discuss ad break implications. - -The exact timecode of each ad break, in (HH:MM:SS:FF) format, will be required in both the Segment Rundown and Metadata deliverables. Both templates were provided in the Post Kickoff Deliverables Packet. Please reach out to Roku Post if you did not receive one. - -#### 5.2.4 Rating guidelines - -Roku Originals content must fall within a TV-PG or TV-14 rating. Some general ratings guidance has been provided below for you to keep in mind as the creative story progresses in editorial. Please note, however, this is a very subjective process and the rating tiers below are regularly reviewed and may be modified in response to shifts in industry standards. So please be sure to reach out to your Roku Legal contact if you have any questions or clarifications. - -**Rating Tiers** - -| | VIOLENCE | SEX/NUDITY | SUBSTANCE USE/ABUSE | LANGUAGE | -| :-------- | :----------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------: | -| **TV-PG** | **✔** Shootings, brawls, fist fights
**✖** No blood | **✔** Limited to kissing, couples in bed, implied sexual situations
**✖** No nudity at all
**✖** No sexual violence | **✔** Implied drug use (not glorified or must show consequences) | **✔** Limited use of bleeping/dropping strong language. Ass, damn, hell, and bitch | -| **TV-14** | **✔** Brief violence, OK with some blood shown
**✕** No gore | **✔** Covered sex is allowed, brief thrusting, implied sexual abuse OK
**✔** Exposed butt/side breast OK
**✖** No full nudity | **✔** Visuals/use of drug abuse (not glorified, must show consequences)
**✖** No smoking minors | **✔** Shit, asshole, bastard (when used in a pejorative matter), goddamn, bitch, dick and pussy (as an insult) | -| **TV-MA** | **✔** On-screen graphic violence, gore | **✔** Depictions of graphic sexual activity or sexual violence
**✔** Full male or female nudity | **✔** Graphic visuals of substance use/abuse, injection, etc. (both. minors and adults)
**✖** No smoking minors | **✔** Use of fuck, tits, twat, cum, pussy, and cunt
**✖** Racial slurs and hate speech on a case-by-case basis | - -### 5.3 Rough cut review - -#### 5.3.1 Review platform - -Roku’s approved platform for dailies, rough cut release, and final archive is [Frame.io](http://frame.io/). All content being sent for review by the Roku team will need to be shared via this platform. If you are working with a partner who utilizes a different internal platform, there will not be a need to render out separate files just for use with [Frame.io](http://frame.io/); [Frame.io](http://frame.io/)’s platform is compatible with most commonly used codecs, which allows the same file to be uploaded to both platforms. - -The Roku Post team will initiate onboarding prior to the first day of production. That will trigger a member of the [Frame.io](http://frame.io/) team to reach out to set up a training session with your team. Each series will only be granted one ‘Team Manager’, who will have the ability to add users and download content (with Roku’s approval). - -#### 5.3.2 Cut review & turnaround timing - -For each episode, Roku will provide notes within 48 business hours after receipt, whether the Production Company is based in the United States or outside the United States. Cuts received by Roku after 6:00 pm Pacific Standard Time will be deemed received the following business day. When sending cuts earlier than the scheduled release date, please note that the original notes return timing will need to be honored unless otherwise approved by Roku Creative. - -Locked cuts are approved if no notes have been sent after 48 hours. - -Rounds of Review: - -- 101-103\*: Rough Cut 1 → Rough Cut 2 → Fine Cut → Locked Cut -- 104+: Rough Cut 1 → Fine Cut → Locked Cut - -Review Order: - -- **Serialized Series:** Please prioritize RC1s over RC2s and FCs. - - Example - 101 RC1 → 102 RC1 → 103 RC1 → 101 RC2 -- **Formatted Series:** Please prioritize all cuts for 101 over subsequent episodes. - - Example - 101 RC1 → 101 RC2 → 101 FC → 102 RC1 - -\*If sending out of production order, please ensure the first three episodes sent to Roku receive Rough Cut 2’s. - -Please follow turnaround timing parameters below when sending cuts and addressing notes from Roku Creative: - -- Rough Cuts - - Eps. 1-2 Rough Cut 2’s must be turned around within 5 business days of receiving notes from Roku - - For half-hour shows: - - Any given Rough Cut 1 will be accepted at up to 5 minutes over the 24-minute max run time per episode - - Any given Rough Cut 2 will be accepted at up to 1 minute over the 24-minute max run time per episode - - For hour-long shows: - - Any given Rough Cut 1 will be accepted at up to 5 minutes over the 48-minute max run time per episode - - Any given Rough Cut 2 will be accepted at up to 1 minute over the 48-minute max run time per episode - - For short form shows: - - Any given Rough Cut 1 will be accepted at up to 5 minutes over the 15-minute max run time per episode - - Any given Rough Cut 2 will be accepted at up to 1 minute over the 15-minute max run time per episode -- Fine Cuts & Locked Cuts - - All Fine & Locked Cuts must be to delivered per Roku’s exact formatting specifications or they will be rejected. - - Eps. 1-2 Fine Cut, Locked Cut cuts must be turned around within 3 business days of receiving notes from Roku - - Eps. 3+ Fine Cut, Locked Cut cuts must be turned around within 3 business days of receiving notes from Roku - -Up to 2 half-hour episodes (or 1 hour-long episode) can be sent within a 48-hour period. No more than 3 10-minute episodes, per show, should be sent within a 48-hour period. - -For series with one or more story arcs, episodes should be sent for review in the order they will ultimately air on the Roku platform. For anthology series, or series consisting of stand-alone/self-contained episodes, rough cuts may be sent out of air order, if necessary. - -Check with your Content Executive regarding single vs. batch delivery of cuts. - -For any variations to the schedule above, please check with your Post Production or Content Executive for review and approval prior to the release of the first rough cut. - -#### 5.3.3 English subtitles - -All Spanish language rough cuts starting from RC2 and onward will require burned in English subtitles. Roku staff relies on the burned in subtitles to properly review. The initial rough cut may remain clean. Rough cut subtitles are not required to be 100% final, a quickly produced method will suffice. - -### 5.4 Technical specifications for rough cuts - -Formatting: - -- Slate before the hour - Please include show title, episode number, cut version (RC1, FC, etc.), total run time and release date -- Hour 01 onward should be solely program material, inclusive of production logo card at tail as LFOP (last frame of picture) - -Video Specifications: - -- Dimensions: 1920 x 1080 (horizontal) -- Codec: h264 (preferred) or MPEG -- Frame Rate: Keep it native to your project (24, 23.976, 25, etc.) -- Bitrate Encoding: VBR, 2 pass -- Target Bitrate: \~ 10mbps -- Aspect: Square Pixels (1.0) -- Visible Timecode Upper Right -- Burned in subtitles (RC2 and onward) - -Audio Specifications: - -- Audio Codec: AAC -- Sample Rate: 48000 Hz -- Channels: Stereo - -Graphics: - -- Remember to adhere to Broadcast Title Safe Zones when adding any burned-in graphics or text. - -### 5.5 Rough & locked cut delivery - -Roku Post Production will provide a recipient list for all rough cuts prior to the scheduled release of the first episode. The [Frame.io](http://frame.io/) team will walk each project through Roku’s preferred rough cut release workflow, which involves two notifications: - -1. An email to the entire distribution list, noting the availability of cuts and when notes are due back. - 1. This email should include a Segment Rundown that relates to the timing of each specific cut being sent. - -2. A notification from [Frame.io](http://frame.io/), which happens automatically after a cut is copied to the Shared Folder on [Frame.io](http://frame.io/). - -For each locked cut, you will be required to deliver the following elements via [Frame.io](http://frame.io/): - -- Locked Cut QuickTime -- Locked Cut EDL -- Locked Cut WAV Files: Mono Dialogue, Mono Music, and Mono Effects - -Cut filenames must follow the proper naming convention below: - -- Show Code (4-digits; Provided by Roku Post) -- Production number (3-digits: 101, 102, 103, etc.) -- Air Sequence (If available; 1-digit: 1, 2, 3, etc.) -- Cut version (RC1, FC, etc.) -- Date the cut was released to Roku (YYYYMMDD) - -Example: FLIP\_102\_AIR\_2\_FC\_20260513 - -All rough cut links should be confined to viewing only (i.e. no download access). When sharing cuts, please do not create any folders, or copy any folders into the Roku Review projects. - -### 5.6 Graphics milestones & review process - -The Roku Content & Post Production teams should be involved in key discussions related to graphics, from title treatments to overall episodic graphics packages. - -All graphics work (title treatment, lower thirds, interstitials, etc.) must be completed by a Roku approved graphics company. The use of freelance staff or in-house graphics teams is not permitted. Please reach out to Roku Post to obtain the list of approved vendors. - -The following milestones require Roku notification and review: - -- **Six Weeks Prior to 1st Rough Cut:** A minimum of 3 graphics vendor options must be sent to Roku for review and approval -- **Four Weeks Prior to 1st Rough Cut:** Due to Roku: Mood board, color palette, title sketches, font, etc. -- **Two Weeks Prior to 1st Rough Cut:** Due to Roku: First round of design and/or animation examples -- **One Week Prior to 1st Rough Cut:** Due to Roku: 2nd round of design and/or animation examples -- **1st Rough Cut Release** - - Temp graphics implemented into the cut that is distributed to Roku. - - All temp graphics must be based on creative input from Roku. Any changes from the agreed upon look of in-show graphics will need to be outlined in an email to the Roku Content team. -- **1st Fine Cut Release:** Final Graphics must be implemented into the cut that is distributed to Roku - -After Roku has approved all in-show graphics and the first cut is locked, no changes should be made without written approval from the Roku Content team. - -## 6. Final mastering & marketing - -### 6.1 Picture & audio mastering - -#### 6.1.1 Uncompressed masters - -For wholly-owned Roku projects, Roku requires both the un-graded and graded high-resolution master sequences as part of final delivery. These files should be exported in DPX format or TIFF format, at the highest bitrate possible (16-bit preferred). Package DPX or TIFF image sequence folders into a single .zip file per episode for delivery. - -If your vendor is unable to export these sequences, please reach out to Roku Post Production. - -#### 6.1.2 Harding testing - -Please alert Roku Post Production if any episodic content contains flashing/strobing lights or other image patterns that have the potential to trigger seizures in viewers with Photosensitive Epilepsy. In these instances, you will be required to run a Harding Test and provide the passing report to Roku Post Production as part of Final Delivery. - -Please refer to the [Ofcom ITC Guidelines](https://www.ofcom.org.uk/__data/assets/pdf_file/0021/16248/gn_flash.pdf) for further information. - -#### 6.1.3 HDR10 & dolby vision - -Currently, Roku Alternative projects are only required to complete an SDR (Rec709) grade. Please keep in mind your final deliverables will need to be in legal video range. - -Roku encourages that all series be graded utilizing the Dolby Vision workflow. Although an HDR deliverable is not yet a requirement for the Roku platform, grading in Dolby Vision will allow for the highest quality visual experience, as well as protect for future inclusion of HDR deliverables. - -For Productions whose budgets and schedules permit HDR10 or Dolby Vision grading, please reach out to Roku Post Production to determine the necessary workflow and related deliverables associated with either. - -#### 6.1.4 Sound mixing - -Roku Alternative projects are required to mix in 5.1 Surround, and then downmix to create Stereo deliverables as well. - -#### 6.1.5 Promotional assets (images and trailers) - -As each production will differ with regards to promotional assets, please reach out to Roku Marketing to determine the specific asks for your show. - -## 7. Credits - -**The first draft of credits (opening title card + end credits) must be submitted to Roku Post for approval with delivery of the first Fine Cut.** - -### **7.1 Opening credits** - -For opening credits, Roku will utilize traditional burned-in credits. Full requirements are noted below. Please reach out to Roku Post Production with any questions. - -#### 7.1.1 Disclaimer use - -If your show contains sensitive content, please reach out to your Roku Legal Executive to see if your episode requires a trigger warning prior to the cold open. - -**For any other opening cards or disclaimers, please reach out to Roku Post Production for approval.** - -#### 7.1.2 Presentation card - -Each project is required to include (2) Roku presentation cards at the top of each program, as follows: - -- 1st card: 'Roku Presents' -- 2nd card: 'A Roku Original' or 'A Roku Original Series' (Please confirm with Roku Post) -- Duration: Minimum of 2 seconds per card -- Please utilize the same font and style that is specific to each project -- Roku prefers these be integrated over picture, during the opening of each program, rather than added as separate cards over black - -#### 7.1.3 Main title option 1: main title card - -During the initial design phase of any title treatments please reach out to your Roku Creative Executives; Roku Production ([production@roku.com);](mailto:production@roku.com) Roku Marketing ([dlrokuoriginalmarketingcreative@roku.com](mailto:dlrokuoriginalmarketingcreative@roku.com)) and Roku Post: ([dlropost@roku.com](mailto:dlropost@roku.com)). - -- Duration of this card will be a maximum of 5 seconds -- The title card will display the show title/logo, burned into picture as part of each final video master -- The Production Company/Producer will have full creative control over how the title appears, subject to size requirements and provided that it is within the 16x9 title safe zone -- No other “Presentation”, possessory, or origination credits permitted anywhere on the program -- Any request to include on-screen credits on this card will require approval by the Roku Content and Post Production teams - -#### 7.1.4 Main title option 2: main title sequence - -For shows that choose to utilize a main title sequence, please follow the formatting requirements below: - -- Duration of this sequence will be a maximum of 15 seconds -- The main title sequence must include the title card or title logo - - Title card or logo must be burned into picture as part of each final video master -- No other “Presentation”, possessory, or origination credits permitted anywhere on the program -- Any request to include on-screen credits within this sequence will require approval by the Roku Content and Post Production teams - -### 7.2 End credit sequence - -For end credits, Roku will utilize traditional burned-in credits. Please follow the formatting requirements below: - -- For half-hour shows, end credits can be no longer than 30 total seconds, inclusive of production company logos - - For hour-long shows, end credits can be no longer than 90 total seconds, inclusive of production company logos - - For short form shows, end credits can have up to 3 production company logos/credits, not inclusive of the Roku Originals logo - -- The Roku Originals Logo should be placed last in the end credits. - - **Please reach out directly to Roku Post for access to the most current Roku Original Logo at: [dlropost@roku.com](mailto:dlropost@roku.com)** - - The 2025 logo is available in UHD or HD (both at 23.98fps), and with either Stereo or 5.1 Audio - -- End Credits must be white text on a black background - -- End Credits must be formatted as separate cards, not as a rolling sequence - -- Placing the show title logo or title card at the end of any episode is not permitted without prior approval from the Roku Content and Post Production teams - -- Production Company Logo Card / Studio Credits - Optional - - Up to 3 production company or studio logos/credits can be included in the end credits, in addition to the mandatory Roku Originals end credit logo - - Separate end cards can have a maximum total length of 3 seconds each - - For shared cards, no more than 2 logos can be combined onto the same end card - - Animated logos/credits are permitted - - Logos can include audio provided there is no cost to Roku to license such audio - - Audio ring outs from the end of the episode are also acceptable - - **The end of the last logo card will signify your last frame of picture.** - - No credits may appear after the end logo cards. - -### 7.3 Other credit requirements - -- Production Company/Producer shall deliver a complete written statement of all credit obligations in a format to be decided by Roku -- Production Company/Producer shall ensure that all credits conform to applicable third-party requirements -- Roku will have approval over all credits in each program, including all credits accorded to third parties - -**Adherence to the credit requirements in this document will be part of Roku’s Quality Check. If any specifications are not met, the asset will be passed back to the Production Company/Producer to modify. Roku’s Content Operation team can advise on how to upload assets for Roku review.** - -## 8. Final delivery - -The specifications below detail all deliverables required for each Roku production. A production will not be considered wrapped until all assets below are delivered and approved by the Roku Post Production team. If you have any questions, please do not hesitate to reach out to Roku Post Production. - -The Delivery Phase begins as soon as your episodes are ready for Quality Control, after Visual Effects color, and mix are complete. The following timeline is required to ensure that all pertinent assets are received on time for Post, Marketing, and Operations: - -- Due 1 Week Before First Episode Delivered to Quality Control Vendor - - Let Roku Post know which vendor you’re proceeding with - - Metadata Ingest Document due to the Hub \[See 8.7.1] -- Due With Delivery to Quality Control Vendor - - Texted Masters - - Textless Masters (if applicable) - - Text Spotting List - -### 8.1 Onboarding - -Roku uses an External Deliverables Hub (“Hub”) to receive specific production documents. This Hub will also provide information necessary for the naming of each document and file deliverable. If you have not heard from the Roku Post Production team prior to delivery, please reach out to be set up with access to the Hub. - -### 8.2 Quality control (QC) - -Each Production is responsible for covering the cost of and delivering 100% QC approved content. All masters noted below will be required to be submitted to QC **using one of Roku’s approved QC vendors:** - -- Texted Master -- Textless Master - -All required versions for each episode should be delivered to the Quality Control facility on the same day. This will ensure the Quality Control operator is able to verify that there is no variation between the texted/textless timings. - -Please be sure to build time into your delivery schedule to account for the Roku Quality Control process. Roku advises that you set aside 2 weeks for each episode to complete the Quality Control of all horizontal masters. Delivery will not be considered ‘Final’ unless all masters have received a passing report from one of Roku’s approved vendors. A list of these vendors will be provided in the Post Kickoff Packet. - -If an episode has passed Quality Control but a revision is necessary (incorrect titles, production card modification, etc.) you **must** reach out to Roku Post before any redelivery is made. Please send an email with a detailed and time coded breakdown of what fixes are being requested so that Roku can review and determine the impact it will have on each team and the show premiere itself. - -#### 8.2.1 Texted spotting list (TSL) - -You will be required to deliver a TSL file for each episode when it is submitted for Quality Control. This list will help Quality Control vendors verify that creatively intended text is included in the final file. A Roku Text Spotting List template was provided in your Post Kickoff zip file. This single file should be updated as episodes are sent to Quality Control so that all information for the series is included in the same master spreadsheet. - -The Text Spotting List should contain any and all text that is burned into picture, and the corresponding timecodes for each. If an episode has no burned-in text, you will still be required to deliver this file, but will specify the lack of text by checking the box at the top of the template. - -### 8.3 Filename specifications - -#### 8.3.1 Paper deliverables - -Paper deliverables should all be uploaded to the “Hub” platform noted above. Please adhere to the following naming conventions when delivering documents to the Hub: - -- ShowCode _ProdNumber_AirOrder\_Version\_LangCode\_Date\_FINAL -- Example: GABH _301_Air\_1\_PostVendorList\_enUS\_20250303\_FINAL - -#### 8.3.2 Master video deliverables - -All master\* video files should be labeled as follows: - -ShowCode\_ProdNumber\_AirOrder\_Version\_LangCode\_Resolution\_ColorSpace\_FN\_Audio\_FrameRate\_Date-v#.mov - -Example: - -NION\_101\_AIR\_1\_TXTD\_enUS\_UHD\_SDR\_FN\_2CH\_23976p\_20190701-v2.mov - -Production Number = As listed on Post Grids - -Air Order = Please list even if the Air Order is the same as the Production Number - -| File Name Segment | File Name Abbreviation | -| ----------------- | ----------------------------------------------------------------------------------------------- | -| Version | TXTD (Texted), TXLS (Textless), or PROXY | -| Language | enUS (American English) or esMX (Neutral Latin American Spanish) | -| Resolution | UHD or HD + Color Space = SDR or HDR | -| Forced Narratives | FN (Present), NC (none present) | -| Audio | 2CH (Interleaved) or 8CH (5.1 and Stereo) – 7.1 audio not permitted on any masters at this time | -| Frame Rate | 23976p, 24p, 25p, 2997p, 30p, 50p, 5994p, 60p | -| Revision Date | Please list in the following format: YYYYMMDD | -| Version Number | To indicate the current or previous passes of QC and track the latest version for delivery | - -\*See 8.5.5 for Proxy file naming. - -#### 8.3.3 Master audio deliverables - -Audio materials should be named to include all appropriate information: - -ShowCode\_ProdNumber\_Vers\_Date\_LangCode\_MaterialType\_Channel#\_SampleRate\_BitRate\_TC\_Channel.wav - -**Examples:** - -MAMA\_102\_v04\_20220919\_enUS\_PM\_Nearfield\_2ch\_48k\_24b\_23976\_LT.wav - -| **Material Type** | **Abbreviation** | -| --------------------------------------------- | --------------------------------- | -| Printmaster | PM | -| Music & Effects | ME | -| Audio Stem | FXStem, MXStem, DIAStem, FFFXStem | -| Optional Tracks | OPT, OPTA, OPTB, GRP | -| Add’l Detail (Dialogue Guide Track, ADR, etc) | GUIDE, ADR | - -| **Channel Type** | **Abbreviation** | -| ---------------- | ---------------- | -| Mono | Mono | -| Stereo | 2CH | -| 5.1 Surround | 6CH | - -| **Track Assignment** | **Abbreviation** | -| -------------------- | -------------------- | -| Mono | N/A | -| Stereo | LT, RT | -| 5.1 Surround | L, R, C, LFE, LS, RS | - -### 8.4 Breakdown of final locations for deliverables - -| **Media** | **Final Location** | -| :---------------------------------------------- | :----------------- | -| TXTD Master | S3 | -| TXLS Master | S3 | -| Clean Proxy | Frame.io | -| Vis. TC Proxy | Frame.io | -| Mono Audio Stems | S3 | -| Stereo & 5.1 Printmaster Stems | S3 | -| Stereo & 5.1 Stems (M\&E, Music, Dialogue, SFX) | S3 | -| Pro Tools Session Files (.ptx) | S3 | -| VAM Image Sequence (in .zip container) | S3 | -| CTM Image Sequence (in .zip container) | S3 | -| Timed Text Files (.srt and .vtt) | S3 | -| Paperwork (Metadata, Credits, etc.) | The Hub | - -### 8.5 Video deliverables - -All video should be delivered at specification unless agreed to with the Roku production team ahead of production. - -If your image capture settings are not at the same data rate or higher of the export settings mentioned in 8.4.3, please reach out to Roku Post or let your Post Manager know. In order to prevent up-sampling, your final export should match the data rate that was captured (for example, if the camera captured ProRes 422, then final export should be ProRes 422 or equivalent instead of 422 HQ). - -_Roku Best Practices_ - -If your capture workflow is different than specified above, please contact Roku Post Production before final mastering begins. It is important to keep master sequences (VAM/CTM) and final deliverables in alignment with dailies capture specifications (i.e. free of any up-scaling, cross-conversions, or up-conversions). - -#### 8.5.1 Video formatting - -All files should be formatted to start at 00:00:00:00. - -Files should begin with the cold open and end on the last frame of the Roku Originals logo end card. - -All video files **MUST NOT** contain any of the following: bars and tone, bumpers, segment recaps or previews, Vertical Interval time code, advertisements, slates, rating cards, FBI warning cards, placards, overlay branding, promotional bugs, informational bugs, watermarks, or website link callouts. - -If promotional bugs or watermarks are required by a 3rd party, Roku Content Legal should be notified. - -#### 8.5.2 Audio formatting - -For the Final Texted Masters, all audio should be contained within the delivered mezzanine file. See the audio settings listed in 8.5.3 for specifications based on delivery codec. - -**The audio channel mapping and tagging of metadata must be verified via a program like QuickTime 7, QuickTime Pro, Telestream Switch or Adobe Media Encoder for all Texted and Textless Masters.** - -- If the audio is not labeled with the correct metadata (for instance if all channels are labeled as “C” or “Mono”) this will prevent ingest on Roku’s end and will need to be corrected and re-delivered. -- Incorrectly labeled audio can be manually adjusted in QuickTime Pro without a re-export. - -Mixing Specifications: - -- Target -24LKFS +/- 2 (any average between -22 & -26). Based on ITU-R 1170-3 measurement. -- Audio should not peak above -2 dBfs (True Peak) - -#### 8.5.3 Texted video masters - -| Video Codec | ProRes | -| ---------------------- | ------------------------------------------------------- | -| Container | MOV | -| Profile | 422 HQ | -| Minimum Bitrate | 175 mbits or higher | -| Landscape aspect ratio | 16:9 (1.77:1) - (no black bars)
W1920 x H1080 (HD) | -| Pixel aspect ratio | Square pixels (1:1) | -| Scan type | Progressive scan type | -| Chroma Subsampling | 4:2:2 | -| Color Space | BT.709 Legal Video Range | -| Bit depth | 10-bit or 12 bit | -| Constant Frame Rate | 23.976p, 24p, 25p, 29.97p, 30p, 50p, 59.94p, 60p | -| Native frame rate | No 3:2 pulldown flags | - -| Audio Codec | PCM | -| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Format | 2 Interleaved Tracks or 8 Mono Tracks | -| Track Layout | Interleaved: Track 1: 5.1, L-R-C-LFE-Ls-Rs Track 2: Stereo, LT/RT
Mono: L, R, C, LFE, Ls, Rs, Stereo LT, Stereo RT
**7.1 audio is not permitted on any masters at this time** | -| Sample Rate/ Bit Depth | 48000Hz/24-bit | -| Channel Mapping & Metadata Tagging | See 8.5.2 - Verify correct audio channel mapping and metadata tagging. | - -#### 8.5.4 Textless delivery - -If your content includes burned-in on screen text, you will be required to deliver a separate Textless Reel or Full Episode. This reel should include clean, text-free versions of any shots that contain burned-in subtitles or graphic text elements. If the show contains a comprehensive graphics package, please strip all graphics and supply the graphics package or elements in Archival. Video and Audio specs should mirror the Texted Masters noted above. - -Audio mapping label verification as noted in 8.5.2 must be verified in textless master. - -Additionally, if foreign language subtitles cover 30% or more of a given episode, you will be required to deliver a fully textless version of that episode. - -Examples of what to remove for the Textless Masters: - -| Forced Narratives | Credits | Text-Based Graphics | -| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | -| ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-1.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-2.png) | ![roku400px - premium-asset-1](https://image.roku.com/ZHZscHItMTc2/post-alt-specs-3.jpeg) | - -
- -_Roku Best Practices_ - -- Background elements with text, such as street signs, do not need to be included in the Textless Reel. -- ‘Forced Narratives’ refers to on-screen text that is used in one of two ways: to translate foreign dialogue into English or to clarify dialogue that may be inaudible. - -#### 8.5.5 Final proxy files (3 total per episode + 1 series opener) - -From each Texted Master created, please export the following proxy files: - -| Video Codec | H.264 | -| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Container | MOV or MP4 | -| Picture | (1) Clean & (1) w/ Vis.TC UR & (1) w/ Burned English CC\* | -| Bitrate | 5mbit/s (total file size \< 1gb to 2gb) | -| Dimensions | W1920 x H1080 (HD) | -| Scan Type | Progressive scan type | -| Color Space | BT.709 Legal Video Range | -| Bit Depth | 10-bit or 12-bit | -| Constant Frame Rate | Should Match Master | -| Native Frame Rate | Should Match Master | -| Audio | Ch.1 Stereo Left, Ch.2 Stereo Right | -| Filename | ShowCode\_ProdNumber\_AirOrder\_Language\_Proxy_HD_
FN(if applicable)\_Audio\_Timecode(Clean or VisTC)\_RevisionDate-v#\_(Final or Pre-QC).mov

THAM\_101\_AIR\_1\_PROXY\_enUS\_HD\_FN\_2CH\_CLEAN\_20200916\_V4\_FINAL.mov | - -**Spanish language series will require a third proxy deliverable with burned in English cc. Closed captions must be 100% final. This should be labeled as “PRESS” preceding “PROXY” in the file name. Example:** - -THAM\_101\_AIR\_1\_PRESS\_PROXY\_enUS\_HD\_FN\_2CH\_CLEAN\_20200916\_V4\_FINAL.mov - -### 8.6 Audio delivery - -Prior to the commencement of principal photography, please reach out to Roku Post Production in order to determine the necessary audio deliverables for your series. As content, formatting, and style will differ from one series to the next, Roku understands that stem delivery may also vary. Please upload to your Archive folder on S3. - -#### 8.6.1 Domestic episodic stems - -Provided below are the stems required for delivery of each episode/project: - -- Mono Dialogue, Music, and Sound Effects stems -- Stereo & 5.1 Printmasters -- Stereo & 5.1 M\&E - Fully Filled -- Stereo & 5.1 Music -- Stereo & 5.1 Dialogue -- Stereo & 5.1 Sound Effects -- Pro Tools Session Files (.ptx) - -Provided below are the stems Roku would like to receive, if available (and applicable): - -- Stereo & 5.1 Mix minus narration -- Score or Original Composition (pending rights) -- Mono M\&E Stems - Opticals, Backgrounds, etc. - -All audio should be archived as 24-bit, 48kHz WAV files. - -Please see section 8.3.3 for full guidelines on labeling audio files. - -ShowCode\_ProdNumber\_Vers\_Date\_LangCode\_MaterialType\_Channel#\_SampleRate\_BitRate\_TC\_Channel.wav - -**Example:** - -MAMA\_102\_v03\_20220919\_esMX\_FXSTEM\_6ch\_48k\_24b\_23976\_R.wav - -_Roku Best Practices_ - -- Roku requires that all music be cleared for both domestic and international use across all media on all devices. -- Optional tracks (foreign language, grunts, breathing, etc.) are preferred, if applicable -- If budget permits, please create Fully Filled FX stems as part of delivery - -### 8.7 Timed text file delivery - -Roku requires all content to be delivered with all of the following timed-text formats: - -- Subtitles: Language solely (no inclusion of sound descriptors) - - Foreign subtitle files should also include any translated forced narratives that are currently burned into picture - -- SDH: Language in addition to sound descriptors (no forced narratives) - -- FN: Forced Narratives solely - -All files are required in an effort to support customers that are deaf or hard of hearing. - -Roku requires closed captions and subtitles in **2** formats: SRT and WebVTT. The files have to have the same timecode and frame rate as the video and audio delivered. Character encoding MUST be UTF-8. - -**Languages & formats required:** - -Spanish (Mexico, Code: esMX): Subtitles, SDH, Closed Caption Files, & FN - -English (American, Code: EN): Subtitles, SDH, Closed Caption Files, & FN - -**All files should be labeled as follows:** - -ShowCode-ProdNumber-LanguageCode\_Format-RevisionDate.mov - -**Filename Examples:** - -NION-101-esMX\_SUB-20190701 - -NION-101-enUS\_SDH-20190701 - -NION-101-enUS\_FN-20190701 - -### 8.8 Paper deliverables - -Roku’s External Deliverables Hub (“Hub”) is a centralized location for all wrap deliverables documents. If you have not been granted access and will be handling this portion of delivery, please reach out to your Post Manager. - -#### 8.8.1 Roku metadata template - -Metadata allows Roku to ingest and display all series related information for our customers. Please do not alter the formatting of this spreadsheet as it will break the coding required for ingest. - -Please find the most recent Roku metadata templates and guidelines [HERE](https://go.roku.com/rokuchannel-ingest-vod#roku-excel-metadata-guidelines-and-templates). - -**Spanish language series will require metadata descriptions in both Spanish and English.** - -The required details will include, but are not limited to, the following: - -- Show - Title, Description, Primary Spoken Language, Production Companies -- Season - Title, Description (leave blank if not applicable) -- Episode - Title, Production Number, Air Order, Total Run Time (TRT) -- Exact timecode of ad break insertion, in (HH:MM:SS:FF) format - -Please note that Air Order and Episode Titles must be a decision made with your Content Executive. The Episode Titles must be creative (no “Episode 1”) and should be written with the show writers or receive writer approval. - -#### 8.8.2 Credits documents - -Please deliver all of the following items as part of Final Delivery: - -1. PNG files relating to the Title Logo and any other logos submitted should be uploaded to [Frame.io](http://frame.io/). -2. Roku Alternative Credit Approval Form - This document should include both main title and end credits for Business Affairs Approval. -3. Traditional Episodic Credits Lists that detail the specific credits tied to each episode should be uploaded to the Hub. This can either be Excel or Word formatted in a standard traditional scrolling or end-card format. - -#### 8.8.3 Segment rundowns - -You will be required to deliver a detailed breakdown of the timecodes pertaining to all segments in each episode. Please utilize the Roku Segment Rundown Template provided in your Kick-Off Delivery Packet. - -**Roku requires that the timecodes within this document be delivered in HH:MM:SS:FF format. Any spreadsheets submitted without this formatting will not be accepted by Roku.** - -#### 8.8.4 As broadcast scripts - -Please deliver one set of As Broadcast Scripts for each series to the Hub **in both Spanish and English**. As Broadcast Script files should have a timecode-based breakdown of each line of dialogue. You are approved to submit the As Broadcast Scripts in any format that a Roku approved vendor utilizes. - -#### 8.8.5 Final font memo - -Please deliver one document that details the font name and size utilized for opening credits, identifiers and/or other on-screen text added to each episode (where applicable) to the Hub. If applicable, please also note which vendor created the show logo. - -#### 8.8.6 Final vendor list - -Please deliver your final version of the Roku Vendor List that you received in the Kick-Off Delivery Packet to the Hub. - -#### 8.8.7 Final text spotting list - -Please deliver the Text Spotting List that was used to Quality Control the final episodes to the Hub. Please ensure that any changes made during Quality Control are reflected in the final document that is delivered to Roku via The Hub. Please deliver a single excel file, via Roku’s template, with episodes separated onto their own tabs. - -#### 8.8.8 Episodic delivery checklist - -Please deliver the final version of the Roku Episodic Delivery Checklist that you received in the Kick-Off Delivery Packet to the Hub. Please fill in all applicable delivery dates of assets and indicate when Archival will be completed. - -- All applicable file version dates and delivery locations for each asset -- All Quality Control Start and End/Approval dates for Texted and Textless Masters -- Any assets not being delivered to Roku, as approved by Roku Post, should be identified as such within the “Delivery Destination/Notes” section of each deliverable -- If archival delivery will trail wrap, please indicate when it will be completed and who the primary point person will be to confirm for Roku Post - -#### 8.8.9 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the American Society of Composers, Authors and Publishers (ASCAP) website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. - -Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Vosper at [svosper@roku.com](mailto:sgrossberg@roku.com). - -#### 8.8.10 Not applicable form - -In cases where a paper deliverable is non-applicable to the project, please upload the Roku Not Applicable Form to the Hub with a written explanation of why this deliverable does not apply. - -## 9. Archival - -### 9.1 High resolution masters & source material - -AWS is Roku's platform for archiving projects. Roku's S3 bucket can be accessed via Aspera Shares. Note that this is separate destination from the Aspera Ingest upload. A Roku Post Manager will request email addresses and names of those who will be uploading archival assets to the designated archival show folder. - -Reach out to Roku Post if you have not received access to Aspera credentials. - -When adding video assets to S3 do not create additional sub-folders. Keep all media (proxies, texted/textless masters) only in the folders provided. Audio files should be grouped by episode (where applicable). - -The following are required deliverables that must be uploaded to the Final Archive folder on S3: - -Required: - -- Final Texted Masters -- Final Textless Masters -- Final Audio Stems -- Graphic Elements – Main title card, credit PNGs, end credit PNGs, on-screen graphics, interstitials, etc. - -Any and all series that are wholly owned by Roku will require delivery of VAMs, CTMs, and final Visual Effects shots (where applicable) via LTO10 or greater. LTOs should be formatted LTFs and include a digital manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. These manifests should be uploaded to The Hub. - -For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -- VAMs – Un-color-corrected, textless, DPX or TIFF format (**Compress** to .ZIP or .TAR) - - Associated Avid bins or EDLs - -- CTM – Color-corrected, textless, DPX or TIFF format (**Compress** to .ZIP or .TAR) - - Associated LUTs or color-grading files - -- Final VFX Shots – Un-color-corrected preferred (if applicable) - -#### 9.1.1 Dailies archival - -Any and all series that are wholly owned by Roku will require delivery of dailies/OCF via LTO10 or greater. LTOs should be formatted LTFS and include a digital manifest for each tape. For all licensed or co-produced content, please reach out to your Roku Post Production Manager to discuss the specific requirements and expectations for each series. - -### 9.2 Offline editorial masters - -Please be sure that all consolidated avid media is archived and removed from [Frame.io](http://frame.io/) prior to wrap. Once each project’s wrap is complete, all media still contained within the [Frame.io](http://frame.io/) platform will be **deleted** and the series users will be disabled. - -## 10. Change log - -### V4.0 - -- 3.3 - Dailies Memo requirements updated. -- 3.4 - Sizzle requirements - Roku's main title presentation cards and deliverables added. -- 3.4.1 - Sizzle TRT updated to 30-45 seconds -- 5.2.2 - Wholly-owned Roku unscripted projects now have access Universal Production Music. -- 6.1.1 - Uncompressed masters - packaging DPX and TIFF folders into one .zip file. -- 7.1.2 - Roku presentation cards, duration and style specifications added. -- 8.4 - Final destination chart for all deliverables. -- 8.7 - Timed Text files will now be delivered to the AWS S3 Archival Bucket. -- 9.1 - Final Archival Media will now be uploaded to AWS S3, rather than Frame.io and for LTO Archive please use LTO10. - -### V3.0 - -- 2.5 - Roku's Localization Team will handle the creation of all English subtitles and audio descriptions. -- 5.2.3 - Ad breaks placement. -- 7.1.2 - Presentation credit requirement added. -- 7.2 - Roku Originals end card updated -- 8.3.1 - Paper deliverable labeling revised. -- 8.4.4 - If one episode in a series requires a full textless asset delivery, now all episodes in that series will require a fully textless master. -- 8.7.1 - Link to current metadata templates and guidelines added. -- 8.7.10 - 'Not Applicable' Form added -- 9.1 - LTO9 is the newest version of the Linear Tape-Open and this is the version that should always be used. - -### V2.1 - -- 5.2.4 – RO Content Rating Guidelines updated -- 5.6 - Graphics vendors guidelines updated -- 8.7.1 - Roku Ingest Specs Link added for access most updated Metadata Template - -### V2.0 - -- Multiple Sections - 5.1 & Stereo Mix required. 7.1 mix no longer being requested. -- Multiple Sections - Timecodes of act breaks updated to HH:MM:SS:FF -- 5.2.1 - Total run time must be locked at Locked Cut stage, inclusive of a slug for the end credit bed. -- 5.5 - Locked Cut requirements updated -- 8.3.2 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX) -- 8.4.5 - Final Proxy file size changed to a maximum of 2gb -- 8.5.1 - Audio Deliverables updated -- 8.6 - Replaced Mexican Spanish (esMX) labeling with Neutral Latin American Spanish (esMX); Removed SCC file requirement -- 9.1 - Archival - Use of [Frame.io](http://frame.io/) Transfer App required for all uploads to the app - -(v1.9 intentionally skipped) - -### V1.8 - -- 2.4 – Roku Marketing Team’s involvement in Sizzle Reel and Main Title Treatment clarified -- 2.5 – Localization Introduction -- 3.1 – Capture requirements adjusted to HD (1920x1080); Approval needed for aspect ratios outside of 16:9 -- 3.2 – Dailies Selects requirements further clarified -- 5.3.3 – Runtime requirements, cut review, and turnaround timing clarified -- 7.1.2 – Main Title Card requires review/approval by Roku Creative Execs, Marketing, Production & Post -- 7.2 – Roku Originals Logo must be placed last in end credits; download link provided -- 8.3.2 – Master Video Deliverables file naming modified -- 8.3.3 – Master Audio Deliverables file naming modified -- 8.4.2 – Audio Channel mapping and tagging of metadata must be verified -- 8.4.3 – Texted Video Masters audio track layout updated and resolution adjusted to HD -- 8.4.4 – Audio mapping label verification as noted in 8.4.2 must be verified in Textless Master -- 8.5.1 – Revised audio labeling guidelines for stem delivery -- 9.1 – [Frame.io](http://frame.io/) & High Resolution Masters instructions revised - -### V1.7 - -- 5.2.2 – Segment Rundown deliverable must include milliseconds in its formatting. -- 5.4 – Revised file naming convention on rough cut deliveries. -- 8.2.1 – Text Spotting List updated -- 8.3 – File naming format for both paper and media deliverables modified. -- 8.4.5 – Additional proxy deliverable added. -- 8.6 – Replaced Latin American (LAS) labeling with Mexican Spanish (esMX) -- 8.7 – Further clarification provided across paper deliverables - -### V1.6 - -- 8.7.2 - Updated to include the “Cast & Crew“ file as a credits document deliverable. -- 9.1.1- Dailies Archival section added. - -### V1.5 - -- 5.5 – Segment Rundowns will be required with delivery of each rough cut -- 8.5.2 – Audio Description files added as a new deliverable - -### V1.4 - -- 5.2.2 – Clarified that cuts will not be accepted if they do not adhere to Ad Break duration specifications -- 6.1.2 – Added Harding Test section for content with flashing/strobing lights and other image patterns -- 7.2 – End Production Logos may include audio provided there is no additional cost to Roku - -### V1.3 - -- 5.2.2 – Clarified that Ad Breaks should have no text -- 7.2 – Updated End Credits section with more detail -- 8.7.9 – Updated Music Cue Sheet information and point of contact for questions - -
diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/scr-prod-legal-guidelines.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/scr-prod-legal-guidelines.md deleted file mode 100644 index 48a09179..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/scr-prod-legal-guidelines.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: "Scripted production legal guidelines" -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- - - -In creating content for exhibition on Roku, there are a few guidelines that the Roku Production Legal team would like you to keep in mind. As a reminder, we expect you to retain your own production legal counsel to represent your interests, as the Roku Production Legal team represents Roku. Please review these guidelines with your legal counsel. If you have any questions or concerns after reviewing, let’s set a time to discuss. - -## Production legal approvals - -Please reach out to Roku Production Legal for approval before engaging in any of the following: - -- Product Placement and Trade Outs - Product placement and trade outs may be allowed at Roku’s discretion. Please inform Roku Production Legal of potential product placement and/or trade outs in advance so that we can discuss and provide our "Trade Out Request Form." -- Clearances - It is your responsibility to obtain all necessary clearances for the production, synchronization, exhibition, performance, distribution, marketing, and exploitation of the content by Roku, including musical compositions and sound recordings contained therein (except for public performance rights). Any potential third-party contractual restrictions that could impact Roku’s rights must be approved by Roku Production Legal in advance. -- Music – Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-context promotional use, unless approved in writing by Roku Production Legal. Please only source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. -- Talent Approvals and Restrictions – When negotiating Talent deals, please advise Roku Production Legal of any restrictions Talent wishes to place on Roku’s ability to exhibit, market or promote such Talent. -- Unions/Guilds - If the Series is produced on a guild/union-covered basis, please reach out to Roku Production Legal to discuss the guild/union classification of the production. -- Insurance - Roku’s insurance requirements are included in the Indemnity Agreement or Standard Terms and Conditions negotiated by your legal counsel. Please send Certificates of Insurance to Roku Production Legal for approval. - -## Additional production legal expectations - -- Casting Notices - Roku is committed to diversity in all of its productions. Casting notices should solicit people of various ages, ethnicities, and socio-economic backgrounds to apply. Please note that certain characteristics are protected by anti-discrimination laws (e.g., age, race, religion, etc.), and generally should not be referenced in casting notices unless central to the core creative of a production. If necessary to include, consult with your legal counsel on how to do so appropriately. Reminder - please do not include the Roku name or logo on your casting notices, unless approved by Roku Production Legal. -- Talent - Please make sure all talent sign their agreements/releases prior to appearing on camera. If for any reason you think this will not occur, please give Roku Production Legal a heads up. Please reach out to Roku Production Legal before giving talent the right to dub their voice in another language. For each talent agreement, please provide Roku Production Legal with a written summary of any approvals, restrictions, or requirements that may impact Roku’s marketing, publicity or promotional activities. -- Nudity/Sex Scenes - Please consult with your legal counsel on whether nudity riders are needed when talent is shooting a nude and/or sex scene. You may also want to consider whether it will be appropriate to have an intimacy coordinator on set. -- Identifiable Brands - Roku does not generally restrict the appearance of branded products or services in content - there is no need to use only generics or mask/blur brands; however, if you wish to include any identifiable brand in “hero” shots, please raise to Roku Production Legal. -- Charities - If you plan to highlight a charity in a production (e.g., have someone sponsor/donate/call out for donations to a charity), please have your counsel confirm the tax-exempt status of the charity and inform Roku Production Legal in advance. -- Smoking - It is Roku’s policy to not depict actual minors or underage characters smoking tobacco or electronic cigarettes in content on its service. If considered critical to the creative for a particular character, please discuss with your Roku Creative Executive. -- Safety/Respect in the Workplace - Roku is committed to supporting safe and respectful work environments. Please consult with your legal counsel to ensure that your production adheres to required health and safety practices and is in compliance with all applicable workplace regulations, including any state-required sexual harassment training. -- Titles - Roku expects content titles to be cleared for exhibition, marketing, and promotion on and in connection with the Roku platform. Proof of bound E&O title coverage should be provided to Roku Production Legal. - -## Compliance with all laws - -Federal, state and local laws (including laws of foreign countries, if applicable) should be respected at all times in creating content for Roku. As a reminder, the following each raise unique legal concerns when producing content: - -- Filming with children - Laws prohibiting child porn, permitting requirements, court-approval of minor contracts, and safety issues may all be relevant to your production. -- Filming with politicians or government officials - Federal and state rules regarding the payments/gifts to candidates or public officials can arise during production (e.g., talent fees for an appearance could equal a campaign gift). -- Marijuana on set - Federal and state laws can impact shooting with real plants or within marijuana shops since, while technically legal to film, it can be illegal to have possession or control of plants depending on the jurisdiction. -- Emergency Action System tones (actual or simulated) - The transmission of EAS alarm tones, under any circumstance other than a genuine alert or authorized test, violates Federal law. The FCC has issued large fines related to the exhibition of content including the EAS tone. -- Filming with drones - In the United States, FAA regulations govern the use of unmanned aerial vehicles (UAVs) for commercial filming and various international jurisdictions have similar regulations and permitting requirements. - - - -Please raise any applicable concerns with your legal counsel - preferably in advance of filming! \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/scripted-prod-guidelines.md b/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/scripted-prod-guidelines.md deleted file mode 100644 index f2cf5453..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/roku-originals/scripted-prod-guidelines.md +++ /dev/null @@ -1,740 +0,0 @@ ---- -title: Scripted production guidelines -excerpt: '' -deprecated: false -hidden: false -metadata: - title: '' - description: '' - robots: index -next: - description: '' ---- -_Version 2.4 - February 2024_ - -## 1. General overview - -Roku pioneered streaming to the TV. The company operates the No. 1 TV streaming platform in the U.S. as measured by hours streamed (Hypothesis Group 2021). The Roku Channel is a top streaming channel on the Roku platform, owned and operated by Roku. It is available to consumers in the U.S., Canada, and the UK for free on Roku streaming devices, the Web, Amazon Fire TV and select Samsung TVs, and iOS and Android devices.  - -The Roku Channel is committed to providing the highest quality content and values its Partners for helping to achieve this goal. The Roku Production Guidelines outline the best practices for the Partner at this time. This document and the requirement are subject to change at Roku’s sole discretion. - -## 2. Welcome to Roku production - -We look forward to working with you! You should have received a “Welcome to Roku Production” email along with the Production Kick-off Documents outlined below. Please review documents in their entirety. Upon series pick-up Roku Production will reach out to schedule a kick-off call. During the call we can address any questions you may have. - -### 2.1 Production kick-off documents - -#### 2.1.1 Scripted production guidelines - -* Roku Production document for scripted projects – document you are currently reading -* Located on the Roku Deliverables Hub (Hub) in the Production – Scripted folder - -#### 2.1.2 Scripted media delivery specifications - -* Roku Scripted Hour-Long Delivery Specifications -* Roku Scripted Half-Hour Long Delivery Specifications - * Roku technical specifications for scripted projects - * Located on the Hub in the Post – Scripted folder - -#### 2.1.3 Scripted production legal guidelines - -* Roku Production Legal guidelines when creating content for exhibition on Roku - -## 3. Roku communication - -### 3.1 Roku emails - -For email correspondence, Roku requests that the full name of the project be included in the subject line. Please do not use acronyms for the title. - -### 3.2 Roku scripted contact sheet - -The Roku Scripted Contact Sheet is for Partner use only. Please do not distribute. The contact sheet can be found on the Hub in the Production – Scripted folder. - -### 3.3 Roku scripted distribution list - -Roku Production will send you a distribution list. You will also find the Roku Scripted Distribution List via the Hub in the Production – Scripted folder. The distro list will include the name, title, email, and required documents/media for each Roku recipient. There are a handful of documents we request be emailed directly to Roku which include, but are not limited to: - -* Budgets -* Call Sheets -* Scripts -* Prep Schedules -* DooDs, One Liners, and Production Calendars -* Cast & Crew Lists -* First/Lunch/Wrap Reports -* Daily Production Reports (Prelim & Approved) -* Cost Reports - -**Do not include the Roku name or logo on any documents** (including contact sheets, call sheets, production reports, casting notices etc.) without written approval from Roku Production Legal. - -### 3.4 Roku calls - -Upon the below milestones, calls will be set with Roku Production: - -* Production Kick-Off Call -* Weekly Prep calls before commencement of Principal Photography -* Weekly or bi-weekly Production/Post/Legal call throughout Principal Photography -* Wrap of Principal Photography -* Any major production or post schedule changes - -Upon completion of Principal Photography or one week prior to delivery of Rough Cut 1, Roku Post will initiate weekly post calls. - -### 3.5 Roku notifications - -Please inform Roku Production, at least 2 weeks prior to any of the following activities or events: - -* Applying for tax incentives -* Traveling and filming outside the domestic United States -* Filming in aircraft/watercraft, including private planes and yachts -* Filming physically challenging or hazardous activities (including filming with firearms) -* Filming with minors or animals -* Filming a ride-along with law enforcement -* Filming nudity and/or sexual activities -* Filming any potential illegal activities -* Filming with government officials, employees, and candidates, including any of the following: - * Faculty and teachers at government owned or controlled businesses or institutions (e.g., public universities, hospitals, national telecom companies) - * Employees of public international organizations, like the United Nations or World Bank - * An elected or appointed official, candidate for public office, or their family or staff - * Members of Royal Families - * Public school employees, firemen, law enforcement, military, etc. - * An elected or appointed official, candidate for public office, or their family or staff - -### 3.6 Roku emergency notifications - -In the event of an emergency or incident, once the situation is stable, please contact Roku Production immediately. If you cannot reach Roku Production, please call Production Legal. Incidents include, but not limited to: - -* Stopping down pre-production, production, and/or post -* Unplanned hiatus or postponement -* Projected or occurring natural events (i.e., earthquakes, wildfires, hurricanes, tornadoes, etc.) -* Any suspected or confirmed drug use by on-camera talent, crew, or producers -* Cast, Crew, and general public medical concern including: - * Physical Altercations - * Hospitalization - * Arrest - * Personal Accident/Injury - * Vehicle Accident -* Covid-19 health-related situation involving an individual, location, or government -* Threat of litigation, claim, or potential claim arising in connection with the production -* Plan to file an insurance claim due to force majeure -* Any other event (or planned event) that may pose a legal or reputation risk to Roku -* Any event, occurring or projected, that may impact any person(s) and/or actual production, physical production, or delivery of the series to Roku -* Any contact by the press or media regarding any aspect of the production, including talent and Covid-19 - -**AFTER** informing Roku, please email detailed information, while respecting the privacy of individuals, regarding the incident to [scrprod@roku.com](mailto:scrprod@roku.com): - -* Title the subject of your email as follows: “Show Name” - Notification - CONFIDENTIAL -* If the incident is sensitive in nature, in the body of your email please relay that an incident has occurred and request an immediate call with Roku Production and Production Legal. - -In the event of any non-emergency incident (property/location damage, equipment damage): - -* Please inform Roku Production -* Please be sure to note in the Production Report - -**SPECIAL NOTE:** In the event you are not able to immediately reach Roku Production or Production Legal please proceed with emailing [scrprod@roku.com](mailto:scrprod@roku.com) but use discretion in the details you share. - -## 4. Roku production - -### 4.1 Budget - -Roku Production looks forward to partnering with you to ensure delivery of the best content to The Roku Channel. Below are guidelines to assist with budgeting, scheduling, and cost reporting for your project. Please reach out to Roku Production with any questions. - -#### 4.1.1 Chart of accounts (COA) - -Please reach out to Roku Production for the Roku COA template when you are ready to begin budgeting for your project. The COA is to be used throughout the lifecycle of the project: i.e., subsequent budget revisions and all Cost Reports, Variance Reports, General Ledgers, etc. - -The COA template is provided in movie magic budgeting format. - -#### 4.1.2 Assumptions page - -Please reach out to Roku Production to provide the Roku Assumptions Template. Please make sure the following information, when applicable, is included on the assumptions page: - -* Title, version #, ‘as of’ date matching budget - -* Writing, Prep, Shoot, and Post Dates - -* Include customary Budget Top Sheet header information such as: - - * Name of the production company(ies) involved - * # of episodes - * Minutes per episode - * Name of person that prepared the budget - * Names of Executive Producers, Producers, and Director - * Key shoot locations - * Post location; city/facility - * Collective bargaining agreements (unions) - * Number of shoot days and total shoot weeks - * Number of total post weeks - * Total weeks from start to final delivery - * Budgeted Shooting Hours - * Script date the budget ties to - * Foreign Exchange Rate - -* Tax incentive estimate, including estimated sales rate for transferable tax credits if applicable - -* FX rate (if any work is to take place outside of the United States) - -* Premium Fee estimate (if applicable) - -* Residuals estimate, broken out by guild, and including any foreign residual buyouts - -* List out all budgetary exclusions against fee calculations (see deal for customary exclusions) - -* List by department number of crew budgeted - -* Note if staff member on a show is staff at Prod Co/Studio - -* Please list out the following types of equipment/software: - - * Camera package - * Specialty equipment: Cranes, dollies, drones, etc - - * Edit software (i.e., Final Cut, Premiere, Avid) - - * Coloring and grading software - -* List “Roku Scripted Media Delivery Specifications” version date - -* List “Roku Scripted Production Guidelines” (this document) version date - -#### 4.1.3 Budget requirements - -Roku Production asks that the following information, when applicable, be included/considered when budgeting: - -* Include the budget as a PDF of the Movie Magic Budget (MMB) using Roku’s provided Chart of Accounts -* Include title, version #, ‘as of’ date and page numbers -* Include Budget Top Sheet header information as noted in [Section 4.1.1](#411-chart-of-accounts-coa) -* Avoid large flat allowances. Provide details instead (cost per day/week/month etc.) -* Fringes should be by category and broken out -- avoid lump sum fringe rates -* Include a variance column between your last budget and current budget -* Suppress zero and empty accounts -* Budget must be in US dollars -* Budget Development Fees -* Budget for script clearance -* Budget for worldwide title clearance and opinion letter -* Include any security and general safety costs, include fees for risk managers, intimacy coordinators, or assessments and safety consultants -* Budget for insurance – minding stunts, aircraft, watercraft etc. -* Extraordinary talent fees and costs should be excluded from all fee calculations -* Budget for all necessary worldwide clearances in all media for music and footage - * All licenses required for the production, synchronization, exhibition, performance, distribution, and exploitation (including in context marketing and promotion) of the Program by Roku for the term of the license - * Include music label waiver costs, if required - * Include American Federation of Musicians fees if applicable - * Reach out to Roku Legal with specific questions related to required terms -* Computer Box Rentals are capped at $50/week and cannot exceed $500 overall - * Please provide an inventory with values for larger box rentals - * Larger rentals are capped at 50% of the total value over the course of the project -* Include any applicable tax incentive amounts and associated auditing costs -* Refer to your Roku Scripted Media Delivery Specifications for the following: - * Cut Review Process for budgeting Post - * Include captioning, subtitles, and technical QC in your budget - * A list of preferred vendors will be provided by Roku Post - * Spend beyond the Approved Budget is never authorized without **written** approval from Roku Production -* For each budget revision please be sure to note the date, version and bullet point relevant changes in the body of the email - -#### 4.1.4 Foreign exchange rate (aka FX) - -If shooting in a location outside of the United States please be sure to note what foreign exchange rate you have assumed in your budget. - -* Partner is responsible for noting the FX on the top of the budget top sheet as well as the assumptions. - -#### 4.1.5 Tax incentives - -If shooting in a location in which a tax incentive or rebate is accessible, please be mindful of the below: - -* Partner is responsible for confirming whether production is eligible for potential incentives based on the project format (episodic, feature, etc) and minimum production spend - -* Partner is responsible for applying for tax incentives/rebates - * Please work with Roku Production when filing for incentives/rebates - -* Unless otherwise specified in the agreement, Roku funds the net budget -- differential between the gross and net budget is the responsibility of the Studio - - * Roku **does not** pay interest associated to financing the tax incentive - * Roku **will allow** the following incentive related expenses to be line items in the approved budget: - * Audit Fees associated with filing for the incentive, (e.g., Certified Public Accountant or Third-Party Auditor/Firm) - * Post Accounting as needed in finalizing expenses in conjunction with submitting final documentation - * Tax Credit Analysis, Applications, and Admin Fees - * Fees associated with transferring/selling credit - * Bank Fees, i.e., account set-up (not fees related to negligence of Partner e.g., late fees, return checks) - -* Roku requires confirmation of the final tax incentive allocation for the production - - * If you plan to access a transferable credit, confirmation of the estimated sales rate should be listed in the budget and assumptions - * Final tax incentive allocation is required to close out the show cost report - -* Final documentation will vary based on the location in which you shoot, and the type of credit received. Below is a list of items that may be required when wrapping out your production: - * Tax Credit Certificate - - * Application/Letter of Transfer/Sale - - * Approval Letter - - * Eligibility Certificate and/or Completion Certificate - -* Please reflect all VAT tax in the Cost Report and flag those costs the General Ledger within the naming convention “VAT” - -* Please review the Roku Credit Requirements per the Roku Scripted Media Delivery Specifications prior to agreeing to any embedded logo credit related to receiving tax credits or incentive uplift. - -#### 4.1.6 Unapproved budgetary line items - -Roku does not typically allow the following examples, or similar, to be included as line items in Approved Budgets: - -* Copyright Costs -* Contingencies -* Partner Overhead -* Legal Fees -* Entity Fees -* State Filings -* Bank Fees -* Partner travel and associated expenses -* Partner software licenses (i.e., PIX, DAX, Adobe Cloud, etc.) -* Advanced financing interest, loans, etc. -* All expenses related to long form version beyond Roku delivery and exhibition - -#### 4.1.7 Approved budget - -All Conditions Precedent and required certificates of insurance (e.g., GL, E&O) must be fulfilled prior to the official Greenlight / Budget Approval being issued. Additionally, prior to Roku Production sending the official Greenlight / Budget approval, Roku requires a final budget packet to review. The packet should consist of the following items: - -* Assumptions - -* Budget - -* Current Calendar - -* Supporting Documents as applicable - -Upon review and acceptance of the final budget packet, Roku Production will issue the official Greenlight / Budget Approval via email. The Budget Approval email will trigger milestone payment review and approval. - -* Upon receipt of the greenlight email, if you have not already done so, send Roku Production the locked budget you will be cost reporting against. - -### 4.2 Calendars - -Revised calendars are required whenever there is a schedule adjustment. Please use the following when submitting calendars: - -* Every version of the calendar should have title, version #, ‘as of’ date and page numbers -* Once in production, any changes to the post schedule/calendar must be submitted to [scrprod@roku.com](mailto:scrprod@roku.com) and [dlropost@roku.com](mailto:dlropost@roku.com) for approval within 24 hours -* In the body of the email that comes with calendar revisions, bullet point relevant changes to current calendar. Roku Production will review and confirmed via email if approved. -* Master delivery dates cannot shift without **written** approval by Roku Production and Post - -#### 4.2.1 Calendar requirements - -Calendar should cover all phases of production (i.e., casting, pre-production, production, post, QC and final delivery) and include key dates, as applicable, for the following: - -* Pre-production -* Writing -* Casting weeks including deadlines -* Key hire start and end dates -* Scout milestones (if applicable) -* Show & Tell -* Table Read -* Production Meeting -* Key VFX design review, as applicable -* Production -* Prep, shoot, and wrap dates – including set build, rehearsal(s), and travel days -* Please identify on your calendar when you plan to shoot and deliver your camera test (see [Section 4.2.3](#423-camera-test-milestone), Camera Test Milestone) -* Post -* Start and wrap, finishing (i.e., audio and color), delivery of cuts and when notes are due, and master delivery dates -* Please refer to your Scripted Media Delivery Specs, Review Cut Process, as you build out your schedule -* VFX milestones (i.e., VFX review 1, VFX review 2) -* Please be sure to build time into your delivery schedule to account for the Roku QC process. Roku advises that you set aside two weeks for each episode or 3 weeks for a feature, to complete the QC of all masters. -* Roku Post will provide a list of approved QC vendors - -#### 4.2.2 Table reads/show & tells - -* Roku requests table reads and show & tell presentations for our content, unless otherwise noted by Roku Creative -* Typically, the table read is a one-time read-thru of all the scripts, with at least the lead talent in attendance -* Typically, the show & tell covers at least wardrobe, set design, locations, color tones, and any/all department presentations depending on the specific creative needs of the show -* Please reach out to Roku Production for an invitation list to both the table read and the show & tell presentation -* Please provide a dial-in/video conference line for Roku representatives who may not be able to attend the table read in-person - -#### 4.2.3 Camera test milestone - -* The Director, Director of Photography and/or producing team should oversee the camera test -* Please provide scratch framing mocks or test storyboard compositions -* It can be a “slap-comp sequence” or “center-punching sequence,” generated by the Editor or Assistant Editor -* Ideally this is sent prior to commencement of principal photography. If that isn’t possible, within the first two days of shooting or rehearsal -* Your Roku Post Manager will create a specific folder via [Frame.io](http://frame.io/) for uploading the camera test - -#### 4.2.4 Production meetings - -Roku Production will attend in person or via dial-in. It is asked that a phone dial-in be made available for all participating Roku departments. - -### 4.3 Internal ad sales needs - -As the The Roku Channel is 100% ad supported, we will reach out prior to commencement of principal photograpy to discuss capturing a very simple, straight forward message from talent about the show to be used internally only. - -* This is a very simple video, straight to camera, not color corrected, for internal use only. -* Roku will manage all aspects of the content (i.e. wording). This should take no more than 10-20 minutes to capture. -* For example, talent talking straight to camera says: “Hey, I’m TBD, coming to you live from the set of _insert Show Title here_ streaming soon on The Roku Channel!” - -### 4.4 Cost report requirements - -Please confirm with your Roku Production Executive the cadence in which cost report packages are submitted and to find out if Hot Costs will be a requirement for your project. Cost Report packets will be required throughout all phases of production, using industry standard software. Please use the following when submitting cost reports: - -* The cost report should reflect the Approved Production Costs, do not include the Premium (if applicable) -* The approved budget column must match the amounts and chart of accounts of the budget submitted and approved by Roku Production -* Cost report must include the following columns: actuals to date, committed costs, total costs, estimate to complete, estimated final costs, approved budget and variance (over/under) -* In the event of approved breakage, the approved breakage amount must appear in an approved overage column in the cost report. Cost report software must have this capability. -* Fringes should be per category to match the approved budget -* No negative ETC’s -* Cost report to be accompanied with general ledger, trial balance, purchase order log, and variance report -* If applicable - Please reflect all VAT tax in the Cost Report and flag those costs the General Ledger within the naming convention “VAT” -* Movement between budget accounts in an amount less than $35,000 is permissible. Amounts at or over $35,000 are subject to written approval by Roku Production -* Any movement from the following accounts require prior approval from Roku Production: - * Cast - * VFX - * Music - * Safety Costs - * Adjusting number of shooting days - -Roku will not be responsible for any amounts in excess of the Approved Budget without prior **written** approval by Roku Production. - -### 4.5 Staff & crew - -Roku Content, Production, and Post reserves customary approval of department heads, key creative, and key production staff. This can include, but is not limited to: - -* Showrunner, Casting Director/Company, Director, Director of Photography, Line Producer, Accountant, Post Supervisor and Editors -* Please submit credit, resume and/or reel (as applicable) to the appropriate Roku Content, Production, or Post contacts -* Please do not put any production hires on “pay or play” deals without prior **written** approval from Roku Business Affairs -* Outside production counsel must be experienced and qualified based on the nature of the program -* Please notify Roku Production if you are engaging an Intimacy Coordinator - -### 4.6 Covid-19 - -Roku follows the guidance of the AMPTP and local regulations when it comes to Covid-19 health and safety guidance. Please work with Roku Production if you have any questions. - -## 5. Finance - -### 5.1 Payments - -* Cash Flow or Milestone Payment Approval and funding occurs after all the Conditions Precedent have been met and the official greenlight / budget approval email has been sent by Roku Production; including but not limited to, receipt and approval of COIs -* If applicable, Cash Flow Template will be provided Roku Production Finance -* Milestone payment schedule should match terms of your closed deal and approved budget -* Submit milestone payment schedule to Roku Production Finance and cc your Roku Production Executive for review and approval - * Include dates, percentage, and amounts -* Premium Fee (if applicable), Breakage, and Residuals/Buyouts can be listed, but should not roll up into the total milestone payments -* Any previously paid development costs will be drawdown from your first Milestone payment - -#### 5.1.1 Payment descriptions - -Please reference closed deal for contractual payment terms. Possible payment milestones and when to submit invoices for processing listed below: - -* Commencement of Pre-Production – Invoice due upon first day of pre-production -* Commencement of Principal Photography – Invoice due upon first day of principal photography -* Completion of Principal Photography – Invoice due upon last day of principal photography -* Commencement of Post – Invoice due upon start of post/editorial staff -* Delivery of First Rough Cut – Invoice due upon Roku’s receipt of first rough cut -* Complete Delivery / Complete & Final Delivery – Invoice due upon receipt and approval of all Roku Post Paper and Media Deliverables -* Premium – If applicable, due upon receipt and approval of all Paper Deliverables and Final Cost Report -* Audit - Reference closed project deal terms for audit language - -#### 5.1.2 Invoices - -All invoices should be sent via email to [roinvoices@roku.com](mailto:roinvoices@roku.com) - -When submitting invoices, the subject line should read “Project Name” | Invoice “Description” - -* For example: Best Show Ever | Invoice: December Cashflow - -Email must include: - -* Vendor Name -* Project Name -* Season # -* Invoice description (i.e., December Cash Flow or Commencement of Principal Photography) - -### 5.2 Changes to banking information - -If your banking information changes at any given point, Partners must send an email to [roinvoices@roku.com](mailto:roinvoices@roku.com) - -*Please note this email must come from an employee of the company or will not be accepted. - -The subject line should read “Vendor Name” | “Project Name” - UPDATED Banking Information - -The email must include: - -* Studio/ProdCo name - -* Project Name - -* What Banking Information has been updated - i.e. Routing or account or both - -* Attachment with updated information on company letter head - -* Contact information for the point person: Name and phone number - -Please note, AP will need to verify validity with a phone call to the point person noted above. - -Sample email below: - -_Hello,_ - -_This email is to let you know we "INSERT COMPANY/VENDOR NAME" have updated routing and/or account information for the project currently known as "INSERT PROJECT NAME". Please see attached updated information._ - -* _TBD Studio_ -* _Project Title_ -* _Updated routing number attached (or updated account number attached)_ -* _Contact: TBD at xxx.xxx.xxxx_ - -Once AP confirms the update has been made, Production Finance will let you that you may submit your invoices. - -Important Notes: - -* Roku requires 1 week to amend in the system. -* Invoice(s) may be submitted no earlier than 1 week from any bank change requests. -* Invoice(s) must be submitted no later than EOD Thursday to potentially make the following week pay run. - -### 5.3 Premium calculation - -Please refer to your agreement to determine if a Premium fee is applicable. If so, please see below. - -* Calculate your premium with applicable exclusions as per your closed deal and include the Premium amount on the Budget Assumption Page -* If applicable, please calculate your premium with applicable exclusions as per your closed deal and include the estimate on the Budget Assumptions Page -* Although the Premium Fee is part of the overall fee, it should not be a line item in the budget - -### 5.4 Residual calculation - -The Roku Channel is a free to consumer ad supported platform (AVOD). Roku asks that Partners calculate the estimated residuals, again **please be mindful of The Roku Channel’s AVOD status**. - -* Check the definition of “accountable receipts” or “distributor’s gross” with the applicable guild -* Include the project residual estimate on the Budget Assumptions Page -* Residuals and/or Buyouts should **not** be a line item in the budget - * For purposes of calculating a rebate, if you need to include buyouts in your budget please discuss with Roku production -* Roku may request an updated residual estimate prior to closing out the project - -Please check with your Roku Production Executive if this applies to this project. - -### 5.5 Overages & breakage - -Roku will not be responsible for any overages. Production spend over and above the Approved Budget is never authorized without written approval from Roku Production (talent fees to be approved by Roku BA as well). If there is a request made by Roku that materially changes the creative elements or delivery of the project it is the responsibility of the Prod Co/Studio to reach out to Roku Production to discuss the financial implications **before** any decisions/changes are made. - -* Approved talent breakage is paid 50% upon commencement of principal photography, 50% on the completion of principal photography -* Fringe is paid on actuals which is typically in the last 50% payment or later -* If circumstances call for non-talent related breakage (i.e “Other” breakage) this payment is held until Roku Production receives and vets the final cost report -* Underages will offset approved breakage, unless approved in writing by Roku Production - -### 5.6 Close out - -In order to start the project close out process Roku must receive and approve all media and paper deliverables including the final cost report. Please follow the below when submitting your final cost report: - -* For a cost report to be considered finalized all Purchase Orders’s and ETC’s should be zeroed out unless agreed to in writing by Roku Production -* When sending through your final cost report packet, please note “FINAL Cost Report” in the subject line and confirm in the body of the email that all costs for the project are accounted for -* In the case of open Purchase Orders (e.g., Music Rights) Roku requires backup for all pending expenses before approving the final cost report -* When Roku Production confirms the final cost report is approved, Roku Finance will release the final payment (e.g. Production Company fee) - -### 5.7 Audit - -Please reference the closed deal regarding Audit election and timelines. - -* Roku will notify Partner in writing as to whether it intends to conduct an audit -* Roku Production Legal will provide Partners with the “Roku Audit Requirements". -* Audit Requirements Document will elaborate on the following: - * Non-reimbursable expenses unless previously approved - * Overages/Breakage - * Required documentation - -**PLEASE NOTE:** The Audit holdback payment will not be released until the audit is complete or waived. In the event Roku elects not to proceed with an audit: - -* You will be notified by Roku Production if there will be no audit - -* If the audit is waived, the Audit Holdback payment will be released upon reconciliation of final cost report and submission of the final invoice - -### 5.8 Roku marketing / publicity - -You will be introduced to Roku Marketing during or following the production kick-off call. - -Unless otherwise discussed and approved by Roku Production, all Marketing and PR costs are expected to be excluded from the budget. - -There may be circumstances when Roku requests assistance with marketing efforts. In the event Roku pre-approved any marketing expenses (i.e., unit photography, behind the scenes, hair and make-up, etc.) please review the below: - -* Marketing invoices should be sent to your Roku Marketing contact -* Marketing expenses should not be included as part of the series budget -* Marketing expenses should not be included as an expense in the cost report - -## 6. Production legal - -Prior to creating content for exhibition on The Roku Channel, please review the Roku Production Legal Guidelines below with your legal counsel. Reach out to Roku Production Legal if there are any questions or concerns. - -### 6.1 Roku production legal guidelines - -The Roku Production Legal Guidelines will cover the topics listed below. You can review the complete legal guidelines via the link sent to you. If you do not have it, please reach out to your Roku Production point. - -* Guilds/Unions -* Clearances -* Integrations/Sponsorships/Trade-Outs -* Cast Notices -* Nudity & Sex Scenes -* Talent Publicity and Promotion -* Risk & Safety -* Intimacy Coordinators -* Safety/Respect in the Workplace -* Music (approved PRO's) - -### 6.2 Insurance - -We rely on our production Partners to acquire the appropriate coverage as deemed necessary for each production. When binding your coverage please ensure it satisfies all of Roku’s insurance requirements with the exception of Workers’ Compensation/Employer’s Liability, Owned Automobile, Guild Travel Accident (if your production is union) and any local foreign compulsory coverage(s) (such as auto liability) which are collectively the responsibility of the production company. - -#### 6.2.1 Certificates of insurance - -Certificates of insurance (COIs) should be bound and sent to Roku Production and Production Legal prior to the commencement of any production activities. - -Below is list of COIs that may be required by Roku. This information along with coverage limits for this project shall be provided by Roku Production Legal. - -* Errors & Omissions -* General Liability -* Auto Liability -* Statutory Workers Compensation Coverage -* Umbrella/Excess -* Entertainment Package -* Applicable Collective Bargaining Agreement/Guild Travel Accident Coverage -* Foreign General Liability -* Cast Insurance - * Necessary cast members should be declared so they are eligible for cast insurance. - * Please discuss with Roku Production Legal whether your talent needs to be declared separately for Cast Insurance Coverage; and additionally, whether accident-only or full coverage would be preferable. -* High-Hazards & Special Risk Coverage (i.e., aircraft/watercraft etc.) - * There may be special risks associated with your project. This includes but is not limited to stunts, firearms, minors, pyrotechnics, precision driving, aircraft, drones, watercraft, railroads, foreign activities, animals, or any unusual or hazardous exposures and/or conditions involving either cast or crew. Special Risk Coverage may be required for your production, please budget accordingly. - -Roku must be named as an additional insured. Please use the following for issuing COIs to Roku: - -Purple Tag Originals, LLC -1173 Coleman Avenue -San Jose, CA 95110 - -Under “Description” on COIs, please list: - -Purple Tag Originals, LLC, its parent, its subsidiaries and affiliates and their respective officers, directors, agents and employees, as now or hereafter may exist and any other persons or entities as Roku may designate to Produce from time to time. - -Please inform Roku Production and Production Legal in writing, of any claims, threats of claims, suits, damage to property or any other loss. Roku Production will need to be updated throughout the claim process and any receipts that will offset production costs. - -### 6.3 Music - -Roku distributes content worldwide. Music should be cleared in perpetuity (or for licensed projects, the full length of the license), and allow for in-contect promotional use, unless approved in writing by Roku Production Legal. Please source music that is covered by the following PROs: BMI, ASCAP, SESAC, and GMR. - -Please reach out to your Roku Production Executive with specific questions or if there are cost implications above and beyond what is in the budget to license per the aforementioned guidelines. - -### 6.4 Content takedown request - -We understand there may be occasions when content needs to be removed from The Roku Channel (e.g., 3rd party rights issues, legal orders, PR concerns). In the event content needs to be removed, please email Roku Production and Production Legal. - -We ask that you provide the following information in the body of your email request: - -* The episode # and title -* The specific reason for the removal request (e.g., "wrong photo included in opening shot," "music was not cleared properly”) -* A point of contact along with email and phone number to call for any follow up questions -* An ETA for delivery of a replacement episode - * Ideally when requesting that content be removed from the Roku eco-system, you will be able to provide a replacement episode ASAP. If this is not possible (or deemed not necessary based on the content), Roku will address on a case-by-case basis - -## 7. Post - -Please review the Roku Scripted Media Delivery Specifications for a comprehensive breakdown of all post workflows and media deliverables. The document can be found via the “Welcome to Roku Production” site or the Hub in the Post – Scripted folder. - -Roku’s approved platform for dailies, rough cut release, and final archive is [Frame.io](http://frame.io/), which Roku provides free of charge to our production partners. All content sent to Roku for review needs to be shared via [Frame.io](http://frame.io/). - -### 7.1 Music cue sheets - -Music Cue Sheets are required for all projects. Please use the cue sheet template found on the ASCAP website linked [here](https://www.ascap.com/help/royalties-and-payment/cue-sheets) or similar cue sheet template when submitting to Roku. The ASCAP template is also available via the Hub in the Production Legal – Scripted folder. - -Upload completed cue sheets to the Hub. If you have specific questions about Roku requirements for Music Cue Sheets, please contact Sydnee Grossberg at [sgrossberg@roku.com](mailto:sgrossberg@roku.com). - -## 8. Paper deliverables - -Roku uses a Deliverables Hub (“Hub”) to receive and retain specific production documents. The Hub is project specific and will serve as the portal for key paper deliverables. Please remember the materials and folders are confidential and may not be shared beyond authorized parties. With a few exceptions, the Hub is used in lieu of emailing various Roku teams’ relevant documentation. - -Prior to pre-production you will receive an email with instructions for accessing the Hub. - -Due to the **confidential** nature of the required paper deliverables, access to the Hub will be limited to four (4) key project personnel. Only those who are responsible for uploading deliverables noted in [Section 8.1](#81-required-paper-deliverables), should have access. - -### 8.1 Required paper deliverables - -Productions should upload documents to the Hub on an ongoing basis throughout all phases of production, starting with pre-production and concluding with uploading final documents during wrap. - -Below you’ll find a list of **paper** deliverables for Production, Post, and Production Legal. Please be aware, this list is subject to amendment (within reason) at any time. Make sure to follow the specific instructions for each document and upload accordingly. Please note other departments may have additional required deliverables. - -#### 8.1.1 Production - -* Call Sheets & Maps (upload at the same time as distribution to crew) -* Cast Lists (all approved and final versions) -* Daily Prep Schedules -* Deliverables Checklist (completed -* DOOD’s (all approved and final versions) -* One Liners (all approved and final versions) -* Outlines & Scripts (all approved and final versions) -* Production Reports (Prelim no later than 24 hours after shoot | Approved when available) -* Script Supervisors Continuity Breakdowns -* Set Status Reports (First Shot, Lunch, Wrap) -* Shooting Schedule -* Staff & Crew Lists (all approved and final versions) -* Vendor List -* Production Calendar (all approved and final versions) - -#### 8.1.2 Post - -* Post Calendar (all approved and final versions) -* As Broadcast Scripts -* CC/Sub/FN Files -* Episodic Delivery Checklist -* Final Post Contact List -* Final Vendor List -* Font Memo -* Ingest Metadata Spreadsheet -* QC Reports -* Segment Rundown -* Text Spotting List (TSL) -* Credits (also vetted by Business Affairs) -* Music Cue Sheets (vetted by Production Legal) - -#### 8.1.3 Production legal - -* Ad/Promo Restrictions -* Fair Use Grid (if appliable) -* Insurance Certificates - GL & E&O -* Pence Document -* Tax Incentive Registration, Certificate, Evidence of Sale/Transfer (if applicable) -* Title Report & Legal Opinion -* Workers Comp -* Talent Agreement(s) -* Location Agreements -* Guild & Union Documentation -* Employment Agreements - -#### 8.1.4 Public relations/marketing - -* Approved Bios -* Still Photography - -### 8.2 Deliverables checklist - -On the Hub you will find a Deliverables Checklist. The checklist is considered part of your paper deliverables. Only mark items as complete once the final versions are uploaded. If an item is not applicable (“N/A”), please upload a word document that says N/A and a short explanation as to why it is not applicable to your production. You may then mark that item complete on the checklist. - -Email Roku Production once all items are delivered and the checklist is filled out completely. Once final delivery is received and approved, access to the Hub will be removed. - -For questions or concerns reach out to Roku Production at [scrprod@roku.com](mailto:scrprod@roku.com). - -### 8.3 Naming conventions - -All Roku projects have a unique Project Title ID (PTID). You must follow specific naming conventions for the files to be considered acceptable. Examples of how each file should be named can be found on the Hub in the Production – Scripted folder. - -If items are not delivered correctly, they will not be accepted. Please do not add or remove folders. If you have questions or can't find specific folders, please reach out to Roku Production. - -### 8.4 Guidelines and templates - -There is a “Guidelines & Templates'” section located on the Hub. Here you will find folders containing key documents in relation to each department (Post, Production, and Production Legal).  - -#### 8.4.1 Post – scripted folder - -* Scripted Post Media Delivery Specifications -* Credits Approval Form -* Episodic Delivery Checklist -* Ingest Metadata Template -* Post Grid Template -* Preferred Vendor List -* Segment Rundown Template -* Text Spotting List - -#### 8.4.2 Production legal – scripted folder - -* Ad Promo Template -* Insurance Guidelines -* Music Cue Sheet Template - -#### 8.4.3 Production – scripted folder - -* Scripted Production Guidelines -* Chart of accounts (COA) diff --git a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/_order.yaml b/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/_order.yaml deleted file mode 100644 index 4a721e1a..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/_order.yaml +++ /dev/null @@ -1,2 +0,0 @@ -- unlocking-svod-content-as-free-fvod -- avails-and-committed-title-list-field-definitions diff --git a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/avails-and-committed-title-list-field-definitions.md b/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/avails-and-committed-title-list-field-definitions.md deleted file mode 100644 index b5824902..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/avails-and-committed-title-list-field-definitions.md +++ /dev/null @@ -1,421 +0,0 @@ ---- -title: Avails and Committed Title List - Field Definitions -excerpt: Field-by-field reference for every column in the Avails/CTL sheet. -deprecated: false -hidden: true -metadata: - robots: index ---- -## Overview - -This page is the field-by-field reference for the Avails and Committed Title List (CTL) Excel sheet. For process, policy, and submission rules, see [Avails and Committed Title Lists for The Roku Channel](#avails-and-committed-title-lists-for-the-roku-channel). - -Fields are grouped into: **Availability Attribute Fields** (License Type, Territory, Language, dates) and **Title Metadata Fields** (descriptive and identifying information). - -*** - -## Availability Attribute Fields - -Each unique combination of these attributes, bound by a start and end date, represents **one availability window** and should occupy its own row. - -### Content Partner - -Name of the content owner/studio/network availing the content to The Roku Channel. - -| Type | Accepted Values | Required | -| ------ | ----------------------- | -------- | -| string | Example: Roku Originals | Required | - -### Content Type - -The content type of the program: - -| Value | Definition | -| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `episode` | TV program structured in a series/season/episode hierarchy. | -| `movie` | Full-length, stand-alone program not intended to nest in a series/season/episode hierarchy, exceeding roughly 15 minutes runtime — includes stand-alone TV specials. | -| `shortForm` | Short-duration, stand-alone program not exceeding roughly 15 minutes runtime, not intended to nest in a series/season/episode hierarchy. | - -| Type | Accepted Values | Required | -| ---- | ------------------------------- | -------- | -| enum | `movie`, `episode`, `shortForm` | Required | - -### License Type - -Available distribution rights for the content. Multiple rights **may** be submitted on the same row, provided all other availability attributes are identical across them. The License Type **must** adhere to the distribution rights defined in the agreement signed with The Roku Channel. - -| Value | Definition | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `AVOD` | Ad-Supported Video on Demand — plays free for all users, with advertisements. | -| `SVOD` | Subscription Video on Demand — plays for users with an active subscription. _Premium Subscriptions Partners only._ | -| `FVOD` | Free Video on Demand — plays free for all users, without monetization. FVOD windows must fall within an active SVOD window. _Premium Subscriptions Partners only._ | -| `Linear OTT` | Over-the-top linear streaming rights, for inclusion on Roku-built channels. | - -| Type | Accepted Values | Required | -| ---- | ------------------------------------ | -------- | -| enum | `AVOD`, `SVOD`, `FVOD`, `Linear OTT` | Required | - -### Excluded Rights - -Distribution exclusions for the content, using the same value definitions as [License Type](#license-type) above. Multiple exclusions **may** be submitted on the same row, provided all other availability attributes are identical. - -| Type | Accepted Values | Required | -| ---- | ------------------------------------ | -------- | -| enum | `AVOD`, `SVOD`, `FVOD`, `Linear OTT` | Optional | - -### Start Date - -Start of availability. If the content has no set start date, `"open"` is acceptable. Start dates without a time value assume a relative start of `12:00:00 AM` on the date listed. - -| Type | Accepted Values | Required | -| ----------- | ---------------------------------------------- | -------- | -| date string | `YYYY-MM-DD`, `YYYY-MM-DDTHH:MM:SS`, or `open` | Required | - -### End Date - -End of availability. If the content has no set end date, `"open"` or `"end of term"` are acceptable. End dates without a time value assume a relative end of `11:59:59 PM` on the date listed. - -| Type | Accepted Values | Required | -| ----------- | ------------------------------------------------------------- | -------- | -| date string | `YYYY-MM-DD`, `YYYY-MM-DDTHH:MM:SS`, `open`, or `end of term` | Required | - -### Language - -The language(s) made available to users. Values **must** conform to a supported [language code](#language-codes). Multiple language/localization-type combinations **may** be provided on the same row, provided all other availability attributes are identical. When multiple languages are provided, each **must** include its localization type, appended with a colon: - -| Localization Type | Meaning | -| ----------------- | ------------------------------------------------------------------------------------ | -| `dub` | The language property refers to an audio track (applicable to original voice audio). | -| `sub` | The language property refers to a subtitle track. | -| `subdub` | Includes both subtitles and dubbed audio. | -| `any` | Includes any combination of subtitles or dubbed audio, whichever is available. | - -| Type | Accepted Values | Required | -| ---- | ------------------------------------------------------ | -------- | -| enum | Examples: `en:dub`, `fr:sub`, `de:subdub`, `es-mx:any` | Required | - -### Localization Type - -Applies **only** when a single language code is provided in the [Language](#language) column (i.e., without an inline `:type` suffix) — this column then carries the localization type separately. Uses the same values as the inline suffix above (`dub`, `sub`, `subdub`, `any`). - -> **Note:** the relationship between this column and the inline `language:type` syntax can be easy to miss — use the inline suffix when providing multiple languages on one row, and use this separate column only when providing a single language without a suffix. - -| Type | Accepted Values | Required | -| ---- | ----------------------------- | ---------------------------------------------------------------- | -| enum | `sub`, `dub`, `subdub`, `any` | Required when providing a single language in the Language column | - -### Excluded Languages - -The language(s) that must **not** be made available. Values **must** conform to a supported [language code](#language-codes). Multiple exclusions **may** be provided on the same row, provided all other availability attributes are identical. - -| Type | Accepted Values | Required | -| ---- | ------------------- | -------- | -| enum | Example: `en`, `de` | Optional | - -### Territory - -[ISO 3166-1 alpha-2](https://www.iso.org/obp/ui/#search) country code for the territory where the content may be available. Multiple territories **may** be submitted on the same row, provided all other availability attributes are identical. - -| Type | Accepted Values | Required | -| ---- | ---------------------------------------------- | -------- | -| enum | Example: `US`, `CA`, `GB`, `MX`, `LATAM`, `WW` | Required | - -### Excluded Territories - -[ISO 3166-1 alpha-2](https://www.iso.org/obp/ui/#search) country code for territories where the content should **not** be available. Multiple territories **may** be excluded. - -| Type | Accepted Values | Required | -| ---- | ------------------- | -------- | -| enum | Example: `DE`, `FR` | Optional | - -*** - -## Title Metadata Fields - -### Series Title - -Title of the series, for episodic TV content. Include **only** the name as it should appear on platform — no non-title parentheticals (e.g., `(Classic)`, `(1987)`, `(Season #)`). - -| Type | Accepted Values | Required | -| ------ | ----------------- | --------------- | -| string | Example: Die Hart | Required for TV | - -### Series ID - -Immutable, unique identifier for a TV series. Generated/supplied by the partner; **should** match the ID provided in the metadata at ingest. - -- **Must not** be the same as the unique episode ID. -- **Must** be included with, and consistent across, all episodes of a series. -- **Must not** exceed 50 characters. -- Alphanumeric characters, hyphens, and underscores only. - -| Type | Accepted Values | Required | -| ------ | ---------------------- | --------------------------------------- | -| string | Example: `diehartshow` | Required for TV. 50 characters maximum. | - -### Title - -Title of the movie, episode, or shortForm video. Include **only** the name as it should appear on platform — no non-title parentheticals. - -| Type | Accepted Values | Required | -| ------ | --------------- | -------- | -| string | Example: Pilot | Required | - -### Title ID - -Immutable, unique identifier for a movie, episode, or shortForm video. Generated/supplied by the partner; **should** match the ID provided in the metadata at ingest, to aid tracking from Avails/CTL submission through publication. - -- **Must not** exceed 50 characters. -- Alphanumeric characters, hyphens, and underscores only. - -| Type | Accepted Values | Required | -| ------ | ---------------------- | -------------------------------- | -| string | Example: `dieharts1e1` | Required. 50 characters maximum. | - -### Season Number - -Season number for the episode. **Must** follow the original broadcast/distribution sequence and be a number — letters are not allowed. - -| Type | Accepted Values | Required | -| ------- | --------------- | --------------- | -| integer | `#`, `##`, … | Required for TV | - -### Episode Number - -Episode number. **Must** follow the original broadcast/distribution sequence within a season and be a number — letters are not allowed. **Do not** use production numbers (e.g., `201` for season 2, episode 1). - -| Type | Accepted Values | Required | -| ------- | --------------- | --------------- | -| integer | `#`, `##`, … | Required for TV | - -### Country of Origin - -The primary country where the content was produced, and where the main creators, crew, and producers are established. Must conform to a supported [ISO 3166-1 alpha-2](https://www.iso.org/iso-3166-country-codes.html) code. **Include one country only.** - -| Type | Accepted Values | Required | -| ---- | ------------------------- | --------------------------- | -| enum | Example: `US`, `CA`, `DE` | Required. One country only. | - -### Original Spoken Language - -The language in which the content was produced — usually the primary language of the country of origin, and the language that synchronizes with performers' mouth movements. Must conform to a supported [language code](#language-codes). **May** include multiple languages, comma-separated. - -| Type | Accepted Values | Required | -| ---- | ------------------------- | -------- | -| enum | Example: `en-us`, `fr-ca` | Required | - -### Run Time - -Runtime of the content, in whole minutes. **Minimum runtime is 1.** - -| Type | Accepted Values | Required | -| ------- | --------------- | -------- | -| integer | Example: `22` | Required | - -### Format - -Highest video resolution available for the content. All lower resolutions are assumed to also be available. - -| Type | Accepted Values | Required | -| ---- | ----------------- | -------- | -| enum | `SD`, `HD`, `UHD` | Required | - -> Roku does not currently support playback of UHD/4K content, but can accept UHD/4K as a source for future playback availability. - -### DBO (Domestic Box Office Gross) - -| Type | Accepted Values | Required | -| ------ | --------------------- | -------- | -| string | Example: `$2,000,000` | Optional | - -### Closed Captioning - -Whether captions are included with the content, per [FCC guidelines](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming). If captions are **not** included, a Caption Exemption value **must** be provided. - -| Type | Accepted Values | Required | -| ------- | --------------- | -------- | -| Boolean | `true`, `false` | Required | - -### Caption Exemption - -**US avails only.** FCC exemption code for the closed caption requirement. - -| Code | Definition | -| ---- | ------------------------------------------------------------------------------------------------------------------------------------- | -| 1 | The content has never aired on television in the United States. | -| 2 | The content has only aired on television in the United States without captions. | -| 3 | The content has not aired on television in the United States with captions since September 30, 2012. | -| 4 | The content does not consist of full-length video programming. | -| 5 | The content does not fall within a category of online programming that requires captions under FCC regulations (47 C.F.R. § 79.4(b)). | -| 6 | The FCC and/or U.S. Congress has granted an exemption from captioning requirements for this content. | - -| Type | Accepted Values | Required | -| ---- | ---------------------------- | ---------------------------------------- | -| enum | `1`, `2`, `3`, `4`, `5`, `6` | Required if Closed Captioning is `false` | - -### Audio Description - -Whether an audio description track is included. [Audio description](https://www.fcc.gov/audio-description) (also called video description) is narrated description of a program's key visual elements, inserted into natural dialogue pauses — making content more accessible to blind/visually impaired viewers. If required for the content and not provided, an Audio Description Exemption **must** be included. - -> Audio description is not currently required for all content by the FCC, but Roku prefers to make content as accessible as possible, and this may become a requirement in the future. - -| Type | Accepted Values | Required | -| ------- | --------------- | -------- | -| Boolean | `true`, `false` | Optional | - -### Audio Description Exemption - -Exemption reason for not providing an audio description track where required. - -| Type | Accepted Values | Required | -| ------ | --------------- | -------- | -| string | — | Optional | - -### Original Release Date - -Original date the content was first made available in any presentation. **Must** include the year of release at minimum. - -| Type | Accepted Values | Required | -| ----------- | ---------------------- | -------- | -| date string | `YYYY-MM-DD` or `YYYY` | Required | - -### Genre - -Genre classification of the content. **May** provide multiple genres, comma-separated. - -| Type | Accepted Values | Required | -| ---- | --------------------- | -------- | -| enum | See [Genres](#genres) | Required | - -### Tags - -Freeform field for keywords/tags/categories used to surface content on The Roku Channel UI. See the [Best Practices: Content Tags and Metadata](https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md) page for guidance. - -| Type | Accepted Values | Required | -| ------ | ------------------------------------------ | -------- | -| string | Example: `exciting`, `timely`, `political` | Optional | - -### Rating Source - -The rating system applied to this edit of the title within the territory of avail. **Must** be formatted and paired with Rating Value per [Ratings](#rating-values-by-rating-system-and-country). - -| Type | Accepted Values | Required | -| ---- | ---------------------------------------------------------- | -------- | -| enum | See [Ratings](#rating-values-by-rating-system-and-country) | Optional | - -### Rating Value - -The rating value within the specified Rating Source. **Must** be formatted and paired with Rating Source per [Ratings](#rating-values-by-rating-system-and-country). - -| Type | Accepted Values | Required | -| ---- | ---------------------------------------------------------- | -------- | -| enum | See [Ratings](#rating-values-by-rating-system-and-country) | Optional | - -### Kids-Directed - -Indicates the content is intended for young/family audiences. **Must** adhere to the [Kids-Directed Content Policy](#kids-directed-content-policy). - -| Type | Accepted Values | Required | -| ------- | --------------- | -------- | -| Boolean | `true`, `false` | Optional | - -### Recommended Age Group - -When Kids-Directed is `true`, a recommended age range **may** be supplied. **Only one** allowed. - -| Value | Definition | -| ------------- | ---------------------- | -| `ages_1-3` | Viewers ages 1–3 | -| `ages_4-6` | Viewers ages 4–6 | -| `ages_7-9` | Viewers ages 7–9 | -| `ages_10plus` | Viewers ages 10 and up | - -| Type | Accepted Values | Required | -| ---- | ------------------------------------------------- | -------------------------------------------- | -| enum | `ages_1-3`, `ages_4-6`, `ages_7-9`, `ages_10plus` | Optional. Used when Kids-Directed is `true`. | - -### Main Cast - -Top-billed cast, comma-separated, in `Firstname Lastname` format. - -| Type | Accepted Values | Required | -| ---- | ------------------------------------ | -------- | -| list | Example: `Kevin Hart, John Travolta` | Required | - -### Synopsis - -A short synopsis of the content, for selection purposes. **Not to exceed 250 characters.** - -| Type | Accepted Values | Required | -| ------ | --------------- | -------- | -| string | — | Required | - -### External ID Source - -Source entity for the external ID provided. **May** include IDs from multiple sources, comma-separated, with the source indicated via a colon. - -| Value | Definition | -| ------ | ------------ | -| `TMS` | Gracenote ID | -| `IMDb` | IMDb ID | -| `Wiki` | Wikipedia ID | - -| Type | Accepted Values | Required | -| ------ | ----------------------------------------------------------------------------------------------------- | -------- | -| string | Example: `TMS, IMDb, Wiki`. Multi-source example: `TMS:E12345678, IMDb:tt12345678, Wiki:benson_s1_e1` | Optional | - -### Series External ID - -Third-party identifier of the series. - -| Type | Accepted Values | Required | -| ------ | --------------------------- | -------- | -| string | Example: `diehartshowExtId` | Optional | - -### External ID - -Third-party identifier of the content. - -| Type | Accepted Values | Required | -| ------ | --------------------------- | -------- | -| string | Example: `dieharts1e1ExtId` | Optional | - -### Screener Link - -URL to stream or download a screener for the content, to aid content selection. Any required password should also be included. - -| Type | Accepted Values | Required | -| ------ | ------------------------------------------------------ | -------- | -| string | Example: `https://urlLinkToScreener`, password: `1234` | Optional | - -### Exclusive - -Indicates the content is available **exclusively** on The Roku Channel. - -| Type | Accepted Values | Required | -| ------- | --------------- | -------- | -| Boolean | `true`, `false` | Optional | - -### Notes - -Freeform field for additional avail notes — for linear content, this includes run/telecast restrictions or any other specifics not captured elsewhere in the Avails/CTL. - -| Type | Accepted Values | Required | -| ------ | --------------- | -------- | -| string | — | Optional | - -### Merchant of Record - -Name of the entity to which financial transactions should be attributed, if other than the listed Content Partner. - -| Type | Accepted Values | Required | -| ------ | --------------- | -------- | -| string | Example: Roku | Optional | - -### Day Parting - -**Linear content only.** Any day-parting rules for the content. - -| Type | Accepted Values | Required | -| ------ | --------------- | -------- | -| string | — | Optional | \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/index.md b/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/index.md deleted file mode 100644 index ef9f97b8..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/index.md +++ /dev/null @@ -1,331 +0,0 @@ ---- -title: Avails and Committed Title List specifications -deprecated: false -hidden: false -robots: index ---- - -## Avails and Committed Title Lists for The Roku Channel - -Roku requests an initial launch list of titles/episodes/shortForm videos in the current library that are available to Roku at the time of onboarding and a schedule when the content will be refreshed. For ongoing production, Roku requests that a Committed Title List be provided **60** days prior to licensing window start and the content be delivered in accordance with [The Roku Channel Ingest Specification](https://go.roku.com/ingest-ovp-specs) at least 30 days before licensing window start to allow ample time for selection, ingest, processing, and QC of the content before it goes live on The Roku Channel. - -### Roku content policies - -#### Ad-supported content on The Roku Channel - -The Roku Channel is looking for ad-supported content that is appropriate for our users and advertisers – for example, The Roku Channel does not want ad-supported content that contains excessive nudity or extreme/graphic violence. Please use your best judgement when sharing content. If an asset is questionable, please find an alternative to share. We reserve the right to remove or reject any content that we deem inappropriate. - -#### Kids directed content policy - -“Kids-Directed Content” is content that either: (i) is directed to children as defined by the applicable law of the jurisdiction in which the content is shown (e.g., The Children's Online Privacy Protection Act); or (ii) was made for viewing primarily by children within the jurisdiction in which the content is shown. - -- You may NOT submit or distribute Kids-Directed content without Roku’s express written approval. -- Roku must be made aware of the intent to submit or distribute Kids-Directed content via submission of the avails and Committed Title List document populating the columns outlined below: - - Kids-Directed column must be populated with the value "true" - - The Rating Source column must be populated with a valid Rating Source - - The Rating Value column must be populated with a valid parental [Rating](#ratings) from that Rating Source - - “UNRATED” and “Not Rated” are not acceptable ratings for kids directed content - -##### Optional age demographics tags - -Additional tags can be provided to help categorize kids-directed content around age demographics. Please use these tags to define different content directed age groups: - -| Ages | Tags | -| -------- | ----------- | -| Ages 1-3 | ages_1-3 | -| Ages 4-6 | ages_4-6 | -| Ages 7-9 | ages_7-9 | -| Ages 10+ | ages_10plus | - -### Avails - -“Avails” is short for availability. It refers to the list of available content for licensing or distribution. The avails list is shared with Roku to aid in understanding what content is currently available for acquisition or distribution. Avails typically include information about the titles, such as the title name, genre, duration, rights availability (e.g., exclusive or non-exclusive rights), and any other relevant details about the content. Avails should be sent to the Content Partnerships team ([trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com)) for Selections review. Once the Content Partnerships team has reviewed the Avails, they will provide the Avails sheet back with Selections marked for review and any revisions. The agreed-upon list of Selected content becomes the Committed Title List - -### Committed Title List: - -A “Committed title list” (CTL) is a comprehensive list of all the titles that have been committed and made available to Roku as agreed upon through the Selections process. Similar to avails, a CTL includes information about each title, such as the title name, genre, duration, and any other relevant details. CTLs are used for content management purposes and provide an overview of the committed content catalog from the content Partner. CTLs should be finalized for ingestion into Roku's Rights Management system at least 60 days prior to the start date of the titles in the list. The data provided in the CTL will control the availability of titles on The Roku Channel. - -*The descriptive metadata (Title, Synopsis, Genre, etc.) provided in the avails and/or title list will be used for selection purposes only. Descriptive metadata must be included at the time the content is delivered in accordance with [The Roku Channel ingest specifications](https://go.roku.com/ingest-ovp-specs).* - -### Availability windows - -An availability window is the length of time during which a title is viewable by a user on The Roku Channel. Availability windows can include several different attributes in a number of combinations. Each unique combination of attributes bound by a start and end time is considered its own availability window. Each availability window should be represented in the avails or Committed Title List on its own row. The availability attributes currently supported by Roku are: - -- License Type -- Territory -- Language - -#### Availability date and time - -Roku has the ability for content to display on-device and for user playback at a specific starting time. By default, content will go into window at 12:00 am (midnight) and expire at 11:59:59 pm in the users’ time zone. - -If content is to go live at a time other than midnight or expire at a time other than 11:59:59 pm, the license window start or end values in the inbound metadata must include the desired times. - -There are two types of specific time designations – relative and absolute. - -- Relative Time – a Saturday night premiere of a movie goes into window at 9pm local time for all users. A user in the Eastern Time Zone watches at 9pm but a user in the Pacific Time Zone, at the exact same moment (6pm PT), cannot watch that content. -- Absolute Time – a new episode of a series goes into window at 9pm Eastern and becomes immediately available across all time zones. A user in the Pacific Time Zone can watch the content at 6 pm local time. - - While time settings are dictated by the content owner, Roku will need the metadata as follows: - -- If the content has a relative start time, that time must be indicated in the ingest metadata and formatted as “yyyy-mm-ddThh:mm:ss” (2019-11-01T21:00:00) -- If the content has an absolute start time, that time must be indicated in the ingest metadata. The time must be presented as UTC time and formatted as “yyyy-mm-ddThh:mm:ssZ” (2019-11-02T01:00:00Z). -- In this example, 9 pm Eastern Time on November 1 is 1 am UTC (https://www.thetimezoneconverter.com) -- If the metadata arrives without a time, Roku will assume a relative start time of 12:00:00 am and a relative end time of 11:59:59 pm - -### Submitting Excel Avails/Committed Title Lists - -Avails must be submitted via email to [trcpartnersupport@roku.com](mailto:trcpartnersupport@roku.com) for selection review. Committed Title Lists must be finalized at least 60 days prior to the intended licensing window start date of the titles within the list. In certain cases we may be able to accept avails and Committed Title Lists via Aspera. Please reach out to your Roku representative for current delivery options. - -When submitting avails and Committed Title Lists via Excel workbook, all required fields must be populated. Roku has provided hints on row 2 of the Roku avails and Committed Title List template to highlight the required cells and any special formatting needed for each cell. Please refer to these hints when filling out the Roku avails and Committed Title List template. Other considerations when filling out the Roku Avails and Committed Title List Excel sheet include: - -- All data MUST begin on row 3. DO NOT DELETE THE HINTS ON ROW 2 -- Any formulas used must be converted to text prior to submission. Inclusion of a formula will result a rejection of the avails and Committed Title List sheet -- Do not link to external data or Excel workbooks. All data must be self contained within the Excel workbook delivered to Roku -- Do not add additional sheets to the workbook -- Do not add additional columns to the workbook -- Do not change any of the column header names -- Do not supply a value of “N/A” or “n/a”. Required cells should contain valid data and optional cells may be left blank -- Each row is considered a unique availability window for an episode/movie/shortForm video -- Do not leave a blank row between entries in a worksheet. The system will terminate processing at the first empty row -- Avails and Committed Title List sheets must be saved with .xlsx extension - -## Avails and Committed Title List sheet field definitions - -### Availability attribute fields - - -| **Field** | **Description** | **Type** | **Accepted Values** | **Required** | -| --- | --- | --- | --- | --- | -| Content Partner | Name of content owner/studio/network availing the content to The Roku Channel | string | Example:
Roku Originals | required | -| Content Type | Describes the content type of the program as defined below:
- **episode** - TV program that is structured in a series/season/episode hierarchy
- **movie** - Full length, long form, stand-alone program that is not intended to be nested in a series/season/episode hierarchy and exceeds roughly 15 minutes run time including stand-alone TV Specials
- **shortForm** - Short duration, stand-alone program that does not exceed roughly 15 minutes run time and is not intended to be nested in a series/season/episode hierarchy | enum | movie, episode, shortForm | required | -| License Type | Available distribution rights for the content. Multiple rights may be submitted on the same row so long as all availability attributes are identical across the rights listed. The License Type provided in the Avails or Committed Title List must adhere to the distribution rights for the content as it pertains to the agreement signed with The Roku Channel.
- **AVOD** – Ad-Supported Video on Demand. Video will play for free for all users and will contain advertisements
- **SVOD** – Subscription Video on Demand. Video will play for users with an active subscription. *Only to be used by Premium Subscriptions Partners on The Roku Channel*
- **FVOD** – Free Video on Demand. Video will play for free for all users without monetization. FVOD windows must fall within an active SVOD window. *Only to be used by Premium Subscriptions Partners on The Roku Channel*
- **Linear OTT** - Over-the-top linear streaming rights for inclusion on Roku-built channels | enum | AVOD, SVOD, FVOD, Linear OTT | required | -| Excluded Rights | Distribution exclusions for the content. Multiple exclusions may be submitted on the same row so long as all availability attributes are identical across the rights listed.
- **AVOD** – Ad-Supported Video on Demand. Video will play for free for all users and will contain advertisements
- **SVOD** – Subscription Video on Demand. Video will play for users with an active subscription. *Only to be used by Premium Subscriptions Partners on The Roku Channel*
- **FVOD** – Free Video on Demand. Video will play for free for all users without monetization. FVOD windows must fall within an active SVOD window. *Only to be used by Premium Subscriptions Partners on The Roku Channel*
- **Linear OTT** - Over-the-top linear streaming rights for inclusion on Roku-built channels | enum | AVOD, SVOD, FVOD, Linear OTT | optional | -| Start Date | Start of availability in YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS format. If the content has no set Start Date, “open” is an acceptable value. Start Dates without time values will assume a relative start time of 12:00:00 am on the Start Date listed | date string | YYYY-MM-DD, YYYY-MM-DDTHH:MM:SS, or open | required | -| End Date | End of availability in YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS format. If the content has no set End Date, “open” or “end of term” are acceptable values. End Dates without time values will assume relative end times of 11:59:59 pm on the End Date listed | date string | YYYY-MM-DD, YYYY-MM-DDTHH:MM:SS, open, or end of term | required | -| Language | The language(s) that will be made available to users of The Roku Channel. Language values must conform to one of the enumerated [supported language codes](#language-codes) . Multiple language/localizationType combinations may be provided on the same row so long as all availability attributes are identical across the languages listed. When multiple languages are provided, the localization type related to that language must be included by appending a colon (":") and the localization type as defined below.
- **dub** – indicates the language property refers to an audio track. Applicable to original voice audio
- **sub** – indicates the language property refers to subtitle
- **subdub** – includes both subtitles and dubbed audio
- **any** – includes any combination of subtitles or dubbed audio (whatever is available) | enum | Examples:
en:dub, fr:sub, de:subdub, es-mx:any | required | -| Localization Type | Applies to the Language column when only a single language code is provided. Indicates that the language property refers to either an audio track or a text track (subtitle). Localization Type would be “dub” for original voice audio. Valid values defined below:
- **dub** – indicates the language property refers to an audio track. Applicable to original voice audio
- **sub** – indicates the language property refers to subtitle
- **subdub** – includes both subtitles and dubbed audio
- **any** – includes any combination of subtitles or dubbed audio (whatever is available) | enum | sub, dub, subdub, any | required when providing a single language in the Language column | -| Excluded Languages | The language(s) that must not be made available to users of The Roku Channel. Language values must conform to one of the enumerated [supported language codes](#language-codes) . Multiple language combinations may be provided on the same row so long as all availability attributes are identical across the languages listed. | enum | Example:
en, de | optional | -| Territory | [ISO 3166-1 alpha-2](https://www.iso.org/obp/ui/#search) country code for the country or territory in which the content may be made available. Multiple territories may be submitted on the same row so long as all availability attributes are identical across the territories listed. | enum | Example:
US, CA, GB, MX, LATAM, WW | required | -| Excluded Territories | [ISO 3166-1 alpha-2](https://www.iso.org/obp/ui/#search) country code for the country or territory for which the content should NOT be made available. Multiple territories may be excluded. | enum | Example:
DE, FR | optional | - - -### Title metadata fields - - -| **Field** | **Description** | **Type** | **Accepted Values** | **Required** | -| --- | --- | --- | --- | --- | -| Series Title | Title of series for episodic TV content. Include only the name of the series as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, or video format. Examples: (Classic), (1987), or (Season #) | string | Example:
Die Hart | required for tv | -| Series ID | Immutable, unique identifier for a TV series. IDs are to be generated and supplied by the Partner for content that is availed and delivered to Roku. The IDs in the avails and Committed Title List document should match the IDs provided in the metadata at the time of ingest into The Roku Channel.
- Must not be the same as the unique episode ID
- Must be included with all episodes of a series
- Must be consistent for all episodes of a series
- Must not exceed 50 characters
- Allowable characters: alphanumeric characters, hyphens, and underscores only | string | Example:
diehartshow | required for tv
50 characters maximum | -| Title | Title of the movie, episode, or shortForm video. Include only the name of the content as it should appear on platform. Do not include non-title parentheticals such as indicator of original/remake, year of release, season, or video format. Examples: (Classic), (1987), (Season 1), or (HD) | string | Example:
Pilot | required | -| Title ID | Immutable, unique identifier for a movie, episode, or shortForm video. IDs are to be generated and supplied by the Partner for content that is availed and delivered to Roku. The IDs in the avails and Committed Title List document should match the IDs provided in the metadata at the time of ingest into The Roku Channel. This will aid in tracking the content throughout Roku’s pipeline from avails and Committed Title List submission through publication on The Roku Channel.
- Must not exceed 50 characters
- Allowable characters:
alphanumeric characters, hyphens, and underscores only | string | Example:
dieharts1e1 | required
50 characters maximum | -| Season Number | Season number for the episode. Must follow the original broadcast/distribution sequence of seasons and must be a number. Letters are not allowed | integer | #, ##, … | required for tv | -| Episode Number | Episode number. Must follow the original broadcast/distribution sequence of episodes within a season and must be a number. Letters are not allowed.
Do not use production numbers (e.g. 201 for season 2 episode 1) | integer | #, ##, … | required for tv | -| Country of Origin | Defines the primary country where the film was produced and where the main creators, crew, and producers are established. Value must conform to one of the supported country codes as defined in the [ISO 3166-1 alpha 2](https://www.iso.org/iso-3166-country-codes.html) list of 2-character country codes. Please include 1 country only | enum | Example:
US, CA, DE | required
1 country only | -| Original Spoken Language | Language in which the content was produced. This is usually the primary language of the country of origin and the language that synchronizes exactly with the movements of the performers mouths as they speak. Must conform to one of the enumerated [supported language codes](#language-codes) . May include multiple languages separated by commas. | enum | Example:
en-us, fr-ca
| required | -| Run Time | Runtime of the content in whole minutes. Minimum runtime is 1 | integer | Example:
22 | required | -| Format | Highest video resolution available for the content. All lower resolutions will be assumed* | enum | SD, HD, UHD | required | -| DBO | Domestic Box Office Gross | string | $2,000,000 | optional | -| Closed Captioning | Communicating if captions are included with the content per [FCC guidelines](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming) . If captions are not included with the content, a Caption Exemption value must be provided | Boolean | true
false | required | -| Caption Exemption | US avails only. FCC exemption for closed caption requirement. Allowable value and their definitions:
- The content has never aired on television in the United States.
- The content has only aired on television in the United States without captions.
- The content has not aired on television in the United States with captions since September 30, 2012.
- The content does not consist of full-length video programming.
- The content does not fall within a category of online programming that requires captions under FCC regulations (49 C.F.R. § 79.4(b)).
- The FCC and/or U.S. Congress has granted an exemption from captioning requirements for this content. | enum | 1, 2, 3, 4, 5, 6 | required if Caption Included is false | -| Audio Description** (see note below) | Communicating if an audio description track is included with the content. [Audio description](https://www.fcc.gov/audio-description) (also referred to as video description) is audio-narrated descriptions of a television program's key visual elements. These descriptions are inserted into natural pauses in the program's dialogue. Audio description makes television programming more accessible to individuals who are blind or visually impaired. If Audio Description is required for content, and is not provided, an Audio Description Exemption must be included. | Boolean | true
false | optional | -| Audio Description Exemption** (see note below) | Exemption reason for not providing audio description track where required. | string | | optional | -| Original Release Date | Original date content was first made available in any presentation. Must include year of release at a minimum | date string | YYYY-MM-DD or YYYY | required | -| Genre | Genre classification of the content. May provide multiple genres separated by comma | enum | See [Genres](#genres) for allowed values | required | -| Tags | Free form field to provide keywords, tags, categories, or keywords to be used to surface content on The Roku Channel UI. Please see our [Best Practices](https://developer.roku.com/trc-docs/video-on-demand/content-tags-and-metadata.md) page on how best to provide tags to The Roku Channel | string | exciting, timely, political | optional | -| Rating Source | Rating system applied to the edit of title within territory of avail. Rating systems should be formatted and paired with Rating Value as per [Ratings](#ratings) | enum | See [Ratings](#ratings) for allowed values | optional | -| Rating Value | Value representing the rating within the specified Rating Source. Ratings should be formatted and paired with Rating Source as per [Ratings](#ratings) | enum | See [Ratings](#ratings) for allowed values | optional | -| Kids-Directed | Indicator that the content is intended for young audiences/family audiences. Must adhere to guidelines defined in [Kids Directed Content Policy](#kids-directed-content-policy) | Boolean | true, false | optional | -| Recommended Age Group | When Kids Directed is True, a recommended age range for the content can be supplied. Only one Recommended Age Group allowed. Allowable values:
- **ages_1-3** - For viewers 1 to 3 years of age
- **ages_4-6** - For viewers 4 to 6 years of age
- **ages_7-9** - For viewers 7 to 9 years of age
- **ages_10plus** - For viewers ages 10 and up | enum | ages_1-3, ages_4-6, ages_7-9, ages_10plus | optional Used when Kids-Directed is true | -| Main Cast | Top billed cast of content separated by comma in Firstname Lastname format | list | Example:
Kevin Hart, John Travolta | required | -| Synopsis | A short synopsis of the content being availed for the purposes of content selection. Not to exceed 250 characters | string | | required | -| External ID Source | Source entity for external ID provided. Allowable values:
- **TMS** – Gracenote ID
- **IMDb** – IMDb ID
- **Wiki** – Wikipedia ID *Roku does not support the playback of UHD/4K content at this time but can accept UHD/4K as a source to make available for playback in the future.* * *The Roku Channel prefers to make as much content accessible to as many users as possible. Audio Description, while not currently required for all content by the FCC at this time, may be in the future.*
May include IDs from multiple sources, separated by commas. ID originating from that source is indicated by appending a colon (":") and the ID | string | Example:
TMS, IMDb, Wiki
IDs from multiple sources examples:
TMS:E12345678, IMDb:tt12345678, Wiki:benson_s1_e1 | optional | -| Series External ID | 3rd party identifier of the series | string | Example:
diehartshowExtId | optional | -| External ID | 3rd party identifier of the content | string | Example:
dieharts1e1ExtId | optional | -| Screener Link | URL link to stream or download a screener for the content. Any passwords required should also be included. Inclusion of a screener is helpful for content selection | string | Example:
https://urlLinkToScreener
password: 1234 | optional | -| Exclusive | Indicator that the content is available exclusively on The Roku Channel | Boolean | true, false | optional | -| Notes | Free form field for additional avail notes. For linear content, runs and telecast restrictions, or any other specifics not captured in the avails and Committed Title List document should be recorded here | string | | optional | -| Merchant of Record | Name of the entity to which financial transactions should be attributed if other than the Content Partner listed | string | Example:
Roku | optional | -| Day Parting | For Linear content ONLY
Any dayparting rules for the content | string | | optional | - - -### Ratings - -A valid film or TV rating from the rating authority (Rating Source) of the Territory the title will be available in shall be provided for each movie, episode, or shortForm video. If the title has not been rated by that Territory’s official rating authority, a rating of NR (Not Rated) may be provided, however please note that Roku strongly prefers an actual rating on all content. Titles with a rating of NR (Not Rated) will be subject to manual verification which can delay the selection process and publishing to The Roku Channel. Discoverability on The Roku Channel may also be impacted for titles with the NR (Not Rated) rating and placement within the Kids & Family experience will be prohibited. In lieu of the NR (Not Rated) rating, the title should be self rated using the USA_PR rating system. Guidelines pertaining to the USA_PR ratings can be found [here](http://tvguidelines.org/) - -#### Rating values by rating system and country - - -| **Ratings Authority and Territory** | **Country** | **ratingSystem** | **Rating Value** | | | -| --- | --- | --- | --- | --- | --- | -| British Board of Film Classification
United Kingdom | GB | BBFC | U
PG
12A | 12-A
12
15 | 18
NR [*](#unrated-vs-not-rated)
R18
R-1 | -| Canadian Home Video Rating System
Canada | CA | CHVRS | G
PG
14A | 14-A
18A
18-A | NR
RE | -| Motion Picture Associate of America
United States | US | MPAA | G
PG
PG13 | PG-13
R
NC-17 | NC17
NR | -| Canadian Parental Rating
Canada | CA | CPR | 14+
18+
C | C8
C-8
G | NR
PG
E | -| Dirección General de Radio, Televisión y Cinematografía
Mexico | MX | RTC | AA
A
B | B-15
B15
C | DD
D
NR | -| USA Parental Rating (V-Chip)
United States | US | USA_PR | TV-Y
TVY
TV-Y7
TVY7 | TV-G
TVG
TV-PG
TVPG | TV-14
TV14
TV-MA
TVMA
NR | - - -### Genres - -Below is the complete list of supported Genres for The Roku Channel - - -| action
action sports
adventure
aerobics
agriculture
animals
animated
anime
anthology
archery
arm wrestling
art
arts/crafts
auction
auto
auto racing
aviation
awards
badminton
ballet
baseball
basketball
beach soccer
beach volleyball
biathlon
bicycle
bicycle racing
billiards
biography
blackjack
boat
boat racing
bobsled
bodybuilding
bowling
boxing
bullfighting
bus./financial
canoe
card games
cheerleading
children
children-music
children-special
children-talk
collectibles
comedy
comedy drama
community
computers
consumer
cooking
cricket | crime
crime drama
curling
dance
dark comedy
darts
debate
diving
docudrama
documentary
dog racing
dog show
dog sled
drag racing
drama
educational
entertainment
environment
equestrian
erotic
event
exercise
fantasy
faith
fashion
fencing
field hockey
figure skating
fishing
football
food
fundraiser
gaelic football
game show
gaming
gay/lesbian
golf
gymnastics
handball
health
historical drama
history
hockey
holiday
holiday music
holiday music special
holiday special
holiday-children
holiday-children special
home improvement
horror
horse | house/garden
how-to
hunting
hurling
hydroplane racing
indoor soccer
interview
intl soccer
kayaking
lacrosse
law
luge
martial arts
medical
military
miniseries
mixed martial arts
motorcycle
motorcycle racing
motorsports
mountain biking
music
music special
music talk
musical
musical comedy
mystery
nature
news
newsmagazine
olympics
opera
outdoors
parade
paranormal
parenting
performing arts
playoff
sports
poker
politics
polo
pool
pro wrestling
public affairs
racquet
reality
religious
ringuette
rodeo
roller derby
romance
romance comedy | rowing
rugby
running
sailing
science
science fiction
self improvement
shooting
shopping
sitcom
skateboarding
skating
skeleton
skiing
snooker
snowboarding
snowmobile
soap
soap special
soap talk
soccer
softball
special
speed skating
sports
sports talk
squash
standup
sumo wrestling
surfing
suspense
swimming
table tennis
talk
technology
tennis
theater
thriller
track/field
travel
triathlon
variety
volleyball
war
water polo
water skiing
watersports
weather
weightlifting
western
wrestling
yacht racing | -| --- | --- | --- | --- | - - -### Language codes - -The below list is the full set of language codes Roku currently supports for content ingest. This list is a simplified version of the [RFC 5646](https://datatracker.ietf.org/doc/html/rfc5646) specification. - -| Language Code | Language | Language Code | Language | -| ------------- | ------------------------ | ------------- | ------------------------------ | -| af | Afrikaans | km | Khmer | -| sq | Albanian | rw | Kinyarwanda | -| am | Amharic | ko | Korean | -| ar | Arabic | ko-kr | Korean (Korea) | -| ar-dz | Arabic (Algeria) | ku | Kurdish | -| ar-bh | Arabic (Bahrain) | ky | Kyrgyz | -| ar-eg | Arabic (Egypt) | lo | Lao | -| ar-iq | Arabic (Iraq) | la | Latin | -| ar-jo | Arabic (Jordan) | lv | Latvian | -| ar-kw | Arabic (Kuwait) | lt | Lithuanian | -| ar-lb | Arabic (Lebanon) | mk | Macedonian | -| ar-ly | Arabic (Libya) | mg | Malagasy | -| ar-ma | Arabic (Morocco) | ms | Malay | -| ar-om | Arabic (Oman) | ms-my | Malay (Malaysia) | -| ar-qa | Arabic (Qatar) | ml | Malayalam | -| ar-sa | Arabic (Saudi Arabia) | mt | Maltese | -| ar-sy | Arabic (Syria) | mr | Marathi | -| ar-tn | Arabic (Tunisia) | mn | Mongolian | -| ar-ae | Arabic (U.A.E.) | nd | Ndebele | -| ar-ye | Arabic (Yemen) | ne | Nepali | -| hy | Armenian | no | Norwegian | -| as | Assamese | no-no | Norwegian (Norway) | -| az | Azerbaijani | or | Oriya | -| eu | Basque | om | Oromo | -| be | Belarusian | ps | Pashto | -| bn | Bengali | fa | Persian (Farsi) | -| bh | Bihari | pl | Polish | -| bs | Bosnian | pl-pl | Polish (Poland) | -| bg | Bulgarian | pt | Portuguese | -| bg-bg | Bulgarian (Bulgary) | pt-br | Portuguese (Brazil) | -| my | Burmese | pt-pt | Portuguese (Portugal) | -| ca | Catalan | pa | Punjabi | -| zh | Chinese | qu | Quechua | -| zh-hk | Chinese (Hong Kong) | rm | Rhaeto-Romanic | -| zh-cn | Chinese (PRC) | ro | Romanian | -| zh-sg | Chinese (Singapore) | ro-md | Romanian (Republic of Moldova) | -| zh-tw | Chinese (Taiwan) | ro-ro | Romanian (Romania) | -| zh-hans | Chinese (Simplified) | rn | Rundi | -| zh-hant | Chinese (Traditional) | ru | Russian | -| hr | Croatian | ru-md | Russian (Republic of Moldova) | -| hr-hr | Croatian (Croatia) | ru-ru | Russian (Russia) | -| cs | Czech | se | Sami | -| cs-cz | Czech (Czech Republic) | sa | Sanskrit | -| da | Danish | gd | Scottish (Gaelic) | -| da-dk | Danish (Denmark) | sr | Serbian | -| dv | Divehi | sn | Shona | -| nl | Dutch | ii | Sichuan Yi | -| nl-be | Dutch (Belgium) | sd | Sindhi | -| nl-nl | Dutch (Netherlands) | si | Sinhalese | -| dz | Dzongkha | sk | Slovak | -| en | English | sl | Slovenian | -| en-au | English (Australia) | sl-si | Slovenian (Slovenia) | -| en-bz | English (Belize) | so | Somali | -| en-ca | English (Canada) | st | Sotho | -| en-ie | English (Ireland) | es | Spanish | -| en-jm | English (Jamaica) | es-ar | Spanish (Argentina) | -| en-nz | English (New Zealand) | es-bo | Spanish (Bolivia) | -| en-za | English (South Africa) | es-cl | Spanish (Chile) | -| en-tt | English (Trinidad) | es-co | Spanish (Colombia) | -| en-gb | English (United Kingdom) | es-cr | Spanish (Costa Rica) | -| en-us | English (United States) | es-do | Spanish (Dominican Republic) | -| et | Estonian | es-ec | Spanish (Ecuador) | -| fo | Faeroese | es-sv | Spanish (El Salvador) | -| fi | Finnish | es-gt | Spanish (Guatemala) | -| fr | French | es-hn | Spanish (Honduras) | -| fr-be | French (Belgium) | es-mx | Spanish (Mexico) | -| fr-ca | French (Canada) | es-ni | Spanish (Nicaragua) | -| fr-lu | French (Luxembourg) | es-pa | Spanish (Panama) | -| fr-ch | French (Switzerland) | es-py | Spanish (Paraguay) | -| fy | Frisian | es-pe | Spanish (Peru) | -| ff | Fulfulde (Fulah) | es-pr | Spanish (Puerto Rico) | -| gl | Galician | es-es | Spanish (Spain) | -| ka | Georgian | es-uy | Spanish (Uruguay) | -| de | German | es-ve | Spanish (Venezuela) | -| de-at | German (Austria) | sw | Swahili | -| de-de | German (Germany) | sv | Swedish | -| de-li | German (Liechtenstein) | sv-fi | Swedish (Finland) | -| de-lu | German (Luxembourg) | sv-se | Swedish (Sweden) | -| de-ch | German (Switzerland) | tl | Tagalog | -| el | Greek | ty | Tahitian | -| el-gr | Greek (Greece) | tg | Tajik | -| gn | Guarani | ta | Tamil | -| gu | Gujarati | tt | Tatar | -| ht | Haitian (Creole) | te | Telugu | -| ha | Hausa | th | Thai | -| he | Hebrew | th-th | Thai (Thailand) | -| hi | Hindi | bo | Tibetan | -| hu | Hungarian | ti | Tigrigna | -| hu-hu | Hungarian (Hungary) | ts | Tsonga | -| is | Icelandic | tn | Tswana | -| ig | Igbo | tr | Turkish | -| id | Indonesian | tr-tr | Turkish (Turkey) | -| iu | Inuktitut | tk | Turkmen | -| ik | Inupiaq | uk | Ukrainian | -| ga | Irish | ur | Urdu | -| it | Italian | uz | Uzbek | -| it-it | Italian (Italy) | ve | Venda | -| it-ch | Italian (Switzerland) | vi | Vietnamese | -| ja | Japanese | vi-vn | Vietnamese (Vietnam) | -| ja-jp | Japanese (Japan) | cy | Welsh | -| kn | Kannada | xh | Xhosa | -| kr | Kanuri | yi | Yiddish | -| ks | Kashmiri | yo | Yoruba | -| kk | Kazakh | zu | Zulu | - -## Resources - -| Title | Link | -| --------------------------------------------------- | ------------------------------------------------------------ | -| Roku Avails and Committed Title List Excel Template | [https://go.roku.com/trc-avail-template](https://go.roku.com/trc-avail-template) | -| US MPAA Ratings | [https://www.filmratings.com/](https://www.filmratings.com/) | -| US TV Ratings | [http://tvguidelines.org/](http://tvguidelines.org/) | -| UK BBFC Ratings | [https://bbfc.co.uk/](https://bbfc.co.uk/) | -| Canadian Film Ratings | [https://www.mpa-canada.org/film-ratings/](https://www.mpa-canada.org/film-ratings/) | -| Canadian TV Ratings | [https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/](https://www.cbsc.ca/tools/for-english-ca-and-third-language-broadcasters/) | -| FCC Closed Captioning Guide | [https://www.fcc.gov/consumers/guides/captioning-internet-video-programming](https://www.fcc.gov/consumers/guides/captioning-internet-video-programming) | -| FCC Audio Description | [https://www.fcc.gov/audio-description](https://www.fcc.gov/audio-description) | -| Sample Avails/Committed Title Lists | [https://go.roku.com/avail-ctl-samples](https://go.roku.com/avail-ctl-samples) | - -## Change Log - -**v1.3 - 2024-04-22** - -- Defined Avails and Committed Title List -- Added Ad-supported content guideline -- Renamed "Rights Available" to "License Type" -- Added availability windows section -- Added distribution lists for delivery of avail and Committed Title List sheets -- Clarified: Country of Origin, Language, Season Number, Episode Number fields -- Separated field definitions into sections -- Replaced Window Type with FVOD Right -- Defined License Types -- Clarified when and where to provide Localization Type -- Fixed Localization Type list of supported values -- Updated ratings table to the format used in the Ingest Specification -- Updated language codes table to align with the list used in the Ingest Specification -- Removed UR as a valid rating -- Added preference that not rated content be self rated using USA_PR system -- Removed Reference ID -- Added maximum character limit for Series and Title IDs -- Added Excluded Rights -- Added Excluded Languages -- Updated max character count for Synopsis to 250 -- Added requirement to remove links to external data in Excel workbooks -- Updated example data -- Updated Tags to reference Best Practices page -- Updated template with Instructions and more hints on Row 2 -- Added zip file contains sample documents \ No newline at end of file diff --git a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/unlocking-svod-content-as-free-fvod.md b/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/unlocking-svod-content-as-free-fvod.md deleted file mode 100644 index 2eda05da..00000000 --- a/docs/THE ROKU CHANNEL/video-on-demand/title-avail-specifications/unlocking-svod-content-as-free-fvod.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: FVOD submissions -excerpt: Offering free preview windows for Premium Subscriptions content -deprecated: false -hidden: false -metadata: - robots: index ---- -All content rights and availability on Roku Channel are managed by Roku’s Rights Management system. Rights include license type, start/end dates, territories, and languages. Partners can submit avails using one of two specifications: - -- [EMA Avails Specification](https://movielabs.com/md/avails/) -- [Roku Channel Avails and Committed Title List Specification](https://go.roku.com/ingest-ovp-specs) - -# Unlocking SVOD content as free (FVOD) - -To temporarily make Premium Subscription content available for free on Roku Channel, submit an avail for the titles with the license type “FVOD” (Free Video on Demand). The title must have an active SVOD window, and the FVOD window must be fully contained within that active SVOD window. Roku does not support FVOD-only availability (FVOD without an overlapping SVOD window). For example, if Title A’s SVOD window is 2025-04-01 to 2025-10-31, the FVOD window cannot start before 2025-04-01 or extend past 2025-10-31. - -## Key rules - -- The title must have an active SVOD window. -- The FVOD window must be fully contained within the active SVOD window. -- Roku does not support FVOD-only availability (FVOD without an overlapping SVOD window). - -### Valid vs. invalid window combinations - -| Status | SVOD Window | FVOD Window | Reason | -| ------- | ----------------------------- | ----------------------------- | -------------------------------------------------- | -| Valid | 2025-04-01 to
2025-10-31 | 2025-05-01 to
2025-06-15 | FVOD is entirely within the SVOD window. | -| Valid | 2025-04-01 to
2025-10-31 | 2025-04-01 to
2025-10-31 | FVOD matches the SVOD window exactly. | -| Invalid | 2025-04-01 to
2025-10-31 | 2025-03-25 to
2025-05-01 | FVOD starts before the SVOD window. | -| Invalid | 2025-04-01 to
2025-10-31 | 2025-09-01 to
2025-11-15 | FVOD ends after the SVOD window. | -| Invalid | none | 2025-06-01 to
2025-06-30 | FVOD-only is not supported; no active SVOD window. | - -## Delivery method - -- Submit avails to the “avails” folder in your configured delivery endpoint: - - Aspera: Place files in the avails folder on your assigned Aspera workspace. - - Amazon S3: Place files in the avails folder within the S3 bucket configured for your delivery. -- Access requests: if additional users need access to Aspera, email [rokuchannel_onboarding@roku.com](mailto:rokuchannel_onboarding@roku.com). - -## Reference samples - -Examples of SVOD and FVOD windows in Roku’s Avail specification: [https://go.roku.com/avail-ctl-samples](https://go.roku.com/avail-ctl-samples)