Direct Icecast

With the Icecast v2 protocol, metadata (cue points) are transported on a separate HTTP connection, which can create alignment issues with ad insertion for mid-rolls. Therefore, it recommended to not do mid-roll ad insertion in Icecast mode. Triton recommends only using pre-roll ad insertion when using Icecast. For more information, see Metadata and Mid-roll Ad Injection / Replacement, below.

Note that a few seconds of misalignment for song metadata does not significantly degrade the listener's experience, so it's acceptable to use icecast to pass song metadata.

For information about connecting to the Triton Streaming Network using various Icecast devices, see this article.

Triton Digital's Direct Icecast Ingest provides a way to ingest audio stream and metadata into the Triton content delivery network (CDN) without using Station Manager. The Triton Digital Media Relay (MR) can receive an Icecast v2 encoded stream as a source for streaming. This support is dependent on specific configurations and availability of feature set on specific MRs.

Only the Icecast v2 protocol is supported. Therefore, this feature is provided for neither Shoutcast nor RTMP. For direct streaming via those sources, see Server-side Transcoding.

Supported Codecs

The streaming parameters in the Icecast encoder must exactly match those in the Triton CDN configuration. If they do not, the connection will be refused by the MR.

Triton officially supports a specific list of Codec/Sampling rate presets. See the Help Center knowledge base article "Choosing Audio Bitrate Settings" for a list of supported codecs.

If your encoder can't be set to one of our presets, please reach out to Triton Customer Support.

How to Connect Icecast Streams to the Triton Network

For specific information on connecting to third-party products or services such as Telos Z/IP Stream and Wheatstone, see Connecting Third-party Icecast Products/Services.

As part of the implementation process, you will be sent one or two hostname DNS URLs. (URL A and URL B.) Connect to the Triton Network's Media Relays via those DNS URLs, using a separate URL for each Icecast source.  

Example URLs:

• URL A: europe.icecast.tritondigital.com

• URL B: europe2.icecast.tritondigital.com

The actual URLs to use are provided by the Triton Digital Implementation Team.

Single Icecast Encoder

If you run a single Icecast encoder setup with one stream use URL A for the source. If you were sent two URLs you can ignore URL B. (See illustration above, minus the yellow highlight.)

Dual Icecast Encoder/Stream

If you run a dual/redundant Icecast streaming setup (either two separate encoders, or one encoder that outputs two streams), use URL A for the first source and URL B for the second source.  (See illustration above, including the yellow highlight.)

Encoder Parameters

Triton Digital's Icecast Ingest supports Icecast v2 parameters.

Source Method Examples

Request

SOURCE Method

SOURCE /mp3test ICE/1.0\r\n
content-type: audio/mpeg\r\n
Authorization: Basic c291cmNlOmhhY2ttZQ==\r\n
ice-bitrate: 128\r\n
ice-audio-info: ice-samplerate=44100;ice-bitrate=128;ice-channels=2\r\n
\r\n

PUT Method

PUT /mp3test HTTP/1.0\r\n
content-type: audio/mpeg\r\n
Authorization: Basic c291cmNlOmhhY2ttZQ==\r\n
ice-bitrate: 128\r\n
ice-audio-info: ice-samplerate=44100;ice-bitrate=128;ice-channels=2\r\n
\r\n

Response