Video: Overview of MPEG’s Network-Based Media Processing

Building complex services from microservices not simple. While making a static workflow can be practical, though time-consuming, making one that is able to be easily changed to match a business’s changing needs is another matter. If an abstraction layer could be placed over the top of the microservices themselves, that would allow people to concentrate on making the workflow correct and leave the abstraction layer to orchestrate the microservices below. This is what MPEG’s Network-Based Media Processing (NBMP) standard achieves.

Developed to counteract the fragmentation in cloud and single-vendor deployments, NBMP delivers a unified way to describe a workflow with the platform controlled below. Iraj Sodagar spoke at Mile High Video 2020 to introduce NBMP, now published as ISO/IEC 23090-8. NBMP provides a framework that allows you to deploy and control media processing using existing building blocks called functions fed by sources and sinks, also known as inputs and outputs. A Workflow Manager process is used to actually start and control the media processing, fed with a workflow description that describes the processing wanted as well as the I/O formats to use. This is complemented by a Function Discovery API and a Function Repository to discover and get hold of the functions needed. The Workflow Manager gets the function and uses the Task API to initiate the processing of media. The Workflow Manager also deals with finding storage and understanding networking.

Next, Iraj takes us through the framework APIs which allow the abstraction layer to operate, in principle, across multiple cloud providers. The standard contains 3 APIs: Workflow, Task & Function. The APIs use a CRUD architecture each having ‘update’ ‘Discover’ ‘Delete’ and similar actions which apply to Tasks, Functions and the workflows i.e. CreateWorkflow. The APIs can operate synchronously or asynchronously.

Split rendering is possible by splitting up the workflow into sub workflows which allows you to run certain tasks nearer to certain resources, say storage, or in certain locations like in the case of edge computing where you want to maintain low-latency by processing close to the user. In fact, NBMP has been created with a view to being able to be used by 5G operators and is the subject of two study items in 3GPP.

Watch now!
Speaker

Iraj Sodagar Iraj Sodagar
Principal Researcher
Tencent America

Iraj Sodagar,
Tencent America

Video: The Fenix Project: Cloud-Based Disaster Recovery

“Moving to the cloud” is different for each broadcaster, some are using it for live production, some for their archives, some just for streaming. While confidence in the cloud is increasing and the products are maturing, many companies are choosing to put their ‘second MCR’ in the cloud or, say, tier-2 playout to test the waters, gain experience and wait for a fuller feature set. Sky Italia, has chosen to put all its disaster recovery transmission capability in the cloud.

Davide Gandino joins us from Mile High 2020 to show – and demo – their disaster recovery deployment which covers playout, processing, distribution and delivery to the end-user. Davide explains this was all driven by a major fire at their facility in Rome. At the time, they managed to move their services to Milan with minimal on-air impact, but with destroyed equipment, they were left to rebuild. It wasn’t long before that rebuild was planned for the cloud.

This is no insignificant project, with 117 channels of which only 39 are third-party pass-through going on to four platforms, the full deployment uses 800 cloud encoders. This amounts to 4Gbps being sent up to the cloud and 8Gbps returning. David highlights the design uses both Google and Amazon cloud infrastructure with 3 availability zones in use for both.

A vital part of this project design is that not all 800 encoders would be working 24×7. This misses the point of the cloud, but the only scalable alternative is fully automated deployment which is exactly what Sky chose to do. The key tenants of the project are:

  • Everything automated – Deployment and configuration are automatic
  • Software Defined – All Applications to be software defined
  • Distributed – Distributed solution to absorb the loss of one site
  • Synchronised – All BAU (business as usual) changes to automatically update the DR configuration. This is done with what Sky call the ‘Service Control Layer’.
  • Observed – Monitoring of the DR system will be as good or better than usual operation

To active the DR, Davide tells us that there is a first stage script which launches a Kubernetes cluster on which the management software sits and 13 Kubernetes clusters across Google and AWS which will run the infrastructure itself. The second script, uses Jenkins jobs to deploy and configure the infrastructure such as encoders and DRM modules etc. Davide finishes the talk showing us a video of the deployment of the infrastructure, explaining what is happening as we see the platform being built.Watch now!
Speaker

Davide Gandino Davide Gandino
Head of Streaming, Cloud & Computing Systems,
Sky Italia

Video: Growing the Next Generation of Us

Hiring is one of the most important things you will do in your company. Bad hires, at best, are a drain of money, time and opportunity costs. Good hires, on the other hand, can be incredible, long-term assets within your company. So when we have the new hire, we want to onboard them in the best way and continue giving them opportunities to learn and develop. This talk from Disney Streaming Services shares their progressive approach to developing engineers so they can handle the toughest moments when the production system is out of commission – AKA ‘the crucible’.

Alexanadria Shealy explains that teams are often made of people with a whole range of backgrounds, often people who are full of transferable skills, but with no specific from your exact domain. As teams grow, the team needs to constantly strive to onboard new people and bring them into the team both to work within the culture and to round off the skill set of the team at large.

Alexandria says their team has the best of intentions at all times and works hard to prevent any problems. As we all know, though, it’s impossible to prevent problems. “Scaling the software is easier than scaling the team,” she continues, and it’s best not to keep going back to the same people time and time again simply because they have become the experts as this isn’t scalable. The trick is to make the difficult things we do into something which is accessible for the inexperienced.
 

 
Kevin Fuhrman introduces ‘the crucible’ as a stressful place to be. It’s the time that you have a production outage which everyone is waiting to be fixed, and they’re repeatedly asking you when, and they’re watching you. But these fixes are never straight forward. They need a lot of focus and a lot of fault-finding. The stress of delivering under pressure adds to the stress of delivering under pressure. The crucible is not an easy place to be but is well known in broadcasters and streaming providers everywhere.

After your next outage, ask yourself how many of your staff would need to be on a bus travelling to their vacation before your team wouldn’t be able to handle it. In an ideal time, you’d have to have pretty much the whole team on holidays before you couldn’t deal with an outage. But many places know that if a few key people weren’t around, their ability to recover would be significantly compromised.

The advice from the Disney Streaming Services team comes in two packages. The first is taking care of onboarding your new colleagues. Looking for highly applicable tasks which have immediate relevance to them and will allow them to contribute quickly. They suggest giving new joiners a history lesson explaining why things are how they are. How did you choose the software your using, either the systems or the langauges. Explain what you would have preferred to do differently and better. This helps people understand what parts of the system they feel able to improve upon, in code as well as in workflow. It’s important, they explain, to help people spot the parts of the system which were put in because something was simply needed and the parts which are there due to a lot of thought and due diligence. Again, true of code as much as workflows.

We all know that mistakes are important in the learning process. One option laid out is to find parts of projects which are difficult enough to allow someone to dip their tow below the surface and to learn. The underlying point is not to shield junior members of the team from projects. In fact, heading a project with all your experienced engineers may be a way to deliver the project with low risk, but the cost of not investing in getting your less experienced team members involved will be paid when the project is delivered and needing support, maintenance and development. It also works against the interest of the less experienced individuals by reducing the speed at which they advance.

Alexandria and Kevin summarise by saying you should create and grow owners, rotate who is on the A-team, give everyone the chance to be in the crucible and share notes and experiences freely. The video finishes by remarking that the technology of today was built by us standing on the shoulders of giants. It’s important, therefore, that the giants of today remember to let people climb aloft.

Watch now!
Speakers

Alexandria Shealy
Director, Technical Project Management
Disney Streaming Services
Kevin Fuhrman Kevin Fuhrman
Staff Software Engineer,
Disney Streaming Services

Video: Usage of Video Signaling Code Points Automating UHD & HD Production-to-Distribution Workflows

As complicated as SD to HD conversions seemed at the time, that’s nothing on the plethora of combinations available now. Dealing with BT 601 and 709 colour spaces along with aspect ratios and even conversions from NTSC/PAL kept everyone busy. With frame rates, different HDR formats and wide colour gamut (HDR) being just some of the current options, this talk considers whether it would be better to bring in a ‘house format’ as opposed to simply declaring your company to be a ‘ProRes HQ’ house and accepting any content, HDR or SDR, in ProRes rather than being more specific regarding the lifestyle of your videos.

This talk from Chris Seeger from NBCUniversal and Yasser Syed from Comcast discuss their two-year effort to document common workflow video format combinations talking to companies from content providers to broadcasters to service distributors. The result is a joint ITU-ISO document, now in its second edition, which provides a great resource for new workflows today.

Yasser makes the point that, in recent years, the volume of scripted workflows has increased significantly. This can motivate broadcasters to find quicker and more efficient ways of dealing with media in what can be a high-value set of workflows that are increasingly being formed from a variety of video types.

Discussing signalling is important because it brings workflows together. Looking at videos we see that multiple sources arrive on left, need to identify correctly and then converted. This video talks about keeping separate video codecs and the identifying metadata needed for contribution and distribution which is best done automatically. All combinations are possible, but take advantages o the best content, having everything converted into a single, HDR-friendy mezzanine format is the way forward.

Watch now!
Speakers

Yasser Syed Yasser Syed
Comcast Distinguished Engineer,
Comcast
Chris Seeger Chris Seeger
Director, Advanced Content Production Technology,
NBCUniversal, Inc.