 |
You should have already installed QNX Neutrino and become familiar with its architecture. For a detailed overview, see the System Architecture guide. |
This chapter includes:
The Audio Developer's Guide is intended for developers who wish to write audio applications using the QNX Sound Architecture (QSA) drivers and library.
This table may help you find what you need in this guide:
| To find out about: | Go to: |
|---|---|
| The structure of an audio application | Audio Architecture |
| Playing and recording sound | Playing and Capturing Audio Data |
| The structure of a mixer | Mixer Architecture |
| Audio library functions | Audio Library |
| How to code a .wav player in C | wave.c example |
| How to code a .wav recorder in C | waverec.c example |
| How to code a mix_ctl in C | mix_ctl.c example |
| Why libasound.a isn't offered | LGPL License Agreement |
| Terms used in this guide | Glossary |
|
You should have already installed QNX Neutrino and become familiar with its architecture. For a detailed overview, see the System Architecture guide. |
The key components of the QNX Audio driver architecture include:
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.
To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
This section summarizes the changes in the following releases:
The QNX Sound Architecture has evolved away from ALSA. You should reread this entire guide.
Copyright © 2000–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.