E1 not connecting to Chrome

Bug reports
1

Hello,

I’m having an issue connecting the E1 to Chrome on macOS (Mac mini M2). The E1 shows as “not connected” in the web app, even though it’s recognized and working in Cubase at the same time, and also appears as connected in Audio MIDI Setup.

So far I’ve tried: quitting Cubase, using different USB ports (direct USB‑A and USB‑C via adapter, no hub), swapping cables, and clearing Chrome’s site data for the E1 web app.

Does anyone have any further ideas?

PS: The issue seams to have started since updating to MacMini M2 and OSX26

2

Idk how about Mac, but i have problem to connect electra via chrome, coz i’m still using win 7 software, i needed to change browser to supermium.

3

Feels like the new Chrome update broke things… Same here… Can no longer connect via the web editor in Chrome…

4

Yes I’ve been having problems with Chrome on Windows 11. A reboot fixed it yesterday, but the issues are fairly regular.

5

For me Chrome restarts are an almost daily occurrence. But have always been able to get connected to E1 web editor eventually.

6

@kiwigrass Used to be like that for me. But since today I haven’t been able to get to the E1 with the web editor… Not good!

7

@homeelectra @eusti can you share info about version of your chrome?

1 Like
8

Hi Martin!

On my MacMini i updated Chrome to the latest version, 152.0.7977.65.

9

I tried Edge and everything is working fine.

So thanks to everybody for the support!

1 Like
10

FYI, I’m currently on Chrome 152.0.7977.65, and Windows 11 25H2 build 26200.9278. I am able to open and use the web app with Chrome.

1 Like
11

152.0.7977.65 (Official Build) (arm64) on my Mac M1 Mac OS 26.6.2 (25G83).

12

And by the way I seem not able to connect with Edge either… :sob:

13

From chatgp

Yes — there is one potentially important WebMIDI change around Chrome 152, even though neither Chrome 151 nor 152 lists a Web MIDI API change in the official release notes. �

Chrome for Developers +1

The significant one is macOS + Chrome 152. On July 22 Chromium substantially refactored its macOS MIDI backend to use the newer CoreMIDI MIDIEventList / Universal MIDI Packet (UMP) APIs, converting between UMP and the MIDI 1.0 messages exposed through Web MIDI. That commit is Chromium main position #1665988. �

Chromium

Chrome 152 branched later, at main position #1669021, so that new MIDI implementation is definitely part of Chrome 152. �

Chromium

And importantly: it introduced a real SysEx regression. Chromium subsequently found that SysEx7 conversion was wrong: the code incorrectly included F0/F7 inside UMP payloads and failed to reconstruct them correctly on incoming messages. Chromium explicitly describes this as:

“breaking Web MIDI SysEx on the default macOS UMP backend”

The fix landed August 3 at main position #1672730. �

Chromium

That position is after the M152 branch point, and I can’t find evidence that the fix was merged/cherry-picked into the 152 branch. So if your problem is Chrome 152 on macOS and involves SysEx, I would consider Chrome 152 itself a very strong suspect.

For Chrome 151, there wasn’t a comparable public WebMIDI API change. There was some internal Windows work before the M151 branch, including a June 4 fix to the experimental WinRT MIDI backend concerning stale callbacks/session rebinding. � The WinRT backend is still disabled by default in Chromium, though. �

Chromium

Chromium

So the short version is:

Chrome 151: no obvious intentional WebMIDI behavior change.

Chrome 152 / macOS: yes, major backend change, plus a known SysEx regression.

Chrome 152 / Windows: I haven’t found a comparable change that should alter ordinary WebMIDI behavior.

The proposed change making MIDIAccess transferable/available in workers is only an Intent to Prototype from August 25, not something that shipped in 151/152. �

Mail Archive

If you’re seeing something break specifically between 151 → 152, tell me OS + what exactly fails (device enumeration, MIDI input, output, SysEx, reconnect, etc.) and I can trace the exact Chromium changes involved.

I can also keep an eye on whether the SysEx fix gets backported in to Chrome 152 stable.

2 Likes
14

Looks like the latest Chrome update may have broken something. Same issue here — I can no longer connect through the web editor in Chrome. I could yesterday.
Chrome, version 152.0.7977.65 (Official Build) (arm64)

Edit: I just tried on an older version of Chrome and that worked.
Version 116.0.58.45.187

1 Like
15

I am looking at the issue.

EDIT:

they have fix for it ready in upcoming Chromium 153. The issue is caused by the bug they made while adding support for MIDI 2.0 UMP. I assume it will go out soon. I am still looking at options but for now not-updating or downgrading is the fastest option.

Just provide more insight: the latest version of chrome adds extra F0 and F7 around every SysEx message, effectively making broken messages that connected MIDI device will not handle.

3 Likes
16

Thanks Martin.

Edit: I downgraded to version 151.0.7922.76 (Official Build) (arm64). Now it works.

Edit: I updated Chrome today with latest version 153.0.8010.37 (Official Build) (arm64). Everything seems to work as usual now. :grinning_face:

3 Likes
17

I’m finally able to connect to the web editor as well as Chrome for the Mac has been updated to 153.

1 Like