Configuring Media Workflow Resources - Cisco · Configuring Media Workflow Resources This chapter provides procedures for configuring media workflow resources – the channels, policies,

Cisco

C H A P T E R 7
Configuring Media Workflow Resources
This chapter provides procedures for configuring media workflow resources – the channels, policies, profiles, templates, archives, and other resources that can be referenced from multiple media workflows. Media workflows bind policies, templates and other resources together to ingest and package assets for one or more media sources.

Configuring Media Sources

Configuring an ATS Channel

Step 1 From the navigation menu, choose Media Workflow Manager > Media Workflows > Media Sources > ATS Channels.

Step 2 Click Add (+) to add a new channel. The Create ATS Channel dialog opens.

Figure 7-1 Create ATS Channel Dialog

Step 3 Complete the fields in this dialog by specifying the following:

• Name – Name of the channel (required).

7-1Virtualized Video Processing Controller User Guide

Chapter 7 Configuring Media Workflow ResourcesConfiguring Media Sources

• Max Audio Streams – Maximum number of audio streams for the channel (required). Beginning with V2PC Release 3.3.5, the default value of 10 can be changed to any value from 1-32.

• Channel ID – ID for the channel (required).

• Description – A brief description of the channel (optional).

• No De-Dup – If TRUE, segments from this stream are not archived by an associate recording and storage system. If FALSE, the segments are archived.

Note This option only applies for cDVR use cases, and can only be specified when the channel is created. A channel set to No De-Dup TRUE cannot be modified later.

• Source Type – Source for the channel (required), either UDP or HTTP.

• Target Multicast Address – Primary (required) and Secondary (optional) multicast addresses.

• Source IP – Primary (required) and Secondary (optional) source IP addresses.

• I-Frame Segment Duration – For segmented files, the maximum time in seconds to write to a file before starting a new segment (required for Live or cDVR use cases). The segment duration must match the encoder boundary Point (EBP) configured on the encoder, or it must be a multiple of the EBP value. This value must be an even integer from 2-10, specifying 2, 4, 6, 8, or 10 seconds.

Step 4 To associate one or more ABR profiles with the ATS channel, locate the desired profile in the Available ABR Profiles list, check the profile, and then click >> to add the profile to the Selected ABR Profiles list.

Note • ABR profiles are configured separately. See Configuring ABR Profiles, page 7-3 for details.

• ABR profiles are not sharable among ATS channels. If you use the V2PC GUI to associate ABR profiles with an ATS channel and then delete the channel, the associated ABR profiles are also deleted. If you create ABR profiles outside the V2PC GUI and then share them among multiple ATS channels, you cannot delete the shared ATS channels through the V2PC GUI.

Step 5 Click Save.

Configuring an ATS Channel Lineup

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > ATS Channel Lineups.

Step 2 Click Add (+) to add a new channel lineup. The ATS Channel Lineups page opens.

Figure 7-2 ATS Channel Lineups Page

7-2Cisco Virtualized Video Processing Controller User Guide


Step 3 Add the desired channel(s) from the right pane to the new channel lineup in the left pane.

Step 4 Specify a Name, Description, and Media Archive for the channel lineup.

Step 5 Click Save.

Note The right pane only displays channels belonging to the media archive currently selected in the drop-down list. If multiple media archives exist, select the desired media archive from the list to make its corresponding channels available in the right pane.

Configuring ABR ProfilesBeginning with Release 3.3.5, V2PC supports configuring ABR profiles and associating them with audio groups, as further described in Configuring Publishing Templates, page 7-14.

You can configure a publish name for each ABR profile that can then be used to determine the order of the profiles in the manifest MPD file (in the case of HLS content) or to selectively publish the profiles (in the case of HLS or DASH content). When both a Publish Name and Manifest Renaming are configured for HLS content, ordering is by Publish Name first and then by manifest naming.

Note ABR profiles are not sharable among ATS channels. If you use the V2PC GUI to associate ABR profiles with an ATS channel and then delete the channel, the associated ABR profiles are also deleted. If you create ABR profiles outside the V2PC GUI and then share them among multiple ATS channels, you cannot delete the shared ATS channels through the V2PC GUI.

To configure ABR profiles:



Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > ABR Profiles.

Step 2 Click Add (+) to add a new ABR profile. A system-generated Name is applied to the new ABR profile.

Step 3 Enter the following information for the new ABR profile:

• Publish Name – This string of up to 255 characters including alphabetic or numeric characters (or both) as well as the hyphen (-). This name must be unique across all ABR profiles associated with the ATS channel.

• ATS Rate – Data rate for the adaptive transport stream in bits per second.

• Video Streams – Video stream format for the profile.

• Audio Streams – Audio stream format for the profile.

• Audio Group – Audio group for the profile.

Note Audio groups are configured in the Stream Configuration section of the Publishing Templates dialog. See Stream Configuration, page 7-20 for details.

Figure 7-3 ABR Profiles Page

Step 4 Click Save.

Configuring Media ArchivesMedia archives are storage locations for stream segments that have reached a predefined archive time. Segments stored in media archives can be reconstituted for later use and then re-archived.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > Media Archives.



Step 2 Click Add to add a new archival configuration. The Media Archives page opens.

Figure 7-4 Media Archives Page

Step 3 Specify the following parameters as needed (all are optional):

• Archive Time – Elapsed time after which the stream is put into archive storage.

• Re-archive Time – Time after which the reconstituted stream can be archived again.

• Archive Start Time – Time to start running the archival process for any segment that has passed the Archive Time.

• Archival Duration – How long to run the archival process before taking a break.

• Archival Pause – Pause time between archival runs.

Step 4 Click Save.

Configuring NAS Media Sources

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > NAS Media Sources.

Step 2 Click Add (+) to add a new NAS media source. The NAS Media Sources page opens.

Figure 7-5 NAS Media Sources Page


Chapter 7 Configuring Media Workflow ResourcesConfiguring Policies

Step 3 Specify the following parameters:

• Name – Name of the NAS media source, or content library (required). The name is a string of up to 30 characters. Acceptable characters are uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.) and is not case-sensitive.

• Description – Description of the NAS media source. The description is a string of up to 30 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Share Path – Share path used by the NAS media source on the network (required). The share must be mounted and active on the V2PC system before the files in this path are accessible.

• NFS Version – Version of the Network File System (NFS) used by the NAS media source. Valid versions are 3.0 and 4.0.

• Servers (IP Address Ranges) – Range of servers available to the NAS media source. For a single server, the Start and End IP addresses are the same.

Step 4 Click Save.

Configuring Policies

Configuring HTTP Header PoliciesThe HTTP header policies control the HTTP headers for publishing content.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Policies > HTTP Header Policies.

Step 2 Click Add (+) to add a new HTTP Header Policy. The HTTP Header Policies dialog opens.

Figure 7-6 HTTP Header Policies Dialog




• Name – Name of the HTTP header policy (required). The name is a string of any length. Acceptable characters are uppercase and lowercase letters and numbers. No special characters are allowed. The name is not case-sensitive.

• Description – Description of the HTTP header policy. The description is a string of up to 70 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Request Type – Indicates whether the rule is for a Manifest or Chunk.

• HTTP Version – Version of HTTP request. The only valid value is HTTP 1.1.

• Header Name – HTTP header name. Predefined headers are provided, but can be edited or modified.

• Header Value – HTTP header value.

Note For a Live service, if Request Type is set to Manifest and HTTP Version is set to HTTP 1.1, Header Name must be set to Cache-Control and Header Value must be set to max-age=0. Each HTTP header policy must contain at least one rule.

Step 4 Click OK.

HTTP Header Policy Examples

• Chunk http 1.1 Cache-control max-age=3600 (recommended for VOD; 0 for Live)

• Manifest http 1.1 Cache-control max-age=3600 (recommended for VOD; 0 for Live)



Configuring Asset Lifecycle PoliciesAsset lifecycle policies control the Time-Shift TV (TSTV) window for Live capture.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Policies > Asset Lifecycle Policies.

Step 2 Click Add (+) to add a new Asset Lifecycle Policy. The Asset Lifecycle Policies dialog opens.

Figure 7-7 Asset Lifecycle Policies Dialog


• Asset Lifecycle Policy Name – Name of the asset lifecycle policy (required). The name is a string of up to 63 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.

• Type – Type of asset lifecycle policy. The only valid value is DVR Window.

• Description – Description of the asset lifecycle policy. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Policy Rules – Specify the following:

– Match Tags – Indicates whether the rules apply to an entire asset or only to a segment. Segment is required for a Live service. MatchTags can be configured for both Segment and Manifest, and can be stored either locally (in virtual memory on CE workers) or remote (in NAS or COS storage).

– Time – Time in seconds after which the specified action is to be taken.

– Action – Action to apply to the asset or segment. Valid values are Move and Purge.

– Storage – NAS store associated with the rule.

– Enabled – Indicates whether the rule is enabled. Valid values are True (enabled) and False (disabled).


Chapter 7 Configuring Media Workflow ResourcesConfiguring Profiles

Step 4 Click OK.

Configuring Profiles

Configuring Auth ProfilesAuthorization (auth) profiles are profiles that point to an auth provider. To set up an auth profile:

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Profiles > Auth Profiles.

Step 2 Click Add (+) to add a new auth profile. The Auth Profile dialog opens.

Figure 7-8 Auth Profile Dialog


• Name – Name of the auth profile (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.

• Type – Type of auth profile. The only valid value is swauth.

• User ID – User ID for auth profile.

• Access Key – Auth profile access key.

• Auth Server URL – URL for the auth server.

• Token Refresh Interval – Time in seconds after which the auth token is refreshed.



• Description – Description of the auth profile. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

Step 4 Click OK.

Configuring ESAM ProfilesThe Event Signaling and Management (ESAM) profiles define ESAM multi-screen ad insertion.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Profiles > ESAM Profiles.

Step 2 Click Add (+) to add a new ESAM Profile. The ESAM Profile dialog opens.

Figure 7-9 ESAM Profile Dialog


• Name – Name of the ESAM profile (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters, numbers, and underscores (_). The user ID must not begin with a period (.), and it is not case-sensitive.

• POIS URL – Placement Opportunity Information System (POIS) URL of the ESAM server (required).

• Description – Description of the ESAM profile. The description is a string of up to 235 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Version – Version of the ESAM profile. Choose a version from the drop-down list. Valid versions are OC-SP-ESAM-API-I01 and OC-SP-ESAM-API-I03.

Step 4 Click OK.



Configuring Key ProfilesThe key profiles define encryption profiles.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Profiles > Key Profiles.

Step 2 Click Add (+) to add a new key profile. The Key Profile dialog opens.



Figure 7-10 Key Profile Dialog


• Key Profile Name – Required name for the key profile. The name is a string of up to 200 characters. Acceptable characters include uppercase and lowercase letters, numbers, and underscores (_). The user ID must not begin with a period (.), and it is not case-sensitive.

• Description – Optional description for the key profile. The description is a string of up to 235 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• KMS Type – KMS type used by the key profile. Valid KMS types are VGC (supports DRM types HLS-AES-128) and NAGRA.

• DRM Type – DRM type used by the key profile. Valid DRM types are VGC-HLS and CENC-DASH CENC. Choose CENC-DASH to enable Common Encryption Scheme (CENC) for DASH.

• Key Service URI – Optional key service URI used to acquire the key profile.

• CENC Priority – Required when CENC DASH is enabled (DRM Type = CENC-DASH). Choose Widevine or PlayReady as appropriate.

• Widevine – Choose Enable or Disable as appropriate.

• License Acquisition URL – Required if Widevine is enabled; optional if Widevine is disabled.

• Widevine Provider – Optional field used to identify the provider for Widevine, if used.

• Playready – Choose Enable or Disable as appropriate for PlayReady content protection.

Step 4 Click OK.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Storage

Configuring StorageCisco Cloud Object Storage (COS) provides virtual object-based storage for V2P media workflows. COS storage nodes are organized into clusters to provide a distributed, scalable, and resilient storage solution.

Configuring COS Stores

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Storages > COS Stores.

Step 2 Click Add (+) to add a new COS Store. The COS Stores page opens.

Figure 7-11 COS Stores Page


• COS Store Name – Specify a name to identify the COS Store. The name must be unique.

• Container – Specify the container.

• Auth Profile – Choose the auth profile from the drop-down list.

• Description – Enter a name.

Step 4 Click Save.

Configuring Network-Attached Storage

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Storage > Network-Attached Storage (NAS).

Step 2 Click Add (+) to add a new NAS store. The Network-Attached Storage (NAS) page opens.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Templates

Figure 7-12 Network-Attached Storage (NAS) Page


• Name – Name of the NAS store (required). The name is a string of up to 30 characters. Acceptable characters are uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.) and is not case-sensitive.

• Description – Description of the NAS store. The description is a string of up to 100 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Share Path – Share path used by the NAS store on the network.

• NFS Version – Version of the Network File System (NFS) used by the NAS store. Valid versions are 3.0 and 4.0.

• Start and End IP Address – The first three bytes of the Start IP Address must match those of the End IP Address. For example, 1.1.1.1 to 1.1.1.2 is a valid start and end IP address range, but not 1.1.1.1 to 1.1.2.2. For a single server, the Start IP Address and the End IP Address are the same.

Step 4 Click Save.

Configuring Templates

Configuring Publishing Templates

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Templates > Publishing.

Step 2 Click Add (+) to add a new publishing template. The Publishing Templates dialog opens.

Figure 7-13 Publishing Templates Dialog




• Name – Name of the template (required). The name is a string of up to 63 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.

• Description – Description of the template. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Package Format – Package format supported by the template. The available options are as follows:



– DASH – Dynamic Adaptive Streaming over HTTP (DASH), also known as MPEG-DASH or DASH-MP4. An ABR streaming format for high-quality media, MPEG-DASH breaks live or recorded video source content into a sequence of small segments representing several seconds of playback time for streaming over standard web servers.

A DASH asset can include multiple sets of segments representing different resolution and bit rate profiles. The client device can then automatically select the appropriate set to deliver the highest quality possible under current network conditions. Together with the segment files, the DASH asset includes a Media Presentation description (MPD) manifest file.

The MPD is an XML document containing asset metadata and identifying the segments included in the asset, their available bit rate and resolution profiles, and their order of reassembly for presentation.

– HLS – HTTP Live Streaming, the default package format, is an Apple streaming solution equivalent to MPEG-DASH, and is intended for native consumption by devices running the Apple iOS operating system.

– HLS-MP4 – A later version of HLS that supports fragmented MP4 content.

– HSS – HTTP Smooth Streaming, a Microsoft streaming solution equivalent to MPEG-DASH, intended for native consumption by devices running the Windows operating system.

– HDS – HTTP Dynamic Streaming, an Adobe streaming solution equivalent to MPEG-DASH, intended for native consumption by devices using Flash media server or Flash media player for playback.

– CIF – Common Intermediate Format, a format for packaging, ingest, storage, and delivery of segmented video assets using ABR video and audio encoding. A CIF asset includes a Media Presentation Document (MPD) manifest file in XML format describing the overall program, the segments included in it, the profiles (bit rates and resolutions) included, and the order of segment presentation.

– CIF-DASH-TS – A CIF format based on MPEG DASH-TS, which is a profile of MPEG DASH that uses MPEG-2 transport stream (TS) segments. This alternative CIF option is required for certain customer deployments.

Note Current deployments no longer use CIF or CIF-DASH-TS package formats.

• Segment Duration – For segmented files, maximum time, in seconds, to write to a file before starting a new segment (required). The segment duration must match the encoder boundary Point (EBP) configured on the encoder, or it must be a multiple of the EBP value.

• Key Rotation – Number of seconds to wait before using a new encryption key.

• Manifest Renaming – For HLS package format, optional name of a template file used to rename the manifest. See Configuring HLS Manifest Renaming, page 7-18 for details.

• Segment Renaming – This option selects one of three possible templates for use with HLS segment renaming. See Configuring HLS Segment Renaming, page 7-20 for details.

• DVB Bitmap Pass Through – Only applicable to HLS package format. Enables passthrough of DVB bitmap subtitle PID to downstream applications. The DVB bitmap subtitle data in the source is retained in the TS segments.

• DVB Bitmap To ID3 – Only applicable to HLS package format. Transforms DVB bitmap subtitles to SMPTE Timed Text (SMPTE-TT) format. SMPTE-TT XML files containing subtitle images are tagged by the ID3 tag and embedded as timed metadata in TS segments.

• Subtitle Policy – Subtitle policy associated with the template.



• Muxed Stream – Multiplexed (muxed) stream associated with the variant for HLS use cases. If True, audio and video are muxed together in segments; if False, audio and video are published in separated stream manifests.

• SCTE35 Event – Configures SCTE 35 ad insertion support as either InBand or Outband and enables additional configuration options. See Configuring SCTE 35 Ad Insertion, page 7-23 for details.

Step 4 Specify the following Package options:

• Stream Configuration – Configure the stream as described in Stream Configuration, page 7-20. The stream can be HLS, HSS, CIF, or CIF-DASH-TS based on user requirements. Choose HLS for Apple clients, HSS for Microsoft players, or CIF as appropriate.

• Variants – Enables you to provide a subset of video and audio bit rates to specific devices. For example, you could create a variant called mac and assign three top bit rates to it, and then create another variant called ipad and assign three lower bit rates to it.

– Name – Name of the variant (required). The name is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

– Version – Version of the variant (required). Valid versions are 2-5. The default setting is 4.

– Order – Ordering criterion for the variant. The available options are BITRATE, RANK, and PROFILE_NAME. The variant manifest will include specified profiles ordered by BITRATE or RANK specified later. Choose PROFILE_NAME to order by ABR Profile Publish Name.

– Selective Publish – Supports selective publishing of DASH video profiles as detailed in Configuring Selective Publishing, page 7-22. When set to FALSE, no video is filtered and the system appends these profiles to the manifest. When set to TRUE but without specifying any video streams, no video is filtered.

Note Selective publishing is supported for HLS content through the VMP Service Manager GUI. For details, see the Cisco Virtual Media Packager User Guide for your VMP release.

– Default Audio Stream – Name of the default audio stream associated with the variant.

When the (default) HLS package type is selected, the following fields also appear:

– Precise Start – The value is an enumerated string; valid strings are YES and NO. If the value is YES, clients SHOULD start playback at the Media Segment containing the TIME-OFFSET, but should not render media samples in that segment whose presentation times are prior to the TIME-OFFSET. If the value is NO, clients should attempt to render every media sample in that segment.

– Start Time – The value of TIME-OFFSET is a signed-decimal-floating-point number of seconds. A positive number indicates a time offset from the beginning of the Playlist. A negative number indicates a negative time offset from the end of the last Media Segment in the Playlist. The absolute value of TIME-OFFSET SHOULD NOT be larger than the Playlist duration. If the absolute value of TIME-OFFSET exceeds the duration of the Playlist, it indicates either the end of the Playlist (if positive) or the beginning of the Playlist (if negative).

– Muxed Stream – Multiplexed (muxed) stream associated with the variant. If TRUE, audio and video are muxed together in segments. If FALSE, audio and video are published in separate stream manifests.

– Manifest Naming – When configured for HLS playout, the user can rename sub-stream playlists in the master playlist. Beginning with VMP Release 2.12.1, the master playlist can also be renamed. See Configuring HLS Manifest Renaming, page 7-18 for additional information.

– Default Audio Stream (PID) – Name of the default audio stream associated with the variant.



– Enable SMPTE-TT – Enables (if TRUE) or disables (if FALSE) SMPTE Timed Text format for the variant.

– Enable WEBVTT – Enables (if True) or disables (if False) Web Video Text Tracks format for the variant.

– Enable CC608 – Provides the option to disable or enable pass-through of CEA-608 closed captions.

– Enable CC708 – Provides the option to disable or enable pass-through of CEA-708 closed captions.

• Video Streams – Identifies the individual variants by bit rate in bits per second and resolution in pixels.

• Content Protection – Specifies the DRM method.

• Transport – Specifies the HTTP transport policy.

• Multi-Period Generation on Event Stream – Enables or disables generation of multiple periods for SCTE 35 ad insertion. See Configuring SCTE 35 Ad Insertion, page 7-23 for details.

• Profile Ordering – The Profile Ordering table displays the profile ordering by Profile Name. To add entries, click Add (+) and then enter the corresponding Profile Name. To delete entries, check the profile(s) to be deleted and click Delete (X).

Step 5 Click OK.

Configuring HLS Manifest Renaming

The following system macros are used to generate name values for manifest renaming. You combine these macros with literal strings to configure a renaming template for an HLS publish template variant. You then specify this template in the Manifest Renaming field of the Publish Templates dialog.

Note You can also configure HLS Manifest Renaming using the Publishing Templates dialog in the VMP Service Manager GUI, or manually using the MPE Configuration File. For details, see the Cisco Virtual Media Packager User Guide for your VMP release.

Note System macro values are case-sensitive.

Table 7-1 System Macros for HLS Manifest Renaming

Macro Description

{Type} For A/V muxed segment playlist, the value is empty "".

For i-frame playlist, the value is "iframe".

For audio only playlist, the value is "audio".

For WebVTT subtitle playlist, the value is "subtitle".

{BITRATE} The peak bit rate value of the stream, equal to the value of the BANDWIDTH attribute in the master manifest for the corresponding sub playlists.

{NUMBER} Two-digit string ranging from "01" to "99". This macro applies to the sub playlists by playlist type order: segment, iframe, audio only, subtitle.



For example, for variant variant_iphone and content ID contentid_12345, the renaming template configuration is:

{NUMBER}_{REGEX:CONTENTID:contentid_(.*):$1}_{REGEX:VARIANTNAME:variant_(.*):$1}_{TYPE}_{LANGUAGE}_{BITRATE}.m3u8

The resulting master playlist might appear as shown in the following example:

#EXTM3U#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",FORCED=NO,AUTOSELECT=YES,LANGUAGE="pol",NAME="pol",URI="09_12345_iphone_subtitle_pol_0.m3u8"#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",FORCED=NO,AUTOSELECT=YES,LANGUAGE="eng",NAME="pol",URI="10_12345_iphone_subtitle_pol_0.m3u8"#EXT-X-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=761959,CODECS="avcl.4D400C,mp4a.40.2",RESOLUTION=320x180,SUBTITLES="subs" 01_12345_iphone___761959.m3u8#EXT-X-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=1015653,CODECS="avcl.4D401F,mp4a.40.2",RESOLUTION=1280x720,SUBTITLES="subs" 02_12345_iphone___1015653.m3u8#EXT-X-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=1242684,CODECS="avcl.4D401E,mp4a.40.2",RESOLUTION=800x450,SUBTITLES="subs" 03_12345_iphone___1246864.m3u8

{LANGUAGE} The language of the audio or subtitle. It only applies to audio only playlist and subtitle playlist.

{REGEX:CONTENTID:XXX:YYY}

Each content or live channel ingested is specified by a Content ID value. When renaming the manifest, the Content ID is detected and replaced by a specified value, as follows:

• XXX is the regex match pattern searched for in the Content ID value. The regex pattern must follow the Perl regex syntax defined at:

http://www.boost.org/doc/libs/1_53_0/libs/regex/doc/html/boost_regex/syntax/perl_syntax.html

• YYY is the replacement string of the Content ID value. Use $N to reference the nth match value, where N can range from 1 to 9.

For example, if Content ID value is "VOD_20170218_CDN_1487127063", with the renaming template “{REGEX:CONTENTID:VOD_(.*)_CDN_(.*):$1_$2.m3u8}", the generated string will be "20170218_1487127063.m3u8".

{REGEX:VARIANTNAME:XXX:YYY}

Each HLS publish template can have one or more variants configured, each specified by a variant name. When renaming the manifest, VMP detects the variant name value and replaces VARIANTNAME with the specified value, as follows:

• XXX is the regex match pattern which is searched for in the variant name, the regex pattern must follow the Perl regex syntax defined at:


• YYY is the replacement string of the variant value, use $N to reference the nth match value, N can range from 1 to 9.

For example, if variant name is "HLS_iphone_HD", with the renaming template "{REGEX:VARIANTNAME:HLS_(.*)_HD:index_$1.m3u8}", the generated string will be "index_iPhone.m3u8".

Table 7-1 System Macros for HLS Manifest Renaming

Macro Description





#EXT-X-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=1696746,CODECS="avcl.4D401F,mp4a.40.2",RESOLUTION=1024x576,SUBTITLES="subs" 04_12345_iphone___1696746.m3u8#EXT-X-I-FRAME-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=761959,CODECS="avcl.4D400C",RESOLUTION=320x180,URI="05_12345_iphone_iframe_761959.m3u8"#EXT-X-I-FRAME-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=1015653,CODECS="avcl.4D401F",RESOLUTION=1280x720,URI="06_12345_iphone_iframe_101563.m3u8"#EXT-X-I-FRAME-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=1242684,CODECS="avcl.4D401E",RESOLUTION=800x450,URI="07_12345_iphone_iframe_1242684.m3u8"#EXT-X-I-FRAME-STREAM-INF:PROGRAM-ID=l,BANDWIDTH=1696746,CODECS="avcl.4D401F",RESOLUTION=1024x576,URI="08_12345_iphone_iframe_1696746.m3u8"

Note The renaming template must generate unique names for all sub-stream playlists.

Configuring HLS Segment Renaming

For HLS use cases, the Segment Renaming option offers a choice of templates used for renaming audio, video, and I-frame segments to support ad insertion.

Note HLS segment renaming is only supported through the V2PC GUI.

The Segment Renaming drop-down list offers three template options. Select one of the following as appropriate for your application:

• {SEGMENT_TIMESTAMP} – The default template, which aligns with the behavior of prior VMP releases. Segments are named {SEGMENT_TIMESTAMP}.ts or {SEGMENT_TIMESTAMP}.vtt as appropriate.

• {SEGMENT_SEQUENCE_NUMBER}-{PLAYLIST_INDEX} – When this template is selected, manifest renaming is disabled and the manifest (playlist) names conform to a static pattern. The segment naming pattern is XXXXX-YY.ts, where XXXXX is the segment sequence number and YY is the two-digit index value of the playlist to which the segment belongs.

• {SYNC_BASE}/{SEGMENT_SEQUENCE_NUMBER}-{PLAYLIST_INDEX} – This template works only with URL pass-through mode. The naming format of the master playlist is the same as the format of the sequence number template except that URL pass-through information is added before the index number.

For video, audio, and I-frame playlists, it is required the segments with the same sequence number across the playlists will have the same base URL, resulting in one base URL for audio and video playlists and one base URL for I-frame playlists.

Stream Configuration

Expanding the Stream Configuration section of the Publishing Templates dialog opens the Stream Configuration table as shown in the following example.

Figure 7-14 Stream Configuration Table



The Stream Configuration table displays the following parameters for each stream associated with the selected variant:

• Type – Type selections are Audio, Subtitle, Video, ID3, UserConfig (required).

• Action – Update or Disable Stream Configuration (required).

• Language – Language used for the stream, such as en for English.

• PID/ID – ID of the PID.

• Codec – Format of the stream, such as AAC, DD/AC-3, DD+/EC-3.

• Bitrate (bps) – This column is available when the order of the variant is BITRATE. The bit rate that you enter must be within 5% of an actual bit rate. The output manifest will include these profiles with the order user specified.

• Name – Name of the output stream. The name is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Language – Language used for the output stream, such as en for English (required).

• Group – Identifies the audio group to which the stream is assigned. If the stream is not assigned to an audio group, choose audio.

Note Audio groups are assigned to ABR profiles in the Create ATS Channel dialog. See Configuring an ATS Channel, page 7-1 for details.

• Default – Determines whether this stream is the default stream type for its audio group.

Click the appropriate icon to add, edit or delete, then click Save to save your settings or Cancel.

When configuring bit rates for video and audio streams, keep the following considerations in mind:

• The order in which you configure the bit rates is the order in which they are displayed in the manifest.

• The bit rates must be within 5% of an actual output stream generated by the source. Otherwise, the system excludes that bit rate from the manifest.



• If none of the bit rates in a list is within 5% of an actual bit rate, the VMP generates a 404 error code when you request a manifest.

• If you do not specify a list of bit rates, then the VMP includes all of the bit rates generated by the source in the manifest.

For example, if you have a Digital Content Manager (DCM) that generates video bit rates of 1MB, 2MB, 3MB, 4MB, and 5MB:

– You can configure video bit rates of 1 MB, 4 MB, and 5 MB to display them in the manifest in descending order, or of 5 MB, 4 MB, and 1 MB to display them in ascending order.

– If you configure 1.5 MB and 4 MB, only 4 MB is displayed in the manifest. 1.5 MB is not within 5% of an actual bit rate.

– If you configure 1.5 MB and 3.5 MB, the VMP generates a 404 error code because neither bit rate is within 5% of an actual bit rate.

– If you configure 1.05 MB and 2.9 MB, both 1 MB and 3 MB are displayed in the manifest because both are within 5% of an actual bit rate.

• For all filtering and ordering functions, refer to the audio and video bit rate values shown in the Assets fields of the associated media workflow. For example, see Figure 8-7 of Creating a Live Media Workflow.

Configuring Selective Publishing

Selective publishing lets you configure DASH I-frame video stream assets in a selection of video profiles, or variants, to tailor the resolution and frame rate of the stream to specific TV and mobile display devices. Only assets matching the specified filter conditions are published.

Variants for mobile devices support HE-AAC audio profiles only. Variants configured for TV delivery support either HE-AAC or AC3 audio profiles.

Regarding filter conditions, either resolution or bit rate, or both, can be specified. If resolution is specified, only assets that exactly match are published. If resolution and bit rate are both specified, the settings should be compatible. In the event of a conflict, resolution takes priority over frame rate.

To enable selective publishing for a DASH video asset from the V2PC GUI:

Step 1 From the V2PC GUI navigation menu, choose Media Workflow Manager > Resources > Templates > Publishing.

Step 2 Choose DASH-MP4 as the Package Format.

Step 3 Choose Publish Template > Package > Variant.

Step 4 In the DASH publish template, choose True for Selective Publish.

Step 5 In Video Streams, add the required resolution (in pixels) and bit rate (in bits per second) filter conditions.

Note If there are filters specified in video streams but no video assets match them, no video is output. If there are multiple filters specified in video streams, video assets matching any filter are published.



Configuring SCTE 35 Ad Insertion

Beginning with V2PC Release 3.3.5 and VMP Release 2.12.1, support is provided for the following SCTE 35 commands and segmentation types:

SCTE 35 Commands

• splice_insert

• time_signal

Segmentation Types

• 0x34 "Provider Placement Opportunity Start"

• 0x35 "Provider Placement Opportunity End"

• 0x10 "Program Start"

• 0x11 "Program End"

• 0x20 "Chapter Start"

• 0x21 "Chapter End"

• 0x30 "Provider Advertisement Start"

• 0x31 "Provider Advertisement End"

• 0x32 "Distributor Advertisement Start"

• 0x33 "Distributor Advertisement End"

• 0x36 "Distributor Placement Opportunity Start"

• 0x37 "Distributor Placement Opportunity End"

Note SCTE 35 support is provided for HLS VOD and Live use cases, and also for cDVR when used in conjunction with Cisco Virtual Media Recorder (VMR).

Use the following options to configure SCTE 35 support in the Publishing Templates dialog:

• Multi-Period Generation on Event Stream – This option is available when the Package format is set to DASH-MP4. If Enabled, multiple periods are defined according to the events in the EventStream if the event presentationTime is within the scope of one segment duration (MCE video_seg_auto). If Disabled, all events in an EventStream are put in one period. New periods are available starting from the segment start time.

When enabled, also choose at least one event type. Based on your selection, the events will trigger new DASH periods and discard other events. When disabled, SCTE 35 Event does not trigger new dash periods, and other events are discarded.

• SCTE 35 Event – For DASH-MP4, SCTE 35 Inband Event support is provided by encoding SCTE 35 messages in MP4-DASH emsg boxes. If set to InBand, you must also make the following changes to the DASH MPD file and MP4 fragment:

– In the DASH MPD file, set all audio adaptation sets to include an InbandEventStream element with @schemeIdUri set to "urn:scte:scte35:2013:bin" and @value set to "1". For example, <InbandEventStream schemeIdUri="urn:scte:scte35:2013:bin" value="1"/>.

– In the MP4 fragment, update all first audio fragments in one DASH period to nclude the same number of emsg boxes as the Event number in the EventStream.




Documents

Configuring Media Workflow Resources - Cisco · Configuring Media Workflow Resources This chapter provides procedures for configuring media workflow resources – the channels, policies,