For Internet-based contribution an Input is the component in the platform to receive the media stream. Supported transport protocol is RTMP which all major live video production software supports such as Livestream Studio, OBS, vMix, and much more. An Input is always available and has a static endpoint. This means that it can be reached using the same address and you can start sending data to it and it will be accepted regardless whether an event has been planned and created. This is a great benefit if you want to ensure beforehand that you have connectivity and sufficient bandwidth from the venue to our platform.
In simple terms an Event channel can be seen as a virtual live encoder and recording storage that are created and started automatically on-demand. Unless you are running an event with multple events back-to-back you don't really need to care about this concept. You create and plan the event and our system will allocate and start the necessary resources. Once the event is finished the content on the recording storage is copied to a long-term store and the live encoder and recording storage are virtually destroyed. If you are running events back to back on one event channel they will all be part of the very same recording as we today only support one recording per event channel. A recording can be either encrypted or unencrypted.
An Event is an entity that can be exposed to the viewer and has a start-time and end-time. An Event always belongs to one single Event channel. When creating a new Event it is either attached to an existing Event channel or the system automatically creates a new one. There can be any number of events belonging to an event channel and events can be either back-to-back or overlapping.
If the system recognies that two events are close to each other they will be attached to the same event channel. The reason for this is that there is a lead time involved when creating and tearing down the server resources in the cloud. An event channel is made available before the start time of the event to give you as a broadcaster time to verify signal quality etc before the event acually starts. Events can be added and removed (some limitations applies) but understand that this can have an effect on the event channel duration as it is always based on currently included events.
As soon as you create an event in the system there will always be an Event asset created for you. If you delete the event the Event asset will be removed as well. As for any other asset within the platform you add titles, images descriptions etc. You can also add publications to make it visible for end users.
Event asset publications¶
It is the publications for the event asset that decides when and for who the event is visible in the apps.