Scribd
Upload
81 views

ProStream 9000 Splicing

ProStream 9000 Splicing

Uploaded by

Robert
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
81 views

ProStream 9000 Splicing

ProStream 9000 Splicing

Uploaded by

Robert
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Configuring ProStream 9000 Splicing

© 2017 Harmonic. All rights Reserved.


Table of Contents
Splicing on ProStream 9000............................................................................................ 1

Configuring Splicing on ProStream 9000 ..................................................................... 1

iii
Splicing on ProStream 9000
Configuring Splicing on ProStream 9000
This topic describes setting up ad splicing using a ProStream 9000 with a Quad GbE
card as the splicer.

SERVICE DEFINITION:

 Each ProStream 9000 splicer can support up to 70 spliced services.


 The network feed source is an IP transport stream carrying services for
AVC/MPEG-2 HD/SD video at 50Hz/60Hz. Each service contains one (1) video,
up to eight (8) audio streams, up to four (4) data streams.
 The ad insertion feed is an IP input stream at a CBR of 0.5 to 12 Mbps.

AD SERVER:

The Ad Server is not managed by NMX. See the Ad Server documentation for
instructions on setup for the Ad Server properties. To configure the Ad Server to
communicate with the splicer under NMX, you will need:

 The splicer SCTE 30 port number (usually 5168).


 The splicer device name.
 The splicer IP Address and the port on which to receive the ads. The Ad Server
typically requires the splicer device name, Quad GbE card slot number, and GbE
port number. The card number should match the slot number (1 to 5) that holds
the Quad GbE card in the ProStream splicer.
 The output service name as configured in the service plan properties. A unique
name is required for each splicing service.

IN NMX OPTIONS:

1. In the NTP page, enable NTP and designate an NTP server.

NTP is required for synchronizing the ad insertion. The synchronization should


be in the millisecond range. Harmonic recommends using a stratum 2 or lower
NTP server. The Ad Server must use the same NTP server.

2. In the General page, set the ProStream 9000 DPI Settings.


o SCTE 30 Port: Harmonic recommends using the default SCTE 30 Port
number (5168).

1
ProStream 9000 Splicing

o Compliance Mode: Set in accordance with the Ad Server.

IN NMX DESIGNER:

1. Create the Network Group. Only ProStream 9000 splicers with Quad GbE Quad
cards are supported. The NG can include either one ProStream 9000 splicer, or
a redundant pair (1:1) of splicers.
2. In the splicer properties page, set the device name, IP Address and Port
properties. Take note of these—you will use these when you configure the Ad
Server to communicate with the device. The names/values must match exactly.

IN NMX SERVICE PLAN EDITOR:

This example lists only the essential settings for enabling splicing. Set all other
properties as desired. You can use input discovery to create the input transport, or
create it manually. In this example, we create the transport manually:

1. On the inputs tree, add an input transport of device-type ProStream 9000.


2. Add a service that matches your input. You can define the streams, or add a
Reference service.

For input to the Quad GbE card, the only VBR input that is supported is from a
Harmonic DiviTrack pool. If the pool contains streams from Electra encoders
with DPI streams, the following properties must be enabled:

The Inputs > DPI properties page > CBR During Ad must be enabled.

The Outputs > Pools > Video properties page > CBR During Ad Bitrate must be
set to match the ad bitrate.

3. The service can include SCTE 35 messages, or another trigger mechanism. If


the SCTE 35 messages are carried in a DPI stream, you specify the DPI stream
to use for triggers when you configure the output. Inclusion of the DPI stream in
the output is optional.
4. On the outputs tree, add a transport of device-type ProStream 9000 Broadcast.
5. Add the service from the input—add it as a Regular service (ACE transcoded
services do not support splicing). Note the service name. The service name you
created on the input is the default name. You can change the output service
name. You will use this when you configure the Ad Server to designate which
service gets the ads.

Each splicing service on the same splicer must have a unique service name.

6. In the output service properties page, select the Enable Splicing check box to
allocate resources and enable splicing for the service. If the input is from a
2
Splicing on ProStream 9000

DiviTrack system, it must be MBTS that contains all services in the same pool.
All output services must have splicing enabled, to ensure that all services in the
pool have the same delay.

Note: Up to eight (8) audio and up to four (4) data streams are supported in a
splicing service. NMX prevents you from enabling splicing if the service
stream count exceeds those limits. When adding streams to an existing
splicing service, you can only add streams up to the limit, all other streams
are ignored. The device adds streams in sequence. If you have more than 8
audio or 4 data, you have to delete some existing streams first, to be able to
add others.
7. If the service includes SCTE 35 messages in a DPI stream as the trigger,
indicate the stream PID in the output service properties > Input DPI PID field.
This instructs the device which stream PID carries the messages. For
Reference services you don't need to configure the Input DPI PID, as the device
automatically expects the splicing messages to be on a stream PID with ES
type 0x86.

Splicing triggers (this example for the Input DPI PID):

– PID (Select from the input PIDs)

3
ProStream 9000 Splicing

– ES type (Selected automatically from the input service as the first PID which
has ES type 0x86)

– Component (Selected automatically from the input service as the first PID
which has appropriate component)

– Service ID (For a reference service, selected automatically from the input


service, the first PID with ES type 0x86)

8. If your service includes data streams such as DVB subtitles or teletext, you can
set the set the PID Match Mode in the output data stream properties page to
suit your content. It determines the handling of the service data PID during ad
insertion.

When you have saved all your settings and you activate the service, splicing will begin
when triggered.

You might also like