Manual contents
← Manual

MANUAL / 09

Audio settings & stability

Understand buffers, channels, device changes and Resume.

All instructional screenshots in this manual show iPad. · NAM FX 1.x

Buffer size

Settings offers requests of 64, 128, 256 or 512 frames. Smaller values generally respond faster but leave less processing headroom. Start at 128, check stability, then try 64. If audio breaks up, increase the buffer and compare with fewer complex models or effects.

NAM FX on iPad — Buffer size
iPad · Settings · audio and input channels

Find it on screen

  1. Choose 64 / 128 / 256 / 512 under Buffer size.
  2. If a small buffer causes dropouts, raise it and compare with the same rig.
More iPad screens →

Requested versus actual

The device may negotiate a different buffer. Check the actual buffer and sample rate shown by the app. Total latency includes conversion, the operating system and effects such as NAM or pitch processing, as well as buffering. One fixed latency figure cannot describe every setup.

Preparing and Resume

Preparation status appears at launch or during device changes. Automatic startup preparation differs from Audio Ready after an interruption that requires your confirmation. Audio Ready presents Resume; check the connection before resuming. Buffer changes can briefly reconfigure audio.

NAM FX on iPad — Preparing and Resume
iPad · Audio interface disconnected

Find it on screen

  1. When the interface disconnects, audio pauses and Resume is disabled. Check USB and power connections.
  2. Continue editing lets you edit the rig; reconnect the interface before resuming audio.
More iPad screens →
NAM FX on iPad — Preparing and Resume
iPad · Audio Ready · Resume

Find it on screen

  1. Once the interface is ready, Audio Ready shows an enabled Resume button.
  2. Check the connection and monitor level, then tap Resume to restart audio processing.
More iPad screens →

Long sessions

Rehearse long enough on the actual device, interface and rig to check heat and stability. Power, hubs, cables and background tasks also matter. Interfaces that report the same channel count can still map headphone outputs differently.