I also just noticed that chrome is adding a media directive when the zoom is 100% or larger (maybe its related to my 4k screen too):
@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi)
1 Like
It seems adding a style override on the div.container turns off the (buggy?) monaco hc-black theme cursor css, maybe you could try that ?
1 Like
When creating presets on the web editor for the mini, my presets information is rearranged or lost when i log back in. Have to recreate everything once again. Importing the project doesnāt help either since it seems to convert it to MK2 insteadā¦
hi @Erik I will look at that now. One additional question, do you have your browser content zoomed in? I can see on the screenshot that layout of certain elements is not as it should be. Pls let me know. Thanks.
How do I get the old editor. This new one has big issues and Iām dead in the water. Itās only showing me the pages that I donāt have set? I can select the pages on the left I do have set (1-6) but they donāt show up on the screen when I select them. And when they do display when I start up the selection items at the bottom cover some of the display. Has this been tested with Edge? Can I get the old editor back? Iāll need this new on for the Mini I am sure. Iām afraid to compile anything in this new version. Thanks.
@rkram what is the resolution of your screen?
Laptop running recommended 1900 x 1200.
Yes, i did have it zoomed in. It appears that when i hit undo, this is when it reverts to MK2. I tried redoing the preset and I was able to recreate the issue where the presets in the app reset and pages go missing. This happens when i push the changes to the electra mini. I zoomed out of the screen and finalized a new presetā¦lām thinking this will remain unchanged unless I edit the preset again.
1 Like
@Erik The undo/redo should work ok now. Let me know if it works for you too.
@Erik / @rkram53 I am looking the scaling now. The editor should run ok from anything higher than 1024x600:
I think it will be cause by sub-pixels or some kind of scaling. I am looking at it.
OK. The Issue for me was that in Edge at 1900x1200 I needed to set the zoom resolution to 80% to see things properly. Even though Edge said Electra One supports 90% zoom and I had it on 100%. So maybe add this to docs. Iām back in business!
1 Like
Some issues I found while playing with the new web editor.
- If I make the height of the browser window too small, I only see the buttons for page 7-12 not those for page 1-6
- If I select two controls (a checkbox and a relative controller), and then switch to the āSelectedā view both controls are rendered way too big at the right of the page (and overlap).
In the Midi Device drop down now 32 devices are listed, the first sixteen assigned to port 1, the next sixteen to port 2. Has this always been the case? Or is the port assignment a new option?
Also an older issue I just noticed again: with a four stage envelope, the detailed view scales vertically to always let the highest point hit the top of the popup window. This is super confusing if you for instance lower Level 1 from 127 down, actually all other levels move up! And level 1 stays at the top (until it becomes smaller than any of the other levels).
Oh and it would be awfully nice if all controls were supported on all devices, i.e. dial and V fader 4 also on mkII, and XYpad and thin fader on Mini
1 Like
Hey everone, i never had any issues with webeditor. Since the last time i created something a couple of my presets doesnt work anymore. āFix duplicate referencesā is the error message. Some of the fields and parameters are not on the right place.
Ive no idea how to fix this. 
Does anyone know this problem?
Hi, can you share (PM or other channel) URL of the preset that gives you this warning? I will take a look at it. It means that there are controls with duplicate identifiers, the previous version of the editor sometimes silently ignored that.
Today, deleting a preset from a slot is working for me again. Iāve not been checking every day, but it was not working for a few days following the initial preset editor upgrade. Did you change something, @martin?
Another bug with the new web editor, unless this is by design.
Summary
After sending a preset that has just been changed to the Electra, Save Revisions is disabled.
Steps to Reproduce
In the preset editor, make a change to the Lua code.
The Save Revisions button becomes enabled, if it was not already.
Send the changed preset to the Electra.
Expected Result
The Save Revisions button should remain enabled.
Actual Result
Once the send has completed and the preset has loaded on the Electra, the Save Revisions button is disabled.
I released a few minor fixes yesterday. The deleting the presets was one of them.
This is by design. Sending a preset to the controller will automatically create a saved revision. This is there to make sure thereās always have a saved copy of anything you had in the controller.
1 Like
Thanks @martin for the great update!
If I may drop a minor feature request:
Please, can we have a keyboard shortcut to clear then content of the debug listing windows?
As debuging LUA code on the E1 relies mostly on outputs from the custom code, this would be really an enhancement of the debugging workflow (as it heavily relies on manual debug prints from the custom code)
As a suggestion, I throw COMMAND+K (on Mac) in the ring, as the free Midi Monitor which comes in all the time uses the same hotkey for cleaning itās output 
Thanks, I really love my E1 and I am amazed by this community and the continuous work that goes into the product
1 Like