audio-thread

Forbidden operations on a real-time audio thread include memory allocations, locks, file I/O, and Objective-C calls on macOS. Preventing these blocking actions in JUCE audio callbacks ensures deterministic execution and avoids audio glitches.

You can safely share state between the UI and audio thread by using lock-free communication patterns. These patterns prevent the audio thread from waiting on locks, ensuring real-time DSP callbacks execute without blocking or causing glitches.

JUCE audio plugins often glitch when unsafe operations like memory allocations or locks occur within the real-time audio callback. Auditing your audio-path code for these blocking operations and applying lock-free patterns resolves the timing issues.

Yes, you can use Tracktion Engine for real-time audio metering without thread locks by applying lock-free communication patterns. This approach safely shares metering state between the audio thread and UI without blocking real-time DSP callbacks.

The best way to prevent memory allocation in audio callbacks is to audit your audio-path code for dynamic allocations and pre-allocate necessary buffers. Applying lock-free patterns ensures safe cross-thread communication without triggering real-time audio thread allocations.