Understanding StreamHub Usage with Automated Routes
Hub 360 allows you to configure how live transmissions from your transmitters and MoJoPro devices are automatically directed to your multiple StreamHubs (on-premise and cloud). This page helps explains the two different options available: full use and split load.
Suppose you have two on-premise and two cloud StreamHubs defined within a group in Hub 360 with the following number of inputs:
Device Name | Inputs |
|---|---|
StreamHub 1 | 8 |
StreamHub 2 | 16 |
Cloud StreamHub 1 | 4 |
Cloud StreamHub 2 | 4 |
Below is a sample screenshot of these StreamHubs setup within a group in Hub 360:
Also, suppose that we have defined the priority within the group as follows. See Managing the Priority of StreamHubs within a Group for how to access this modal.
To decide whether to use Full Use or Split Load in this modal, see the following tabs.
Suppose we have manual bookings already assigned in Hub 360 as follows:
Inputs 1-2 of StreamHub 1
Inputs 1-2 of Cloud StreamHub 1
Input 1 of Cloud StreamHub 2
In full-use mode, as transmitters or MoJoPro devices within this group start Lives, they will fully use the first on-premise StreamHub before moving to the second on-premise StreamHub. The following animated image illustrates the existing manual bookings in blue and the auto-assigned transmissions in green as they are allocated to each available StreamHub input.
Suppose we have same manual booking setup in Hub 360 as follows:
Inputs 1-2 of StreamHub 1
Inputs 1-2 of Cloud StreamHub 1
Input 1 of Cloud StreamHub 2
In split-load mode, as transmitters or MoJoPro devices within this group start Lives, Hub 360 will ensure that the StreamHub performance is balanced across the group based on the number of available inputs. The following animated image illustrates the existing manual bookings in blue and the auto-assigned transmissions in green as they are allocated to each available StreamHub input. Since StreamHub 1, the highest priority StreamHub, has six available inputs, no transmissions are assigned to it until the other StreamHubs are reduced to six available inputs each.
