Thank you so much for this! Will check it out over the weekend.
You mentioned some performance improvements in our other message history - just wondering in what area that was since I’m not seeing it mentioned here in the list?
1 Like
Bootloader took 8 minutes to complete. That’s expected I guess.
Then a message both on E1 and browser appeared:
- E1: “UPDATING FIRMWARE”, with an empty progress bar above that did not move
- Browser: “Please wait for the update to be applied” with a progress bar that is already on 100%
→ There should be a message asking the user to restart the controller. Then the progress bar on the E1 started moving.
" Do not cycle the list items when using the knobs. The lists work as they did prior to 4.0.0. @jhh @NewIgnis @Electrolove"
→ is ok now using the Default variant
" * Move on-screen page selector to the top of the screen. It was at the bottom of the screen in 4.0.0. A few users mentioned that it would be better to have it at the top of the screen. @Electrolove"
→ It still hides the text on the lowest line, which is annoying, because presets use ‘settext’ for context. Suggestion: The page selector can stay on top, but it should cover the monitor line (the one from ‘USB DEVICE’ onwards to ‘MIDI 2 IN’), so the controls should not or only slightly drop, keeping the lowest settext line on screen.
I’ll do some more tests later on.
1 Like
I forgot to mention that in the release notes. There have been optimizations made, I was not, however, be able to verify the impact on your reaper plugin. Please test that out if you can. Thanks!
Will do (about to wrap up a new clap plugin). I’m interested in the specific area you improved the performance (text rendering, a certain type of control, …?).
I have further improved the way that E1 aggregates several changes applied to one component to single repaint between the frame switch.
1 Like
Some further tests. Sorry, but testing will be a bit scattered.
Could it be the surface for page selection at the top of the screen got a smaller surface? It’s more difficult to make it instantly react to finger touch.
The midi.sendNrpn works well now . superb!
1 Like
The 4.0.0 brought a new Performance page, macro controls and data pipes that can be used to send data between presets running on the controller. Version 4.0.2 adds a simple editor to allows to:
- add preset controls to the performance page directly on the controller
- add macros to set value or modulate up to 4 preset controls with one knob (limit of 4 is imposed by the current editor UI, Electra manages up to 16 controls in one macro)
- macros to receive “modulation data” from other presets
all much inspired by work done by @NewIgnis . It is very early beta I will be happy for any feedback.
a sneak preview:
The idea is that scripting-savvy users can create presets to modulate, transform, and generate MIDI data for preset controls. Other users can then take advantage of these presets with just a few clicks in their own presets.
How does it work.. The “LFO” preset creates a named data pipe, something similar to a MIDI channel. The data pipes use text names instead of a number 1 .. 16. Once the data pipe exists, the preset can write numbers (signed floats) to it. If such preset is pinned, it will stay running even if user switches to another preset. Users can use performance page of their presets to see all data pipes currently active on the controller and use them to modulate preset controls.
More details to follow…
5 Likes
Bootloader is taking more than 8 minutes to complete over here. It’s showing “UPDATING FIRMWARE” now for about 15 minutes. Will wait and see …
that is not ok - The “updating firmware” should not take longer than 2 minutes.
The transfer can take longer if the browser window does not have the focus. Without the focus, things slow down. I need to take a look at it.
Yes, I noticed that on my MacBook.
Came back from a walk at the beach - still “UPDATING FIRMWARE”. What should I do now - restart the E1 and then redo all update steps?
Open the current bootloader and enable the USB disk mode. Check if there is an update.srec file in the /boot folder. If it is there, remove it and try to repeat the update process via the browser.
Yes, that file is there with checksum SHA256 `87F9B8355885A8F41083F46517097E5BED0CAEB1F0E7389E18DA1CE101F181BC`.
Just deleted it and redid the whole process but it seems to be happening again.
Electra uses MD5 checksum, it should be ‘c4467056097271d7151de243d4325a37’.
What would be interesting to see is what your JavaScript console is saying when you are transferring the data from the computer to the controller.
Can you take a look? Chrome > View > Developer > JavaScript Console
Any errors or warnings there? It should report every transferred data chunk there.
No errors in Chrome’s Java Script console, but after restarting the device, the update went through successfully.
ok, I see. So it looks like that everything goes ok but the final restart that will apply the update. That restart is triggered with a sysex message sent to the controller. I will try to investigate it a little bit. I think @NewIgnis run into the similar thing.
Just to make sure: you have updated your bootloader before trying to update the firmware?
1 Like
Yes, both of my devices were on v4.0.0
1 Like
There’s a font rendering issue with BITE (see white pixels below the I char, that’s not dust):
Also, similar issue rendering post (see white pixels right of the t char):
Thank you, initial tests suggest that this is working as expected! Will take some more days to update my plugin to this and to compare the performance improvements (I’m on vacation right now).
I have a strange bug in this EnvelopeMidi preset
Depending on the value of loopmode, some of the controls to the right of it should be visible or not. This is controlled through the lua function loopmode (assigned to the control of the same name). Strangely enough, it makes controls visible but doesn’t hide them. However, if I switch to the performance page and then back to the normal page, the controls that should be hidden are now hidden. I’m stymied. I’ve checked other presets (I use this trick a lot in my Live presets, but others still seem to work).
1 Like
Just a heads-up. I am fixing the issues reported here and also experimenting with some of the ideas mentioned in this thread. Another beta update is on the way.
5 Likes