Real-time Check
Find audio code that can cause dropouts, like memory allocation, locks and file access on the audio thread.
The Real-time Check plays your plugin hard, away from Studio, and finds calls in its audio code that can cause dropouts: allocating or freeing memory, waiting on a lock, sleeping, file or network work, and starting threads. It isn't part of the Freqlab Standard.
Run itLink to this section
- Build the version you want to check. The check runs its CLAP.
- Open Controls, then Debugging.
- Under Real-time Check, click Check.
Read the resultsLink to this section
Each finding shows what kind of call it is, where it was made, and its call stack (click a line to open it). It's tagged by where it comes from:
- Your code: fix these.
- Framework: often fine, but worth knowing.
- Not known: Studio couldn't tell where it comes from (often no line numbers). Worth a look.
- Note: a one-time setup, or something the framework does by design. Usually fine.
Findings also appear in the editor's Problems list. With an agent set up, Ask Agent drafts a message about one finding, or Ask Agent About All.
Line numbers come from the build's debug info: keep Line numbers in crash reports on in Settings, Local Build.
OptionsLink to this section
By default the check plays 30 seconds of audio, shared across 44.1, 48 and 96 kHz, with blocks of 64, 512 and 2048 plus uneven blocks, playing notes and moving parameters. Change it in Settings, Debugging, or Customize for this project.
macOS and WindowsLink to this section
Uses LLVM's RealtimeSanitizer. Needs macOS 11 or later.