Planning and Designing the IP Broadcast Facility
Metadata
- Author: Gary Olson
- ASIN: B084T7D6GQ
- Reference: https://amazon.co.uk/dp/B084T7D6GQ
- Kindle link
Highlights
There is still no silver bullet or single solution that encompasses all the production needs and solves all the issues of integration, interoperability, business and workflow or technology associated with the entire broadcast and production lifecycle of media and its value chain. The design considerations need to start from the very beginning (creation) and continue right through to the end-user experience (distribution and delivery), which includes interaction and transaction. — location: 394
Solid-state drives require specialized card readers, and these are frequently upgraded and changing. The continuing evolution of these technologies create compatibility challenges, so it is reasonable to question their backward compatibility. There are many considerations to be taken into account for even the simplest of storage decisions. — location: 1379
As media moves throughout the entire infrastructure, it needs to be accessible to all departments/units including production, distribution, library, legal, finance, marketing and business intelligence. — location: 1464
The editing workflow has evolved and editor applications are tightly integrated with media managers and their search and browse engines. Additionally, this makes media and metadata more easily accessible via remote access. — location: 1649
In the IP workflow, automation plays a significant role and the term orchestration can be used to describe a larger use of automation across multiple and diverse systems and devices. — location: 1658
For commercial networks the integration of commercials is substantially different for each platform. — location: 1724
Linear program channels have one type of commercial integration, On Demand has a different one and streaming to devices even another. — location: 1724
There are differences streaming over broadband vs. mobile. — location: 1725
The traffic department manages playlists not only for multiple channels and time zones, but also across multiple platforms. — location: 1732
The traffic logs being fed to the automation systems have to include the instructions that specify which metadata fields accompany the content to each platform. There is no standard metadata for the different content distribution channels. — location: 1733
The traffic and scheduling process provides the command and control metadata that are the instructions to the automation system for what type of processing the content requires for distribution. — location: 1735
Problem solving, maintenance and support for the IP infrastructure are mostly software centric. — location: 1748
The broadcast engineer needs to be skilled in network routing, switching, server applications and storage. Understanding the interfaces between different software systems and middleware is an essential knowledge base. — location: 1754
This metadata is what content delivery networks use to enable program guides, recommendation engines and search tools use to locate the asset, — location: 1774
See Michael’s automated content description with LLM.