Preset sorting, EQ params

[madejm]

Preset sorting

I would like to implement a custom preset sorting list, to change the order without using the editor app. Ideally that would be available both on web config and 4.3 UI.

Lets take an example of having 4 dedicated preset footswitches, by default they would trigger presets 1, 2, 3 and 4, but I'd want to have preset 13 under FS number 4 so that I don't have to scroll through the banks while playing.

I think that would need to start with requesting details of all 20 presets to get their names, or can we get that with a single request? Then tConfigData could store the custom order like uint32_t PresetMap[20]; and it would be modified by UI and Web Config.

What do you think about that?

4.3 EQ controls

I find that Treble/Mid/Bass Freq would be very useful to have on 4.3 UI, along with their appropriate values displayed (with db/Hz).

However I noticed that the UI project already uses 145 of 150 available widgets for the personal plan in Squareline Studio. Would it be possible to separate the screen into separate projects so that the limit applies to a single screen?

[Builty]

Hi. I have had some other requests for something similar to the first part. To be able to change the mapping so that e.g. Midi control change 1 loads preset 11. This could help with that request also.
Getting details of all 20 presets requires sending a command 20 times, with the preset number changing each time. I am doing this once on startup for the current preset, so the code is there, but it would need something like a state machine to allow it request the next one after the previous one is done, and stop after 20.

The 150 widget limit is a pain. I've hit it multiple times and had to restructure things to save them.
I'm not sure about having multiple projects. Its certainly worth a look. I'd guess Squareline projects would need to have different destination folders to avoid overwriting, and then the CmakeLists including both sets.
It might need some different handling for launching the settings screen. The cog icon does this screen load, but if different projects then that might need to be changed to a function call in app code, that then calls lvgl to load the settings screen.

The settings screens are a bit tight on space to fit 3 more items. That could be worked around though.

[madejm]

Maybe migrating the UI to EEZ Studio would be a good idea? It's free and open source.

When I find some time, I'll try to fetch the 20 preset details and POC the preset mapping for Web Control.

[Builty]

I will have a look at EEZ studio, but another option for the 150 widget limit would be to change the settings screen away from a tab view, and use a single panel along with buttons to replace the tab headings. The panel would have maybe 6 or 8 toggles/sliders/labels/listviews, that could be dynamically configured in code.
E.g. when the EQ page is to be requested, hide the toggles and enable sliders for each quantity and set the labels.
When the Reverb page is requested, enable power/pre post toggles, a list item for the model, and the needed sliders.

I'm doing similar already for parts of the modulation page as the number of sliders and there function depends on the modulation model.

Doing this I would estimate to save 50 - 70 widgets.

[madejm]

Good idea, although the code will be a bit more complicated. Are you going to refactor this? And if so, could you add text vales to sliders?

I already have a raw implementation of custom preset order mapping for footswitches that is configured by Web Control. I also mapped the preset colors from pedal state data to match the colors in Tonex Editor App.

Design assumptions I'm considering for best user experience:

• Preset order on Web dropdown should be left intact so it's consistent with changing presets with the knob on the pedal.
• Display UI should always show a number of the footswitch in the preset name (so if preset 1 is mapped to footswitch 3, then display will show "3: PRESET NAME").
• Next/previous footswitches and Display UI arrows have to follow the mapped order.

Implementing the custom order setting on Display UI would probably need a lot of new widgets.

[Builty]

I will look into the UI refactor. Yep text values, and also units.

I am of the opinion that complex UI configuration stuff should be in web editor only.

[Builty]

This is what I am thinking about.
A panel instead of tabs (but tab header exist for visuals/buttons)
4 switches, 1 select, and 7 sliders max.
Inside a flex layout so the child positions are automatically set.
Then enable the groups needed and configure the labels and values in code.

59 spare widgets available.

[Builty]

I have this coded now, but still working though various bugs.
I've added EQ frequency sliders.
Added an EQ icon to the main screen that can be long pressed to jump to the EQ screen.
Got rid of the green tick to save room, and added Exit to the tab row.
Added parameter units to the label on the left.
The value to the right updates as the slider is dragged,

I hope to get it debugged and committed in the next day or 2.

[madejm]

Great, I also downloaded some amp and pedal skin images from Tone Net website. They have better resolution, current images are a little blurry. I also added two more amps and replaced some with a bit more distinctive amps (I think there are too many black amps that are similar to each other).
I'll make a PR with the changes later.

[madejm]

I have finished custom preset order, PR is ready. I tested it on Zero board, and 4.3B with external footswitches. Please test it yourself before merging!

[Builty]

Merged and it looks wonderful. Only thing, I might add text to the UI to show "Syncing" when its getting all of the preset names. Similar to the Tonex software. Just so people understand why its a few seconds slower than it used to be.

[madejm]

That's a great idea!

[Builty]

With the new 4.3B settings UI, unfortunately it didn't go well. Ran into a lot of issues with trying to jump to a specific tab from the effect icons. Often crashing due to the components not being created yet, or updates happening late after the screen has loaded, which looks terrible.
Plenty of other weird bugs also. Blew 20+ hours on it.

I've decided to reverse it all out and go back to the original scheme, and just add EQ icon on main screen. I'll need to come up with something else. Will look more closely at EEZ studio.
There is room and widgets for EQ frequencies, but that is not addressing the issue propely as there would be none left,

[madejm]

That's unfortunate. I hope migration to EZZ studio will cause less troubles!

[madejm]

I have found some minor issues with the Display components. I'll push a fix tomorrow.

The bottom buttons look a bit blurry too. Do you have the source PSD files for those so I could export them in better quality?

[Builty]

Here's the effect icons psd. They came from screen captures from the Tonex software.

effect_icons.zip

[madejm]

I have retrieved original SVGs from the TONEX app binary. I will upload a PSD with updated icons 😊

[Builty]

EEZStudio is fantastic.

[madejm]

Amazing! Are you going to migrate it all soon? I'm wondering if I should fix the bugs or wait for the migration to be done 😄

[Builty]

I'll keep working on this, but it will take some time. maybe a week.

[Builty]

EEZ studio port is taking longer than I thought. The event system is much more complicated. It looks like I need to move some event handling into the main code, which is a pain.

[madejm]

On the positive side, it looks much easier to understand what the events are doing just from the attached screenshot compared to Squareline.