At swXtch.io we know that the media companies rely highly on both compressed and uncompressed content. cloudSwXtch has SMPTE 2110 support without the necessity of additional gateways or other on-ramp/off-ramp appliances. The cloudSwXtch architecture is designed to treat content the same whether it is compressed or uncompressed. This means the ingest of streams from on-prem to the cloud and the streaming of content within the cloud, whether unicast or multicast, is the same regardless of the content type. No SDK is required for uncompressed video, and the cloud network becomes an extension of your broadcast network.
There are two workflow examples below, one is a compressed workflow and the other is an uncompressed workflow. The compressed workflow is a typical playout scenario where compressed inputs come into the cloud environment and are distributed via multicast to the necessary VM workloads by cloudSwXtch. All that is required is for the workloads to subscribe to the necessary multicast group(s). This eliminates the need to continually update unicast configurations to ensure your streams get to where they need to go. However, if there are workloads that only work with unicast, cloudSwXtch can map multicast streams to unicast devices.
Example Compressed Playout in the Cloud with SMPTE 2110 Multicast TS
Example Uncompressed Playout in the Cloud with SMPTE 2110 Multicast
Consider the following production workflow:
The workflow consists of a playout server which receives multiple camera feeds via 2 production switchers and determines which camera's to take to air. The cloudSwXtch is used to deliver the various streams via mulitcast to the workloads that subscribe to the stream:
Step 1: Two inputs red and black go from Network Bridge into cloudSwXtch.
Step 2: Red stream goes from cloudSwXtch to Production Switcher 1 and black stream goes to production switcher 2.
Step 3: The modified ouptut stream from production switcher 1 is represented by the yellow path and the modified output stream from production switcher 2 is represented by the green path to the cloudSwXtch.
Step 4: All streams are multicasted to the multiviewer, via cloudSwXtch, so the director can make operational decisions.
Step 5: The playout server is directed to process and output one of the switcher outputs as represented by the dotted black to the cloudSwXtch.
Step 6: cloudSwXtch outputs the stream to the multiviewer, and the network bridge.
Step 7: The network bridge distributes to the clients for viewing consumption.