Windows + Chrome MIDI port blocking is hell on earth.
Could we get additional settings toggle to disable automatic assignment of MIDI ports? So that ports are assigned only manually only when syncing with the EC4 is actually going to take place?
(and/or for the editor to remember a set pair of ports and auto-grab only those)
It often happens that the editor grabs some ports that should be used elsewhere and then other things don't work. And then Chrome needs to be completely killed to release them.
This happens especially after resuming the computer from sleep / hibernation, where Chrome seems to be faster to grab them then the rest of the Windows MIDI infrastructure.
Windows + Chrome MIDI port blocking is hell on earth.
Could we get additional settings toggle to disable automatic assignment of MIDI ports? So that ports are assigned only manually only when syncing with the EC4 is actually going to take place?
(and/or for the editor to remember a set pair of ports and auto-grab only those)
It often happens that the editor grabs some ports that should be used elsewhere and then other things don't work. And then Chrome needs to be completely killed to release them.
This happens especially after resuming the computer from sleep / hibernation, where Chrome seems to be faster to grab them then the rest of the Windows MIDI infrastructure.