Loopstyler patches explained

The patch files are stored on SD card, in "patches" directory. You can edit them as you wish (don't forget to make a backup :)

Implementing a complete in-device mechanism to edit, store and duplicate patches is on my TODO list. In the meantime you can edit the patches manually as text files, rearrange them by renaming the files, or create a new patch by copying one file to another and then editing it. Filenames must adhere to the existing format, so the Loopstyler can find them: patch[N].json.txt (all lowercase). The N can be one, two or three digits; valid patch numbers are 1 to 999.

There are two ways to access the SD card: either by removing it from the device or by connecting Loopstyler to a PC (the SD card will appear as a new disk drive). Never remove or insert the SD card while the unit is powered on. Please observe precautions about powering on or off as mentioned here.

When modifying a patch, the Loopstyler software might need to be restarted - depending on whether this patch was already loaded during the session - as then a cached version of the file might keep being used. To restart, power the unit off and wait until the red LED light stops glowing, slowly count to 5 in order to not stress the electronics, and then power it on again (in the next firmware update there will be a command to reload patches without restart).

Patch validator

Here is a simple validator for checking patches, to make sure they will work in the Loopstyler. This may be faster than testing them in the device. If there is an error, you can get a detailed message to help you locate it.

Patch file format

Patches use JSON as their file format, with additional ".txt" extension for convenience (so they can be easily opened in any text editor). The JSON syntax is less strict than required by the JSON standard, for example you can completely omit double quotes from non-numerical keys and values. Also it can tolerate comments of various styles: inline comments beginning with # or // and multi-line comments wrapped between /* and */.

Let's take patch1.json.txt as an example (you can right click on the link and open the file in another tab).

Following parameters and sections can currently be present in file (this will be expanded over time):

Each "regions" block (unless configured as "one_sample_per_pad") can use following parameters: