Advanced Content Management In Demanding and Decentralized ...€¦ · Advanced Content Management In Demanding and Decentralized Environments Alex Grossman ... •Basic OTS MAM •MAM

© 2019 • SMPTE® | Enabling Global Education • www.smpte.org

SMPTE Technology Series Webcast


Advanced Content Management In

Demanding and Decentralized Environments

Alex Grossman

[email protected]

SMPTE Technology Webcast Series Sponsored by:

Your Host

Joel E. Welch

Director of EducationSMPTE


1

2

mailto:[email protected]


SMPTE Technology Webcast Sponsors

• Thank you to our sponsor for their generous support:


© 2019 • SMPTE® | Enabling Global Education • www.smpte.org 4

3

4


SMPTE Technology Webcasts

• Series of monthly 60- to 90-minute online, interactive webcasts covering a variety of technical topics

• Free professional development benefit for SMPTE members

• Sessions are recorded for member viewing convenience.


Housekeeping

• If the stream should stop, please refresh your browser window

• Please type your questions in the chat box

• SMPTE provides a PDF of select slides used during webcasts in exchange for your feedback

• Once your feedback is submitted, you will automatically be redirected to the PDF for downloading

• Please feel free to post or blog about today’s webcast on your social media platform of choice

@smpteconnect

#SMPTEWebcast

#EnablingGlobalEducation


5

6


Views and opinions expressed during this SMPTE Webcast are those of the presenter(s) and do not necessarily reflect those of SMPTE or SMPTE Members.

This webcast is presented for informational purposes only. Any reference to specific companies, products or services does not represent promotion, recommendation, or endorsement by SMPTE


Today’s Speaker

Alex Grossman

Founder and CEO

Symply, Inc.


7

8



Presentation Outline

• Content Management Fundamentals

• Changes and Challenges

• Advantages and Considerations of Modernization

• Applications in a Decentralized And Demanding Environments

• Summary

9


Defining The Terms

• There are three commonly used terms associated with the management of content - and while these terms are often interchanged, they are not identical

• MAM - Media Asset Management - essentially any video format and any audio format

• PAM - The production side of MAM

• ECM - Enterprise Content Management - The kitchen sink of content management, essentially anything in digital format

• DAM - Digital Asset Management - essentially digital video and images in any format

10

9

10



Defining The Terms

• If you come from an AVID environment your definition of MAM and PAM may be a bit different…

• Non AVID PAMs generally deal with All the aspects of production including automation categorizing and asset tracking, where MAMs are used by editors for asset searching, acquisition and other aspects of content creation, in the AVID world that is reversed

• But no matter how you slice pieces - DAM, MAM, and PAM are invaluable to today’s Content lifecycle

11


A Brief History - from my perspective

• Born out of publishing in the late 1980’s

• Had to keep track of printed materials

• I keynoted the first DAM Expo in 1998

• DAM’s were managed by Librarians almost exclusively

• DV 61834 was the standard…

• DAM is ever evolving (in a good way)

• From CD catalogs to Web Content Management

• MAM - Became a “thing”

• Management moved beyond maintaining a catalog

12

11

12



MAM and DAM

• DAM was first and DAM is likely to be last

• If MAM’s are the Archive, and PAM’s are the workflow trackers, then DAM’s represent the Assets Lifecycle and family relationships

• Think of DAM as the master content manager

13


The Role Of Content Management

• Technically minded people tend to think of the role of content management as categorizing assets to improve efficiency throughout the content lifecycle

• While this is true, the real role is monetization expansion and efficiency

• Content value and ownership management are key today and moving forward

• From acquisition to delivery, re-delivery and archive

• It is not just where it is - but what it is worth…

14

13

14



Generalized Content Management

• Simply think of it as a federated content repository

• Categorize and track media asset acquisition, movement and disposition (lifecycle management)

• Provide search, browse, view, and collect (job/client management)

• Re-order, re-categorize, and replace (library clean up)

• Transform, QA, Annotate, Deliver (WIP operations)

• Archive, restore, review

15


Components of a Modern DAM

16

Creators Producers Administrators

Acquistition sources

Quality Assurance

Automated categorization/ Schema completion

NLE Integration

Delivery Automation

Archive Automation

15

16




17

Ingest

QC

Edit

Deliver

Archive

Producers



18

WORKFLOW vs

LIFECYCLE

17

18



Back to the Usage Model

• The Basic goal - making the creative process more efficient

• You need to match your workflow (tools) to the model that matches the product you choose

• You must also match the needs - mostly what can be automated

• This is how we have always picked a tool and this is why evolving usage models may be a difficult transition

19


The Basic Hardware “today”

• Protected Repository

• RAID protected

• Archived on and offsite (cloud… maybe)

• Completely Scalable

• Capacity - Storage

• Performance - Cluster

• Codec Agnostic

• Transcode - thumbnail/mezzanie

• Multiplatform

• Mac/Windows/Linux

20

The hardware is commodity and replaced frequently. The most difficult aspects

are managing it and securing it

19

20



The Basic Software “today”

• Common Interface

• All OS types

• Remote Users (web)

• All levels of Users

• Industry Standard Metadata

• Common database format ***

• NLE Compatibility

• Plug ins

• Integrated with Archive packages

21

The basic rule is look for anything that can be

automated to take the repeatable tasks away from

your creative team


Metadata and Schema

• This has long been the elusive key element

• Getting the schema right - Garbage in/ Garbage searches

• Metadata portability

• Multi-level user types

• Flexible licensing

• Workflow optimization

• Simple navigation

• automated .. well everything***

22

If you can’t find it, you can’t use it.. or more importantly

monetize it

21

22



How We “Look” at Content Management

• We take an IT approach, and this no longer works…

• Roles and Permissions

• Auditing

• Analysis

• Reporting

• Schema Customization

• On-Premise Hardware

• Purchased Software

• LTO backup/archive

23

This thinking imposes severe limitations on how to do the

most with content management


Content Management Goes Macro

• Our Content Value Needs to Be Maximized

• We Need to Share It More Readily Across an Organization

• We Need Access to All of It Faster

• We Must to Streamline The Movement And Availability

24

We Need Simultaneous Operations

23

24



Two Reasons That Should Matter

• #1 Everything is going remote

• Locations

• Workers

• Archive

• Compute

• Storage

• Ingest

• Delivery

• QA

• Rights Management

25


Locations – ONSET

26

25

26



What’s Missing?

27

• Where is Content Management?

Pre-Production On Location

28

PRE

PRODUCTION

• Content management before ingest breaks the system

• Bringing new content in and finding It is difficult and time consuming

• You cannot wait until it is physically on-site

• Thousands of hours of content parked on the SAN

• Complex directory structure

• Primary metadata = file and folder names


27

28



Breaking Up Is Hard To Do

29

• It’s not your First Rodeo

• Industry standard’s do not often apply

• The majority of your MAM is likely custom

• The company that designed the custom features may be gone

• Transitions take time


Traditional Architecture

30

Remote Users

Remote Users

Local Users

RemoteReviewers

• Pick One - We See the All

• Mac Finder

• Camera embedded metadata

• Basic OTS MAM

• MAM with custom metadata

• MAM/DAM with custom automations

• All require content to be present

29

30


Future-facing Architecture

31© 2019 • SMPTE® | Enabling Global Education • www.smpte.org

Public Cloud

Remote Users

Remote Users

RemoteReviewers

Local Users

• Move the content management closer to the edge

• where the content is being created

• Build on open API’s

• Leverage multiple architectures and applications

The Path Forward

32© 2019 • SMPTE® | Enabling Global Education • www.smpte.org

Public Cloud

Remote Users

Remote Users

RemoteReviewers

Local Users

Remote Users

Remote Users

Local Users

RemoteReviewers

Difficult Path, but Additional Capabilities

31

32


Limitations of Traditional Repository

33

• Bandwidth (from all directions)

• Performance (hardware)

• Flexibility (growth and contraction)

• COST (hardware and IT)

• Closed architecture

• Required refresh cycles

• Slow to add new features

• Limited eco-system

Remote Users

Remote Users

Local Users

RemoteReviewers


Advantages of Public Cloud

34

Public Cloud

Remote Users

Remote Users

Remote Users

Local Users

• Someone else’s bandwidth

• Massive scalability

• Unlimited performance

• Outsourced management

• Access to huge eco-system

• No refresh cycles

• Ability to change quickly to meet evolving needs

33

34



On-Premise vs Cloud Content Management

35

• It does not matter where the content lives - it matters where the compute is

AcquisitionCloud Based Processing

Cloud Based Archiving

Cloud Based Delivery

Cloud Based Relay

Remote Users

Local Users Local Repository

SMPTE Technology Webcast SeriesSMPTE – Enabling Global Education

Moving the repository and management to the cloud provides greater capabilities for remote workers and locations - but there may be an even more compelling reason to move the repository to the cloud

36

35

36



Huge Changes in Workflow

• #2 Getting the Best Metadata Faster, Easier, More Accurate

• Eliminate human error

• Eliminate lazy humans

• Take advantage of automation

• Faster

• Better

• More accurate

• Less management

• Lower cost*** (maybe)

• Removes the guess work

37


Getting the Metadata Right

• Automation

• AI and Machine Learning

• HPC meets M&E

• Two Types of Usage

• Initial Ingest

• Categorizing the Archive

• Rights liability

• AI= Automation Supercharged

• Not East to Do Without moving to the Cloud

38

Ai

37

38



“Canned” Advantages of AI

• These are advances features provided by the cloud that many Content managers and MAMs are rushing to integrate

• Requires an Open Architecture

• Automated metadata tagging based on:

• Scenes

• Locations

• Events

• Automated Facial Recognition

• Transcript Search

39

Ai


Open Architecture “Canned”

40

• Ability to tap into cloud Microservices

• Can hook in web based API sets (usually JSON)

• It helps if the App is web basedMICROSERVICES

EXAMPLE

39

40



Serverless Microservices Function

41

Trigger EventServerless

Functions

Access a

Cloud Service


Serverless Microservices Function

42

Trigger EventServerless

Functions

Access a

Cloud Service

Captured

Video Clip

Cloud

Storage Bucket

Serverless

Function

Serverless

Function

Serverless

Function

Proxy Built

Facial Rec

Location tag

41

42



API driven Integration

43


You Can Do this Without Being A Data Scientist

• You don’t have to be a data scientist - but it sure helps

• Everyone is talking about it

• There is no generic solution

• Machine learning and deep learning can be tailored to the specific usage model, but…

• The cloud providers give you the pieces, you need to put them together

• Fear and respect the “cost”

• Its not something you can learn online

44

Puzzle courtesy of clipartmag.com

43

44

http://clipartmag.com



Advanced Functionality Available

45

• Audio Fingerprinting

• Geolocation

• Object Recognition

• OCR

• Voice Recognition

• Text Analytics

• Metadata Extraction

• Text Translation

• Keyword Spotting

• Text Analysis

• Phonetic Searches

• Transcription

• Version Compares

• QA Services

• Transcoding

• Automated Archive

• High Speed Replication

• Scene Extrapolation

• Key Phrase Spotting


Basic Example

46Facility

High-speedLink

Cloud Interface API

Web App

Storage Gateway

Data Sync

Compute Scheduler

Transfer Accelerator

Serverless Ingestengine

IngestBucket

Proxy Generation

ArchiveBucket

AIBucket

ML/AIToolset

QAToolset

ResultsBucket

45

46



Summarizing…

• Managing content with remote users, reviewers, and locations is difficult with existing traditional architectures

• The best solution may be to break with tradition and move the repository to the cloud - but what cloud? how?

• Leverage the advantages of Machine Learning and AI to take automation to the next level, and improve monetization capabilities, eliminate human errors, and limit digital rights violations (or enforce them)

• The cloud becomes the answer to managing difficult and decentralized workflow

• Adding modern pieces to an existing DAM/MAM/PAM is usually more work (cost) than moving, or is it?

48

SMPTE Technology Series Webcast


Thank YouAlex Grossman

[email protected]

SMPTE Technology Webcast Series Sponsored by:

48

49

mailto:[email protected]


SMPTE - Enabling Global Education

Questions?

Alex Grossman

Founder and CEO

Symply, Inc.


SMPTE Technology Webcast Sponsors

• Thank you to our sponsor for their generous support:


50

51

Documents

Advanced Content Management In Demanding and Decentralized ...€¦ · Advanced Content Management In Demanding and Decentralized Environments Alex Grossman ... •Basic OTS MAM •MAM