OpenAL Soft Reverb Silent? Diagnosing AL_EXT_EFX Failures

The symptom: reverb is enabled but you hear no change

You configure an AL_EXT_EFX reverb, attach it to a source, and playback sounds dry. No crash occurs, parameters appear to be set, yet the audible result is unchanged. The useful takeaway is that silent reverb in OpenAL Soft is rarely a parameter tuning issue. It is almost always an extension availability, creation, or attachment failure that is masked by OpenAL's error state.

AL_EXT_EFX is the OpenAL extension for effects. It provides effects, effect slots, auxiliary sends, and filters. OpenAL Soft implements EFX as an optional module. If the module is missing or the runtime cannot allocate resources, calls succeed superficially but produce no processing.

Cause to signal table

Observable condition	Likely cause	Diagnostic signal
alIsExtensionPresent("AL_EXT_EFX") returns false	Library built without EFX or runtime lacks support	No EFX entry points available
alGenEffects returns 0 or alGetError returns AL_INVALID_OPERATION	Effect type unsupported by build	Effect object is invalid
Effect slot created, alSourcei with AL_EFFECTSLOT fails	Slot attachment not supported or source in invalid state	AL_INVALID_OPERATION after attach
Extension present but allocation fails with AL_EFX_NO_EFFECTS	Driver or hardware resource limit	Cannot allocate internal EFX resources
All calls succeed, no audible change	Send level zero, auxiliary send not routed, or dry mix	Waveform unchanged in capture

Ordered checks

1. Confirm extension presence

Run a small program on the target host where the application will run. No elevated permissions are required. Link against OpenAL Soft headers and library.

// check_efx.c
#include 
#include 
#include 

int main(void) {
    ALCdevice *device = alcOpenDevice(NULL);
    if (!device) { return 1; }
    ALCcontext *context = alcCreateContext(device, NULL);
    alcMakeContextCurrent(context);

    ALboolean present = alIsExtensionPresent("AL_EXT_EFX");
    printf("AL_EXT_EFX present: %s\n", present ? "yes" : "no");

    alcMakeContextCurrent(NULL);
    alcDestroyContext(context);
    alcCloseDevice(device);
    return 0;
}

Expected check: the program prints "yes". If absent, all later EFX calls are invalid. Risk: none. This only queries the context.

2. Verify effect creation and error state

After confirming presence, attempt to generate an effect and check the error immediately.

ALuint effect = 0;
alGenEffects(1, &effect);
ALenum err = alGetError();
if (err != AL_NO_ERROR || effect == 0) {
    /* log err and treat EFX as unavailable */
}

Expected check: error is AL_NO_ERROR and effect id is non-zero. If AL_INVALID_OPERATION is returned, the effect type is unsupported in this build.

3. Verify slot creation and source attachment

Create an effect slot, assign an effect to it, then attach the slot to a source.

ALuint slot = 0;
alGenAuxiliaryEffectSlots(1, &slot);
err = alGetError();
if (err != AL_NO_ERROR || slot == 0) { /* handle failure */ }

alAuxiliaryEffectSloti(slot, AL_EFFECTSLOT, effect);
err = alGetError();
if (err != AL_NO_ERROR) { /* handle failure */ }

ALuint source = 0;
/* assume source created and valid */
alSourcei(source, AL_EFFECTSLOT, (ALint)slot);
err = alGetError();
if (err != AL_NO_ERROR) { /* handle failure */ }

Expected check: no error after slot creation, effect assignment, or source attachment. AL_INVALID_OPERATION here means the slot cannot be used with the current source or context.

4. Check resource limits

If the extension is present but creation fails repeatedly, the driver or OpenAL Soft build may not have allocatable EFX resources. On Windows, certain audio drivers may not expose EFX even if the library supports it. On Linux, distribution packages sometimes ship OpenAL Soft without the EFX module enabled.

5. Audible verification

When all calls succeed, play a known sound with a non-zero auxiliary send level. Capture output with a waveform viewer and compare dry versus processed output. This confirms the processing chain is active rather than relying on perceived loudness.

Fixes tied to findings

If extension absent: install or build OpenAL Soft with EFX enabled. On Linux, verify the package provides libopenal.so.1 with EFX symbols. On Windows, ensure the OpenAL Soft DLL in use is the one loaded by the application, not a legacy Creative DLL.

If alGenEffects returns invalid operation: rebuild the application against a build that includes EFX, or switch to a fallback without effects. Replacing the library changes state; keep a rollback copy of the previous library file.

If slot attachment fails: ensure the source is valid and not deleted, and that AL_EFFECTSLOT is used with alSourcei. Verify the effect is assigned to the slot before attachment.

If AL_EFX_NO_EFFECTS is observed: reduce the number of simultaneous effects, or increase EFX resource limits via OpenAL Soft configuration if supported on the platform. This is platform dependent and may require restarting the audio subsystem.

Escalation criteria

Escalate when the extension is present, creation and attachment succeed with no errors, send levels are non-zero, yet waveform capture shows no change. This suggests a driver-level processing bypass.

Escalate also when the same binary works on one operating system and fails on another with identical library versions. Provide the output of the extension presence check, the error codes after alGenEffects and slot attachment, and the OpenAL Soft version string from alcGetString.

Limitations

EFX support is optional in OpenAL Soft builds. Some distributions ship with the module disabled to reduce binary size. Behavior can vary between builds and driver stacks. Verification on the target platform is required because extension availability cannot be assumed from documentation alone.