...
Amount of movement in the video frames, as with any compressed stream.
Important notes:
Source type, bitrate and resolution have no affect on the bridge channel bitrate, meaning, if you’re transfering a low quality compressed stream through the bridge it’s very likely that the bridge channel bitrate will be higher than the source, since the compresseion we’re using has lower compression ratio then MPEG2, H264 and especcialy H265, but it is much faster then any of those other codecs to maintain lowest latency possible.
The bridge channel’s maximum resolution is 1920X1080, so the bitrate will be identical if you’re trying to display it on a full screen HD output, full screen UHD or 1/4 UHD.
The bridge channel will consume up to 5 points from the server generating the mosaic, not the one generating the bridge channel.
Here’s an estimation of the bridge bitrate based on the source frame rate and target tile size, these numbers are flactuating by about 20%.
...
On the MCS navigate to Devices Management page. Please ensure atleast two MCM9000 devices are configured on the MCS. Please refer to Adding MCM9000 devices to MCS to configure MCM9000 devices, make sure they’re both running the same version.
Ensure that the Video Bridge is enabled for the right NIC in the interface configuration:
Go to “interface configuration” tab, double click on the interface through which you want the bridge traffic to be transferred, and check the “bridge” box.
It can be any type of NIC supported by TAG.
You can have up to two NICS per MCM with bridge enabled, in case one fails at will automatically switch to the other one.
NOTE: network names of the NICS used for the bridge traffic MUST BE IDENTICAL.
...