Where Does the Codec Engine Fit into My Architecture?
1.3Where Does the Codec Engine Fit into My Architecture?
The application code (or the middleware it uses) calls the Codec Engine APIs. Within the Codec Engine, the VISA APIs use stubs and skeletons to access the core engine and the actual codecs, which may be local or remote.
The following figure shows the general architecture of an application that uses the Codec Engine. It also shows the user roles involved in creating various portions of the application. See Section 1.4, What Are the User Roles? for more on user roles.
Role 4:
Application
Author
Application
media middleware
Codec Engine Runtime
Role 3: Core Engine APIs
Engine
Integrator
Core Engine
Runtime
Role 2:
Server
Integrator
Core Engine SPIs
VISA APIs
Video Encode
stubs
Video Encode
skeleton
VISA SPIs
Role 1:
Algorithm
Creator
MP4 Encode VC1 Encode
The application (or middleware it uses) calls the core Engine APIs and the VISA APIs. The VISA APIs use stubs to access the core engine SPIs (System Programming Interfaces) and the skeletons. The skeletons access the core engine SPIs and the VISA SPIs. The VISA SPIs access the underlying algorithms.
