Did you try mod-ui hotfix-1.13 branch? I think each firmware uses the same number hotfix for mod-ui and mod-host. Mod-desktop probably uses master branch.
But then some new functionalities like drag&drop plugins are lost…. Perhaps it could be better plugin-store branch?
Andrea, you’re right, the latest official release we can download has that layout.
But I’m sure that the one that was fetched OTG was different: the ability to visualize beta plugin was a filter similar to “Ïnstalled only” and was something like “Include beta plugins”.
Hey @AndreaDelSignore, from where did you install the image? From the one available in the wiki?
On the official image, which is called “show beta plugins”.
If you installed the image from the wiki and that stayed like that, it may be something else and I would suggest that you do a factory reset (with all the security backups) and see if that goes back to beta.
Anyway, I guess that with that image, the plugins that appear with the Labs switched on, are exactly the beta plugins…if I’m not wrong.
Hi @AndreaDelSignore, I found another minor bug that I managed to confirm and it happens only with your image (not on the official one).
It is related to the System Upgrade. With your Starless version, the device keeps stuck on the “Starting Upgrade. Please Wait” screen when you do it either from the Device Settings menu or from the WebGUI settings.
The only way that I managed to do it was by booting the device while holding footswitch A + the left-most button.
You’re welcome
I was thinking a bit about that yesterday. It may be related to the fact that you should not receive notifications on the WebGUI for a new (official) MOD OS release.
But I would say the “no notifications” can make some sense.
yesterday I found the reason and it’s something totally unrelated to the mod-ui o dwarf-controller modifications.
It’s the way I unpacked and packed the tar file after applying my work.
I don’t use the -p parameter in the tar command, so executables with the “sticky” bit set (like /sbin/reboot) can only be used by root, instead the hmi program is logged on the system serial port with the hmi user so it can’t reboot the system in order to start the update process.
I patched my script and I’ve done some successful tests, I also fixed the bug signaled by @Abotte so this weekend I planned another beta release (hopefully the last one).
Alongside store support, the next release will include a small but useful new feature: A/B comparison during pedalboard parameter tweaking.
How It Works
Suppose you want to adjust some parameters on a pedalboard and quickly compare your changes with the previous state.
In this version, when you load a pedalboard, you’ll notice a new A/B Compare section in the upper-right corner of the interface.
This section contains three buttons:
A – Switch to the A parameter slot
Take – Capture the current state and store it in both the A and B slots
At first, all controls are disabled except for the Take button (represented by a “photo” icon).
When you click the Take button, all plugin parameters are stored in both the A and B slots — essentially creating two in-memory snapshots.
After this initial capture, A and B are identical, and the Dwarf automatically switches to the B slot.
You can move back and forth, editing each slot independently and switching quickly between them to hear the differences.
Each time you switch slots, the current state is automatically saved to the corresponding A or B slot.
Once you’re satisfied, you can save the current state to the pedalboard or as a snapshot, just like usual.