Saving State

Your App / applet state will not be remembered between power cycles unless you:

  • (A) Manually save to EEPROM (Long-press RIGHT encoder to escape to main menu, long-press RIGHT again to save)
  • (B) Store the current state of Hemisphere to a preset
  • (C) Turn on Auto Save

To Save/Load presets or toggle Auto Saving in Hemisphere, long-press the DOWN button to open the config menu, and (if necessary) rotate the LEFT encoder to paginate to the floating preset menu.

When storing a Preset, it immediately triggers an EEPROM Save (with a potential 2ms interruption, fyi) so there is no need to also long-press-save on the main menu.

EEPROM Save

All of the Apps included in your firmware build have Config Settings that can change at runtime. You can make them persist after a power cycle with the built-in Ornament and Crime storage system:

  • Return to the main menu by long-pressing the right encoder.
  • Then, long-press the right encoder again.

This will save the state of all applications in the module, as well as the active App and various Global Settings (user scales, waveforms, sequence patterns, turing machines, etc).

Teensy 4.0 & 4.1

Several Apps have been updated to store settings in binary files on T4 hardware instead of using emulated EEPROM. This includes: Hemispheres/Quadrants, Scenery, Calibr8or, Captain MIDI.

Settings are typically saved when you store a Preset, which happens automatically in some cases. Global settings like custom Scales and Vector Waveforms are stored in a separate config file, only when you invoke it with a R-Enc-Long-Press on the Main Menu.

Newer Teensy’s have enough space in flash storage to accomodate a filesystem (aka LittleFS or LFS). Teensy 4.1 also has a microSD card slot; you could theoretically add one to a Teensy 4.0 as well. This allows significantly more storage, and will also makes it easier to backup/restore/transfer settings by simply copying files. (Files on the internal LFS storage will become more accessible when USB MTP Disk support is stable.)

The binary file format used by Phazerville Apps (PhzConfig) has a small header with a signature & checksum, followed by a simple KEY-VALUE hashmap using 16-bit KEYs and 64-bit VALUEs. External editors are a possibility.