Destination Menu
Destinations allow you to route streams to different platforms, decoders, and more.
All Destinations are listed in the Destinations tab. Destinations are ordered numerically and then alphabetically.
Each destination displays the Destination Name, Destination Type, Destination URL, the Input Stream, Created On date, and the last Updated On date.
The right column includes the Status icon, Statistics icon, the Edit icon, the Duplicate Destination icon, the Start icon, the Stop icon, and the Delete icon.
Click on the Duplicate icon to create a destination with the same settings as the original destination.
Creating a Destination
A Destination allows users to route their streams to any platform or destination that accepts SRT or RTMP.
You need an active stream to create a Destination.
Go to the Destinations tab and click Add New Destination.
You can also click on the Outputs tab under your stream and click Add Destination.
Give the Destination a name.
Click on the Stream Name dropdown menu and select the stream you want to use.
Stream Encoders
Stream Encoders allow multiple sources to send to the same VVCR stream simultaneously. This requires at least two instances on the cluster. Then you can failover to a backup if you experience issues with your primary stream.
Once the encoders are configured in stream settings (go to page ___ to learn more) go to the Destinations Tab and click on the Edit icon in the far right menu bar of your destination.
Click on the Stream Encoder dropdown menu and switch from Primary to Backup.
Configure the rest of the Destinations Settings and Press Save.
It can take 5-10 seconds for the change to reflect on the platform.
If you want to learn more about Primary and Backup Encoders, check out our video and article at support.vvcr.tv.
Destination Output Types
RTMP Push:
This is used for most social media platforms or any destination that provides an RTMP Stream URL and Stream Key.
SRT Caller:
Use this for a destination that provides an SRT IP Address and Port Number.
VVCR Stream:
Use this to take an active VVCR stream and route it to an inactive VVCR stream. This essentially creates a duplicate stream, without requiring you to send another feed to VVCR.
HLS Origin:
HLS is a widely used video streaming protocol that can run on almost any server and is supported by most devices. HLS allows devices to seamlessly adapt to changing network conditions by raising or lowering the quality of the stream.
RTMP Authorization Schema
VVCR supports newer and more secure implementations of RTMP, such as RTMPS and various Authorization formats. This allows for streaming to platforms that require RTMPS streams, like Facebook, as well as Platforms like Wowza that require specific authorization formats.
Select the Authorization Schema dropdown menu to select a schema.
An Authorization Schema is only needed for password-protected streams or other protected platforms.
Select None for non-protected streams. This is the option for most destinations and platforms like YouTube, Instagram, Facebook, etc.
There are several authentication options for protected streams.
The most common requires a username/password handshake mechanism where credentials are transmitted. This is required for platforms like Wowza and some RTMP hardware encoders/decoders. For these platforms, use Default.
VVCR supports the following custom authentication mechanisms implementation:
- Akamai
- Limelight
- Telegram
- Twitch
- (X) Twitter
Click here to learn more about Primary and Backup Encoders.
Click here to learn more about Multichannel Audio for Destinations.
Click here to learn more about Authorization Schemas.