Migrating to IT-based playout
Feb 1, 2009 12:00 PM, By Michel Proulx
There's widespread acceptance that broadcasters will move toward IT-based playout over the coming years. The benefits in terms of lower capital and operating costs, as well as greater workflow flexibility, are just too significant to ignore.
However, the reality is that many broadcasters are unsure about how best to make the transition to IT-based playout. Many station engineers are wary of making a radical move to a completely new production and playout model, due to the obvious risks to business continuity. Many others simply don't have the resources right now for such a bold move.
Hence, there is a demand for a migration path to IT-based playout that is phased, smooth and secure. Before looking at how a gradual transition can be achieved, let's first consider the IT-based playout model, and how it differs from traditional playout.
Contrasting traditional and IT-based playout
Figure 1. Traditional television playout chain overview
Click to enlarge
Traditionally, television playout has involved multiple hardware devices in a typical playout chain, including a video server, router, master control switcher and channel branding device, which are all controlled by playout automation. (See Figure 1.) Each of these dedicated pieces of hardware is typically costly and demands its own automation interface. It's the norm for these pieces of equipment to come from multiple vendors, and this sometimes creates demanding installation, integration and support issues.
In contrast, the IT-based model involves replacing many of these elements with a single device that combines the functions of a playout server, master control switcher and branding processor. (See Figure 2.) The leading systems on the market offer all the rich capabilities of the traditional equipment, including multichannel audio handling and high-end graphics performance. These channel-in-a-box devices typically provide several days of video storage, with content updated as file transfers originating from low-cost, IT class archival storage. Like the traditional model, the channel-in-a-box can also accept HD/SD signals to allow switching to network feeds or live action. By dramatically reducing the amount of equipment required for playout, the capital costs are significantly reduced with IT-based playout. Automation interfacing and maintenance are also simplified with less hardware.
Figure 2. Streamlined IT-based playout model
Click to enlarge
The simpler channel-in-a-box architecture has significant benefits for multichannel playout. Whenever an additional channel is required, the system can be expanded by increasing the number of channel-in-a-box devices on the network. Naturally, with larger systems, the cost savings inherent with a more streamlined playout path are even more significant. This lower cost for additional channels is a critical issue when revenues per channel are generally falling, and it can make the difference between a new channel being viable or otherwise in a tight market.
Whenever more functionality is packed into a single box, there is often some concern about reliability because a failure is potentially more catastrophic. In reality, feature-rich designs often work in favor of resiliency because critical products are generally designed with exceptional levels of redundancy. Naturally, there are also fewer parts that may fail in the playout chain overall.
| Want to use this article? Click here for options! |  |
