What Are the User Roles?
1.4.3Engine Integrator
The Engine Integrator defines various Engine configurations. This can include the names of the Engines, as well as the codecs and their names within each Engine, whether each codec is local or remote relative to the application, which groups each codec should be integrated into (for environments which support resource sharing), the name of the Codec Server image if a particular Engine contains remote codecs, etc. This is done via an XDC configuration script (*.cfg).
This script, when run, generates code and build instructions appropriate for the configuration.
The Engine Integrator receives the name of a Codec Server and a list of the codecs it contains from the Server Integrator. Using these, this person creates an Engine configuration file (.cfg) that may reference a Codec Server. (On
The Engine Integrator hands the Engine configuration file to the
Application Author.
The Engine Integrator uses the following resources:
❏Chapter 5 of Codec Engine Application Developer’s Guide (SPRUE67)
❏Configuration Reference.
CE_INSTALL_DIR/packages/xdoc/index.html
❏Example Build and Run Instructions.
CE_INSTALL_DIR/examples/build_instructions.html
❏Example configuration scripts (*.cfg)
1.4.4Application Author
The application uses the Codec Engine APIs (Engine_, VISA, and other utility APIs) to create/delete preconfigured Engine instances, create/delete and interact with codecs, acquire buffers appropriate for the codecs, etc.
Since Codec Engine doesn't perform any I/O, the application is responsible for handling I/O. This includes such task as file access (for example, open/read/write/seek/close) and driver interaction (for example, open/close/ioctl and buffer management).
The Application Author is responsible for building the application code, and for linking "the appropriate content" into the executable image.
The Application Author receives the following:
