Troubleshooting

Black screen, nothing on SSH

Put the card in a computer and edit cmdline.txt: on the Pi, on the SYSTEM partition in use (partition 2 on a new card); on a mini PC, EFI/BOOT/grub.cfg. Remove quiet loglevel=3 and add console=tty1 to see the boot messages on the screen. Keep it all on one line.

Wrong resolution, or no picture on a small screen

Some small panels send no or wrong display data (EDID), or are not ready when the Pi starts. Add the mode at the end of cmdline.txt, for instance for a 10” 1024 × 600 screen:

video=HDMI-A-1:1024x600@60D

D forces the output on. Before Linux takes over the display, the screen may show its own “No signal” message for a moment: that is normal.

Screen upside down or sideways

Set Screen rotation in Settings → Audio & system, or display_rotation to 90, 180 or 270 in pedalboard.txt.

No sound

1. Check that the IN meter moves when you play. If it does not, the guitar is not reaching the pedalboard: check the cable and the interface’s input gain.
2. In Settings → Audio & system, step Interface through the sound cards the system sees and pick yours. Over SSH, cat /proc/asound/cards lists them too: audio_device in pedalboard.txt takes the name in brackets.
3. tail -f /var/log/messages shows why the audio server does not start.

Without an interface, the audio server waits for one: plugging it in later works.

One output stays silent

With a multi-channel interface or sound HAT, an output can stay silent while its meter on the Routing page moves. The meter reads what OpenRig sends, so the sound is lost after it. Over SSH:

1. grep -E "Interface|Connected|connect" /var/log/messages shows the ports the interface offers and the connections OpenRig made at start: pedalboard:out_3 → system:playback_3 means output 3 is wired. jack_lsp -c shows the live connections.
2. Many multi-channel cards and HATs have a volume or mute control per channel that starts at zero. amixer -c <card> contents lists them (the card number comes from cat /proc/asound/cards).
3. To test the card without OpenRig: killall jackd; speaker-test -D hw:<card> -c 8 -t wav plays a voice on each channel. The audio server starts again once the test ends (Ctrl+C).

USB devices dropping out

A touchscreen or an audio interface that disconnects is usually short of power. The Pi 5 gives USB devices 1.6 A only with the official 27 W (5 V, 5 A) supply, and 600 mA otherwise. Use that supply, or a powered USB hub.

Clicks and crackles

See Performance.

A block went silent for a moment

If a plugin crashes while processing the sound, OpenRig catches it: the dry signal plays while the chain is built again, so the sound comes back by itself. If it keeps failing, the screen says so and the dry signal plays until your next change: remove the last block you added, or load another preset. grep -E "ERROR|WARN" /var/log/messages shows what happened; send it with an issue.

The tone sounds wrong with a capture

Neural captures are trained at 48 kHz. Check that sample_rate=48000 in pedalboard.txt. Try Normalize on the block, and set Input so the capture is driven as intended.

The mini PC does not start the image

The x86_64 image needs a CPU with AVX2 (Intel Haswell or newer, N100 included; AMD Excavator, Zen). On a Celeron or Pentium without it, such as a J4125 or N4020, it stops right after the boot loader. Check with grep -o avx2 /proc/cpuinfo from any Linux on that PC: see What you need.

A plugin does not show in Add effect

The plugin may need a host feature OpenRig does not provide yet, or be built for another processor. The log says why it was skipped: grep -i lv2 /var/log/messages. See LV2 plugins.

Still stuck

Open an issue with the version (Settings → Updates), your board and interface, and the output of pedalboard-report (see SSH and logs).