Ingest Options

Phenix supports contribution of content from a variety of sources, such as the Phenix Encoder, Phenix SDKs running on platforms such as Web or Mobile, or 3rd-party encoders. If none of those sources are available, Phenix also offers a flexible ingest option.

A summary of options is shown in the table below.

Note: AAC audio must be must be MPEG-2 ADTS, not MPEG-4 LOAS/LATM.

The Phenix Encoder provides content to the Phenix platform via Phenix ITP™ (Interactive Transport Protocol, built on and compatible with W3C-standard WebRTC). The Phenix hardware encoder can extract and pass through CEA-708 closed captions, SCTE-104 and SCTE-35 ad markers, and can convert Nielsen watermarked audio to ID3 tags.

For the best combination of latency and quality, use the Phenix encoder. Please contact Phenix for details.

The Phenix Client SDKs provide content to the Phenix platform via Phenix ITP™ (Interactive Transport Protocol, built on and compatible with W3C-standard WebRTC). Use the SDKs to publish user media such as webcams or cameras on mobile phones.

Publishing is available for:

• Web

• Android

• iOS

The universal route into the Phenix system is a buffered path carrying virtually any stream. The stream is then transcoded into a format that is compatible with real-time delivery. Both the buffering and the transcoding add latency. The amount of latency added varies depending on the variability of the signal (which impacts the amount of buffering needed) and the transcoding.

Streams that require this path include any streams that do not meet the requirements for real-time ingest, as shown in the table above.

To use the flexible ingest, please contact Phenix.

Phenix also supports IP cameras via RTSP as detailed in this article.