FEED Winter 2020/21 Newsletter



IP input bandwidth overview





































   























Number of signals

   

Sources per IP interface port

370









148









66



37

33



26

13

8

7

3

3

0













Port types GbE

   





a cluster, but the overall broadcast system ‘sees’ only one giant multiviewer. The vm_dmv LiveView

needed for one full-resolution 4K signal, ie only about 10% of the input bandwidth. “This unique product architecture allows us to deliver high amounts of unique inputs to a multiviewer regardless of source resolution,” explains Türkay. “We package this data into the same container format that is used to stream 2110 content. The result is still a 2110 stream, but with smaller resolution pictures.” V__matrix blades running the vm_dmv app can be added as demand evolves. In combination with Lawo’s stand-alone LVP LiveView processor, even MPEG-2, H.264, HEVC, J2K and OTT/ABR flows can be converted to LiveView streams and displayed alongside SDI/ST2022-6/ ST2110 uncompressed signals. Lawo’s LiveView approach is almost infinitely scalable, thanks to ability to work with blade clusters, and dynamic management and load balancing of LiveView and head processing capabilities. Each networked V__matrix blade could be stationed in a different location and still be a part of such a cluster. This allows users to leverage their distributed processing infrastructure more effectively. “Best of all, this processing mojo is available in a surprisingly compact footprint,” concludes Türkay. 



engine in the input stage downscales incoming video signals to a fraction of their original size in real time and streams compact mipmap versions on demand to the IP network. The mipmap streams are sized for the multiviewers’ PIPs and consume proportionally less bandwidth than their full-scale parents. Each vm_dmv instance can generate up to 24 Raw to LiveView conversions and make them available to the entire IP network. When a video source is patched to a PiP on a multiviewer head, the vm_dmv’s head processing stage first queries the other blades in the cluster and then ‘dispatches’ the mipmap version whose size is closest to the required PiP resolution. Any remaining differences are scaled in the PiP itself.     



THIS ARCHITECTURE ALLOWS US TO DELIVER HIGH AMOUNTS OF UNIQUE INPUTS TO A MULTIVIEWER

This leads to amazing input bandwidth savings. A 4K multiviewer head hosting a 4x4 layout of unique 4K inputs, for instance, only consumes the bandwidth

@feedzinesocial

Powered by