Introduction to media processing at scale in the cloud with visual effects and broadcast playout examples. Accompanying video: http://www.youtube.com/watch?v=HnGCtnmvogY&list=PL712EF2B0256960A3&index=2
2. Agenda
•
•
•
•
•
•
•
Media workflows
Where AWS fits
Scalability
Cloud media processing approaches
Amazon Elastic Transcoder
Visual effects example
Broadcast playout to web publishing example
3. “I think cinema, movies and
magic have always been
closely associated. The very
earliest people who made
film were magicians.”
— Francis Ford
Coppola
8. Media Workflows: The Real Magic
Archive
Networks
Insert a few
more
workflows
here
Theatrical
DVD/BD
Online
MSOs
Mobile Apps
9. Media Workflows: The Real Magic
Archive
Networks
Insert a few
more
workflows
here
Theatrical
DVD/BD
Online
MSOs
Mobile Apps
10. Media Workflows: The Real Magic
Featurettes
Interviews
2D Movie
3D Movie
Archive
Materials
Stills
Archive
Networks
Insert even
more
workflows
here
Theatrical
DVD/BD
Online
MSOs
Mobile Apps
11. Where AWS Fits Into Media Processing
Compute &
Networking
Application
Services
Database
Storage & Content
Delivery
Deployment &
Management
13. Where AWS Fits Into Media Processing
Analytics and Monetization
Amazon Web Services
Playbac
k
Track
Auth.
Protect
Package
QC
Process
Index
Ingest
Media Asset Management
15. Scalability, Is It Really That Important?
The business wants the new
library of content they just
signed on the VOD site
yesterday.
16. Scalability, Is It Really That Important?
A major event is taking place
and will be live streamed to a
worldwide audience.
17. Scalability, Is It Really That Important?
A second screen app ties-in
with a prime time event and
may have millions of
simultaneous users.
18. Infrastructure Cost
Scalability == Agility
Unable to
serve
customers
Large
Capital
Expenditure
Predicted
Demand
Opportunity
Cost
Traditional
Hardware
Actual
Demand
Cloud
Computing
Time
20. Cloud Media Processing Approaches: Phase 1
Phase 1
• Lift processing
from on-premise
and shift to the
cloud
21. Cloud Media Processing Approaches: Phase 2
Phase 2
Phase 1
• Lift processing
from on-prem and
shift to the cloud
• On-prem and cloud
hybrid model
• Refactor workflow
and cloud-optimize
22. Cloud Media Processing Approaches: Phase 3
Phase 3
Phase 2
Phase 1
• Lift processing from
on-prem and shift
to the cloud
• On-prem and cloud
hybrid model
• Refactor workflow
and cloud-optimize
• Cloud-native
architecture
24. A Transcoding Example
Hybrid and
Refactor
“Lift and Shift”
• Run existing
transcoding software
on AWS
• Run cloud versions of
existing transcoding
software
• E.g. Digital Rapids,
Elemental, Harmonic,
Sorenson, Telestream
25. A Transcoding Example
Cloud Native
Hybrid and Refactor
“Lift and Shift”
• Run existing transcoding
software on AWS
• Run cloud versions of
existing transcoding
software
• E.g. Digital Rapids,
Elemental, Harmonic,
Sorenson, Telestream
• Managed cloud
transcoding service
• E.g. Amazon Elastic
Transcoder,
Encoding.com, Zencoder
26. Amazon Elastic Transcoder
• Built in response to customer demand
• Designed for file-based high volume transcoding
• Simple, low-cost pricing starting at 1.5 cents per
minute of output
• Focused on OTT delivery formats
27. Amazon Elastic Transcoder Features
•
•
•
•
•
•
Fully managed cloud transcoding service
Elastically scalable
Output to MP4, WebM and HLS
Integration across AWS services
Available in multiple AWS regions
API and SDK driven
28. How To Scale With Elastic Transcoder
• Architect around Elastic Transcoder
• Use transcoding pipelines
30. How To Scale With Elastic Transcoder
• Architect around Elastic Transcoder
• Use transcoding pipelines
• Use notifications
31. Cloud Media Processing Summary
• Three different ways to transcode in the cloud
1. Lift and Shift
2. Hybrid and/or refactor
3. Cloud-native
• The right answer? It depends on your scenario
33. Visual Effects in Cloud
“Atomic Fiction has figured out how to use cloud
computing to its advantage, recently delivering 400
shots in only four months for Flight, Zemeckis’
return to live action. It’s a business model that’s
being viewed as the future of the industry.”
Bill Desowitz
Owner ImmersedInMovies.com
Contibuting Editor to Animation Scoop
35. Visual Effects Summary
•
•
•
•
High-resolution pre-release material
Only pay for what you use
Elasticity: scalability when you need it
Standard visual effects workflow using ZYNC
plug-ins with Maya, Mental Ray and Nuke
37. Project Objective
• Get broadcast content to VOD player ASAP
• Enable editorial clipping and review
• Create many different renditions for output
devices
• Elastically scale for high-demand situations (e.g.
breaking news and sporting events)
• Deliver agility for different types of processing
38. Playout To Web Workflow
SDI Feed
Amazon Elastic
Transcoder
Broadcast
Encoder
Business
Rules
Program
Data Feed
Live Ingest
Logic
Amazon S3
Re-assembled
Mezzanine
Elemental
Transcoder
DRM
QC
Editorial
Clipping
MAM
Amazon S3
Distribution
Renditions
39. Best Practices For This Project
•
•
•
•
•
•
Componentize, decouple and be stateless
Design for failure
If data is in motion, use queues
Run at least 3 of everything
Log everything
Use frameworks where possible
40. Project Results
• Quicker turnaround time
• Only pay for what they use
• Ability to support greater number of target
platforms
• Extremely resilient
• Better control over assets
41. Parting Thoughts
• Using AWS for scalable media processing is a
reality
• Different ways to architect:
– Lift and shift
– Hybrid and refactor
– Cloud-native
• Start now
Joined 2 years ago to focus on building a new media-related service.Couldn’t tell you what it was at last year’s eventNow it is Amazon Elastic TranscoderMedia credentialsWorked in event videoWorked on media technologies at MicrosoftTalk today about media processing in the cloud
We’ll cover:Media workflowsWhere and how AWS fits into those workflowsWhy scalability is importantApproaches for cloud media processingNext I’ll talk about Amazon Elastic TranscoderWhat it doesWhy we built itHow it fits into a media workflowThen we’ll have a media processing example for video effectsFinally, I’ll talk about a broadcast example where the broadcaster wants to take content from their playout system and publish it to their web-based VOD service.But first I’m going to talk about magic.
Movie aficionados often talk about the magic of film.After all movies are all about making the audience believe what’s taking place on the screen.And in fact as this well known director says, the history of film and magic is intertwined.Those of you who saw the film Hugo might recall, French magician Georges Méliès invented so many of the movie techniques that we take for granted today: stop trick (where an object disappears), multiple exposures, time-lapse photography, dissolves and hand coloring. What’s amazing is that he did this in the 1900s.
Cameras capture the on-set magic.Beautifully lit scene from a lighting masterclass at Mole Richardson.Glass = ArriAlexa. Light gathering magical box.Super 35 sensor generates almost 20GB for every minute that’s shot.Many of you will be familiar with shooting ratio: the ratio of how much material that’s shot on camera to makes it into the final edit.Conservative number is 10:1. 10 minutes 1 minute.Today’s features are about 140 minutes in duration.With that shooting ratio that’s 26TB before you even think about multiple cameras.100TB for a movie is not unreasonable. We’ll come back to that a bit later.
Now look at the glass at the other end: the screen.And it is a magical experience to watch a movie on a big screen.This one here is at the CGV Starium in Korea.Supposed to be largest in the world: 4000 sqft – almost a basketball court.They use a couple of Christie 2K projectors to power the screen so that’s about 3GB/minute.But I think the real magic is what needs to happen to get the beautiful big images to the beautiful big screen.
The media workflow or the glass to glass workflow is the real magic.Behind every great magic trick is science and engineering. Sorry to disappoint you but David Copperfield doesn’t really levitate: he uses a harnessThe disappearing Statue of Liberty? Stage netting and lighting.All of which requires science and engineering.So what about our media workflows?Media workflowss are part of the engineering that make the magic of the movies possible.
Well you probably all have at least dozen ways to get from camera to screen and then we have things like The Academy’s color workflow.So you’ve got your workflows and that gets you to one screen…
But now you’ve got all these other outputs.
But now you’ve got all these other outputs.And many of them have multiplesHow many online devices do you support?How many different edits, languages, and so on
And an ever increasing number of content sources.In fact we hear that over the course of its life, a particular asset may have been converted 1,000 times.
So where does AWS fit into media processing workflows?As you’ve heard today, we provide infrastructure services: compute, networking, database, storage and delivery and so on. We also provide application services and deployment and management services. Using these services, as your “software defined datacenter”, you can build media processing workflows.
Typical operations in a media workflow would run on top of the AWS services. These operations could be provided by software that you’ve developed or they might be from another vendor like Aspera for ingest or Tektronix for video QC.
On top of all that you’d have business level applications like what Ben’s team at Sony built.
Now one thing you’ve heard us talk about is scalability. I said earlier that you can think of us as a datacenter in software. You need another compute instance, you can create one at the click of a mouse or ideally through code that creates and destroys instances as it needs to. And that’s elasticity – the ability to not only scale up but also to scale down when you need to.We say that you pay for what you use, so build your media processing in such a way to take advantage of that.
So
So now that you’re convinced that AWS is the way to go to build your media workflows on, how do you go about it?
All broadcast content available through catch up servicesSome content is file-basedSome comes from broadcast playout systemContent usually needs some editorial clippingLots of output devices including set top boxes and streaming devices