Skip to content
FRIZZ

Power, battery and bug reports

Power and battery

Section titled “Power and battery”
  • Low battery: unplugged with the battery nearly empty (below 3 V), the knob, transport, CHOMPI, PLAY and LOOP LEDs flash yellow for 15 s and VOLUME’s red, on any page, then the CHOMPI switches itself off. Plugging in power during those 15 s stops it. On a charger too weak to run it with a low battery, it goes dark until it has charged.
  • Battery check: the settings page shows the battery’s level on VOLUME’s LED.
  • Shipping mode: hold CHOMPI, PLAY and LOOP while switching on: the battery is disconnected until the CHOMPI is plugged into power again. Use it to store it for weeks.
  • Hardware test: FRIZZ has no self-test of its own. To check keys, knobs and LEDs, put the stock TAPE or WAVE firmware on a card and hold VOLUME while switching on.

Bug reports

Section titled “Bug reports”

On the settings page (mode switch up), hold SHIFT and press and hold the VOLUME knob for 2 seconds: FRIZZ writes everything you did since switching on to the card, as /FRIZZ/bug-1.txt (the next one bug-2.txt, and so on): every key, knob detent and mode-switch flip with its time, the MIDI clock’s tempo, every MIDI message FRIZZ acted on, and the scenes and compressor the card held at power-on. Do it right after something went wrong (flip the switch up, hold, flip it back down) and send the file with your report: FRIZZ’s developers play it on a virtual CHOMPI on their computer, which then does what yours did, key for key.

  • It’s on the settings page so it can’t be written by accident while playing.
  • While it’s written, both transport LEDs blink white; then they blink 3 times, white when it’s on the card, red when it isn’t (no card, or a full one). A long session takes a moment, and the keys answer late until it’s done; the sound plays on.
  • It doesn’t hold the audio you played in, so a problem that depends on the sound itself needs a description too, nor scenes sent over MIDI. Dense MIDI automation fills it faster: each controller message is an event. It holds about 260,000 events, hours of playing; a session longer than that is cut off at the end.
  • It doesn’t send anything anywhere and costs nothing while you play.