We’ve identified an issue with Chrome 152 on macOS that affects Web MIDI SysEx communication in the Morningstar Editor.
The issue is caused by a regression in Chrome’s MIDI implementation, which can cause valid SysEx messages sent by the Editor to be incorrectly processed before they reach the connected device.
Google has already implemented a fix in Chromium, but the fix has not yet reached the current stable version of Chrome.
For now, macOS users can continue using the Editor by selecting either:
Serial Connect
Bluetooth Connect
Both of these connection methods are unaffected by this Chrome Web MIDI issue.
If you are currently using MIDI Connect in Chrome 152 on macOS and are experiencing connection or communication problems, we recommend switching to Serial or Bluetooth until Google releases the fix.
We’ll update this post once the fix is available in Chrome Stable.
I can understand that users may have some ongoing concerns about issues like this. This is also one of the reasons we provide multiple connection methods in our Editors, including the Serial connection option. It means the Editor is not dependent on a single browser technology or MIDI implementation, so if an issue arises with Web MIDI, users still have another reliable way to connect to their Morningstar devices.
Update: Fix confirmed for Chrome Web MIDI SysEx issue on macOS
We have an update on the Chrome Web MIDI SysEx issue affecting macOS users.
Chromium has now confirmed and fixed the underlying bug in its MIDI 1.0 to UMP/SysEx7 conversion. This was the issue causing valid SysEx messages to be incorrectly framed, resulting in the extra F0 and F7 bytes that some users were seeing in MIDI Monitor.
The fix was merged into Chromium after Chrome 152 branched, which is why the issue is still present in Chrome 152.
The good news is that the fix is included in the Chrome 153 codebase. Chrome 153 has already started rolling out as an Early Stable release, so we expect the issue to be resolved once Chrome 153 becomes generally available.
For now, if you are still running Chrome 152 on macOS, we recommend continuing to use Serial Port or Bluetooth Connect in the Morningstar Editor. These connection methods are not affected by the Web MIDI issue.
Once Chrome 153 is widely available, we’ll verify the fix ourselves and update this thread again.
I have Windows 10 so yours may be different. When you go to open the editor in Crome there is an icon to the left of “editor” in the address bar, click on that and then “reset permission”. That worked for me.
i can connect to my MC8Pro just fine but i haven’t been able to connect at all to my ML10x, via normal port (USB-C) or via serial port. either using the web editor or installed editor (same thing tho i guess?). running macos w/ chrome Version 152.0.7977.76 (Official Build) (x86_64).
same issue? i am running the correct firmware editor for my ML10x, v1.1.2 latest
slight diff in sysex via midi snoop, first midi snoop is normal port attempt 72 F7, second midi snoop is serial attempt, 73 F7; but guessing thats expected.
Adding also that with my MC6 pro acting as the host via usb for my ML10x - i still can’t access the ml10x in any way with my chrome up to date.
The MC6 pro works on the mc series editor though - but currently can’t access the ml10 on the iphone app, the mac app or any browser or ml10 to my devices as a direct connection. It says it can’t detect the firmware version and serial port (or any other port) don’t work. Very surprised what I’d have thought were the offline options (mac and iphone apps) don’t work with a direct cabled connection
Yes, this currently won’t work if you are trying to connect to the ML10X via the MC6 PRO USB Host port. Because of the MIDI issue in Chrome, only using the Serial option (and bluetooth) will work. The Serial option does not communicate with the device via MIDI, so it is not possible to pass the editor messages through to the USB port to communicate with the ML10X..
The ML10x is not working via serial port - it doesn’t show anything. Direct connection via usb from the ML10x to Mac (or iphone). The serial port option doesn’t even see\acknowledge the ml10x. The only way I could get the editor to see it at all was via the method that I mentioned as using the 6 pro as a usb host.
I just tested this with the v1.1 and v1.2 firmware and seems to be working fine. Can you let me know the editor version (displayed at the bottom of the editor page) that you are using?
I’ve tried using all of them ha. 1.2 (and my ml10x is on the newest firmware from recently), I’ve tried 1.1 as well.
At the bottom of the 1.2 editor screen it says v1.3.12.260831472.
The USB cable I’m using works the mc6 pro on Chrome and Brave and on the morningstar offline apps on Mac and iphone.
I’ve now gotten it to work (success!) in brave browser and Google Chrome after it didn’t see the serial port - it suddenly did after multiple attempts.
UPDATE: The Chrome bug has now been resolved. Please update to the latest Chrome version 153 to connect to the Editor as you normally would. To update, Click on Chrome > About Google Chrome.