![]() |
![]() |
![]() |
![]() |
The MME API Library Reference accompanies the QNX Aviage multimedia suite, release 1.2.0. It is intended for application developers who use the suite's MultiMedia Engine (MME) to develop multimedia applications.
This table may help you find what you need in the MME API Library Reference:
When you want to: | Go to: |
---|---|
Learn about MME API functions, data structures, enumerated types and constants. | MME API |
Learn about MME events and the data structures they use. | MME Events |
Learn about MME synchronization events, and synchronization error events. | MME Synchronization Events |
Learn about MME playback events, and playback error events. | MME Playback Events |
Learn about MME media copy and ripping events, and copy and ripping error events. | MME Media Copy and Ripping Events |
Learn about MME metadata events. | MME Metadata Events |
Learn about the MME database schema. | MME Database Schema Reference |
Other MME documentation available to application developers includes:
Book | Description |
---|---|
Introduction to the MME | MME Architecture, Quickstart Guide, and FAQs. |
MME Developer's Guide | How to use the MME to program client applications. |
MME Utilities | Utilities used by the MME. |
MME Configuration Guide | How to configure the MME. |
MME Technotes | MME technical notes. |
MediaFS Developer's Guide | Developer's guide for implementing MediaFS. |
QDB Developer's Guide | QDB database engine programming guide and API library reference. |
Note that the MME is a component of the QNX Aviage multimedia core package, which is available in the QNX Aviage multimedia suite of products. The MME is the main component of this core package. It is used for configuration and control of your multimedia applications.
Throughout this manual, we use certain typographical conventions to distinguish technical terms. In general, the conventions we use conform to those found in IEEE POSIX publications. The following table summarizes our conventions:
Reference | Example |
---|---|
Code examples | if( stream == NULL ) |
Command options | -lR |
Commands | make |
Environment variables | PATH |
File and pathnames | /dev/null |
Function names | exit() |
Keyboard chords | Ctrl-Alt-Delete |
Keyboard input | something you type |
Keyboard keys | Enter |
Program output | login: |
Programming constants | NULL |
Programming data types | unsigned short |
Programming literals | 0xFF, "message string" |
Variable names | stdin |
User-interface components | Cancel |
We use an arrow (→) in directions for accessing menu items, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight important messages:
![]() |
Notes point out something important or useful. |
![]() |
Cautions tell you about commands or procedures that may have unwanted or undesirable side effects. |
![]() |
Warnings tell you about commands or procedures that could be dangerous to your files, your hardware, or even yourself. |
In our documentation, we use a forward slash (/) as a delimiter in all pathnames, including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
At the top and bottom of our HTML docs, you'll see some or all of these buttons:
Use this button: | To move: |
---|---|
![]() |
To the previous part of the document. |
![]() |
“Up” in the document:
|
![]() |
To the keyword index. |
![]() |
To the next part of the document. |
To obtain technical support for any QNX product, visit the Support + Services area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
Copyright © 2007–2009, QNX Software Systems GmbH & Co. KG. All rights reserved.
![]() |
![]() |
![]() |
![]() |