Run-time Player Component for Accurate Stage Preview

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software authoring tools face inefficiencies in rendering a preview of multimedia applications, as they often require integrating run-time player code or maintaining mimic logic, which leads to large tool sizes, inaccuracies, and the need for frequent updates to match evolving run-time players.

Innovation Solution

Employing a run-time player component to render a stage in the authoring tool, utilizing a pre-defined communication interface to generate a live preview of the multimedia application's output, allowing for accurate representation without the need for internal mimic code updates and supporting various run-time players.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If run-time player code is integrated into the authoring tool, then rendering accuracy is improved, but tool size increases

Engineering Contradiction:
Improverendering accuracyVSAvoidtool size
Core Design Contradiction:
Measurement precisionVSWeight of stationary object

Solution Approach 1:

The patent extracts the run-time player rendering functionality from the authoring tool by using a standalone run-time player process. The authoring tool communicates with this external player through standardized protocols (XML, SOAP, REST), allowing rendering accuracy to be maintained while keeping the authoring tool size manageable.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary communication layer using standardized protocols (XML, SOAP, REST) between the authoring tool and the run-time player. This mediator enables accurate rendering communication without requiring direct integration of run-time player code into the authoring tool.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If mimic logic is maintained to match run-time player output, then rendering accuracy is improved, but device complexity increases

Engineering Contradiction:
Improverendering accuracyVSAvoidcode maintenance complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Instead of having the authoring tool mimic the run-time player's behavior, the patent inverts the approach by having the authoring tool communicate design parameters to the actual run-time player, which then generates the authoritative rendering. This eliminates the need for maintaining complex mimic logic.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The run-time player serves itself by directly generating the rendering output based on parameters received from the authoring tool. This self-service approach eliminates the need for the authoring tool to maintain separate mimic logic, as the actual run-time player handles its own rendering generation.

Inventive Principle:
Principle #25Self-service

3Speed

If run-time player code is integrated, then rendering speed is improved, but adaptability to multiple players decreases

Engineering Contradiction:
Improverendering speedVSAvoidmulti-player compatibility
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal communication interface using standardized protocols (XML, SOAP, REST) that enables the authoring tool to work with multiple different run-time players. This universal interface maintains adaptability while allowing each player to render at its own optimal speed.

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

Data Source

PatentUS8739120B2System and method for stage rendering in a software authoring tool
Publication Date: 2014.05.27 ADOBE INC
  • US8739120B2 patent drawing
  • US8739120B2 patent drawing
  • US8739120B2 patent drawing

AI summary

Systems and methods are provided for rendering a stage in a software authoring tool. A run-time player component is employed for rendering the stage for presenting a preview of output of a software application being authored in the software authoring tool. Thus, a software authoring tool outputs a stage which presents a preview of the output of an application being authored, such as a multimedia application. The output presentation of a multimedia application being authored in the authoring tool is rendered to the stage by a run-time player component. Thus, rather than employing code integrated within the authoring tool for mimicking a run-time player in order to generate a preview of output on the stage, embodiments of the present invention utilize a run-time player component to generate such a preview of output on the stage.