Presets (control pad style)

[ewowi]

[ewowi]

Inspiration:

The overall workflow for Madrix is to have a 2D rectangle (or 3D box) for your layout. This is your master layout.

There's an A and B side, in the concept of a DJ mixer. This would be segments, in WLED - except it's assumed each segment sits on the same master output, kinda like an effect layer with an optional map showing what "segment" of the output it is operating on (or the entire thing).

Each layer can have a map, but the map is a single basic rectangle or 3D box.

If I wanted the border to be red, I'd make "solid red" as my effect, full size, and then place a "solid black" layer with a map that allows the red to show thru from behind.

Then on top of that I could place GEQ on the next layer in the center of the black box, with a map that limits it to only the middle 16x16 pixels

And then that entire layout becomes my preset.

An empty preset is always defined internally as "solid black, full size"

Worth noting that there's also always a bank of hundreds of presets. By default they're all "solid black, full size" and as you click on them and change them, they show a different colour button..

You don't "save" a preset, you click on it and change it and it's automatically saved in that slot.

You save the overall project file.

Also when loading a project, you can bring in the specific sections of the project you want.

Just want the layout? Presets? MIDI mapping? Click and choose what you want to bring in during load.

It's also very fundamental that you can copy presets quickly to new preset slots, allowing you to quickly build up a show.

A playlist of presets is also available. A bit more fancy than our timed presets with a timeline interface that can also include, say, an audio file. But similar.

[ewowi]

Ideas: a set of nodes is now saved as a json file on FS (standard esp32-SvelteKit behavior of any screen). If such a set is saved as a preset it creates a subfolder called .animations_presets where . means hidden folder so it’s not (per default) shown in the file explorer. In that folder a copy of that json is made if a preset is saved. That way for each preset a file is saved in the hidden folder and upon recalling a certain preset the corresponding file is copied into the parent folder if the hidden folder.

This should also solve issues like https://discord.com/channels/473448917040758787/801531333067014164/1381237997898305566

Furthermore, if 2 or more instances (esp32 boards) belong to the same instance groep, presets of all instances are synchronized (part of super sync). This kind of resembles the left and right part of madrix (2 channels)

If I am right it’s as easy as copying files, nothing more needs to be done to implement presets as the esp32-SvelteKit event handlers will notify a file has changed and the onUpdate handler will notify what has updated and act accordingly.
Actually manual editing a file will already change things … nice!

especially where we're going with PSRAM boards and the P4 board, caching to RAM is also quite simple if you have the methods already

Color coding of the buttons:

Blue means occupied.
Gray means free.
Yellow means active.