Check Ecasound Buffer Underruns in Interactive Mode

This guide explains how to monitor audio buffer underruns in Ecasound using its Interactive Mode (IAM). You will learn the exact commands used to display real-time underrun statistics, how to run them during an active audio processing session, and how to address buffer underruns if they occur.

In Ecasound Interactive Mode, the command to display current buffer underrun counts is status (or its shorthand alias, st).

Using the Status Command

When running Ecasound interactively (started via ecasound -c or with an interactive option), type the command at the interactive prompt:

ecasound ('h' for help) > status

or simply:

ecasound ('h' for help) > st

Executing this command outputs the current state of the audio processing engine, including:

• Current engine execution status (e.g., running, stopped, paused)
• Current stream position and total duration in seconds and samples
• Input/output processing statistics
• Total count of buffer underruns (xruns) and overruns encountered by the audio engine

If you are interacting with Ecasound programmatically via the Ecasound Control Interface (ECI) protocol rather than the user shell, the underlying command to query the engine state and underrun count is:

engine-status

Interpreting Underruns

A buffer underrun occurs when the audio subsystem requests data from Ecasound faster than the application or system can deliver it, resulting in audible clicks, pops, or dropouts.

If the status command reveals an increasing underrun count:

• Increase the buffer size: Adjust the buffering parameters using the -b:buffersize or -B:buffermode options when launching Ecasound.
• Lower CPU overhead: Reduce real-time effect chains or lower system load during processing.
• Check audio backend settings: If using ALSA or JACK, ensure the period size and periods per buffer are properly aligned with your hardware capabilities.