Troubleshooting and known issues

First checks

Symptom	Check
No Sidecar voices	USB CONFIG is the Overbridge mode; the Rytm is plugged straight in, no hub; the Sidecar’s log shows ob: streaming and MIDI attached (Teensy console, sidecar.local Log & console tab)
Voices silent right after plugging in	once the Rytm sent no USB MIDI for about 50 seconds while its audio already streamed. Wait a minute, or replug the USB cable
A track shows !NAME	the Sidecar cannot play that machine or effect: see !NAME on the Rytm
P2..P5 show numbers, not names	the Sidecar’s firmware is older than the mods: update it
sidecar.local does not open	a direct Ethernet cable; your computer’s port on automatic (link-local) or 169.254.61.59/16; try http://169.254.61.60
STUTTER is silent or always on	see Set up STUTTER: ROUTE TO MAIN off, P2 at 0 first
The Rytm froze	power cycle it, and report what the Sidecar was doing
The Pi does not start	the # sidecar sdboot begin block must stay in config.txt; use the official 5 V 3 A supply (a weak supply browns out with a display attached)

Known issues

Rytm mods

• User FX slots are not available yet. The TYPE list offers the built-in effects only.
• OS 1.73 only. There are no patch files for other OS versions. OS 1.74 will be supported after testing. On OS 1.74 (or any other version), first flash the stock OS 1.73 .syx with Transfer, as any OS update, then patch and flash it.
• The sample browser can lag while you scroll a large folder with the Sidecar connected. Report the folder size and whether the sequencer was running.
• The slot menu can hold the screen for up to 2 seconds while the Sidecar answers.

Stock Rytm behaviour

• After an OS upgrade the Rytm can hang on “Success! Rebooting”. Power cycle it: the update is complete.

Teensy 4.1

• The Rytm connects only after a reboot or many retries, or the Teensy drops off the computer: solder the Teensy 4.1’s USB host header (5 V, D-, D+, GND, shield). Press-fit or unsoldered pins make the host port flaky: the Rytm connects only after a reboot or after many retries (the link comes up at full speed and drops), and the Teensy’s own USB to the computer can drop when the host port’s power switches on. Use a short, good USB cable to the Rytm.

• RINGS, CLOUDSEED and STUTTER run only on the Pi.

• The console’s User machines and Files tabs are in testing.

• USB audio to a computer: stereo in this release (2 in / 2 out); the multichannel mode comes later.

Raspberry Pi 4B

• The Rytm does not connect after many replugs (the log says Cannot set device address): restart the Pi. A fix is planned.

• Wi-Fi is off in the SD card package (see the install page to turn it on); Ethernet has no DHCP client (fixed 169.254.61.60, or ip=).

• The web page has no password.

• Only the Pi 4B is supported. The Pi 5, Pi 3 and Pi 400 are untested.

Remote pages

• A remote page catches only the keys and knobs it uses; PLAY, STOP and RECORD always reach the Rytm. The status pages catch every knob. With a Sidecar firmware older than the key masks, every key except PLAY, STOP and RECORD goes to the Sidecar.

Teensy: user machine space

• The 32 KB plugin code space fits only one of the large NoisePlethora packages (NP VOICES, NP CLUST1, NP CLUST2) at a time; a second shows !ROOM. Use the new, smaller NoisePlethora packages instead (prime, fibo, phase, fm, pw, ring, noise, walk, atari): any two fit together, some three. The Pi has no such limit.

Still in testing

Results from testers are welcome:

• a cold power cycle of the Pi straight into the engine, with no computer attached;
• the Pi’s sample pool and presets by ear, CRUSH and RINGMOD, slot fingerprints in a project shared with another Sidecar.

Reporting

Use the Tester report form under Issues. It asks for the Rytm build (rui1027d / sfx1021), the Sidecar build (from BUILD-INFO), what you did and what happened. A log from the Teensy console or sidecar.local helps a lot.