Troubleshooting

If Bitcrust behaves unexpectedly, this short list covers the most common issues.

The plugin does not load in my DAW

Confirm your DAW supports the format you installed:

• macOS: AU or VST3
• Windows: VST3
• Linux: VST3
• iPadOS / iOS: AUv3

Rescan plugins in your DAW settings. On macOS, you can also run auval -a in Terminal to check AU validation.

The oscilloscope stays flat

The oscilloscope reads from Bitcrust’s output. If no notes are playing, or if the master volume is at zero, the trace will be flat. Check that the monitor rail is visible (toggle with the monitor button in the footer).

Playback is distorted at full polyphony

Bitcrust is most honest at a few voices; fully loaded twelve-voice chords with high unison counts are loud by design. Lower the master volume and check that your DAW bus is not clipping. The built-in soft limiter helps, but it cannot compensate for extreme levels.

Effects rack changes do not take effect

Make sure the effect slot is not bypassed (check the BYPASS toggle on each slot). Also confirm the MIX knob is above zero.

Arpeggiator or sequencer does not play

Arp and Seq are mutually exclusive. If the mode selector is set to OFF, no pattern will play. Also ensure the host is sending MIDI notes to Bitcrust and that the host transport is running (for tempo-synced operation).

Preset browser shows no results

Check that search and tag filters are not too restrictive. Click Clear on the tag filter row and clear the search box to reset.

MIDI-learn does not respond

Right-click a knob to enter MIDI-learn mode, then move the desired CC controller. If the mapping does not appear, confirm that the MIDI channel matches (check SETUP tab).

Something else

Email [email protected] with the plugin version, DAW, OS, and a short description.