ER-301/Persistence

From O|D Wiki
Jump to: navigation, search

Here we discuss the various mechanisms by which the ER-301 helps you save and recall your creations.

SD Card

The SD card slot on the front of the ER-301 is used to hold all of the data that belongs to the user such as samples and presets. There is an additional SD card slot on the back of the module but this one is reserved for system use (e.g. firmware and system settings) and does not need to be accessed by the user during regular use. See ER-301/Rear for more information.

Requirements

  • Accepts micro SD (uSD) cards.
  • Any speed class, but Class 10 (C10) and above is recommended.

Mounting and ejecting

You can remove or insert the SD card when the safe LED is lit.

The STORAGE toggle switch next to the SD card slot can be used to safely eject and mount a card.

To mount a card:

  1. Make sure the STORAGE switch is in the eject position and the safe LED is lit.
  2. Insert the card.
  3. Move the STORAGE switch from the eject position to either admin or user.

To eject a card:

  1. Move the STORAGE switch to the eject position.
  2. If no files are actively being accessed, then the safe LED will light up and it is now safe to remove the card.
  3. If files are actively being accessed, then the safe LED will NOT light up and you should NOT remove the card. A list of active files that are preventing the ejection will be displayed.


Quicksave

The quicksave screen shows 24 slots where you can store and recall the state of the ER-301.
Renaming a quicksave slot.
A renamed quicksave slot.

A quicksave stores all of the essential state of the ER-301 in one place for recalling later.

State that is stored in a quicksave: State that is NOT stored in a quicksave:
  • Channel grouping
  • OUT1-OUT4 chains and contained units (*)
  • Global chains and contained units (*)
  • 6-track recorder configuration
  • Sample pool contents (links only)
  • Mute state of OUT1-OUT4 chains
  • Admin>Settings (**)
  • Last quicksave slot loaded or saved (***)
  • Which UI context is focused
(*) For further details on how a chain's state is saved see #Chain Presets.

(**) Stored on the rear SD card along with other system data.

(***) Stored on the front SD card in the ER-301/meta/boot.lua file.

At anytime and anywhere, pressing SHIFT+M1 (silkscreened as QUICKSAVE) will bring up the (modal) quicksave screen. The last quicksave slot that was loaded or saved will be highlighted. Pressing CANCEL will allow you to leave the screen without any effect. Highlight the desired quicksave slot with the knob and/or M soft buttons. Once highlighted, the sub display shows a summary of the contents of the quicksave slot, as well as 3 commands:

  • save (S1): store the current state to the highlighted slot.
  • rename (S2): edit the name of the highlighted slot. Press CANCEL to leave the rename screen without changing the slot's name and press ENTER to set the new name of the slot.
  • load (S3): restore the contents of the highlighted slot.


Tip-bulb.png
Quicksaves as Templates
In addition to using quicksaves to save your completed patches, it is also very useful to use quicksaves to put the ER-301 into a convenient state for creating a new patch.


Tip-bulb.png
Restore last quicksave on boot?
There is a setting in Admin>Settings where you can choose to have the last accessed quicksave automatically recalled when powering up the ER-301.


Some technical details

Quicksaves are saved to a folder called ER-301/sc/quicksaves. Inside this folder, there is a folder for each slot (e.g. slot1, slot2, and so on). This slot folder contains up to 4 files (e.g. Q01.lua to Q04.lua). The most recent quicksave data saved to this slot will be Q01.lua, whereas the previous 3 saves will be in Q02.lua to Q04.lua as backups. The slot names are maintained in a file called ER-301/sc/quicksaves/names.lua.

Quicksaves (in fact all presets) are serialized as loadable Lua code which defines a table containing all of the data pertinent to the preset. Although should never be necessary, with some practice and knowledge of Lua, it is possible to edit these files by hand.

Chain Preset

When the chain header is focused a menu of chain operations is shown in the sub-display.
Pressing a chain's "Save" command will bring you to this screen where you can specify the destination file for the chain preset.
For further details on chains, see ER-301/Signal Flow#Chains.

Chains of units are stored as chain presets for later recall. A chain preset consists of:

  • a list of unit presets (one for each unit in the chain)
  • the source assignment (if applicable)
  • the location of the focus cursor

You can create a chain preset from any chain by focusing the chain's header to get access to its header menu and pressing Save (S3). To load a chain preset into a given chain, again focus the chain's header but this time press Load (S2) and select a chain preset file via the file browser screen. The current contents of the chain will be replaced by the units contained within the chain preset.

Volatile.png
Currently chain presets are saved in files with a *.lua extension. Soon this will change to a more recognizable extension of *.cha.


Some technical details

Chain presets are saved to a folder called ER-301/<version>/presets/chains by default but you can save them anywhere you like. A chain's Load and Save commands will open by default to this folder so it might be easier to keep your chain presets there.

Unit Preset

The preset load/save commands are located in a unit's extended menu, accessed by focusing the unit's header.
Pressing "Save Preset" will bring you to this screen where you can specify the destination file for the unit preset.
For further details on units, see ER-301/Signal Flow#Units.

The complete state of an individual unit can be stored in and recalled from a unit preset. A unit preset will persist the following items:

  • the values of all parameters
  • fine vs coarse setting of each parameter
  • sub-chains of parameters that have them
  • the name of the unit (if renamed)
  • bypassed or not

You can create a unit preset from any unit by pressing the M soft button beneath its header (i.e. focusing the header) to reveal the "Save Preset" command (among other commands). Pressing the M soft button underneath "Save Preset" command will open a file saving screen where you can choose an existing file (to overwrite) or create a new file. Later you can load this preset into an existing unit (of the same type) by using the "Load Preset" command.


Pitfall.png
Often (especially beginner) users will try to load a unit preset using a chain's load command which is meant for chain presets and thus will fail. In future firmware, I will try to redesign the UI to make this less of a problem but in the meantime please be careful to use an existing unit of the same type to load a unit preset.


Some technical details

The default path for a unit preset is ER-301/<version>/presets/units/<unit-type> where <unit-type> is replaced with the filename-friendly version of the unit's type. So for example, a Sample Player unit will have the default preset path of ER-301/<version>/presets/units/sample-player.

Volatile.png
Currently unit presets are saved in files with a *.lua extension. Soon this will change to a more recognizable extension of *.uni.



Global Chains Preset

You can save and later recall all of your global chains using global chain presets. Simply, focus the global chain header to reveal the "Load Chains" (S2) and "Save Chains" (S3) commands.

Tip-bulb.png
To load individual chains into the global chain area, just create a chain of the desired type (mono vs stereo) and then use its "Load" command to populate it via a chain preset.



6-track Recorder Preset