Why does the ARM application require “DSP” codec packages?
In addition to a library, codec packages contain meta-data which the Codec Engine uses during the application’s configuration. Among other details, this meta-data includes things like: • The codec’s type (needed so you get an error rather than a crash if the app tries to VIDDEC_create() an audio decoder!) • The codec’s location (i.e. local or remote). If local, the codec’s library will be linked into the app. If remote, only a reference to the codec will be linked into the app – this reference is composed from the packages meta-data). • A unique codec-specific ID (generated from it’s globally unique package name). This ID is built into both the Application and Server codec tables, and sent from the ARM-side app to the remote Server to identify which codec to create. Additionally, often the codec package will contain codec-specific extensions (e.g. data types, commands, etc.). The ARM-side application will require these interfaces files, provided in the codec package, during its compila
