falkTX
/
rtaudio
mirror of https://github.com/falkTX/rtaudio


			
							/*! \mainpage The RtAudio Tutorial

<BODY BGCOLOR="white">

<CENTER>
\ref intro &nbsp;&nbsp; \ref download &nbsp;&nbsp; \ref start &nbsp;&nbsp; \ref error &nbsp;&nbsp; \ref probing &nbsp;&nbsp; \ref settings &nbsp;&nbsp; \ref playbackb &nbsp;&nbsp; \ref playbackc &nbsp;&nbsp; \ref recording &nbsp;&nbsp; \ref duplex &nbsp;&nbsp; \ref methods &nbsp;&nbsp; \ref compiling &nbsp;&nbsp; \ref osnotes &nbsp;&nbsp; \ref acknowledge
</CENTER>

\section intro Introduction

RtAudio is a C++ class which provides a common API (Application Programming Interface) for realtime audio input/output across Linux (native ALSA and OSS), SGI, and Windows operating systems.  RtAudio significantly simplifies the process of interacting with computer audio hardware.  It was designed with the following goals:

<UL>
  <LI>object oriented C++ design</LI>
  <LI>simple, common API across all supported platforms</LI>
  <LI>single independent header and source file for easy inclusion in programming projects (no libraries!)</LI>
  <LI>blocking functionality</LI>
  <LI>callback functionality</LI>
  <LI>extensive audio device parameter control</LI>
  <LI>audio device capability probing</LI>
  <LI>automatic internal conversion for data format, channel number compensation, de-interleaving, and byte-swapping</LI>
  <LI>control over multiple audio streams and devices with a single instance</LI>
</UL>

RtAudio incorporates the concept of audio streams, which represent audio output (playback) and/or input (recording).  Available audio devices and their capabilities can be enumerated and then specified when opening a stream.  Multiple streams can run at the same time and, when allowed by the underlying audio API, a single device can serve multiple streams.

The RtAudio API provides both blocking (synchronous) and callback (asynchronous) functionality.  Callbacks are typically used in conjunction with graphical user interfaces (GUI).  Blocking functionality is often necessary for explicit control of multiple input/output stream synchronization or when audio must be synchronized with other system events.

\section download Download

Latest Release (22 January 2002): <A href="release/rtaudio-2.0.tgz">Version 2.0 (111 kB tar/gzipped)</A>

\section start Getting Started

The first thing that must be done when using RtAudio is to create an instance of the class.  The default constructor RtAudio::RtAudio() scans the underlying audio system to verify that at least one device is available.  RtAudio often uses C++ exceptions to report errors, necessitating try/catch blocks around most member functions.  The following code example demonstrates default object construction and destruction:

\code

#include "RtAudio.h"

int main()
{
  RtAudio *audio;

  // Default RtAudio constructor
  try {
    audio = new RtAudio();
  }
  catch (RtAudioError &error) {
    // Handle the exception here
  }

  // Clean up
  delete audio;
}
\endcode

Obviously, this example doesn't demonstrate any of the real functionality of RtAudio.  However, all uses of RtAudio must begin with a constructor (either default or overloaded varieties) and must end with class destruction.  Further, it is necessary that all class methods which can throw a C++ exception be called within a try/catch block.


\section error Error Handling

RtAudio uses a C++ exception handler called RtAudioError, which is declared and defined within the RtAudio class files.  The RtAudioError class is quite simple but it does allow errors to be "caught" by RtAudioError::TYPE.  Almost all RtAudio methods can "throw" an RtAudioError, most typically if an invalid stream identifier is supplied to a method or a driver error occurs.  There are a number of cases within RtAudio where warning messages may be displayed but an exception is not thrown.  There is a private RtAudio method, error(), which can be modified to globally control how these messages are handled and reported.


\section probing Probing Device Capabilities

A programmer may wish to query the available audio device capabilities before deciding which to use.  The following example outlines how this can be done.

\code

// probe.cpp

#include <iostream.h>
#include "RtAudio.h"

int main()
{
  RtAudio *audio;

  // Default RtAudio constructor
  try {
    audio = new RtAudio();
  }
  catch (RtAudioError &error) {
    error.printMessage();
    exit(EXIT_FAILURE);
  }

  // Determine the number of devices available
  int devices = audio->getDeviceCount();

  // Scan through devices for various capabilities
  RtAudio::RTAUDIO_DEVICE info;
  for (int i=0; i<devices; i++) {

    try {
      audio->getDeviceInfo(i, &info);
    }
    catch (RtAudioError &error) {
      error.printMessage();
      break;
    }

    // Print, for example, the maximum number of output channels for each device
    cout << "device = " << i;
    cout << ": maximum output channels = " << info.maxOutputChannels << endl;
  }

  // Clean up
  delete audio;

  return 0;
}
\endcode

The RTAUDIO_DEVICE structure is defined in RtAudio.h and provides a variety of information useful in assessing the capabilities of a device:

\code
  typedef struct {
    char name[128];
    DEVICE_ID id[2];                      // No value reported by getDeviceInfo().
    bool probed;                          // true if the device probe was successful.
    int maxOutputChannels;
    int maxInputChannels;
    int maxDuplexChannels;
    int minOutputChannels;
    int minInputChannels;
    int minDuplexChannels;
    bool hasDuplexSupport;                // true if duplex supported
    int nSampleRates;                     // Number of discrete rates, or -1 if range supported.
    double sampleRates[MAX_SAMPLE_RATES]; // Supported sample rates, or {min, max} if range.
    RTAUDIO_FORMAT nativeFormats;
  } RTAUDIO_DEVICE;
\endcode

The following data formats are defined and fully supported by RtAudio:

\code
  typedef unsigned long RTAUDIO_FORMAT;
  static const RTAUDIO_FORMAT  RTAUDIO_SINT8;   // Signed 8-bit integer
  static const RTAUDIO_FORMAT  RTAUDIO_SINT16;  // Signed 16-bit integer
  static const RTAUDIO_FORMAT  RTAUDIO_SINT24;  // Signed 24-bit integer
  static const RTAUDIO_FORMAT  RTAUDIO_SINT32;  // Signed 32-bit integer
  static const RTAUDIO_FORMAT  RTAUDIO_FLOAT32; // 32-bit float
  static const RTAUDIO_FORMAT  RTAUDIO_FLOAT64; // 64-bit double
\endcode

The <I>nativeFormats</I> member of the RtAudio::RTAUDIO_DEVICE structure is a bit mask of the above formats which are natively supported by the device.  However, RtAudio will automatically provide format conversion if a particular format is not natively supported.  When the <I>probed</I> member of the RTAUDIO_DEVICE structure is false, the remaining structure members are likely unknown and the device is probably unusable.

In general, the user need not be concerned with the minimum channel values reported in the RTAUDIO_DEVICE structure.  While some audio devices may require a minimum channel value > 1, RtAudio will provide automatic channel number compensation when the number of channels set by the user is less than that required by the device.  Channel compensation is <I>NOT</I> possible when the number of channels set by the user is greater than that supported by the device.

It should be noted that the capabilities reported by a device driver or underlying audio API are not always accurate and/or may be dependent on a combination of device settings.


\section settings Device Settings

The next step in using RtAudio is to open a stream with a particular set of device settings.

\code

#include "RtAudio.h"

int main()
{
  int channels = 2;
  int sample_rate = 44100;
  int buffer_size = 256;  // 256 sample frames
  int n_buffers = 4;      // number of internal buffers used by device
  int device = 0;         // 0 indicates the default or first available device
  int stream;             // our stream identifier
  RtAudio *audio;

  // Instantiate RtAudio and open a stream within a try/catch block
  try {
    audio = new RtAudio();
    stream = audio->openStream(device, channels, 0, 0, RtAudio::RTAUDIO_FLOAT32,
                               sample_rate, &buffer_size, n_buffers);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    exit(EXIT_FAILURE);
  }

  // Clean up
  delete audio;

  return 0;
}
\endcode

The RtAudio::openStream() method attempts to open a stream with a specified set of parameter values.  When successful, a stream identifier is returned.  In this case, we attempt to open a playback stream on device 0 with two channels, 32-bit floating point data, a sample rate of 44100 Hz, a frame rate of 256 sample frames per read/write, and 4 internal device buffers.  When device = 0, RtAudio first attempts to open the default audio device with the given parameters.  If that attempt fails, an attempt is made to find a device or set of devices which will meet the given parameters.  If all attempts are unsuccessful, an RtAudioError is thrown.  When a non-zero device value is specified, an attempt is made to open that device only.

RtAudio provides four signed integer and two floating point data formats which can be specified using the RtAudio::RTAUDIO_FORMAT parameter values mentioned earlier.  If the opened device does not natively support the given format, RtAudio will automatically perform the necessary data format conversion.

Buffer sizes in RtAudio are <I>ALWAYS</I> given in sample frame units.  For example, if you open an output stream with 4 channels and set <I>bufferSize</I> to 512, you will have to write 2048 samples of data to the output buffer within your callback or between calls to RtAudio::tickStream().  In this case, a single sample frame of data contains 4 samples of data. 

The <I>bufferSize</I> parameter specifies the desired number of sample frames which will be written to and/or read from a device per write/read operation.  The <I>nBuffers</I> parameter is used in setting the underlying device buffer parameters.  Both the <I>bufferSize</I> and <I>nBuffers</I> parameters can be used to control stream latency though there is no guarantee that the passed values will be those used by a device.  In general, lower values for both parameters will produce less latency but perhaps less robust performance.  Both parameters can be specified with values of zero, in which case the smallest allowable values will be used.  The <I>bufferSize</I> parameter is passed as a pointer and the actual value used by the stream is set during the device setup procedure.  <I>bufferSize</I> values should be a power of two.  Optimal and allowable buffer values tend to vary between systems and devices.  Check the \ref osnotes section for general guidelines.

As noted earlier, the device capabilities reported by a driver or underlying audio API are not always accurate and/or may be dependent on a combination of device settings.  Because of this, RtAudio does not attempt to query a device's capabilities or use previously reported values when opening a device.  Instead, RtAudio simply attempts to set the given parameters on a specified device and then checks whether the setup is successful or not.


\section playbackb Playback (blocking functionality)

Once the device is open for playback, there are only a few final steps necessary for realtime audio output.  We'll first provide an example (blocking functionality) and then discuss the details.

\code
// playback.cpp

#include "RtAudio.h"

int main()
{
  int count;
  int channels = 2;
  int sample_rate = 44100;
  int buffer_size = 256;  // 256 sample frames
  int n_buffers = 4;      // number of internal buffers used by device
  float *buffer;
  int device = 0;         // 0 indicates the default or first available device
  int stream;             // our stream identifier
  RtAudio *audio;

  // Open a stream during RtAudio instantiation
  try {
    audio = new RtAudio(&stream, device, channels, 0, 0, RtAudio::RTAUDIO_FLOAT32,
                        sample_rate, &buffer_size, n_buffers);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    exit(EXIT_FAILURE);
  }

  try {
    // Get a pointer to the stream buffer
    buffer = (float *) audio->getStreamBuffer(stream);

    // Start the stream
    audio->startStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    goto cleanup;
  }

  // An example loop which runs for about 40000 sample frames
  count = 0;
  while (count < 40000) {
    // Generate your samples and fill the buffer with buffer_size sample frames of data
    ...

    // Trigger the output of the data buffer
    try {
      audio->tickStream(stream);
    }
    catch (RtAudioError &error) {
      error.printMessage();
      goto cleanup;
    }

    count += buffer_size;
  }

  try {
    // Stop and close the stream
    audio->stopStream(stream);
    audio->closeStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
  }

 cleanup:
  delete audio;

  return 0;
}
\endcode

The first thing to notice in this example is that we attempt to open a stream during class instantiation with an overloaded constructor.  This constructor simply combines the functionality of the default constructor, used earlier, and the RtAudio::openStream() method.  Again, we have specified a device value of 0, indicating that the default or first available device meeting the given parameters should be used.  The integer identifier of the opened stream is returned via the <I>stream</I> pointer value.  An attempt is made to open the stream with the specified <I>bufferSize</I> value.  However, it is possible that the device will not accept this value, in which case the closest allowable size is used and returned via the pointer value.   The constructor can fail if no available devices are found, or a memory allocation or device driver error occurs.  Note that you should not call the RtAudio destructor if an exception is thrown during instantiation.

Because RtAudio can be used to simultaneously control more than a single stream, it is necessary that the stream identifier be provided to nearly all public methods.  Assuming the constructor is successful, it is necessary to get a pointer to the buffer, provided by RtAudio, for use in feeding data to/from the opened stream.  Note that the user should <I>NOT</I> attempt to deallocate the stream buffer memory ... memory management for the stream buffer will be automatically controlled by RtAudio.  After starting the stream with RtAudio::startStream(), one simply fills that buffer, which is of length equal to the returned <I>bufferSize</I> value, with interleaved audio data (in the specified format) for playback.  Finally, a call to the RtAudio::tickStream() routine triggers a blocking write call for the stream.

In general, one should call the RtAudio::stopStream() and RtAudio::closeStream() methods after finishing with a stream.  However, both methods will implicitly be called during object destruction if necessary.


\section playbackc Playback (callback functionality)

The primary difference in using RtAudio with callback functionality involves the creation of a user-defined callback function.  Here is an example which produces a sawtooth waveform for playback.

\code

#include <iostream.h>
#include "RtAudio.h"

// Two-channel sawtooth wave generator.
int sawtooth(char *buffer, int buffer_size, void *data)
{
  int i, j;
  double *my_buffer = (double *) buffer;
  double *my_data = (double *) data;

  // Write interleaved audio data.
  for (i=0; i<buffer_size; i++) {
    for (j=0; j<2; j++) {
      *my_buffer++ = my_data[j];

      my_data[j] += 0.005 * (j+1+(j*0.1));
      if (my_data[j] >= 1.0) my_data[j] -= 2.0;
    }
  }

  return 0;
}

int main()
{
  int channels = 2;
  int sample_rate = 44100;
  int buffer_size = 256;  // 256 sample frames
  int n_buffers = 4;      // number of internal buffers used by device
  int device = 0;         // 0 indicates the default or first available device
  int stream;             // our stream identifier
  double data[2];
  char input;
  RtAudio *audio;

  // Open a stream during RtAudio instantiation
  try {
    audio = new RtAudio(&stream, device, channels, 0, 0, RtAudio::RTAUDIO_FLOAT64,
                        sample_rate, &buffer_size, n_buffers);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    exit(EXIT_FAILURE);
  }

  try {
    // Set the stream callback function
    audio->setStreamCallback(stream, &sawtooth, (void *)data);

    // Start the stream
    audio->startStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    goto cleanup;
  }

  cout << "\nPlaying ... press <enter> to quit.\n";
  cin.get(input);

  try {
    // Stop and close the stream
    audio->stopStream(stream);
    audio->closeStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
  }

 cleanup:
  delete audio;

  return 0;
}
\endcode

After opening the device in exactly the same way as the previous example (except with a data format change), we must set our callback function for the stream using RtAudio::setStreamCallback().  This method will spawn a new process (or thread) which automatically calls the callback function when more data is needed.  Note that the callback function is called only when the stream is "running" (between calls to the RtAudio::startStream() and RtAudio::stopStream() methods).  The last argument to RtAudio::setStreamCallback() is a pointer to arbitrary data that you wish to access from within your callback function.

In this example, we stop the stream with an explicit call to RtAudio::stopStream().  When using callback functionality, it is also possible to stop a stream by returning a non-zero value from the callback function.

Once set with RtAudio::setStreamCallback, the callback process will continue to run for the life of the stream (until the stream is closed with RtAudio::closeStream() or the RtAudio instance is deleted).  It is possible to disassociate a callback function and cancel its process for an open stream using the RtAudio::cancelStreamCallback() method.  The stream can then be used with blocking functionality or a new callback can be associated with it.


\section recording Recording

Using RtAudio for audio input is almost identical to the way it is used for playback.  Here's the blocking playback example rewritten for recording:

\code
// record.cpp

#include "RtAudio.h"

int main()
{
  int count;
  int channels = 2;
  int sample_rate = 44100;
  int buffer_size = 256;  // 256 sample frames
  int n_buffers = 4;      // number of internal buffers used by device
  float *buffer;
  int device = 0;         // 0 indicates the default or first available device
  int stream;             // our stream identifier
  RtAudio *audio;

  // Instantiate RtAudio and open a stream.
  try {
    audio = new RtAudio(&stream, 0, 0, device, channels,
                        RtAudio::RTAUDIO_FLOAT32, sample_rate, &buffer_size, n_buffers);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    exit(EXIT_FAILURE);
  }

  try {
    // Get a pointer to the stream buffer
    buffer = (float *) audio->getStreamBuffer(stream);

    // Start the stream
    audio->startStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    goto cleanup;
  }

  // An example loop which runs for about 40000 sample frames
  count = 0;
  while (count < 40000) {

    // Read a buffer of data
    try {
      audio->tickStream(stream);
    }
    catch (RtAudioError &error) {
      error.printMessage();
      goto cleanup;
    }

    // Process the input samples (buffer_size sample frames) that were read
    ...

    count += buffer_size;
  }

  try {
    // Stop the stream
    audio->stopStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
  }

 cleanup:
  delete audio;

  return 0;
}
\endcode

In this example, the stream was opened for recording with a non-zero <I>inputChannels</I> value.  The only other difference between this example and that for playback involves the order of data processing in the loop, where it is necessary to first read a buffer of input data before manipulating it.


\section duplex Duplex Mode

Finally, it is easy to use RtAudio for simultaneous audio input/output, or duplex operation.  In this example, we use a callback function and pass our recorded data directly through for playback.

\code
// duplex.cpp

#include <iostream.h>
#include "RtAudio.h"

// Pass-through function.
int pass(char *buffer, int buffer_size, void *)
{
  // Surprise!!  We do nothing to pass the data through.
  return 0;
}

int main()
{
  int channels = 2;
  int sample_rate = 44100;
  int buffer_size = 256;  // 256 sample frames
  int n_buffers = 4;      // number of internal buffers used by device
  int device = 0;         // 0 indicates the default or first available device
  int stream;             // our stream identifier
  double data[2];
  char input;
  RtAudio *audio;

  // Open a stream during RtAudio instantiation
  try {
    audio = new RtAudio(&stream, device, channels, device, channels, RtAudio::RTAUDIO_FLOAT64,
                        sample_rate, &buffer_size, n_buffers);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    exit(EXIT_FAILURE);
  }

  try {
    // Set the stream callback function
    audio->setStreamCallback(stream, &pass, NULL);

    // Start the stream
    audio->startStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
    goto cleanup;
  }

  cout << "\nRunning duplex ... press <enter> to quit.\n";
  cin.get(input);

  try {
    // Stop and close the stream
    audio->stopStream(stream);
    audio->closeStream(stream);
  }
  catch (RtAudioError &error) {
    error.printMessage();
  }

 cleanup:
  delete audio;

  return 0;
}
\endcode

When an RtAudio stream is running in duplex mode (nonzero input <I>AND</I> output channels), the audio write (playback) operation always occurs before the audio read (record) operation.  This sequence allows the use of a single buffer to store both output and input data.

As we see with this example, the write-read sequence of operations does not preclude the use of RtAudio in situations where input data is first processed and then output through a duplex stream.  When the stream buffer is first allocated, it is initialized with zeros, which produces no audible result when output to the device.  In this example, anything recorded by the audio stream input will be played out during the next round of audio processing.

Note that duplex operation can also be achieved by opening one output stream and one input stream using the same or different devices.  However, there may be timing problems when attempting to use two different devices, due to possible device clock variations.  This becomes even more difficult to achieve using two separate callback streams because it is not possible to explicitly control the calling order of the callback functions.


\section methods Summary of Methods

The following is short summary of public methods (not including constructors and the destructor) provided by RtAudio:

<UL>
<LI>RtAudio::openStream(): opens a stream with the specified parameters.</LI>
<LI>RtAudio::setStreamCallback(): sets a user-defined callback function for a given stream.</LI>
<LI>RtAudio::cancelStreamCallback(): cancels a callback process and function for a given stream.</LI>
<LI>RtAudio::getDeviceCount(): returns the number of audio devices available.</LI>
<LI>RtAudio::getDeviceInfo(): fills a user-supplied RTAUDIO_DEVICE structure for a specified device.</LI>
<LI>RtAudio::getStreamBuffer(): returns a pointer to the stream buffer.</LI>
<LI>RtAudio::tickStream(): triggers processing of input/output data for a stream (blocking).</LI>
<LI>RtAudio::closeStream(): closes the specified stream (implicitly called during object destruction).  Once a stream is closed, the stream identifier is invalid and should not be used in calling any other RtAudio methods.</LI>
<LI>RtAudio::startStream(): (re)starts the specified stream, typically after it has been stopped with either stopStream() or abortStream() or after first opening the stream.</LI>
<LI>RtAudio::stopStream(): stops the specified stream, allowing any remaining samples in the queue to be played out and/or read in.  This does not implicitly call RtAudio::closeStream().</LI>
<LI>RtAudio::abortStream(): stops the specified stream, discarding any remaining samples in the queue.  This does not implicitly call closeStream().</LI>
<LI>RtAudio::streamWillBlock(): queries a stream to determine whether a call to the <I>tickStream()</I> method will block.  A return value of 0 indicates that the stream will NOT block.  A positive return value indicates the  number of sample frames that cannot yet be processed without blocking.</LI>
</UL>


\section compiling Compiling

In order to compile RtAudio for a specific OS and audio API, it is necessary to supply the appropriate preprocessor definition and library within the compiler statement:
<P>

<TABLE BORDER=2 COLS=5 WIDTH="100%">
<TR BGCOLOR="beige">
  <TD WIDTH="5%"><B>OS:</B></TD>
  <TD WIDTH="5%"><B>Audio API:</B></TD>
  <TD WIDTH="5%"><B>Preprocessor Definition:</B></TD>
  <TD WIDTH="5%"><B>Library:</B></TD>
  <TD><B>Example Compiler Statement:</B></TD>
</TR>
<TR>
  <TD>Linux</TD>
  <TD>ALSA</TD>
  <TD>__LINUX_ALSA_</TD>
  <TD><TT>libasound, libpthread</TT></TD>
  <TD><TT>g++ -Wall -D__LINUX_ALSA_ -o probe probe.cpp RtAudio.cpp -lasound -lpthread</TT></TD>
</TR>
<TR>
  <TD>Linux</TD>
  <TD>OSS</TD>
  <TD>__LINUX_OSS_</TD>
  <TD><TT>libpthread</TT></TD>
  <TD><TT>g++ -Wall -D__LINUX_OSS_ -o probe probe.cpp RtAudio.cpp -lpthread</TT></TD>
</TR>
<TR>
  <TD>Irix</TD>
  <TD>AL</TD>
  <TD>__IRIX_AL_</TD>
  <TD><TT>libaudio, libpthread</TT></TD>
  <TD><TT>CC -Wall -D__IRIX_AL_ -o probe probe.cpp RtAudio.cpp -laudio -lpthread</TT></TD>
</TR>
<TR>
  <TD>Windows</TD>
  <TD>Direct Sound</TD>
  <TD>__WINDOWS_DS_</TD>
  <TD><TT>dsound.lib (ver. 5.0 or higher), multithreaded</TT></TD>
  <TD><I>compiler specific</I></TD>
</TR>
</TABLE>
<P>

The example compiler statements above could be used to compile the <TT>probe.cpp</TT> example file, assuming that <TT>probe.cpp</TT>, <TT>RtAudio.h</TT>, and <TT>RtAudio.cpp</TT> all exist in the same directory.

\section osnotes OS Notes

RtAudio is designed to provide a common API across the various supported operating systems and audio libraries.  Despite that, however, some issues need to be mentioned with regard to each.

\subsection linux Linux:

RtAudio for Linux was developed under Redhat distributions 7.0 - 7.2.  Two different audio APIs are supported on Linux platforms: OSS and <A href="http://www.alsa-project.org/">ALSA</A>.  The OSS API has existed for at least 6 years and the Linux kernel is distributed with free versions of OSS audio drivers.  Therefore, a generic Linux system is most likely to have OSS support.  The ALSA API is relatively new and at this time is not part of the Linux kernel distribution.  Work is in progress to make ALSA part of the 2.5 development kernel series.  Despite that, the ALSA API offers significantly better functionality than the OSS API.  RtAudio provides support for the 0.9 and higher versions of ALSA.  Input/output latency on the order of 15-20 milliseconds can typically be achieved under both OSS or ALSA by fine-tuning the RtAudio buffer parameters (without kernel modifications).  Latencies on the order of 5 milliseconds or less can be achieved using a low-latency kernel patch and increasing FIFO scheduling priority.  The pthread library, which is used for callback functionality, is a standard component of all Linux distributions.

The ALSA library includes OSS emulation support.  That means that you can run programs compiled for the OSS API even when using the ALSA drivers and library.  It should be noted however that OSS emulation under ALSA is not perfect.  Specifically, channel number queries seem to consistently produce invalid results.  While OSS emulation is successful for the majority of RtAudio tests, it is recommended that the native ALSA implementation of RtAudio be used on systems which have ALSA drivers installed.

The ALSA implementation of RtAudio makes no use of the ALSA "plug" interface.  All necessary data format conversions, channel compensation, deinterleaving, and byte-swapping is handled by internal RtAudio routines.

\subsection irix Irix (SGI):

The Irix version of RtAudio was written and tested on an SGI Indy running Irix version 6.5 and the newer "al" audio library.  RtAudio does not compile under Irix version 6.3 because the C++ compiler is too old.  Despite the relatively slow speed of the Indy, RtAudio was found to behave quite well and input/output latency was very good.  No problems were found with respect to using the pthread library.

\subsection windows Windows:

RtAudio under Windows is written using the DirectSound API.  In order to compile RtAudio under Windows, you must have the header and source files for DirectSound version 0.5 or higher.  As far as I know, you cannot compile RtAudio for Windows NT because there is not sufficient DirectSound support.  Audio output latency with DirectSound can be reasonably good (on the order of 20 milliseconds).  On the other hand, input audio latency tends to be terrible (100 milliseconds or more).  Further, DirectSound drivers tend to crash easily when experimenting with buffer parameters.  On my system, I found it necessary to use values around nBuffers = 8 and bufferSize = 512 to avoid crashing my system.  RtAudio was developed with Visual C++ version 6.0.  I was forced in several instances to modify code in order to get it to compile under the non-standard version of C++ that Microsoft so unprofessionally implemented.  We can only hope that the developers of Visual C++ 7.0 will have time to read the C++ standard. 


\section acknowledge Acknowledgments

The RtAudio API incorporates many of the concepts developed in the <A href="http://www.portaudio.com/">PortAudio</A> project by Phil Burk and Ross Bencina.  Early development also incorporated ideas from Bill Schottstaedt's <A href="http://www-ccrma.stanford.edu/software/snd/sndlib/">sndlib</A>.  The CCRMA <A href="http://www-ccrma.stanford.edu/groups/soundwire/">SoundWire group</A> provided valuable feedback during the API proposal stages.

RtAudio was slowly developed over the course of many months while in residence at the <A href="http://www.iua.upf.es/">Institut Universitari de L'Audiovisual (IUA)</A> in Barcelona, Spain, the <A href="http://www.acoustics.hut.fi/">Laboratory of Acoustics and Audio Signal Processing</A> at the Helsinki University of Technology, Finland, and the <A href="http://www-ccrma.stanford.edu/">Center for Computer Research in Music and Acoustics (CCRMA)</A> at <A href="http://www.stanford.edu/">Stanford University</A>.  This work was supported in part by the United States Air Force Office of Scientific Research (grant \#F49620-99-1-0293).

These documentation files were generated using <A href="http://www.doxygen.org/">doxygen</A> by Dimitri van Heesch.

*/