Ok having a super weird issue. Using current version of Ableton Live 12. And latest version of ableset. Using a brand new MC8pro. In ableton it shows up fine in the midi settings. It shows up in my device manager in windows. But when I click Edit Midi Mapping in Ableset everything is just black and I can’t see any options to edit mappings or devices or anything. I have looked at guides of Leo using an MC6 and and he a list of connected devices but for me its just black. Any ideas what I am doing wrong?
Hey @opengrip, welcome to the forum!
That sounds like a bug. I don’t have an MC8 Pro, but I don’t see why it shouldn’t be recognized by AbleSet. Does AbleSet see any other MIDI controllers you connect to your PC?
In any case, please feel free to send me a log package so I can take a closer look at what might be going wrong under the hood. You can create one by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package”.
You can also include screenshots or a video of the issue, that often helps with troubleshooting.
If the files are too large to send via email, you can upload them to my support inbox instead.
I’m looking forward to your reply!
Hey Leo I sent a log package and a video of my screen showing my ableton midi settings and ableset midi settings. I don’t currently have any other midi controllers to test unfortunately but hopefully this is enough to help troubleshoot the issue.
Thanks
Hey @opengrip, thank you for the log package!
That’s very strange, AbleSet reports no errors related to MIDI devices, but it seems like Windows just returns an empty list when AbleSet requests all MIDI inputs. If you haven’t already, could you try restarting your computer and check if that helps?
You could also try unchecking all boxes (Track/Remote/etc) related to the MIDI device in Ableton and setting the Input and Output of the AbleSet control surface to “None”. There’s an issue with how Windows handles MIDI devices where only one application can access a given MIDI device at a time. I’m not sure it is related to the issue you’re seeing, but it might be worth a try.
Let me know if this solves the issue for you. I’m looking forward to your reply!
Hey Leo, thanks again for your help!
I wanted to give you a clearer picture after some more testing. Based on your suggestion, I experimented with different combinations in Ableton’s MIDI settings.
– I tried leaving the AbleSet control surface input/output off while keeping the MC8 ports enabled for Track/Remote.
– I also tried the opposite: leaving the AbleSet control surface input/output on while disabling Track/Remote.
In both cases AbleSet still showed a blank MIDI mapping page. The only way I could get AbleSet to recognize the MC8 was to turn everything off in Ableton, then do a full PC restart.
Even then, it’s been a bit inconsistent — most of the time one restart works, but one time it actually took two restarts before AbleSet finally showed the MIDI devices. It seems like Windows 11 is still “holding on” to the device occasionally even after settings changes and restarts.
So while the workaround fixes the blank page, it means I can only use the MC8 with AbleSet or Ableton, not both.
Do you have any recommendations for running the MC8 with AbleSet and Ableton simultaneously on Windows 11? Should I be looking into something like loopMIDI or another virtual MIDI splitter/multi-client driver, or is there a better method you’d suggest?
Thanks again for all your support and for helping me narrow this down!
Hey @opengrip, using a virtual MIDI splitter might be a good idea if you’d like to use your MC8 Pro with AbleSet and Live simultaneously. Others have found MIDI-OX to be a good tool, here’s a post with a video on how to set it up:
Let me know if this works for your use case! 
Yeah I will have to spend some more time playing with this to see how well it works. For now at least I understand the issue. Even using the editor on my PC for MC8pro will prevent ableset from being able to access the Midi. Thanks for the help and guidance Leo!