DRM Protected Streaming Content - Content Specifications

Summary

Swank Streaming titles are encoded to support Adaptive Bitrate Streaming in order to be as network friendly as possible. Adaptive Bitrate Streaming technologies have several key features.

• They create multiple files from one source to cater to viewers on various devices and connection speeds.
• They also adaptively distribute these files, adjusting the stream based on changes in throughput and CPU availability.

Each Swank title is currently encoded at 5 different bit rates. 

Encode Specifications

Note: These are the standard bitrates for Swank streaming; however, your content may have specific bitrate requirements that do not encompass all of those listed below.

File Structure	MPEG-DASH Modular DRM
Video Encode:	H.264 MP4
Audio	AAC-LC
Bitrates	Content with an HD master	Content with an SD master
	3000 Kb/sec, @ 720p	1500 Kb/sec @480p
	2000 Kb/sec, @ 720p	800 Kb/sec @ 360p
	1500 Kb/sec @480p	400 Kb/sec @240p
	800 Kb/sec @ 360p
	400 Kb/sec @240p
Content encoded prior to 6/1/2018	3000 Kb/sec @ 720p	1500 Kb/sec @ 480p
	2000 Kb/sec @ 720p	800 Kb/sec @ 480p
	1500 Kb/sec @480p
	800 Kb/sec @ 480p
Closed Captions	EIA-608/EIA-708	EIA-608/EIA-708
DRM Encryption Supported
CMAF	CMAF is our latest DRM package supporting Windows, Android (7.1+), and Apple devices (iOS, iPadOS, MacOS) via Safari or Chrome.  The important thing to note is for CMAF there are two manifests in the folder right next to each other, a .mpd for MPEG-DASH and a .m3u8 for HLS.  Use the .m3u8 on Apple devices and Safari; use the .mpd on all others.
CENC	Supports adaptive streaming for Widevine and PlayReady DRM systems only.

Audio Volume: Please keep in mind that our processes include streamlining all audio through an industry-level Dolby application that outputs a consistent “across-the-board” audio for all files we master and/or deliver to our customers. We do not deviate from this for any specific content or orders. Volume level that is perceived as too high or low in your playback environment could have numerous different reasons why. 

Content Order File Structure

The typical structure goes as follows (with directories in bold). 

• OrderNumber
  • Content
    • DRM Type
      • Product#_Version
        • Unique Content/Package Id
          • subtitles
            • (productNumber).(language).vtt - If available .vtt/subtitle files will be here.
          • (productNumber)_(resolution)_(bitrate)_(language).mp4 - Content file(s)
          • (productNumber)_(language).mp4 - If available additional language files will be here.
          • (productNumber)_(version).mpd - MPEGDash file
        • (Line #)
          • productNumber)_enc.ts- Content file
          • (productNumber)_enc.ts.MediaFileInfo.json - Specifications for the content file in json format
          • (productNumber)_enc.ts.MediaFileInfo.xml - Specifications for the content file in xml format
          • (productNumber).(language).srt - If available .srt/subtitle files will be here.
  • Publicity
    • (productNumber)
      • (Language)
        •  
        • (publicity asset file name, for each publicity asset)
      • (productNumber).FilmMetadata.xml - Publicity metadata for specific title.
  • Schemas
    • Manifest.xsd
    • FilmMetadata.xsd
  • UpgradePackages
    • package_(version).dat - Current upgrade package file for Swank Deployed Streaming servers
  • License.dat - Encrypted XML detailing all the active licenses for the portal associated with the shipment.
  • Manifest.json - Describes the contents of the drive including where the content and publicity can be found for each item in json format.
  • Manifest.xml - Describes the contents of the drive including where the content and publicity can be found for each item in xml format.
  • ShipmentInformation.txt - Digital packing slip for the order.