Troubleshooting
Solutions to common issues in the Audio Visualizers app.
Visualizer Doesn't React to Audio
Check the audio source: Open Settings → Audio (Ctrl+K) and make sure something is actually playing — a demo track, a loaded file, or the microphone toggle. The NOW PLAYING mini player at the bottom of the canvas confirms track playback.
Microphone permission: If using mic input, click the lock icon in the address bar → allow microphone, then refresh.
Wrong input device: With the mic enabled, pick your interface in the device dropdown in Settings → Audio — the selection applies immediately, and the live level meter shows whether signal is arriving. On macOS, also check System Settings → Privacy & Security → Microphone.
Mic vs. track: Enabling the microphone pauses track playback — they're exclusive. Toggle the mic off to go back to the track.
Visuals Are Choppy / Low FPS
Close other tabs: Other browser tabs share GPU resources.
Use a tested browser: Chrome and Edge are the supported choice for the heavier particle, simulation, and WebGPU visualizers. See Browser Support before troubleshooting another browser or device.
Check what's actually happening: Enable the Performance HUD below to see live FPS and the active renderer.
WebGPU Visualizer Shows Error
"WebGPU Required" means the browser or device did not make WebGPU available to the visualizer.
- Check the current browser and platform requirements in Browser Support
- Update the browser and restart it
- Make sure graphics acceleration is enabled in the browser's system settings
- If the visualizer still shows unavailable, try the same link in current Chrome or Edge to separate a browser limitation from a device limitation
APC Mini MK2 Pads Not Lighting Up
- Connect the APC Mini before opening the browser, and grant MIDI permission when prompted
- Switch to Performer mode — the LED integration only runs there
- Open Performer Settings → MIDI (click the MIDI status in the control bar) and check CONNECTED DEVICES — the APC Mini should be listed as connected
- Check the LED DISPLAY MODE — if it's set to a meter mode, the pads show audio levels instead of the preset grid; open the PRESETS panel or select PRESET GRID
If still no response, unplug the USB and replug, then refresh the page.
Scene Sequencer Running at the Wrong Speed
Scene timings in beats follow the current BPM:
- Set the tempo: Click the BPM readout (settings footer or Analysis Engine) or press
Ton the beat — three taps lock an override. See Tempo & Tap Tempo. - Check the BPM sync toggle: The sequencer's BPM button converts scene durations between beats and seconds — a 16-beat scene at 60 BPM holds much longer than at 170 BPM.
- External clock: If Performer Settings → MIDI → Clock Source is set to EXTERNAL, the tempo follows incoming MIDI clock, not your taps.
Loading a Preset Changed My Visualizer
That's by design — a preset stores the visualizer type plus its full parameter set, so launching one switches to its visualizer. To restyle the current visualizer instead, open the Customize panel and adjust parameters (or load one of that visualizer's own presets in Visualizer mode). See Presets.
Performance HUD (Developer Mode)
A diagnostic overlay that displays live FPS (frames per second) and the active renderer type (Canvas2D, WebGL, or WebGPU) in the bottom-right corner of the canvas. It is off by default.
Enabling the HUD
- Open Settings (gear icon)
- Go to the Display tab
- Scroll to the DEVELOPER section
- Toggle PERFORMANCE HUD on
The setting persists across sessions and applies to both Visualizer and Performer modes.
When to Use It
| Use Case | What to Look For |
|---|---|
| Frame drops during live performance | FPS dropping below 30 (shown in red) or fluctuating. Try closing other tabs or reducing resolution. |
| Verifying GPU acceleration | The renderer badge shows Canvas2D, WebGL, or WebGPU. If you expect WebGPU but see Canvas2D, check WebGPU troubleshooting above. |
| Comparing visualizer cost | Switch between visualizers and watch the FPS counter. Some visualizers (particles, 3D terrain) are heavier than others (waveform, bars). |
| Testing on different hardware | Enable the HUD to benchmark performance on laptops, tablets, or external displays at different resolutions. |
The FPS counter is color-coded: green (55+ fps), amber (30–54 fps), red (below 30 fps). If you see consistent red, try the suggestions in Visuals Are Choppy above.