Where are my Closed Captions? Managing and …bento.cdn.pbs.org/hostedbento-prod/filer_public/2013/04/...Looking at a simplified view of a typical playout workflow, we will find programs,

Where are my Closed Captions? Managing and Monitoring

Ancillary Data

Sara Kudrle Miranda Technologies

A BELDEN Brand

Wild West of Files Anatomy Lesson

Manage The Chaos

Wrap It Up The Poor Cousin

What We Can Do Now

Ingest and Quality Control

Playout and Graphics

Publishing for On Demand

Editing and Content Prep

Live Production

Media Management and Storage

Automation

Linear Channels

Pre- Produced Content and Ads

WAN Non Linear Delivery WAN

Typical Television Broadcast Facility and Workflow

Presenter

Presentation Notes

Looking at a simplified view of a typical playout workflow, we will find programs, promos and advertising which need to be ingested and checked for quality, then be formatted for air and finally be presented at a given time according to a schedule through a chain of equipment used to build the final output. ** Traditionally the content arrives as tapes and satellite feeds ** but increasingly this material is delivered as files over a Wide Area Network or on a physical support. ** Most always the final result of a playout operation is directly fed to air ** but increasingly the same or a very similar version of the content will be delivered as files for non-linear consumption through VOD or other modes of on-demand content delivery. Nowadays, the only areas of workflow that have been very little affected by files remain Live Production and the actual output of the playout chain ** most other areas of playout have been touched in one way or another by the advent of file centric systems.

Broadcast Facilities Have Been Stream / SDI Centric



Non Linear Publishing


Live Production


Automation

Linear Channels


WAN

Linear Feeds

Tape (Linear Medium)

Linear Streams

Isolated Islands of IT / File Based Infrastructure

Broadcast Industry Specific SDI Infrastructure

Non Linear Delivery WAN

Today Facilities Becoming Increasingly “File Based”



Non Linear Publishing


Live Production


Automation


Live Production

Linear Channels


WAN

Tape (Linear Medium) Non Linear

Delivery WAN

Media Files

Media Files

Linear Feeds

Linear Streams

Isolated Islands of IT / File Based Infrastructure



IT / File Base Infrastructure

Presenter

Presentation Notes

This has had a deep effect on the nature of the infrastructure required to support playout and has transformed yesterday’s facility which was almost solely based on SDI ** to an entirely new beast where SDI is mostly relegated to Live requirements and files carried over data networks have become the new blood of the infrastructure.

It Was So Easy in the Good Old Days

Video: Location Fixed, Format Specified (SMPTE-292M / 274M …) Audio: 16 Channel, Location Fixed in ANC Data Space (SMPTE-299M) Timecode: Location Fixed in ANC (SMPTE-291M) Captions: Location Fixed in ANC (SMPTE-299M) AFD: Location Fixed in ANC (SMPTE-2016M) Dolby Metadata: Location Fixed in ANC (SMPTE-2020M)

HD-SDI

Presenter

Presentation Notes

As with any paradigm shift in technology, underneath the obvious potential benefits, there are many problems with the details. Take ingest: I’m sure many of you believe it was easier in the old days of dubbing. Connect an SDI cable to a source and the content you need would record for storage and playout. This was possible because of well-established and rigid standards. You could replace one device with another and most often, it would work just as well. With SDI video, some required pieces of metadata also made the trip intact.

Perhaps Too Easy?

Essence Descriptors: • SOM: HH:MM:SS:FF • EOM: HH:MM:SS:FF

• Audio 1, 2:e Dolby E Descriptive Metadata:

• Title • Episode

• Creation Date

THESE DATA?

HD-SDI

Presenter

Presentation Notes

However, as the list of metadata required for playout grew, this wasn’t sufficient for long. We now had a second list of items that was needed, but not carried in that SDI signal. Other metadata that would be needed was simply left to other systems to manage, such as traffic and automation. Unfortunately, one of those problematic details is that the shift to file-based content anticipates that those required metadata will be included in that file. This, of course, will greatly simplify the upcoming processes of content preparation, storage and playout. So let’s see how we’re doing with that.

Contrasting the good ‘ol days versus today

• File wrapper format “standards” that are too loose and interpreted in too many different ways (e.g. MXF)

WAN Files

• Missing / misplaced meta data

SDI

• “Iron Clad” tape formats • “Cast in stone” device

interconnect (SMPTE SDI) with precise

• No provisions for descriptive meta data

Then (the good ‘ol days)

Today (the wild west)

Presenter

Presentation Notes

This important shift in technology has come at a cost. I am pretty sure that some of you think that it used to be much easier in the good old days of dubbing. Connect an SDI cable and everything would copy across from one machine to another. ** This was possible because of very well established and rigid standards. ** You could replace one device with another and most often rest assured that it would work just as well. Of course these standards are still around but the advent of files has multiplied the number of formal or de facto standards that modern systems need to comply to sometimes more, sometimes less successfully. The diversity of file wrappers, codecs and essences has created a situation where every little detail of every element in a file needs to be documented AND implemented by all software manufacturers in order to work.

The Early Days of File Based Same Vendor Provides Ingest and Playout

SDI

SDI

SDI

Third party media server

Homogeneous Environment ONE Common File Format

INGEST PLAYOUT

STORE

Presenter

Presentation Notes

In the early days of file-based playout systems, most often users would continue using their existing SDI workflow ** and ingest from tape ** or from satellite feeds ** This even included server-to-server transfers ** This resulted in very homogeneous environments.

Today’s Reality – The Wild West of Files

SDI


INGEST

PLAYOUT

STORE

Networked VTRS

WAN File Delivery Service

IMX

LXF

?XF Ethernet /

IP Network

MXF Flv A

Presenter

Presentation Notes

Today, an increasing amount of content is received or transferred as files. Most often these files are of different formats and rely on the agility of the destination system to be properly interpreted. You can call that the “Wild West of Files”.

Most File Formats are Not

Interoperable

IMX LXF ?XF MXF Flv X X X X


Manage The Chaos


What We Can Do Now

Anatomy of a Media File

Wrapper

Codec

Essence

Presenter

Presentation Notes

First, let’s look at the anatomy of a media file. ** It all starts with the essence. The essence is the video, the audio, the ancillary data or descriptive metadata that make up the essence of the file. Let’s compare this to the juice of an orange. This is ultimately what we’re after when we create, copy, process or playback a media file. ** Let’s then take this orange juice, concentrate to reduce its size and freeze for easy conservation. This is essentially what a codec does. It most often reduces the size of the essence in a file in a way that is predictable so that it can be retrieved at a later time. Codecs can be lossless or lossy but even with the latter your objective is to retrieve the essence of the file as close as it was to begin with given the “concentration” benefits that you were looking for in a codec. ** Most often, the codec will be stored in a wrapper. Here the analogy is the cardboard can that will be used to contain the frozen orange juice. Most of the time, the role of the wrapper will be to contain more than one essence and maintain the relationship between all of them.

Anatomy of a Media File

Ties Essence together & describes it • Structural metadata such as SOM, EOM,

Duration, types of media included in file, etc. • Descriptive metadata such as creation date, usage

rules, key words • Time References and Index

• Video (typically compressed) • Multiple Audio (often compressed) • Ancillary Data (e.g. Captions, AFD, …)

“Essence”:The actual media which includes:

Wrapper:

Media File

Presenter

Presentation Notes

The wrapper ties the essence together and describes it ** It includes all the structural metedata such as In and Out points, Durations, Essence descriptors ** Descriptive metadata such as creation date and keywords ** As well as indexes and temporal references ** The essence is the actual media and includes ** video, audio and Ancillary Data

Two Storage Approaches

Wrapper

Descriptive Metadata

Timecode / index

Video Essence

Audio Essence(s) Audio Essence(s)

Ancillary Data Essence

Method 1: Embedded Essence

Examples: • MXF XDCAM • GXF • LXF

One File

Structural Metadata

Method 2: Reference Files / External Essence

Wrapper


Timecode / index

Video Essence



Structural Metadata

Main File

Multiple “Referenced” Files

Examples: • Omneon MOV • MXF P2 • MXF AS-02

Presenter

Presentation Notes

There are two main ways to relate wrappers and essence. ** The first method is the embedded essence where all elements are stored in a single file. ** Examples include MXF XDCAM, GXF and LXF ** And there is also an alternative method where the essence is stored as one or multiple separate files top the wrapper. This is called external essence and the wrapper is often referred to as a Reference File. ** Examples include Omneon MOV, MXF P2 and MXF AS-02 Files can sometimes be hybrid and embed some of the essence while also referencing some external additional essence files.

Two Storage Approaches

Wrapper


Timecode / index

Video Essence



Method 1: Embedded Essence

Examples: • MXF XDCAM • GXF • LXF

One File

Structural Metadata

Method 2: Reference Files / External Essence

Wrapper


Timecode / index

Video Essence



Structural Metadata

Main File

Multiple “Referenced” Files

Examples: • Omneon MOV • MXF P2 • MXF AS-02

Benefit: one file includes everything, easier media management

Benefit: Additional essences can be more quickly added after the fact (e.g multiple languages audio and captions)

Presenter

Presentation Notes

There are two main ways to relate wrappers and essence. ** The first method is the embedded essence where all elements are stored in a single file. ** Examples include MXF XDCAM, GXF and LXF ** And there is also an alternative method where the essence is stored as one or multiple separate files top the wrapper. This is called external essence and the wrapper is often referred to as a Reference File. ** Examples include Omneon MOV, MXF P2 and MXF AS-02 Files can sometimes be hybrid and embed some of the essence while also referencing some external additional essence files.


Manage The Chaos


What We Can Do Now

Popular Wrapper Formats

Vendor Specific Wrappers Associated with Camera and VTR Formats

Vendor Specific Server Formats

Generic Industry Wrappers

.MOV

P2 MXF (Panasonic)

Wrappers Originating in PC/Multi-Media

MXF OP1a

MXF-AS-XX

GXF (Grass Valley)

LXF (Harris)

IMX/XDCAM MXF (Sony)

.AVI

MPEG TS File

Television Distribution format

Presenter

Presentation Notes

Let’s look at a list of popular wrapper formats that you are likely to be familiar with. ** One of the oldest still in use is the MPEG Transport Stream file. Technically this is not a file format but rather a distribution bitstream captured to a file. ** MOV and AVI. These originate from over 20 years ago as some of the first widespread Personal Computer formats. ** XDCAM and P2 MXF. These are wrapper formats closely associated to VTR and camera manufacturers. ** The we have generic industry wrappers such as MXF OP1a and AS-02 ** And finally, we have some vendor house formats which sometimes are a bit more difficult to interpret especially when they contain undocumented metadata

Key Features of Popular Media Wrappers

MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2 MXF

Avid MXF

(OP Atom)

MXF AS-02

Editing NLE Support Random Access Edit-while-ingest Playout Transcoder Support Native Server Support ANC carriage Additions/Changes without full remux Archiving Descriptive Metadata Carriage Future-proofness

Popular Wrapper Formats

Presenter

Presentation Notes

Here are some of the characteristics you may be looking for in a wrapper in relation to their capabilities in ** Editing ** Playout * Archiving


MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2 MXF

Avid MXF

(OP Atom)

MXF AS-02


Key Features / Functionality


MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2 MXF

Avid MXF

(OP Atom)

MXF AS-02


Not Supported

(Bad)

Strongly Supported (Very Good)

Partially Supported


MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2

MXF

Avid MXF

(OP Atom)

MXF AS-02


Observation 1: There are a lot of wrapper formats and they are obviously very different

Observation 2: No ONE wrapper format supports all the identified functionality

Presenter

Presentation Notes

Let’s now take a look at some of the key characteristics relevant to playout for some of the most popular file formats in use today. ** BUT before you head starts spinning and you rush to take note of all of this. Please understand that the characteristics and ratings shown here are debatable views on these file formats. You may not fully agree with what is in this table. This table is meant to illustrate the complexity of the situation and try to explain why there are so many formats available on the market. This also tries to illustrate that there isn’t any magic format that does it all, at least today. As a first observation we can see that there are a lot of wrapper formats and that they are obviously very different. ** We can also observe that No ONE wrapper format performs well at all the identified functionality


MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2

MXF

Avid MXF

(OP Atom)

MXF AS-02


Observation 3: There are a couple clear “bad choices”

Presenter

Presentation Notes

However, there seems to be a few clear bad choices.

MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2

MXF

Avid MXF

(OP Atom)

MXF AS-02


Observation 4: At first glance MXF appears promising but in reality has turned out to have major interoperability issues


Presenter

Presentation Notes

At first glance MXF appears to be interesting


MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2

MXF

Avid MXF

(OP Atom)

MXF AS-02


Observation 5: Hard-core constraints (Tape Fmt Heritage), Clearly Documented, No Ambiguity Reasonable bit rate (HD at 50 Mbps), Wide NLE and Server Support IMX / XDCAM MXF has turned out to be a very popular Generic File Format

Presenter

Presentation Notes


Wrapper Divergence!

Why MXF Cannot Solve All The Issues

More Specific More constraints Better Generic MXF

LXF Leitch Harris

GXF Grass Valley

IMX/XDCAM MXF Sony

Vendor Specific Variants

Generic Variants

• Far too loose & flexible

• Subject to broad interpretation

• No hard reference

• Vendor specific • Some published • Some proprietary • Overly constrained • Harder to Extend • No reference

implementation

AS-02 Versioning

AMWA Application Specifications

AS-03 Program Delivery

AS-10 Production AS-12

Ad Delivery

AS-11 Contribution

• Constraints on MXF for different Applications

• Industry Standard ?

AMWA MXF AS-XX Application Specifications • Defined by AMWA (Advanced Media Workflow Association)

• AS-XX MXF Specifications Define a set of rules / constraints on MXF to suit a particular use

• Defines MXF use for different situations / applications • Shims constrain further to meet needs of a user

MXF

Constrained Parameters, and Values

Available Codecs

Constraints on Codecs and

Bit-rate ranges

AS-XX - Application Specification User A SHIM User B SHIM

Presenter

Presentation Notes

AS stands for Application Specification. This is not a new version of MXF but rather a constraint on MXF defined by AMWA. It defines the storage of MXF program components to enable multi-version, multi-lingual MXF files. A great advantage of AS-02 is that it allows ** any number of Audio and Caption ** tracks to be added and chosen at playout time.

AS-XX Format Summary

Number Application Domain Essences CODECs

HD Bit Rates (Mbps)

Meta Data

AS-02 Versioning External Not Specified Depends on Codec


Embedded MPEG2, H.264 LGOP

5-50 Mb/s

AS-10 Production (e.g. Sony XDCAM MXF)

Embedded MPEG-2 MP@HL, MPEG-2 422P@HL MPEG-2 MP@H14 LGOP

Depends on Codec

AS-11 Contribution Embedded AVC Intra 100 Mbps

AS-12 Ad Delivery Embedded MPEG2, H.264 LGOP

5-50 Mb/s

PGMX_HDVideo.mxf -

AS02_clips

PGMX_Audio_English.mxf PGMX_Audio_Spanish.mxf

PGMX - PGMX_English.mxf

Media

PGMX_Spanish.mxf

-

PGMX_ANC_English.mxf PGMX_ANC_Spanish.mxf Extra

• Defined by users (AMWA members)

• Places constraints on MXF for versioning of synchronized essences

• Allows any number of audio and caption tracks to be added and chosen at playout time

MXF AS-02

Presenter

Presentation Notes

As mentioned, AS stands for Application Specification. This is not a new version of MXF (that is, an OP or Operational Pattern), but rather a set of constraints on MXF defined by Advanced Media Workflow Association. AS-02 defines the storage of program content in MXF that enables multi-version, multi-lingual files. This simple statement makes AS-02 an immediate candidate as a playout format in the worldwide market.

MXF AS-03

• Optimized for the delivery of finished programs • Carries built-in metadata relevant to playout:

– House ID, ISAN, Ad ID/ISCI or UUID – Slate Title – Series Code and Episode number – SOM/EOM – AFD Code, V-Chip Rating, Nielsen Stream ID

Presenter

Presentation Notes

AS-03 further constrains the model defined by AS-02 to support a single program version with a single language.

MXF AS-02 to AS-03 Re-Wrapping

• Going from AS-02 to AS-03 is a simple re-wrap operation

• Think of AS-03 as a flattened, single language version of AS-02

PGMX_English_AS-03.mxf

PGMX_HDVideo.mxf -

AS02_clips

PGMX_Audio_English.mxf PGMX_Audio_Spanish.mxf

PGMX - PGMX_English.mxf

Media

PGMX_Spanish.mxf

-

PGMX_ANC_English.mxf PGMX_ANC_Spanish.mxf Extra

AS-03

Presenter

Presentation Notes

Moving from AS-02 to AS-03 is a re-wrap operation and is thus very fast. As a pair, AS02 and AS-02 provide an optimized wrapper choice for file-based playout.

Different AS-XX Specifications for Different Apps

AS-12 Ad Delivery

Regional Playout Facility Central Broadcaster / Playout Content Creation

AS-02 Versioning

AS-10 End to End ( Acquisition – Production – Playout)

AS-11 Contribution

Aquisition Post Contribution Playout Preparation Distribution


Packaging of multiple versions of same program Multiple Languages, Multiple Editorial Versions

Delivery of finished programs. Single File, single audio language, constrained codecs

Delivery of finished Commercials. Identical to AS-03 but with Advertising specific Meta Data

Enable Interoperation and an end to end workflow without transcoding. Specifies Long GOP MPEG2 codec at a decent bit rate Designed as extension to SMPTE RDD 9 and is used by IMX & XDCAM-HD

Vendor-neutral file format for the delivery of finished program material. Similar to AS-03 but features higher bit rate AVC-Intra video and uncompressed Audio

Presenter

Presentation Notes

AS stands for Application Specification. This is not a new version of MXF but rather a constraint on MXF defined by AMWA. It defines the storage of MXF program components to enable multi-version, multi-lingual MXF files. A great advantage of AS-02 is that it allows ** any number of Audio and Caption ** tracks to be added and chosen at playout time.

Different AS-XX Specifications for Different Apps

AS-12 Ad Delivery

Regional Playout Facility

Central Broadcaster / Playout

Content Creation

AS-02 Versioning

AS-10 Production using Long GOP Codec (e.g. XDCAM)

AS-11 Contribution

Aquisition Post Contribution Playout Preparation Distribution


Delivery of finished programs. Single audio language, constrained codecs

= User A SHIM User B SHIM Observation : Even within versions, AMWA has specified that “An Application Specification can be further constrained to meet the needs of a user through use of a SHIM”

In other words, they are different

• Constraints on MXF for different Application

• Industry Standard ? More

Specific Better

MXF

LXF Leitch/Harri

s

GXF Grass Valley

IMX/XDCAM MXF Sony

Vendor Specific Variants

Generic Variants

AS-02 Versioning

AMWA Application Specifications


AS-10 Production AS-12

Ad Delivery

AS-11 Contributio

n

Why MXF Cannot Solve All The Issues

Presenter

Presentation Notes

If Only there were One Wrapper to Wrap them all…. Hmmm


Manage The Chaos


What We Can Do Now

MPEG2 TS

MOV/ MP4 AVI

GXF or

LXF

Gen MXF

IMX/ XDCAM

MXF

P2 MXF

Avid MXF

(OP Atom)

MXF AS-02 / AS-03

Timecode *** *** *** *** *** *** ***

Captions *** ** *** *** ** ** ***

AFD *** *** *** ** ** ***

Dolby Metadata

*** *** *** ** ** ***

V-chip *** *** *** ** ** ***

Ad Insertion Triggers

*** *** *** ** ** ***

Ancillary Data Support by Wrapper

Presenter

Presentation Notes

For wrapper support of Ancillary Data, MPEG Transport Stream does a great job, but as we’ve seen, it has weaknesses in other areas GXF and LXF also do the full job here. MXF is now doing much better with Ancillary Data, thanks to the SMPTE 436m standard- which is gaining some momentum in the industry

Ancillary Data Four main ways to carry Ancillary data in files

In the VBI portion of video (IMX only) In the MPEG GOP Header (limited) In the wrapper (limited) As a s436m payload

ANC Data In Legacy File Formats Was Inconsistent and Incomplete

HANC Audio T/C

VANC AFD, Dolby, CC, VCHIP, SCTE Triggers, Private Data

Active Video

File Wrapper

Video Essence

Audio Essence (s)

Some ANC in Codec Header

Some ANC in Wrapper Meta

SDI

Time Code

And / Or

Some, Not All

Some ANC in VBI (SD only)

Legacy File Formats

Ancillary Data

Dolby Metadata

SCTE-104 Ad Triggers

Broadcast Flag

OP47 Teletext

Private Data

$

XDS V-Chip WSS AFD

Timecode Closed Captions

Presenter

Presentation Notes

The most common ancillary data that needs to be used in playout include: Timecode Captions XDS V-Chip Wide Screen Signaling and AFD codes

VBI (IMX Only)

Ancillary Data

Dolby Metadata


Broadcast Flag

OP47 Teletext

Private Data

$

XDS V-Chip WSS AFD


Presenter

Presentation Notes

All of these can be carried in VBI but again this is only available with IMX files.

VBI (IMX Only) Codec Header

Ancillary Data

Dolby Metadata


Broadcast Flag

OP47 Teletext

Private Data

$

XDS V-Chip WSS AFD


Presenter

Presentation Notes

In order to get around this limitation, many have started encoding this data as part of the MPEG User Data but this approach is not always supported and interoperable.


Wrapper Metadata

Ancillary Data

Dolby Metadata


Broadcast Flag

OP47 Teletext

Private Data

$

XDS V-Chip WSS AFD


Presenter

Presentation Notes

An alternative is to carry it with the wrapper structural metadata or as a data track but most implementations are quite limited.

Dolby Metadata


Broadcast Flag

OP47 Teletext

Private Data

$


Wrapper Metadata

Key ANC Data not Captured

Ancillary Data

XDS V-Chip WSS AFD


ANC Data In Legacy File Formats Was Inconsistent and Incomplete

HANC Audio T/C

VANC Various ANC Data

Active Video

Original Source Video Legacy File Formats

File Wrapper

Video Essence

Audio Essence (s) Time Code

Playback Video

Ingest HANC Audio T/C

VANC Various ANC Data

Active Video

Playback

Missing ANC Data

Can’t Easily Add or Modify ANC Data to File

Original ANC Data Subset of

ANC Data


Manage The Chaos


What We Can Do Now

SMPTE To the Rescue

SMPTE 436M: MXF Mappings for

VBI Lines and Ancillary Data Packets

Codec Header

Wrapper Metadata

SMPTE 436m

Key ANC Data NOW Captured

Ancillary Data

XDS V-Chip WSS AFD


Dolby Metadata


Broadcast Flag

OP47 Teletext

Private Data

$

Presenter

Presentation Notes

Finally, SMPTE 436m seems to be the perfect solution since it allows the carriage of all basic Ancillary Data and more. Amongst others it adds support for OP47 Teletext, Dolby Metadata, Broadcast Flags, SCTE-104 triggers which are used for dynamic ad insertion and more ** Finally ANY Ancillary Data

Wrapper

Video Essence

Audio Essence

SMPTE 436 ANC Essence CC

AFD DOLBY SCTE Propri

Frame Accurate Index DID ANC

Data Line Num H C

S

MXF File with 436M Essence

CC AFD

DOLBY SCTE Propri

CC AFD

DOLBY SCTE Propri

CC AFD

DOLBY SCTE Propri

Typical SMPTE 436 Packet

SMPTE 436 Dramatically Improves ANC Carriage


HANC Audio T/C

VANC AFD, Dolby, CC, VCHIP, SCTE Triggers, Special Data

Active Video

SMPTE 436 ANC Essence

SDI MXF File with 436M Essence

File Wrapper

Video Essence

Audio Essence (s) Time Code

ALL ANC

HANC Audio T/C

VANC DID tagged streams

Active Video

VANC Audio T/C

VANC DID tagged streams

Active Video SMPTE 436 ANC Essence


File Wrapper

Video Essence

Audio Essence (s)

Time Code

Original Source Video Playback Video

Ingest Playback

Add and Modify ANC Easily

Original ANC Data

Original ANC Data Augmented ANC Data

Original ANC Data Augmented ANC Data


Ancillary Data Using SMPTE 436M

Standardized by SMPTE in 2006 Can carry any DID/SDID (i.e. future-proof) Carried as a separate essence payload in MXF

Can be embedded or referenced Easy to re-wrap Easy to Add / Modify

Supported in MXF and AS-N Application Specifications Now being added to SMPTE RDD9 for AS-10 / IMX/XD-CAM

SMPTE-436M Ancillary Data

Carriage in Files

It solves the biggest file interoperability problems we have experienced

The most important thing to happen to File Based since the folder was invented

Presenter

Presentation Notes

** S436m was standardized by SMPTE in 2006 ** It can be used to carry a full playload of VBI/ANC including any DID/SDID (i.e. future-proof) ** It is carried as a separate payload in MXF. Can be embedded or referenced (e.g. AS-02). It is easy to re-wrap. ** It is “tolerated” in IMX/XDCAM by most applications. Although technically outside of SMPTE RDD-3/9 ** Ask your preferred vendor to implement it if they haven’t already done so.

MPEG-2 TS

MOV / MP4 AVI

GXF &

LXF Generic

MXF

IMX / XDCAM

MXF P2

MXF

Avid MXF

(OP Atom) MXF

AS-02 Editing NLE Support Random Access Edit-while-ingest Playout Transcoder Support Native Server Support ANC carriage Additions/Changes without full remux Archiving Descriptive Metadata Carriage Future-proofness


ANC Carriage had been weakness of IMX/XDCAM MXF

Now with inclusion of SMPTE 436M ANC Carriage becomes supported

436M

Presenter

Presentation Notes


Contrasting the good ol’ days versus today

• File format standards that are interpreted in too many different ways (e.g. MXF)

WAN Files

• Multiple Codec formats??? • Multiple file wrapper formats • Missing / misplaced

meta data

SDI

• “Iron Clad” tape formats • “Cast in stone” device to

device interconnect (SMPTE SDI)

Then (the good ol’ days)

Today (the wild west)

Incompatible wrappers

Inconsistent, non-extendable ANC data carriage

Improved file Interoperability

SMPTE 436M

AS-XX Specifications AMWA

Presenter

Presentation Notes

AS holds promised to Pay attention to these two things

http://www.amwa.tv/index.shtml

What We Can Do Now


Manage The Chaos


In an Ideal World…..



File Wrapper

Video Essence

Audio Essence (s)

Time Code

There would be one wrapper to wrap them all!

Presenter

Presentation Notes

Applications for monitoring and – extracting, modifying and re-baking There could be captions in many areas Multiple language tracks – multiple caption tracks There could be captions in the VBI – in line

And All Sources Would Be Wrapped The Same


INGEST

PLAYOUT

STORE

Networked VTRS


Ethernet / IP Network

MXF

MXF

MXF

MXF

And It Would Be Simple to Find Your Data – Especially Captions



File Wrapper

Video Essence

Audio Essence (s)

Time Code

Here is Your Data – AND YOUR CAPTIONS!

The Reality….

SDI


INGEST

PLAYOUT

STORE

Networked VTRS


IMX

LXF

?XF Ethernet /

IP Network

MXF Flv A

What Can You Do?

1.Have a Playout System that can handle ALL Types of File Formats

2.Normalize ALL Files at Ingest to One File Format

Option 1: Playout System The SKILLED factory approach

IMX

LXF

?XF

MXF Flv A

MOV

AVI

GXF

GXF LXF IMX MOV MXF Flv A ?XF AVI

Presenter

Presentation Notes

This is the common approach of playout systems is to support every type of file format. This is what we did, we did not create a format of our own, rather we created a system that would work with everyone else’s format. This takes a skilled engine to recognize the file types and carry them through and turn them into something that will playout at the end.

Option 2: Normalize Files The UN-SKILLED factory approach

IMX

LXF

?XF

MXF Flv A

MOV

AVI

GXF

MXF MXF MXF MXF MXF MXF

Presenter

Presentation Notes

Normalizing the files at ingest will keep processing simple. This will handle the case where ancillary data is duplicated in more than one place. The ancillary data will be placed into the S436 space and will be easy to locate. Also if captions or data needs to be changed it will be easier to change and replace the data, since we know where it is. Playout is simplified, as all files are the same format at that point.

Anything That Can Be Done in SDI Needs to Happen in Files

SD Source HD Source 608

708

Presenter

Presentation Notes

For instance, you have an SD source with 608 captions in line 21. However, you need to convert the source to HD and therefore you need to extract the 608 captions, inspect them and turn them into 708 captions and add them into the newly created HD source. This needs to happen at the file level, despite whatever file format the files arrive in. They either need to be identified and the data extracted from the locations that matches the file type or the file need to be normalized and then the data can be extracted from one known location.

Need to be able to Analyze More Than the Essence

File Processing Factory

Graphics Up/Down/X Convert

Video Decode

Video Encode

Loudness Measure / Adjust

Up/Down Mix

Audio Decode

Audio Encode

V-chip AFD CC, Subtitles

Dolby Metadata

Audio Mapping File

unwrap

File wrap

Nielsen Watermark

MPEG Stitching / ReMuxing

Presenter

Presentation Notes

Here is a possible file processing factory. Not only do we need to be able to wrap and unwrap, decode and encode, but we need the ability to extract ancillary data and examine it, modify it, and replace it with ease.

Need to be able to Preview and Manage Offline

• Metadata viewing / editing • Media preview

Monitor The Results

FRE ITA ENG DVB Subtitles

PGM Les Expos sont de retour avec une avance de 9 a 1

Expo sono tornati con un vantaggio di 9-1

ITA FRE

Missing Captions / Subtitles

COM

Presenter

Presentation Notes

Captions are also something that need to be monitored and is becoming as important as freeze or video blacks and audio silences.

What Can I Do? S436m

Get Involved!

Vendor Validation Ask for it!

Presenter

Presentation Notes

Get Involved Currently work is being completed to move ST436 to SMPTE current template Fix conformance language Resolve single video stream problem, and element ordering and padding issues Vendor Validation Effort – validation tests performed – Cinegy is going through this (I believe) – MXF and S436. – verify compliance. ** Ask your preferred vendor to implement it if they haven’t already done so.

Comments or Questions?

[email protected]

Documents

Where are my Closed Captions? Managing and …bento.cdn.pbs.org/hostedbento-prod/filer_public/2013/04/...Looking at a simplified view of a typical playout workflow, we will find programs,