Quick Guide: Foo DSP DolbyHP — Setup & Best Settings

Troubleshooting Foo DSP DolbyHP: Common Issues and Fixes

Below are common problems users encounter with the Foo DSP DolbyHP plugin (audio processing plugin for Foobar2000/related DSP chains) and step-by-step fixes. Assumptions: you’re on Windows, using Foobar2000 or a similar host that supports DSP chains and VST-style plugins.

1. No sound after enabling DolbyHP

• Cause: Plugin bypassed, incorrect routing, or incompatible sample rates.
• Fix:
  1. Ensure DolbyHP is enabled in the DSP chain (not bypassed).
  2. Check Foobar2000 Output device: match its sample rate to the track and DolbyHP expected rate (commonly 44.1 kHz or 48 kHz).
  3. If using exclusive mode, disable it temporarily in output settings.
  4. Test without other DSPs to rule out conflicts.

2. Distorted or clipping audio

• Cause: Gain staging issues or incompatible processing order.
• Fix:
  1. Lower input/gain settings in DolbyHP if available.
  2. Reorder DSPs so DolbyHP processes before any final limiter or after EQ depending on desired behavior; try both orders.
  3. Insert a limiter or adjust output gain to prevent clipping.
  4. Disable other gain-boosting DSPs or normalization.

3. Channels swapped or incorrect stereo imaging

• Cause: Channel mapping mismatch or incompatible downmix/upmix settings.
• Fix:
  1. Verify channel mapping in DolbyHP settings (left/right/center).
  2. Disable automatic upmix/downmix options and set mapping manually.
  3. Test with a stereo-only source and bypass other spatial DSPs.

4. Plugin crashes host application

• Cause: Version incompatibility, corrupt plugin file, or conflicting DSPs.
• Fix:
  1. Update Foo DSP DolbyHP to the latest compatible build.
  2. Reinstall the plugin: remove files, redownload from a trusted source, and reinstall.
  3. Run Foobar2000 in safe mode (disable third-party components) to identify conflicts.
  4. Check Windows Event Viewer for crash logs and search for matching errors.

5. Latency or stuttering playback

• Cause: High processing load, buffer underruns, or driver issues.
• Fix:
  1. Increase output buffer size in your audio device settings.
  2. Use an ASIO driver or WASAPI exclusive for lower-latency, more stable output.
  3. Close CPU-heavy applications and ensure power settings allow full CPU performance.
  4. Lower DolbyHP internal processing quality if an option exists.

6. Settings not saving between sessions

• Cause: Permission issues or corrupt config.
• Fix:
  1. Run host application as administrator once and save settings.
  2. Check plugin settings file location (AppData or Foobar components folder) and ensure it’s writable.
  3. Delete corrupt settings file so plugin recreates defaults.

7. Unexpected loudness changes between tracks

• Cause: Integrated normalization or dynamic processing.
• Fix:
  1. Disable track normalization in DolbyHP or Foobar2000 ReplayGain.
  2. Use a consistent processing chain and avoid per-track dynamic range adjustments unless desired.

8. Poor compatibility with multi-channel/HD audio

• Cause: DolbyHP may expect stereo or certain channel layouts.
• Fix:
  1. Downmix to stereo before processing, or use a host/output that supports the plugin’s channel count.
  2. Check sample rate conversion settings and use SRC if necessary.

Quick diagnostic checklist

• Match sample rates across source, plugin, and output.
• Disable other DSPs to isolate the issue.
• Update plugin and host to latest versions.
• Try different output drivers (WASAPI/ASIO/kernel streaming).
• Check Windows permissions and reinstall if corrupt.

If you want, provide your Foobar2000 version, OS build, exact DolbyHP plugin version, and a short description of the symptom and I’ll give tailored steps.