Bug reports
From v0.11. SHIFT + press the transport knob 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 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.
- 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.