Filter
Top Products
Where Does the Codec Engine Fit into My Architecture?
1-4
1.3 Where 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.
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.
Codec Engine Runtime
Video Encode
stubs
Video Encode
stubs
Core Engine SPIsCore Engine SPIs
Core Engine
Runtime
VISA SPIs
VISA SPIsVISA SPIs
VISA APIsCore Engine APIs
MP4 Encode
VC1 Encode
MP4 Encode
VC1 Encode
Video Encode
skeleton
Video Encode
skeleton
Application
media middleware
Application
media middleware
Role 4:
Application
Author
Role 3:
Engine
Integrator
Role 2:
Server
Integrator
Role 1:
Algorithm
Creator