Close the detail view when uploading a new preset to prevent the system from freezing. @zenmonkey@HDV
Improved handling of value ranges for Dial controls. In some configurations, the value indicator was not shown at all. @egotape
Added an extra handler that is called when a Lua script encounters a fatal error. A debug message and stack trace are printed to the logger.
Fixed a memory leak in the controls.get() function. Subsequent get() calls for the same controlId did not use the cached reference; instead, a new one was always created.
Fixed Preset bank colours. RGB888 format was not correctly translated to RGB565. @egotape@RWilco21
Mk2 Improved the sensitivity of the on-screen page buttons at the top of the screen. At least I tried. The buttons now have larger “touch” area. It works fine on my controllers.@NewIgnis@Mravitz and bunch of others.
Mk2 Improved the sensitivity of the on-screen page buttons at the top of the screen. At least I tried. The buttons now have larger “touch” area. It works fine on my controllers.@NewIgnis@Mravitz and bunch of others.
I tested it, it’s an improvement. The more pages there are (typically 7 or above ) though, the harder it becomes to have it react at first touch. What is the trick to it ? I feel that I should put my finger first slightly above the screen and then enlarge the pressed surface down, and keep pressing for half a second.
Is that the way to do it?
It’s been a while since I was active here so trying to learn about all the new stuff. But, I can’t get the Dial to show up on my MKII with v4.1.4. It gets defaulted to a classic fader instead. The JSON does say “dial” for the control…
Ah, ok. Thanks. So that’s intentional. I couldn’t find anything about it in the documentation or changelog, and it’s also available in the app editor even when using the “Electra One Mk2 6x6” mode. It would be great if it was hidden in that case.
I believe the reason not to have it hidden is to make it easier to move a preset from Mk2 tot Mini and vice versa. In such a case it makes sense to have a fader that appears as a dial when shown on a Mini. At least, that’s my assumption.
Hm.. . well, that seems weird to me. A control type that’s not available in a specific hardware configuration shouldn’t probably be available in it’s software counterpart. That just confuses the user during learning and bloats the UI during development. It’s also hidden information. I mean, right now the editor is lying to me displaying a dial but showing it as a fader on my Mk2. Well, well, thanks anyway. Have to write some more LUA functions now.
I know It is kind of work-in-progress. I wanted to simply hide the dials at first, but because they could still be dragged-dropped from other layouts and copy-pasted I decided to render them as faders in the firmware. Doing it properly in the editor needs more careful approach. The dials - when used in current mk2 grid - are simply too small to be of any practical use. Updates that will improve things are on the way.
I was wondering if the multi-knob control might be available on the mk2 at some point?
Also, a wishlist feature for XY pads - could they work without having to open them fully? Ie, just move a finger on the small instance and have them work as XY pads? Presently only 1 axis works that way.
If you can’t start to the normal mode, open the bootloader, enable the Disk mode and remove all files from the /boot folder. And try to restart the controller. Let me know if it helped.
thanks for the quick reply @martin !
is the bootloader not part of the FW 4.1.2? Last time I have updated it only worked by ejecting the SD card, deleting all files in the “boot” folder, manually downloading the 4.1.2 FW to the same folder and updating manually. This time neither this, nor the web update works for 4.1.4
What also confuses my that USB Disk mode always crashes my Windows explorer, both on my laptop and my desktop PC
ok, it is the source of the problem. In order to update the bootloader, the firmware (4+) must be running. If I understand you correctly, you cannot get the standard firmware running now. Do I read it correct?
While I could successfully update the mini to v4.1.4, both of my mk2s fail to update. It doesn’t matter if I try updating via the web updater or the file updater, the result is always the same: after the firmware file has been placed on the SD card and the device starts to install the new firmware, the progress bar draws a single pixel row at the beginning and then never progresses beyond that within 20 minutes. Any idea?
It is kind of work-in-progress. I wanted to simply hide the dials at first, but because they could still be dragged-dropped from other layouts and copy-pasted I decided to render them as faders in the firmware. Doing it properly in the editor needs more careful approach. The dials - when used in current mk2 grid - are simply too small to be of any practical use. Updates that will improve things are on the way.
