Quick Troubleshooting Guide for Foo DSP BS2B Issues
1. Confirm basics
- Power: Ensure unit and any connected devices have power and LEDs indicate normal operation.
- Cables: Check all audio, Ethernet, USB, and power cables for secure connections and visible damage.
- Firmware/software versions: Verify firmware on the BS2B and any companion software drivers are up to date.
2. Reproduce and isolate the problem
- Reproduce: Note exact steps to trigger the issue (specific input, patch, or processing block).
- Isolate: Swap cables, use a different input/output, or bypass processing blocks to find whether hardware, routing, or DSP configuration causes it.
3. Common symptom fixes
- No audio output:
- Confirm input signal is present (use level meters).
- Check mute/solo settings and output routing.
- Verify sample rate and clock source match across devices.
- Audio dropouts/glitches:
- Increase buffer size or reduce processing load.
- Check CPU/DSP usage—disable nonessential modules.
- Test with shorter cable runs and shielded cables; inspect for EMI sources.
- Latency too high:
- Lower buffer size, enable low-latency mode, or move latency-inducing modules offline.
- Ensure host and device sample rates match; use dedicated audio interfaces if possible.
- Configuration not saving:
- Check file system permissions and available storage.
- Follow proper save/export procedure in the device UI; update firmware if a known bug exists.
- Control surface or MIDI not responding:
- Confirm MIDI/OSC routing and channel assignments.
- Test with another controller or loopback to verify signal.
- Crackling or noise:
- Ground loops: try different power outlets or use ground lifts.
- Replace suspect cables and check connectors for dirt/corrosion.
4. Diagnostic steps and logs
- Safe mode / factory reset: Boot into safe mode or reset to factory defaults to rule out corrupted settings (note: backup presets first).
- Swap components: Substitute known-good modules (cables, interface, computer) to pinpoint failure.
- Collect logs: Export system logs and error reports from the BS2B or companion app; note timestamps and exact actions that produced errors.
5. Performance tuning
- Optimize patching: Reduce parallel processing chains, use more efficient algorithms or lower oversampling.
- Resource monitoring: Keep an eye on DSP/CPU meters; aim for headroom (20–30% free) to avoid overloads.
- Update drivers/firmware: Regularly apply vendor updates addressing stability and performance.
6. When to contact support
- After confirming cables, firmware, presets, and a factory reset, contact vendor support with:
- Exact firmware/software versions, serial number, and detailed reproduction steps.
- Collected logs, screenshots, and a short video showing the issue.
- List of steps already tried (reboots, resets, swaps).
7. Quick checklist (copyable)
- Power on, LEDs normal
- Cables secure and undamaged
- Input signal present on meters
- Routing, mute/solo, sample rate match
- Firmware/drivers up to date
- Safe mode/factory reset tested
- Logs exported for support
If you want, I can adapt this into a one-page printable checklist or a step-by-step flowchart tailored to a specific symptom.
Leave a Reply