This screen enables ZEC to receive an HLS stream. The HLS stream is not protected by the Zixi protocol. There are two options for pulling the stream:
...
| Parameter | Description | ||
|---|---|---|---|
| Stream parameters | |||
| Master Playlist URL | Specify the URL of the HLS stream's master playlist. | ||
| Download Type | Specify whether the variants will be pulled from a single source (adaptive bitrate) or multiple sources (pull all bitrates). | Smoothing Latency | The Smoothing feature uses a buffer to time packets according to the stream's clock. This is useful when there are bursts in the rate in which the stream arrives. The smoothing features creates a queue in the buffer, allowing smoother entry into the Broadcaster. The Smoothing parameter defines the size of the buffer in Milliseconds. A larger buffer enables smoother entry, however, it may influence the latency rate. |
| Inject SCTE35 on CUE Marks | Select this checkbox to inject SCTE markers into the adaptive stream manifest. SCTE-35 markers found in the source input will be used to segment the stream and the #EXT-X-CUE-IN/#EXT-X-CUE-OUT tags will be added to the manifest. | ||
| Enable time shift | Select this checkbox to record the stream content and broadcast it after a specified delay. To deploy an input stream that uses the current stream's time shift, you need to configure a "Delayed" input stream. (See Adding Delayed Streams). | ||
| Maximum delay [hh:mm:ss] (for Time Shift enabled) | Specify the maximum time delay of this input. | ||
| Support EXT-X-DATERANGE | |||
| Start from last segment | |||
| Zixi broadcaster | |||
| Use HTTP parameters for substreams | |||
| Billing Codes | Billing codes are used to identify and differentiate traffic on a ZEC for billing purposes. When a billing code is added to a Source or Target, Zixi can track the traffic on that Broadcaster input or output separately from other inputs and outputs on the same Broadcaster. Billing codes are created by Zixi personnel on the Zixi Customer Portal for a particular organization. | ||
| Billing Code | Enter the billing code that corresponds to this stream. The relevant billing can be obtained from the organization that received the billing code from Zixi. | ||
| Billing password | Enter the password that corresponds to this billing code. | ||
| Enable multicast on pull outputs | Select this checkbox to enable the transmission of this stream’s outputs as multicast. A ZEC that will pull the stream will receive it in multicast. By default ZEC is configured to allow transparent fallback to unicast if it is out of the LAN. Requires enabling Multicast Pull in the Settings. | ||
| Multicast-Only (for Multicast enabled) | If desired, specify multicast only outputs. | ||
| Enable Encryption | Select this checkbox to encrypt the Input stream. For more information, see ZEC Encrypting an Input Stream. | ||
Encryption type (for Encryption enabled) | Specify the type of Encryption (AES 128/192/256). | ||
Encryption key (for Encryption enabled) | Click Generate to generate an encryption key. The generated encryption key must be sent to the end-user to decipher the received encoded stream. | ||
Recording parameters | Select this checkbox to customize the recording parameters. | ||
Destination Type | Select the radio button for the desired storage type and then fill in the relevant parameters. · Record to disk – the recording is saved on the local disk. It is possible to record to an external destination by replacing the default storage location with a symbolic link. To learn more, see Using an External Storage section. · Record to S3 – the file is saved to your AWS S3 Bucket. | ||
Record to Disk Parameters | |||
File Name Template | Specify the file name pattern that Zixi will use to generate when saving the recorded content. A separate file will be generated for each recording up to the time specified in the Max recorded file duration parameter (see above). After this duration a new file will be generated. The file name pattern can include any string and up to five variables listed below. Only the %T=HH.MM.SS creation time is mandatory. You can change the order of these variables and add text as long as you maintain the legitimate structure of the file in Linux and Windows:
For example, the following pattern %Y_recording%T.ts will generate the following file name 2022_recording15:32:35.ts. | ||
Max recorded file duration [hours] | Specify the maximum time allotted for recording a video stream. Default: 2 hours | ||
Keep recorded files for [hours] | Specify the maximum time for storing the recording. Default: 0 hours | ||
Custom Path | Optionally specify a storage location for the recorded files that is relative to the root folder. This location bypasses the location specified as the root folder in the Settings > General screen. | ||
Record to S3 Parameters | |||
File Name Template | Specify the file name pattern that Zixi will use to generate when saving the recorded content. A separate file will be generated for each recording up to the time specified in the Max recorded file duration parameter (see above). After this duration a new file will be generated. The file name pattern can include any string and up to five variables listed below. Only the %T=HH.MM.SS creation time is mandatory. You can change the order of these variables and add text as long as you maintain the legitimate structure of the file in Linux and Windows:
For example, the following pattern %Y_recording%T.ts will generate the following file name 2022_recording15:32:35.ts. | ||
Max recorded file duration [hours] | Specify the maximum time allotted for recording a video stream. Default: 2 hours | ||
URL | Specify the URL of the S3 bucket. | ||
Ignore TLS certificate errors | TLS certificate for S3 bucket might be detected as faulty if bucket name contains dot[s]. When this option is selected, ZEC will ignore the TLS certificate errors and transmit the stream to its destination. | ||
Access Key | The access key that is used for accessing the S3 bucket. | ||
Secret Key | The secret key that is used for accessing the S3 bucket. | ||
...