Shows the streams, configured from the management server, or allows to configure them locally.
It may contain multiple encoders. A single encoder shares the same audio input (LineIn Stereo, LineIn Left Mono or LineIn Right Mono) and audio codec, and may have one or multiple destinations streaming RTP unicast, RTP broadcast, RTP multicast, BRTP, RIST, or SRT.
When the device is set to pull its stream configuration from the Cloud (e.g. Supiconf server), "App Config" tab appears in the menu top bar instead of the "Streams" tab.
Type here the Stream Name for this Encoder.
Choose the desired audio input for this Encoder:
"Left" will pick the signal from the Left audio input.
"Right" will pick the signal from the Right audio input.
"Stereo" will pick the signal from both the Left and Right audio inputs.
"Downmix" will downmix the Left and Right audio inputs to a mono output channel.
NOTE 1: Avoid using "Stereo" for mono codecs, always prefer using "Left", "Right" or "Downmix" inputs in such case.
NOTE 2: If you are using USB audio card, these settings will be applied to the audio input of the USB card.
Configure here the RTP payload type by the Encoder to encode the output stream. Multicoder supports all standard Barix payload types:
| Payload Type |
Description | Payload Type |
Description |
| 0 | 8kHz uLaw mono | 104 | 8kHz PCM LE, mono |
| 8 | 8kHz aLaw mono | 105 | 24kHz PCM LE, mono |
| 10 | 44.1kHz PCM BE, stereo | 106 | 32kHz PCM LE, mono |
| 11 | 44.1kHz PCM BE, mono | 107 | 44.1kHz PCM LE, stereo |
| 14 | MP3 | 108 | 48kHz PCM LE, stereo |
| 96 | 8kHz PCM BE, mono | 109 | 12kHz uLaw, mono |
| 97 | 24kHz uLaw, mono | 110 | 12kHz aLaw, mono |
| 98 | 24kHz aLaw, mono | 111 | 12kHz PCM BE, mono |
| 99 | 24kHz PCM BE, mono | 112 | 12kHz PCM LE, mono |
| 100 | 32kHz uLaw, mono | 124 | AAC-LC, stereo |
| 101 | 32kHz aLaw, mono | 125 | OPUS, stereo |
| 102 | 32kHz PCM BE, mono | 126 | AAC-HE/HEV2, stereo |
| 103 | 48kHz PCM BE, stereo |
NOTE: MP3, AAC, AAC+ and OPUS codecs have additional configuration options that will be displayed when selected. In this way you can have multiple encoders using the same codec with different options (ex. MPEG1/48kHz/192kbps and MPEG2/16kHz/128kbps).
"Stream Always" will send the stream without any interruption.
"Stream Always, with Noise Gate" will send silence if the input audio is below the configured threshold. The stream will not be interrupted. Use that function if you have noisy audio input.
"Stream On Level" will stream if the incoming audio is above the Trigger Level. If the input audio is below the configured threshold, the stream wil be interrupted.
Default: "Stream Always"
Configure here the input audio level (in dB) above which the device will start sending a stream.
Default: "-24dB"
Post Trigger value can be adjusted to prevent cut-offs when audio should be sent longer than detected. It defines the amount of time that the device will continue streaming after the actual trigger has been cleared.
Default: "1024 ms"
Pre Trigger value can be adjusted to prevent cut offs when audio should be sent earlier than detected. It defines the amount of time that will be buffered and streamed before the actual trigger occurred to avoid loss of audio when the stream starts.
Default: "0 ms" (no pre-buffering))
When set to "On", the Multicoder will send the state of its local digital inputs in the RTP stream. The data are encoded as RTP extension header. If the RTP receiver/player can decode the RTP extension header, it will activate the corresponding local relays.
NOTE: This option works only on IPAM-40x devices with digital inputs (ex. LX-400). Otherwise it is ignored.
Default: "Off (no RTP extension header)"
Set here a meaningful name for this destination.
The multicast/broadcast/unicast address where the stream should be sent to.
NOTE 1: The URL shall start with "rtp://", "brtp://", "srt://", or "rist://".
NOTE 2: Do not set the port in the URL, you have to set it in the "Port" field below.
NOTE 3: When the destination type is set to "BRTP", or "LX400-STL", the specified address is ignored. The BRTP clients then will have to connect to the IP address of the Multicoder device using the specified BRTP/LX400-STL port.
NOTE 4: To send broadcast, set "0.0.0.0" or "255.255.255.255" as destination IP address.
NOTE 5: Sending broadcast is supported only for RTP destinations.
The destination port where the stream should be sent to.
Default: "3030"
The Multicoder supports the following stream types:
| Stream Type | Description |
| RTP | The generated stream is RTP. For the list of supported payload types take a look at the Stable above. |
| BRTP | In this case the Multicoder device acts as a BRTP server, and can provide RTP unicast streams to maximum 16 listeners NOTE: Sending digital inputs in this mode is not supported. If "Send Digital Inputs" option is set, it will be ignored. |
| LX400‑STL | In this case the Multicoder device acts as a advanced BRTP server, sending in the RTP stream also the digital inputs and timestamps in order the new generation Barix STL decoder to work properly. NOTE 1: When this option is selected, RTP extension header for this destination is always sent, even if the "Send Digital Inputs" stream option is disabled. NOTE 2: When using old generation Barix STL decoders, you can safely use "BRTP" destination type instead of "STL". |
| SRT/MPEG‑TS | When set, the Multicoder will serve SRT stream in MPEG-TS format. SRT specific options will be displayed in this case. NOTE: Only MP3, OPUS, AAC/AAC+ stream codecs are supported in this case. Sending digital inputs option is also ignored. |
| SRT/RTP | When set, the Multicoder will serve SRT stream in RTP format. SRT specific options will be displayed in this case. NOTE 1: All Barix custom RTP payload types are supported (see the "Stream Codec" table above). NOTE 2: The encoded SRT/RTP stream can be played at best by Barix SRT Flexa application. It is capable of switching the stream the stream according to the RTP payload type, and activating the device relays according to the encoded digital inputs (if the "send Digital Inputs option is enabled). |
| RIST | When set, the Multicoder will serve RIST stream in RTP format. RIST specific options will be displayed in this case. NOTE 1: All Barix custom RTP payload types are supported (see the "Stream Codec" table above). NOTE 2: The encoded stream can be played by first decoding the RIST stream (e.g. using the ristreceiver utility from the libRIST library), then forward the decoded payload to a RTP capable player. Please note that for non-standard RTP payloads you need to pass the generated SDP to the player, or it will not be able to guess the content). |
Configure here the SSRC of the RTP stream. You can choose between the following options:
"Use MAC" will generate SSRC from the first 31 bits of the device MAC address. For example: MAC: 00-08-E1-AB-CD-EF --> SSRC: 0x61ABCDEF
NOTE: If you have more than one destination, use this setting only once, otherwise several streams may have the same SSRC.
"Random" will set randomly generated SSRC for this stream
"Custom" will allow you to set your own SSRC
Default: "Random"
These options are displayed when "SRT/MPEG-TS" or "SRT/RTP" stream type is selected.
Set here the desired SRT mode.
If your SRT streamer is behind firewall/NAT, prefer "Caller". The SRT player must be then in "Listener" mode.
If your SRT streamer has a public IP address, and the SRT player is behind firewall/NAT, set the streamer in "Listener" mode. The SRT player then must be set in "Caller" mode.
If both your player and stream source are behind firewall/NAT, you have to set both devices in "Rendezvous" mode. The following prerequisites must be fulfilled in order the connection to be successfully established:
- You know the public IP addresses of both the SRT player and the SRT sender
- Both the SRT player and the SRT sender shall use the same port number
- The firewall/NAT of both the SRT player and SRT sender shall be set to open the same output port as requested
Default: "Listener"
These options are displayed when "RIST" stream type is selected.
Set here the desired RIST profile.
NOTE: RIST Encryption is supported only in "Main" and "Advanced" profiles, so if "Simple Profile" is selected, "RIST Encryption" and "RIST Password" options will be hidden.
Default: "Simple Profile"