Card and files

FRIZZ keeps what it saves on the SD card, in a folder FRIZZ, as text files, and plays your loops from there. Leave the card in.

File	Holds	Written
FRIZZ/frizz_scenes.txt	The 4 FX scenes	When you save, copy or delete a scene
FRIZZ/frizz_master.txt	The finalizer and its presets, and the settings page: the MIDI settings, the LEDs’ brightness, AUX mono, USB audio, and for AUX, the mic and USB each their input gain, monitoring and effects	2 s after the last change
FRIZZ/frizz_scenes.bak, frizz_master.bak	A file FRIZZ couldn’t read, or the computer’s version that FRIZZ’s own replaced (The card as a USB drive)	When FRIZZ writes its own in that file’s place: at the next save, or when it takes the card back
FRIZZ/frizz_scenes.tmp, frizz_master.tmp	A save on its way, renamed into place when it’s whole	During a save; one a power cut left is finished at power-on
FRIZZ/bug-1.txt, bug-2.txt …	Bug reports	When you ask for one
FRIZZ/a1.wav … h15.wav	Your loops	Only by the Companion, as it uploads, moves or deletes them
FRIZZ/xfer.tmp	A Companion upload under way, renamed to its slot when it’s whole	During an upload; one left over is deleted at power-on
FRIZZ/a1-b2.swp and the like	A Companion swap under way	During a swap; one cut short is put right when FRIZZ next looks for the loops
TAPE/cubbi_a1.wav … cubbi_e15.wav (or in the card’s root)	TAPE’s recordings, on the Cubbi page	Never: FRIZZ only reads them

Scenes and settings on the card

The scenes live in FRIZZ/frizz_scenes.txt on the card, one line per effect, keyed by its name. FRIZZ creates the folder on its first start; after that the scene file is written only when you save, copy or delete, never on a recall. Saving takes a moment in which the LEDs may pause. A scene file FRIZZ can’t read (from another version, or edited into something else) starts it with no scenes but isn’t lost: the first save moves it to frizz_scenes.bak.

If FRIZZ couldn’t read the card at power-on, every save flashes red until you switch off and on again, so the scenes on the card aren’t replaced by the session’s.

frizz_master.txt holds one setting per line, which can be edited on a computer too:

Line	Setting	Values
midi_channel	The global MIDI channel	1-16, 0 every channel
midi_block_trs	Effect channels over TRS	1 on, 0 off
midi_transport	MIDI transport following	1 on, 0 off
clock_factor	Clock factor	100 as sent, 200 double, 50 half
clock_source	Clock source	0 Auto, 1 TRS, 2 USB, 3 internal
midi_out	MIDI out	0 off, 1 TRS, 2 TRS and USB
midi_feedback	MIDI feedback	1 on, 0 off
led_brightness	LED brightness	25-100
mono	Mono input	1 mono, 0 stereo
gain_aux, gain_mic, gain_usb	Each source’s input gain (VOLUME knob)	0-100
aux_dry, mic_dry, usb_dry	Each source’s effects (Input: AUX, the mic or USB)	0 through them, 1 past them
aux_live, mic_live, usb_live	Each source’s monitoring	1 on, 0 off
usb_audio	USB audio	1 on, 0 off
finalizer	The finalizer’s knobs, Level’s four, EQ’s three, Comp’s four, Width’s three	0-1000000 each
finalizer_preset1 … 4	Its presets, each as finalizer, only those stored

A line FRIZZ doesn’t know is skipped, a setting left out or out of its range keeps its default, and a word where a number belongs makes the whole file unreadable: FRIZZ then starts with every setting at its default and keeps the file as frizz_master.bak. Edit the files with the card taken out, in the launcher’s USB storage mode, or on the card lent as a USB drive, which FRIZZ reads again when it takes the card back.

The card as a USB drive

To get files on or off the card (loops, scenes, bug reports) while FRIZZ runs, lend it to the computer: on the settings page, with a computer on USB, hold SHIFT + LOOP for 2 s. LOOP lights blue there while the card is lent, and the computer finds the drive “FrizZ card” with the card on it (the drive is there all the time, empty while the card isn’t lent). The loop and the effects play on meanwhile.

• To take it back: eject the drive on the computer, unplug the cable, or hold SHIFT + LOOP for 2 s again on the settings page; a computer going to sleep takes it back too, and so does a restart over MIDI (the launcher’s), before FRIZZ restarts. FRIZZ then looks for the loops again (the Loops page shows what’s there now).
• Scenes and settings edited on the computer come in: taken back, FRIZZ reads frizz_scenes.txt and frizz_master.txt again if the computer changed them, as at power-on (Scenes and settings on the card). A file the computer left as it was changes nothing.
  • The settings apply at once. The input gains and the finalizer’s knobs glide there as when you turn them, and usb_audio switched takes FRIZZ off USB and back on as the settings page does. What MIDI set without the card (an input gain by CC, say) goes to the file’s value, as after a restart.
  • The scenes come in for their next recall: what plays stays as it is. If the scene that plays changed, its key pulses as edited, as after you turn a knob; if the computer deleted it, what plays stays and no scene key is lit for it, as after a delete.
• If you changed them on FRIZZ meanwhile, FRIZZ’s wins, file by file: a scene saved, copied or deleted while the card was lent, or a setting changed (or still in its 2 s before it’s saved) when you take the card back. FRIZZ then writes its own over the computer’s, and keeps the computer’s as frizz_scenes.bak or frizz_master.bak.
• A file the computer left unreadable changes nothing in FRIZZ: it writes its own at once and keeps the computer’s as the .bak. One the computer deleted changes nothing either, and FRIZZ’s next save writes it again.
• While it’s lent, FRIZZ leaves the card alone: saving a scene or a setting waits until it’s back, a loop can’t be loaded from it, a bug report can’t be written, and a Companion upload running stops: the page waits and sends that loop again from its start once the card is back. A loop from the card you played just before is usually still in memory and switches at once; one that has to be loaded waits until the card is back. Only the settings page shows it (LOOP blue); on the play page FRIZZ plays as always.
• Refused (LOOP blinks red 3 times): without a computer on USB, while LOOP records, while a loop loads or FRIZZ looks for the loops (a few seconds after power-on, and after the card comes back), or while FRIZZ writes the card.

Eject the drive on the computer before you take the card back by the gesture, as you would any drive, so the computer has written everything.

Taking the card out

Take the card out or swap it only while the CHOMPI is off: a card pulled while FRIZZ runs isn’t looked after. To get files on or off it (loops, scenes, bug reports), lend it to the computer as a USB drive, or use the multi-firmware launcher’s USB storage mode, instead of taking it out. On a card with several firmwares, FRIZZ keeps its FRIZZ folder apart from the others’ files.

Files from an older FRIZZ

FRIZZ reads the scene and settings files of earlier versions and carries their values over to where the knobs and keys are now; the changelog says what changed with each version.