Until recently, all commands were generally passed to a device-control engine that kept a master clock synchronized so that all events would happen in lock step. Add the fact that frame accuracy is now critical, and many traffic systems are brought to their knees before they communicate the first byte to the automation system. For most stations today, that information is not part of the log. ![]() Consider the number of individual changes that must occur: drop two streams in the multiplexer, increase the bandwidth for the HD channel, decrease the bandwidth for the remaining SD channel, send new information to PSIP, manage the statmux settings, and perhaps dozens of minor commands necessary to make it all work seamlessly. For instance, at 2000, you want your DTV channel to go from four SD streams to one HD and one SD stream. One problem that often complicates log management is that the log sometimes does not contain accurate machine commands that automation can translate effectively. It might also include secondary events, such as voice-over and pushback to reveal a promo or other graphic, a key of the station logo in the corner on the hour, or other events. ![]() Each single event might be as simple as a cut on the master control switcher to server, play four spots back-to-back, and then a cutback to programming on the switcher.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |