Codec Engine API Reference

ce-r11

Modules

The Codec Engine is partitioned into several components:

• The Codec Engine Runtime (CERuntime_* and Engine_*) - Provides codec-independent services.
• VISA (VISA_*) - A set of services that can be used on algorithms of any class.
• Codec Engine Server Interface (Server_*) - Provides an interface to Servers containing remote algorithms.

• The latest VISA APIs - Providing codec-specific interfaces, reflecting the XDM interfaces for the following classes:
  • Video
    • VIDENC1 - Video encoder codec interface
    • VIDDEC2 - Video decoder codec interface
  • Imaging
    • IMGDEC1 - Image decoder codec interface
    • IMGENC1 - Image encoder codec interface
  • Speech
    • SPHDEC1 - Speech decoder codec interface
    • SPHENC1 - Speech 1.0 Encoder Codec Interface
  • Audio
    • AUDDEC1 - AUDDEC1 Audio Decoder Interface
    • AUDENC1 - AUDENC1 Audio Encoder Interface
  • Video Trancoding
    • VIDTRANSCODE - Video Transcode Interface
  • General Purpose Algorithms
    • UNIVERSAL - Universal Algorithm Interface

• Older VISA APIs continue to be supported, but to align with the XDM roadmap, they are deprecated in this release. These interfaces are comprised of the following:
  • Video
    • VIDDEC1 - Video 1.0 decoder codec interface
    • VIDDEC - VIDDEC Video Decoder Interface
    • VIDENC - VIDENC Video Encoder Interface
  • Imaging
    • IMGDEC - IMGDEC Image Decoder Interface
    • IMGENC - IMGENC Image Encoder Interface
  • Speech
    • SPHDEC - SPHDEC Speech Decoder Interface
    • SPHENC - SPHENC Speech Encoder Interface
  • Audio
    • AUDDEC - AUDDEC Audio Decoder Interface
    • AUDENC - AUDENC Audio Encoder Interface

• Also, this release includes Beta support for the following XDM interfaces:
  • VIDANALYTICS - Video Analytics Algorithm Interface

Additionally, there are several utility modules provided:

• Memory - provides services to manage memory is OS independent environments. Also provides the ability to manage contiguous buffers meeting various alignment constraints.
• TraceUtil - provides utility services to easily manage tracing support.
• ladclient - provides wrappers to allow communication with the Link Arbiter Daemon (LAD).

Note that the previously available ti.sdo.ce.trace GT module has been moved into ti.sdo.utils.trace, and is now distributed as a part of Framework Components. (The package still exists and redirects users to the new location) You will now find GT documentation in that product.