FRIZZ v0.11

FRIZZ v0.11: a settings page on the mode switch, MIDI control over TRS and USB, bug reports you can send in, a steadier MIDI clock, and many fixes.

Install: delete every .bin from the card's top folder, copy FRIZZ.bin there, switch on (a slow rainbow means it's flashing). Your scenes and master settings in FRIZZ/ carry over. The mode switch now matters: down is the play page, up the settings page. If the keys don't play after updating, flip it down. The mono input moved to the settings page, and VOLUME has three pages now.

Added

• MIDI control over TRS or USB, on channel 16 (set in FRIZZ/frizz_master.txt or with
  firmware/remote.py): notes from 48 up play the keys as a keyboard, with CHOMPI, PLAY,
  LOOP and the knob presses below; CCs latch the effects (20-31), set every effect's knobs
  (70-117, in 14 bits over NRPN), the compressor, the gains, the mix and mono (52-60), turn
  the knobs relatively (14-19) and morph to a scene (61-63); program changes 0-4 are the scene
  keys. MIDI Start and Stop can play and pause the loop (off at first). See MANUAL.md, "MIDI".
• Remote control over USB: FRIZZ's SysEx presses keys, turns knobs, and answers the
  state, the LEDs, the processing load and the scenes; firmware/remote.py uses it, and plays
  the virtual CHOMPI's scenarios on the device.
• Settings page on the mode switch: up, the keys set the MIDI channel (the white keys,
  the last one switching between 15 and 16, or every channel), MIDI transport following, the mono input, a clock factor (follow a
  MIDI clock at half, as sent, or double its tempo) and the LEDs' brightness (100, 75 or
  50 %), each saved on the card; VOLUME's LED shows the battery's level throughout. The loop,
  the effects and MIDI play on while it's up; switch down to play. See MANUAL.md, "Settings page".
• Bug reports: SHIFT + press the transport knob writes what you did since switching on
  (every key, knob, the mode switch, MIDI clock and the MIDI it acted on, with the card's scenes as they were at
  power-on) to /FRIZZ/bug-1.txt (then bug-2.txt, ...). Send it with a bug report: the
  virtual CHOMPI plays it back and shows what happened. The transport LEDs blink white while
  it's written, then 3 times white when it's on the card, red when it isn't.

Changed

• The mode switch now matters: down is the play page, up the settings page. If the keys
  don't play after updating, flip it down.
• The mono input moved from VOLUME's page 3 to the settings page (F# of the lower octave), and
  the battery check from holding VOLUME to the settings page's VOLUME LED. VOLUME has three
  pages now: output, input, headphones.
• The crusher, the filter and the resonator take far less processing time while they're
  off, which leaves more room for the effects that are on.
• Turning the master compressor's knobs takes far less processing time while they glide,
  so it no longer adds to crackles on busy scenes.
• The reverb and the delay take less processing time while they play: the reverb's slow
  modulation no longer computes two cosines a sample, the delay no longer divides by the
  tempo every sample. The delay sounds the same; the reverb's modulation is within a
  thousandth of what it was.
• A flash on a key that's already lit nearly white (a select on a loud effect or on the
  compressor working hard, a tap on LOOP near the loop's end) goes dark instead of white, so
  it's seen.
• LOOP's blink while a quantized recording closes or an erase waits for the loop's end is
  slower, the same as a picked scene slot's, so it doesn't look like a refusal's 3 quick blinks.
• Switching on is a little quicker: FRIZZ clears only the part of its sample memory it
  uses (43 of 64 MB), not all of it.

Fixed

• A quantized loop is now as long as its bars to a fraction of a millisecond, so it stays with
  the MIDI clock much longer: from a DAW over USB it used to slip up to 50 ms a minute against
  it, now a few ms at most (a short loop at a fast tempo; longer loops far less). It measures
  the clock over the whole recording, up to where it closes, and averages out the ticks'
  jitter.
• Holding an FX key and tapping CHOMPI twice in a save, copy or delete mode confirmed the
  scene and dropped the latch; it now latches and doesn't confirm, as with one tap.
• The delay's pitch-up events (random knob left of centre) read from the wrong place after
  switching on, until the division knob or the tempo first changed.
• The freezer clicked when pressed again right after a release: the repeats now play on until
  the next 16th and hand over to the new capture.
• The flanger clicked when its stereo knob went back to 0, as a scene recall or morph does.
• A card FRIZZ couldn't read at power-on lost its saved scenes and master settings to the
  first save that got through. A card not read at power-on is now never written until the
  next power-on: saves flash red, and the card's files stay as they are.
• A failed write of the compressor's settings or the mono switch is tried again 3 times,
  as the manual says (it was twice, and not at all for a mono change after earlier failures).
• LEDs at full brightness no longer flicker dark: a value a hair above full wrapped to off
  (the transport's colours at full speed, the boot animation).
• Holding an FX key, then SHIFT with a control that does nothing (the transport, or a knob the
  effect doesn't use) no longer cancels the latch or a pending confirm.
• The effects' tempo from a MIDI clock whose ticks come in pairs (two at once, or a late one
  catching up just before the next, as a busy computer can send them) was off by up to 5 %
  and flapped. A pair now counts as two ticks of the right length.
• A quantized loop recorded against a MIDI clock that delivers ticks late and then catches up
  (as a busy computer can) came out up to 56 samples short for 1 bar, so it drifted up to
  26 ms a minute against the clock. The late ticks no longer count for its length: it's as
  close to its bars as with any other clock.
• A bug report that couldn't be written (the card full) left its file open on the card; it's
  now closed, so the card stays sound and the next report is written.
• A restart over MIDI (FRIZZ's own SysEx, which flash.py, card.py and remote.py send to
  get back to the multi-firmware launcher) right after a setting changed lost the setting; it
  now goes to the card first (waiting a second at most).
• The battery colour didn't follow the charging cable: it stayed green while charging and
  stayed white for 20 minutes after a full charge was unplugged. VOLUME's LED on the settings
  page is now white while the cable is in, and shows the battery within seconds of pulling it.
• A single MIDI clock tick that came a little late (a few ms, a sender's hiccup) moved the
  effects' tempo for a moment: 10 ms late at 120 BPM showed 114. A late tick and the next one
  now count together, so the tempo holds.