What Are the User Roles?
1.4.2Server Integrator
|
|
|
|
| ly |
|
|
|
| n | |
|
|
| o |
| |
|
| l |
|
| |
| a |
|
|
| |
c |
|
|
|
| |
lo |
|
|
|
|
|
To support Engines with remote codecs, a Codec Server must be created. The Codec Server integrates the various components necessary to house the codecs (e.g. DSP/BIOS, Framework Components, link drivers, codecs, Codec Engine, etc.) and generates an executable.
There are two configuration steps that the Codec Server Integrator must perform, one to configure DSP/BIOS (through a Tconf script) and one to configure "the rest" of the components (through XDC configuration of Framework Components, Link, Codec Engine, etc).
The Server Integrator receives the various Codec packages from Algorithm Creators. This person uses Codec Engine and its dependent packages (DSP/BIOS, DSKT2, etc) along with the XDC Tools to create the following:
❏A server configuration file (.cfg)
❏A server DSP/BIOS configuration file (.tcf)
❏A simple main() routine to do minimal initialization
❏A DSP executable created by executing the configuration scripts, and compiling the output. This executable is a Codec Server.
The Server Integrator hands the DSP executable to the Engine Integrator (preferably as a Codec Server package. The Server Integrator should also provide a list of the codecs in the Codec Server.
The Server Integrator uses the following resources:
❏This manual
❏Configuration Reference.
CE_INSTALL_DIR/packages/xdoc/index.html
❏Example Codec Servers
For applications that use only local algorithms, the Codec Server is not used, so this role is not required.
Codec Engine Overview |
