Metadata Plug-in API for Time-Based Media Editing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current video and audio editing systems lack a flexible and interoperable method to associate, share, and manipulate metadata across various computational components and stages of the media production workflow, often leading to loss of original data during manipulation.

Innovation Solution

A metadata plug-in architecture that allows for flexible association and sharing of metadata with time-based media, enabling interaction with computational components and systems, and facilitating metadata processing, generation, and representation through a shared convention, allowing metadata to be imported, exported, and manipulated across different stages of the workflow.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If metadata is imported and attached to time-based media in current editing systems, then metadata can be retained with the media through the workflow, but the metadata processing is limited to predetermined purposes and lacks flexibility

Engineering Contradiction:
Improvemetadata processing flexibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal metadata processing architecture where a single metadata processing component can handle multiple types of metadata through a standardized interface. The system defines a convention that allows different software components to process various metadata types (synchronization data, descriptive information, production metadata) through a unified mechanism, enabling one component to serve multiple functions rather than requiring separate dedicated components for each metadata type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent segments the metadata processing functionality into independent software components that can be selectively executed. The metadata processing component is divided into modular units that can be independently developed, maintained, and deployed. This segmentation allows the system to handle complex metadata processing tasks by breaking them down into manageable, reusable components that can be composed to handle specific metadata types as needed.

Inventive Principle:
Principle #1Segmentation

2Productivity

If imported data directly manipulates source audio and video, then editing operations can be performed, but the original imported data is lost and changes are irreversible

Engineering Contradiction:
Improveediting operation efficiencyVSAvoidoriginal metadata preservation
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements a copying mechanism where metadata is attached to time-based media as a separate, persistent data structure rather than directly manipulating the original media or importing data that gets overwritten. The system creates and maintains copies of metadata through the workflow, allowing editing operations to reference and modify metadata copies while preserving the ability to recover original metadata. This approach enables efficient editing operations on metadata copies while maintaining the integrity of the original imported data through the production workflow.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If a large assortment of metadata is used to define new data for complex media production, then metadata can describe nontraditional functions throughout the editing workflow, but current systems lack the capability to flexibly associate and share metadata across computational components

Engineering Contradiction:
Improvemetadata type varietyVSAvoidmetadata sharing and association
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent establishes a universal convention for metadata representation and processing that enables diverse metadata types to be handled through a common interface. The system defines standardized data structures and processing rules that allow different software components to share and associate various metadata types (synchronization metadata, descriptive metadata, production metadata) without requiring component-specific implementations. This universal approach simplifies metadata sharing across computational components while supporting a large assortment of metadata types needed for complex media production.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If metadata is associated with time-based media for synchronization and production purposes, then metadata functionality can be extended, but interoperability between different systems and devices at various workflow stages is limited

Engineering Contradiction:
Improvemetadata functionalityVSAvoidsystem interoperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a standardized convention that defines how metadata parameters are represented, structured, and processed across different systems. The system establishes consistent data formats, naming conventions, and processing rules that enable metadata to maintain its functionality as it moves through different computational components and workflow stages. This standardization of parameters ensures that metadata associated with time-based media can be reliably exchanged between different systems and devices, maintaining interoperability while extending metadata functionality throughout the production workflow.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8589871B2Metadata plug-in application programming interface
Publication Date: 2013.11.19 AVID TECHNOLOGY INC
  • US8589871B2 patent drawing
  • US8589871B2 patent drawing
  • US8589871B2 patent drawing

AI summary

Computer-based methods and systems for editing a time-based media program involve receiving an instruction to associate metadata with a selected portion of the program, determining a type of the metadata, wherein the type of the metadata is one of a predetermined set of metadata types, identifying a software component available to the editing system that is configured to process metadata of the determined type, and associating the metadata with the selected portion of the program by executing the identified software component to process the metadata. Metadata is represented using a scheme that is shared among the various computational components that manipulate the metadata; the scheme may also be shared with a host media processing system, as well as with other systems that are used in a time-based media editing and production workflow.