The Audio Status Window

The Audio Status Window shows you the complete set all of the parameters of audio input and output in Max. You can use the Audio Status Window to set these parameters, and as a way to monitor your current audio settings.

Using the Audio Status Window, you can:

• Enable/disable audio processing in Max
• View and select an audio driver
• Monitor the amount of signal processing MSP is currently doing
• Set the audio sampling rate
• Set the number of samples MSP processes at a time - the I/O Vector Size) for input and output.
• Enable/disable Overdrive
• Map logical input and outputs channels for I/O in MSP

All of these options can also be changed from within your Max patch by using the adstatus object in your max patch, or by sending messages to the Max application.

The Audio Status Window includes of a set of tabs you can use to change what is displayed in the window, and a listing of all the settings associated with DSP processing in Max.

Audio processing and your system

You can turn audio processing on and off using the Audio Status Window, and also toggle audio processing using the MSP UI objects ezdac~ and ezdac~, or the adc~ and dac~ MSP objects. Audio and levels can be controlled by the Audio On/Off option at the bottom of the right toolbar.

Configuring MSP audio for your system

While some specific features and settings for using audio on your computer will vary according to the type of audio interface and audio drivers you have installed, you can access these settings in MSP using Audio Status Window.

The Driver pop-up menu in the Audio Status Window lets you view and select an audio driver for MSP. The list of available drivers will vary according to the audio drivers installed on your system. Here is a brief summary of the default options:

• None shuts off MSP audio processing.
• CoreAudio is the default audio driver for MSP on Macintosh.
• MME, DirectSound, or ASIO drivers for Windows systems will appear if you have correctly installed external hardware that supports the standard.
• The ad_rewire driver supports ReWire, a standard developed by Propellerhead Software that allows sound generating applications (ReWire Devices) to send multiple channels of audio and midi to other applications (ReWire Mixers) that process and output it.
• The NonRealTime driver enables MSP to work in non real-time mode, allowing you to synthesize and process audio without any real-time processor performance limitations.

When you have selected the audio driver you want to use, various input (Input Channels, Input Device, and Input Source) and output (Output Channels, Output Destination, and Playthrough Input) parameter settings will become available based on the audio driver you choose.

Note: the number of input channels and output channels displayed in the DSP window are displayed with the grey attribute icon because the number of channels is driver/interface-dependent.

You can set the audio sampling rate with the Sampling Rate pop-up menu. For full-range audio, the recommended sampling rate is 44.1 kHz. Using a lower rate will reduce the number of samples that MSP has to calculate, thus lightening your computer’s burden, but it will also reduce the frequency range.

Max processes audio in by using a block of samples called a signal vector (for an introduction to how MSP works, click here). You can use the Audio Status Window to select the I/O vector size (i.e., the number of audio samples) of the block size that Max uses when working with audio input and audio output. You can also set the signal vector size - the number of samples that Max processes at a time.

The I/O Vector size and Signal Vector size in MSP are commonly expressed as powers of two. They can be set as low as 2 samples, and in most cases can go as high as the largest available I/O Vector Size for your audio driver. However, if the I/O Vector Size is not a power of 2, the maximum signal vector size is the largest power of 2 that divides evenly into the I/O vector size.

Optimizing the performance of any particular large audio patch when you are close to the limit of your CPU’s capability is a trial-and-error process that requires an understanding of how signal vector sizes and the Max scheduler interact. THe Audio I/O chapter of the MSP Tutorial contains a thorough discussion of CPU usage, the sampling rate, vector sizes and signal vectors, and Max scheduler parameters such as overdrive and audio interrupt.

Overdrive

When Overdrive is enabled, Max gives priority to timing and MIDI processing over screen drawing and user interface tasks such as responding to mouse clicks. If you are primarily going to be using Max for MIDI or audio processing, Overdrive should be enabled. If you are primarily going to be using Jitter, Overdrive should be disabled. You can use the Audio Status Window to set this feature.

Processing audio in non real-time

MSP includes a non real-time driver that lets you to use MSP as a disk-based audio processing and synthesis system, removing the limit of how much processing you can do with your CPU in real time. Using the NonRealTime driver means that Max calculates samples in MSP independently of any physical scheduling priority, allowing you to process a vector of audio using a signal path that might take your computer more than one vector's worth of real time to compute.

Patches that use the non real-time driver typically use the dsptime~ object to see how long the audio has been turned on, and pipe their output of to sfrecord~ to capture the results.

Max patchers and audio control

Max separates every top-level patcher into its own DSP chain. This flexibility allows Max to use multiple processors to process separate top level patchers, and lets separate patchers remain separate - as one patcher is running, another patcher can be opened, closed, or edited without stopping the global DSP chain.

While you can enable, attenuate, mute, and solo the Audio Engine using the patcher window's right patcher toolbar, the Audio Status Window provides a single access point for setting low-level audio behavior.

The Enable Mixer Crossfade pop-up menu lets you set the Mixer crossfade mode.

Click in the Parallel Processing checkbox to enable parallel processing in the Mixer.

Two number boxes are provided where you can enter values for Crossfade Latency. and Crossfade Ramp Time. Crossfade Ramp Time.

Logical Input and Output Channels

In Max, you can create a dac~ or adc~ object that uses a channel number between 1 and 512. These numbers refer to what are called logical channels. Logical channels can be dynamically assigned and reassigned to the physical device channels of a particular driver using the Audio Status window and its I/O Mappings subwindow, (you can also do this remapping using the adstatus object.

The pop-up menus labeled Input Channel 1, Input Channel 2, Output Channel 1, and Output Channel 2 allow you to map the first two logical channels of I/O in MSP (i.e. the first two outlets of the adc~ object and the first two inlets of the dac~ object) to physical channels used by your audio driver. Different audio drivers give you different options - for example, the MME driver on Windows only supports two channels, so you will normally use the default options. To map additional logical channels, use the I/O Mappings window, which you can view by clicking the I/O Mappings button at the bottom of the Audio Status window.

In addition, you can use the adstatus object from within your patch to map any of the 512 logical audio I/O channels.

The reason for using logical and physical channels is to let you create patches that use as many channels as you need without regard to the particular hardware configuration you're using. For instance, some audio interfaces use physical device channels 1 and 2 for S/PDIF input and output. If you don't happen to have a S/PDIF-compatible audio interface, you may wish to use channels 8 and 9 instead. You can simply go to the Audio Status window and choose the eighth and ninth physical channels listed in the Input and Output pop-up menus.

Logical channels in MSP are only created if there is a dac~ or adc~ object using them. In other words, if you're only using logical outputs 1 and 2, there aren't 510 unused audio streams sitting around hogging your CPU. However, since you can mix any number of logical channels to a single physical channel if necessary, you can create a complex multi-channel setup that will allow other people to hear all of your logical channels when they use it on a two-channel output device.