I was experimenting with the MC 8 (original) inside the USB A host connection of an H2MIDI Pro, and, after some trial and error got the MC 8 the editor connected and was able to go about things as usual. However, today I can no longer connect to the editor.
I removed the MC 8 from the H2MIDI Pro connection and connected directly to the computer, but it is still not connecting.
Firmware is the latest 3.13.6 and editor is the same. The port is recognized but it just will not connect. When it was within the H2MIDI Pro hub, the MC 8 was still being recognized (although editor not connecting starting today).
Now I am only able to connect via the serial port. I did a factory reset and there is no change.
Same problem. Brand new MC8 Pro and ML10x that I am trying to set up. It all worked a couple of weeks ago. Got busy and now neither will connect. I can only get a connection from Bluetooth to the MC8 pro form my iPhone. No USB or bluetooth from laptop for either device (of course no BT to ML).
macOS 26.5.2, Chrome Version 152.0.7977.65 (Official Build) (arm64). Doesn’t work in brave either. Also doesn’t work using previous editor build .
Edit: Also tried on a windows 11 PC. Chrome fully updated. Connected for a few mins to the ML10x and then froze and started with the “Unable to detect firmware version” screen.
Just to share a bit more information about this, the regression appears to have happened because Chrome recently updated its macOS MIDI system as part of its move toward the newer MIDI 2.0/UMP architecture.
Chrome still supports MIDI 1.0 devices by converting MIDI 1.0 messages internally, but a bug in this compatibility layer is currently causing some MIDI 1.0 SysEx messages to be handled incorrectly.
This is a Chrome issue rather than a problem with the Morningstar Editor or device firmware.
That’s why you’re seeing the extra F0 and F7 bytes in MIDI Monitor. They are being introduced by Chrome while it processes and converts the SysEx message, rather than being sent by the Morningstar Editor itself.
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.
After installing firmware 2026-08-17_MC4_PRO_Firmware_v_3_14_0_260817476_NO_KEYBOARD.hex on my MC4 Pro, I was no longer able to connect to the Editor via either Bluetooth or USB.
I tried both the local Editor and the web Editor in Chrome, but neither worked.
My system:
macOS 26.6.2 (25G83)
Google Chrome 152.0.7977.76 (Official Build), arm64
My issue seems similar to some of the reports in this thread, but I’m not sure whether I’m dealing with the same Chrome/Web MIDI issue or if there may also be an issue related to firmware 3.14.0.
As a test, I rolled back to the previous firmware version. After the rollback, Bluetooth connectivity started working again with the local Editor. However, I still cannot connect to the web Editor using Chrome.
Given that Bluetooth and the local Editor stopped working after updating to firmware 3.14.0 and started working again after rolling back, I’m wondering if there could be two separate issues: one related to firmware 3.14.0 and another related to the current Chrome/Web MIDI issue.
Has anyone experienced the same behavior with firmware 3.14.0 on the MC4 Pro? Is there anything else you would recommend testing, or should I stay on the previous firmware version for now?
I’ve just tested both MC4 PRO 260817476_NO_KEYBOARD and 260901478_NO_KEYBOARD firmware versions and can connect successfully to the Editor, both via Chrome browser and the local application.
Please note, if you are on the browser, you need to connect using Serial port as shown below.
