BIAS X Audio Troubleshooting

This guide covers the most common audio issues in BIAS X: no input/output signal, crackling or popping noise, and audio interface not appearing in settings.

Start by identifying your symptom, then jump to the matching section below.

No Input or Output Signal

Signal issues are often caused by permission settings, incorrect I/O channel selection, or missing elements in your preset's signal path.
  1. Check Cable and Instrument Connection

    • Ensure your instrument is securely plugged into your audio interface.
    • Swap cables or try a different instrument to rule out hardware faults.
  2. Grant Permissions on Your Operating System

    • macOS: Go to Apple Menu > System Settings > Privacy & Security. Enable access for Microphone and Files and Folders (look for BIAS X under each section). Ensure the microphone mode is "Standard". Learn more
    • Windows: Go to Settings > Privacy & security > Microphone. Ensure microphone access is enabled for both the system and apps.
  3. Verify Input/Output Channels

    • In BIAS X, navigate to Audio Settings > Input/Output Channels.
    • Select the channels that match your audio interface (e.g., Input 1, Output 1/2).
  4. Check Noise Gate and Output Settings

    • Make sure the master input level is turned up and the Noise Gate is turned off.
    • Ensure your master output or amp volume is not muted or too low.
  5. Confirm Preset Signal Path

    • Check that your preset includes an amp or other signal chain modules.
    • Avoid muted or missing blocks that could break the signal flow.
Try switching to a factory preset to confirm the signal is working correctly before troubleshooting a custom preset.

Crackling or Popping Noise

Crackling or popping sounds often occur when your system cannot keep up with the CPU demand.

Common Causes

  1. High CPU Load — Presets with many effects or dual amps use more processing power.
  2. Low Buffer Size / High Sample Rate — These settings increase CPU usage.
  3. Background Applications — Other apps reduce available CPU resources.
  4. Multiple Plugin Instances — Running several plugins at once significantly increases CPU load.

Recommended Fixes

  1. Adjust Audio Settings — In BIAS X or your DAW, set Sample Rate to 48 kHz or lower and Buffer Size to 256 or higher.
  2. Close Unused Applications — Quit any apps you are not using to free up CPU.
  3. Optimize Windows for Audio — Follow Sweetwater's optimization guide for better CPU performance.
  4. Limit Plugin Instances — Export processed tracks to WAV files and re-import them into your session to reduce CPU usage.

Audio Interface Not Detected

If your audio interface does not appear in BIAS X's audio settings, it may be due to connection issues, missing drivers, or incorrect settings.

BIAS X may not detect your audio interface if it is not properly connected or if the driver type is incompatible.
  1. Check Hardware Connection

    • Ensure your audio interface is properly connected via USB and powered on.
    • Try using a different USB port or cable if available.
  2. Restart BIAS X

    • Completely close BIAS X, reconnect your audio interface, and relaunch BIAS X.
  3. Update or Reinstall Drivers (Windows only)

    • Visit your audio interface manufacturer's website and install the latest driver.
    • Restart your computer after installation is complete.
  4. Confirm the Correct Driver Type

    • In BIAS X's audio settings, ensure the appropriate Audio Driver Type is selected (e.g., ASIO for Windows).
    • If ASIO is not available from your interface manufacturer, try ASIO4ALL.
On macOS, your interface should appear as a Core Audio device without additional drivers.

Common Fixes Across All Issues

  • Restart your computer after any driver installation or settings change.
  • Update BIAS X to the latest version from your Positive Grid account.
  • Try a factory preset to rule out preset-specific problems.
  • Check OS audio settings to ensure your interface is the default device.

If the issue persists, please contact support.

Still need help?
Our support team can help answer questions and solve problems.
Contact Support