Probes
Watch values from your plugin's code live while it plays, and catch the moment one goes bad.
A probe sends a value from your code to Studio while the plugin plays. Studio graphs it and catches it when it goes wrong: NaN or infinity always, and past a limit or a sudden jump if you ask.
Set upLink to this section
Open Controls, then Debugging, and click Set Up under Probes. Studio lists the changes it'll make to your project before making them. Probes work with Cargo and CMake projects.
Add probesLink to this section
In a file that includes freqlab_probe.h:
FREQLAB_PROBE("gain", gain);
FREQLAB_PROBE_BUFFER("out", samples, count);Build, and play the plugin in the preview. Probes only exist in Studio's own builds: cloud builds leave them out.
Watch themLink to this section
The table lists each probe's Value, a small graph (click it for a larger one), and two settings:
- Limit: catch the value when it goes past this, either side of zero.
- Jumps: catch a value that jumps far past its recent range.
In the editor, each probe's live value also shows at the end of its line while the build plays (Settings, Editor, Probe values).
Each catch shows what went wrong, a plot of the moment, and the other probes' values at the time. Open the Line goes to the probe in your code; with an agent set up, Ask Agent drafts a message about it. Studio keeps the newest 10 catches per project until it closes.
A build can have up to 64 probes.