Manipulating the manifest of streamed video allows localisation of adverts with the option of per-client customisation. This results in better monetisation but also a better way to deal with blackouts and other regulatory or legal restrictions.
Using the fact that most streamed video is delivered by using a playlist which is simply a text file which lists the locations of the many files which contain the video, we see that you could deliver different playlists to clients in different locations – detected via geolocating the IP address. Similarly different ads can be delivered depending on the type of client requesting – phone, tablet, computer etc.
Here, Imagine’s Yuval Fisher starts by reminding us how online streaming typically works using HLS as an example. He then leads us through the possibilities of manifest manipulation. One interesting idea is using this to remove hardware delivering cost savings using the same infrastructure to deliver to both the internet and broadcast. Yuval finshes up with a list of “Dos and Don’ts” to explain the best way to achieve the playlist manipulation.
Sarah Foss rounds off the presentation explaining how manifest manipulation sits at the centre of the rest of the ad-delivery system.
ATSC 3.0 is the major next step in broadcasting for the US, South Korea and other countries and is a major update to the ATSC standard in so many way that getting across it all is not trivial. All terrestrial broadcasting in the US are done with ATSC as opposed to many other places, including Europe, which use DVB.
ATSC 3.0 brings in OFDM modulation which is a tried and tested technology also used in DVB. But the biggest change in the standard is that all of the transport within ATSC is IP. Broadcasters now, using broadband as a return path, have two-way communication with their viewers allowing transfer of data as well as media.
In this talk from Imagine Communications, we talk a look into the standard which, as is common nowadays, is a suite of standards. These standards cover Early Alerts, immersive audio, DRM, return paths and more. We then have a look at the system architecture of the ATSC 3.0 broadcast deployed in Phoenix.
South Korea has been pushing forward ATSC 3.0 and Chet Dagit looks at what they have been doing and how they’ve created high quality UHD channels to the consumer. He then looks at what the US can learn from this work but also DVB deployments in Europe.
Finally, Yuval Fisher looks at how the data and granularity available in ATSC 3.0 allows for more targeted ads and how you would manage both internally and harnessing it for ad campaigns.
With the SMPTE 2110 suite of standards largely published and the related AMWA IS-04 and -05 specifications stable, people’s minds are turning to how to implement all these standards bringing them together into a complete working system.
The JT-NM TR-1001-1 is a technical recommendation document which describes a way of documenting how the system will work – for instance how do new devices on the network start up? How do they know what PTP domain is in use on the network?
John Mailhot starts by giving an overview of the standards and documents available, showing which ones are published and which are still in progress. He then looks at each of them in turn to summarise its use on the network and how it fits in to the system as a whole.
Once the groundwork is laid, we see how the JT-NM working group have looked at 5 major behaviours and what they have recommended for making them work in a scalable way. These cover things like DNS discovery, automated multicast address allocation and other considerations.
When? 10th Jan 2019. 1:00 PM EST / 10:00 AM PST / 18:00 GMT
TR 1001-1 from the JT-NM (Joint Task Force on Networked Media) gives guidance on protocols, configuration and architectures to use when setting up large ST-2110 systems.
John Mailhot and Brad Gilmer, both well trusted industry figures who are in the thick of creating and testing ST-2110 and the surrounding specifications, will lead us through what it is, what it tells us and, ultimately, how we can best go about creating a large ST 2110 system.
John Mailhot from Imagine Communications discusses what ‘Full Stack’ means for video over IP. The SMPTE 2110 suite of standards is mainly about the transport of essences – but how to you simply plug in some equipment and get going? You need standards which discover and register the new device, you need timing to synchronise devices. It’s a whole ecosystem.
John walks us through the data flows (and workflows) necessary when you plug new 2110 kit in and we quickly discover there is more depth than we imagined.
John also discusses how DHCP can give you more than just IP addresses.
Covering IS-04, IS-05, PTP/SMPTE 2059, ST 2110 and IEE 802.1AB (LLDP). This is a very practical video. Why? Because understanding all this is key to diagnosis and troubleshooting.
Despite the title, a relatively light and short video for the weekend from NAB on using audio in 2110.
Why is there a separate SMPTE ST 2110-30 standard from AES67? Are AES67 devices compatible with SMPTE ST 2110-30? Why is there a SMPTE ST 2110-31 standard? This presentation from Leigh Whitcomb (Architect, Imagine Communications) is a deep dive into the SMPTE ST 2110-30, 31 and AES67 audio and will answer all these questions.
Video from SMPTE Technical Conference taking a look at why Microservices is a common sense architecture for modern broadcast solutions. What are the alternatives and why are Microservices better?
Darren Gallipeau shows how architectures can break down into small building blocks allowing firms to deploy simpler applications rather than large monolithic applications. This allows easier testing, cross-use and flexibility.
1) What are Microservices?
2) Why do they matter – or what can I do with them?
3) What do they have to do with the future of cloud and virtualisation?
On Demand Webinar
John Mailhot, Imagine’s Architect for IP Convergence, provides a behind-the-scenes look at the real-world IP deployments that are happening today. Find out who’s doing it, how they’re using it and why they made the move.
Here’s just some of what you’ll take away:
Design best practices from IP early adopters
3 field-proven ways to build an IP-based plant
Facility-specific IP considerations — from small studios to mobile production to complex, geo-dispersed operations
Tried-and-tested tips for making a disruption-free IP transition