The 5.0.0 is on beta. Documentation is updated. Unfortunately, I am still looking at the Windows issue. It seems to be happening with 4.1.4 too, always on heave SysEx traffic. (the firmware update is such an activity). that is way it leave Chrome frozen.
1 Like
Old or new midi stack? If new, might make sense to contact Pete at Microsoft thru the windows midi github
Yes. If it’s a Windows MIDI thing then Pete Brown is the go to person. And he really wants to work with developers to make their devices work. I could not connect to my E1 at all today because of Chrome and Edge freezing up. Windows reports the E1 as a MIDI device but the web app says it isn’t responding.
I just emailed Pete. Let’s see if he has any pointers.
1 Like
Will the presets you mention above (LFO, MIDI monitor etc) be bundled with the official 5.0 release or are they available in the beta?
Good luck. His Windows MIDI/Audio Discord server is another place folks ask him questions. He seems to be on that all the time. The web MIDI bug almost seems like it is a race. It doesn’t work for several times in a row and then it does work.
Pete provided very good pointers where to look at. Unfortunately, the issue is in the recent releases of Chromium based browsers. There are two problems that can freeze the browser:
- pulling USB cable out mid-session. This also affects the firmware update procedure, the final reboot is basically identical to pulling the USB cable out.
- heavy sysex traffic
I am finalizing a few corrections to the beta website to guide users through those potential issues. This updated version will be deployed to beta.electra.one later today for a final check.
Pete has agreed to test the E1 for us. We are shipping an E1 Mini to him today. I am really grateful to him for helping us out!
4 Likes
An updated version of the editor has just been released. The editor now adjusts its functionality to match the feature set of the connected controller’s firmware (4.1.4 or 3.5.4).
For now, firmware 5.0.0 is not offered yet. I will make it available once I can see that there are no major issues with the editor.
1 Like
@martin One trick that seems to be working for me now is to make sure the E1 is not connected to the computer when Windows loads. I then open Chrome and then connect the E1 and then open the webapp (not sure if that last order matters - haven’t tested). Anyway, doing this, the last few times the E1 has successfully communicated with the webapp without any problems. Unless you have changed something at your end.
1 Like
I made a few changes to prevent the lock up. I will test the sequence of steps you described. thanks! Regarding the restart/unplug - if you close tabs with the MIDI sessions prior to restarting/unplugging, the browser will survive that
whenever the browser freezes, ending the task in the Task manager is the way to go.
When I try to edit my preset it says it will be upgraded to version 3 and will only run on firmware 5.0.0
How do I edit it and still have it work on my firmware 4 device?
hmm, you controller is 4.1.4 I assume…
please check the preset compatibility settings:
There should can select if the compatibility follows connected controller(s) or if it is overridden with custom settings.
What option do you have selected there?
thanks. I will review it now. If you set the compatibility to 4.0.0, does it resolve the issue (when saving the preset)?
Setting it 4.0.0 - 4.1.4 solves the issue. I can drag a slider to the preset without getting a warning.
1 Like