I use an iMac. Since I updated to the latest firmware my mc8 pro has been acting strangely when trying to connect via bluetooth. When I use the bt connection it either fails and I restart the editor again. I use the standalone editor. other times when it does connect via bt it either show the banks and their titles but not for the presets which show as blank or the banks will show as blank and the pages/presets show up. sometimes only partial filling in of the page/preset data. When connected via usb it is fine. This issue was present prior to firmware update. Any guidance would be appreciated. Thanks
Card created
This is an automatically generated message
A Trello card has been created for this request: Blue Tooth Anomalies
Have you tried using the browser version of the editor? This is always up-to-date whereas the downloadable, standalone version is not. Can you try using the browser editor and see if this resolves things? Try both the stable version (https://editor-mkii.morningstar.io/) and the beta version (https://editor-beta.morningstar.io/)
Let us know if either (or both) of these work for you.
I tried the Chrome browser version and the beta version and they both worked perfectly. I thought it was had read somewhere to use the standalone version but I will stop for now on. Thanks so much. Great product and a great support staff.
1 Like
Definitely use the browser-based versions of the editor if you can. You can also install the browser version as a web app so it can be used offline just like the standalone version.
when I open Chrome it did not show the download until I deleted the app. I used the link and now today I have the same issues as yesterday. It shows the presets but the banks info? It shows on the editor that the mc8 pro is paired but still the same issues.
Can you clarify what you mean by this:
when I open Chrome it did not show the download until I deleted the app
Are you saying that you tried to install the editor as a web app…and it didn’t work? And are you also saying that using the online editor link now gives you the issues as you were experiencing with the standalone editor?
Yes when used chrome it did not show the download option until I deleted the app and then I added the app via chrome and I am having the same issues as the standalone.
This doesn’t make sense. Remove that web app editor and install the web app for the beta editor instead…see how that goes. https://editor-beta.morningstar.io/
I deleted the app and then installed the beta and it worked great. Also this time in the upper right it showed the download symbol so I was able to do that. I appreciate your time and efforts. Great support staff at Morningstar.
1 Like
I’m having the same issue while connecting to the MC6 Pro to the web editor via WIDI Jack. ML10X is connected to USB Host port of the MC6 Pro. I can access both editors simultaneously on two different Chrome pages, and while I’m not experiencing any issues with the MC6 Pro editor, the Preset names and the Loop names on the ML10X are all wrong (sometimes completely blank, sometimes they look like my MC6 Pro preset names, weird!). On some instances I can’t even write the correct names, nothing appears on the tab when I’m typing.
EDIT : after a while I realized that the MC6 Pro also behaves badly when editing with the WIDI Jack. Sometimes clicking on another bank doesn’t change banks at all. It seems that even when connecting this way “Computer USB to MC6 Pro Device USB, MC6 Pro USB Host to ML10X”, completely bypassing the WIDI Jack, editing the ML10X is very buggy (same bugs as above). Both devices have the latest firmware and have the correct MIDI thru settings.
I also have pretty bad experience using bluetooth interfaces.
I really hope this could be adressed somehow. Maybe some modifications and double-checks applied to sent (sysex?) messages. Like, I don’t know, sending something to the editor informing that preset names or other info hasn’t been transferred properly. Would be great if ML10X could communicate via midi ports too – currently, it works only via USB. Not trying to make a drama here, but really, imagine an average-big pedalboard that needs to be dragged to PC just to edit some presets. With two ML10X it becomes twice more unexpectedly painful experience. @james 
I still keep experiencing issues when connecting via bluetooth. I am using the beta as suggested. Yesterday I was using my mc8 pro (I disconnected after use and powered down as usual) and I turned it on today and connected vis bluetooth. Now it pairs up fine but will show the banks as just numbers and the presets empty. This is not consistent. Sometimes the presets will show up but the banks are still blank. I will disconnect power from the mc8 pro and restart and sometimes that resolves it and other times it doesn’t. Usually I have to restart my iMac and then reconnect to the mc8 pro. I am using sequoia 15.6.1 and all programs run fine. I have the latest firmware and these issues showed up when I updated to the latest firmware. Very confusing. Any guidance would be appreciated. Thanks
I’m almost sure it chokes with tons of sysex messages. If so, maybe slowing these messages down would make the tranlation more stable. High hopes the team will resolve this.
Can you explain that? I don’t understand what that means. Thanks and I am glad I am not the only one experiencing these issues.
I cannot state how frustrating it is. I have 2 days where I connect via Bluetooth and all banks and presets show and it works great. Tonight dame procedure and all presets show but all banks are unnamed. Restart mc8 pro same result. I restart my computer and now it all shows up correctly. 
If you’re restarting your computer and everything then works , that tends to point more towards a browser issue than a controller issue.
Are you using Chrome or Brave? I now use Brave solely for the Morningstar editor and am quite happy with it…and updates don’t tend to break things, unlike Chrome updates.
It’s not the browser. It works stable every time using a cable. With BT MIDI it’s always fifty-fifty.
It could definitely be the browser’s BLE MIDI functionality. Issues like this frequently occur with BLE MIDI and browsers.
I am using chrome as that is what Morningstar suggested