Logging & Debugging

This page collects practical debugging tips for PATCHBAY.

Where to look first

• The UI error panel (traceback text on failures)
• Console output when launching from a terminal
• Saved output files + their metadata (sample rate, channels)

See also Troubleshooting.

Suggested logging approach (developers)

• Prefer structured messages in the worker event queue (GUI).
• In the backend, log:
  • model name + device
  • chunk plan (count, window, overlap)
  • anchor count + mode
  • timings per stage

Crash reproduction checklist

1. Re-run with the same audio and the same Config.
2. Disable AudioFX to isolate model issues.
3. Reduce max_len_s to see if the issue is chunk-size dependent.
4. If using GPU, try CPU to separate driver/GPU issues from algorithm issues.

Last updated: 2026-01-24