have you updated your bootloader? Minis are shipped with the new bootloader.
Please check the messages above - you are prolly facing the same issue as @v.rtx_void. ie. older version of the bootloader.
have you updated your bootloader? Minis are shipped with the new bootloader.
Please check the messages above - you are prolly facing the same issue as @v.rtx_void. ie. older version of the bootloader.
So I’m trying to update like I’m guided via the web app. I’m starting here and because I guess I don’t have the latest bootlader (it’s 1.0), I’m following that link as in the description:
That leads here: Firmware update Electra One mkII | Electra One Documentation
Following the info there leads to exactly what I’m describing here: Firmware v4.1.4 for mk2/mini - #20 by Mint-Gecko
Note: at no point in time does that document describe how to update the bootloader. It exclusively writes about updating the firmware. What am I missing? @v.rtx_void didn’t say how to update the bootloader so I’m not sure what to do.
EDIT: found it as well. The web app should state that updating the firmware without updating the bootloader does not work. The sentence “If you have not updated your bootloader or if you want to update the firmware using the Bootlader Disk mode” was true for my situation, so I pressed the first yellow button which explains how to update the firmware (in that context, implying that the bootloader would get updated automatically).
It would be better to clearly separate this. First, check if the bootloader is up-to-date and if not, go to Bootloader | Electra One Documentation (which ultimately leads to Electra One App). If that is at v1.1, either update the firmware using the online updater or using the disk mode.
I will do that. The situation is a bit more complicated though. The v1.1 update of the bootloader brought number of improvements and bug fixes. One of the issues of the original bootloader has become more exposed with the v4.1.4 firmware release. Still, only a fraction of users was actually affected. It took me quite some time to realize that. I will adjust the wording on the web so that it does not sound like that the bootloader update is totally optional.
am i being dumb? I need to update my bootloader. I go here:Electra One App but then i get error “In order to perform the bootloader update, you need to be logged in and the controller must be connected to the USB port.” - i have disconnected from MIO XL and plugged directly into USB , device is detected and i am logged on.
Not to worry, I resolved the issue by manually updating as per this thread : Disk mode and web based updates failing from 4.0.0 on mkII with Bootloader 1.0 [Solved] - #2 by 0xd
Hi, do you open the bootloader update in the Chrome (or other webmidi enabled) browser? The update is performed using the MIDI communication, not all browsers support that.
Chrome. Version 147.0.7727.138 (Official Build) (arm64)
I was making a preset and trying to add start and stop messages but neither are listed not is tune request in the message type dropdown for any of the control types. Is this a problem unique to my app or device or is this a problem in the web app.
Start / Stop / Tune will show up for momentary pads only - due to their nature. The type of the control and its mode affect selection of MIDI message types.
Since this is now a unified fw for both the E1MkII and the Mini, we want those sexy dials or the MkII even more than we wanted them before! )
And (out of curiosity) are there any plans to port the 4-slider controls from the Mini to the big one?