Updating to the new version of Ableset has brought on a new problem that I didn’t have on previous versions. I’m using a Morningstar MC6 Pro to skip to the next song and start play. With the footswitch, skipping to the next song jumps to random songs instead of to the next song assembled in the set of Ableset. Using the mouse and “jump to next song” in Ableset will keep them in the correct order but not using the footswitch. All MIDI mapping is the same as before and my locators in Live don’t have “set song start time here” selected. Any suggestions?
Hey @pb5021967, welcome to the forum!
If the mapping worked fine on previous versions and nothing changed on the MC6 Pro side, the first thing I’d check is whether AbleSet is receiving duplicate or extra MIDI messages from the controller.
This can happen if the MC6 Pro is connected via USB to your computer and at the same time sending MIDI through one of its MIDI ports to another device (like a MIDI interface or audio interface) that also routes back into the computer. In that scenario, AbleSet would receive the same “Next Song” command twice (or more), which could cause it to skip ahead to unexpected songs.
Here’s what I’d suggest:
-
Check your MIDI routing: Make sure the MC6 Pro’s MIDI signal is only reaching AbleSet through one path — either USB or a MIDI port, not both.
-
Use a MIDI monitor: Download a MIDI monitor app (like MIDI Monitor on Mac or MIDI-OX on Windows) and watch what happens when you press the footswitch. You should see exactly one message per press. If you see two or more, that would confirm a double trigger.
-
Check AbleSet’s MIDI Mapping: Go to Settings → MIDI Mapping, OSC & Scripting → Edit MIDI Mapping and confirm the mapping is set to “Next Song” (or a Custom OSC with
/setlist/jumpBySongs 1). Also make sure there aren’t any duplicate mappings for the same note/CC. -
Check Ableton’s MIDI settings: Make sure the MC6 Pro isn’t also enabled as a MIDI input in Ableton Live’s preferences (Link, Tempo & MIDI). On Windows especially, only one app can access a MIDI input at a time, so the device should be disabled in Live if it’s mapped in AbleSet.
Could you try those checks and let me know what you find?
I’m looking forward to your reply!
I appreciate your fast response. I went through everything that you suggested and found no problems other than footswitch assignments in Live. You are correct that if I unassign the footswitch from Live completely, it does correct the problem of songs getting out of order in Ableset. Since I’ve starting using Ableset, I have had two of the buttons on the footswitch assigned to re-enabling automation and follow (which is the cursor scrolling during playback). So part of the footswitch was controlling Ableset and the other part was controlling Ableton Live. If that’s not possible, I can adapt to it. I’m just trying to use the footswitch for everything that would cause me to have to take my hand off of the guitar. It’s no big deal though so I think I’m good.
Thanks again.
Hey @pb5021967,
You can handle re-enabling automation entirely from AbleSet, so you don’t need Live to receive MIDI from the MC6 at all. Just map the footswitch in AbleSet’s MIDI Mapping as a Custom OSC action with:
/global/reEnableAutomation
This does exactly the same thing as Live’s re-enable automation button, but routed through AbleSet.
Would that work for your use case?
Yes thank you! That works for the automation. What about the Follow button? What’s the wording for that?
Hey @pb5021967,
AbleSet doesn’t have a native command for Live’s Follow toggle, so this one would need to go directly through Ableton’s own MIDI mapping.
What I’d suggest is: try mapping a note on message on your MC6 Pro to the Follow button in Live, on a different MIDI channel than the one you’re using for AbleSet.
Make sure that in Live’s MIDI preferences, the MC6 Pro input is only enabled for that specific purpose, and that AbleSet’s mappings are on a separate channel so they don’t overlap, just in case.
Let me know how that goes, I’m looking forward to your reply!