Configuring a Helios Engine (Generic Ingest)

The Helios Engine is currently in beta and allows you to do two things on Core:

• Configure a backup switcher for redundant streaming 
• Ingest 3rd party encoders via RTMP, SRT, or MPEG-TS

In this tutorial, we will show you how to configure a Helios Engine for generic ingest. 

Not sure if you need a Helios Engine? See our FAQ for more information.

Select Engines from the menu on the left and then Helios Engines from the tab above. Name your Engine and select a region closest to the location of the encoder you want to ingest into Core. Choose the protocol that suits your requirements. Remember, the encoder you want to ingest must support the protocol you have chosen. In this tutorial, we're choosing RTMP.

Not sure what protocol to use? Check out this FAQ.

One your Engine has been fired up, select it from the Engines menu and copy the RTMP URL on the Engine Details screen.

Navigate to your encoder (or streaming software - we used OBS) and paste the RTMP URL into the destination field. Note that the field may be called different things by other manufacturers. Type in the stream key found right next to the RTMP URL on the Core UI (if required). 

When you start streaming from your encoder, the video feed will appear on the Dashboard for delivery to online video platforms, recording, or decoders. The cool thing about the Helios Engine is that it allows your 3rd party encoder to stream into Core via RTMP, SRT, and MPEG-TS, and out via any of those 3 protocols - it's your choice! 

If you want to bring a VidiU Pro into Core, simply ingest it through this method. Once in Core, you can convert the feed to MPEG-TS, if you like.