Hi, any suggestions for improving the performance of the Web Editor? Sometimes it starts off performing fairly quickly when editing, but then slowly grinds to painfully slow to complete actions like saving and pasting presets and banks. I have 64MB or RAM and sometimes run applications at the at same time like the HX Stomp Editor and use Chrome as my browser. I’ve tried clearing the browser cache and it doesn’t seem to make a big difference. i have the same experience with the app as well.
Just to clarify, the issue occurs when running both the Stomp Editor and Morningstar Chrome editor at the same time? Does the issue resolve when you close the HX Stomp editpr?
Hi James, Windows 11. It happens when I run the Chrome editor solo mostly. It’s quick for some tasks like opening the midi dictionary, but seems to become super laggy and the performance really slows when I select from a drop down list or save. It’s probably mostly a Chrome issue. I have 64GB of RAM and decent gaming laptop with a AMD Ryzen 5 7640HS.
I tested it on my work Macbook Pro and it runs much faster (in Chrome).
I just started over-hauling my MC6 setup in recent days and am finding the same thing - major, major regression in responsiveness when interacting with the controller (bank change, preset save, etc etc).
I’m using 3.12.1 on MBP, Sequoia 15.1.1 with 16GB of RAM. It’s not memory pressure or CPU load - could possibly be some interaction with Ableton? I’ll try to check that next
I don’t think it’s interaction with Ableton, i suspect it’s a bug in the editor app, some resource growing out of control…even tho it wasn’t enough to cause memory pressure on this Mac it could be bad asymptotics in the code somewhere.
410MB at launch but it was 2.18 GB before i quit it, suggests something amiss.
One further detail - disconnect and reconnect caused memory to go from 400-ish to 750MB but repeated disconnect and reconnect didn’t push it any higher.
Lastly, i’m seeing it connect sometimes in “Demo mode”, always fixable by disconnect/reconnect cycle.