Is there a real script for the MC8 Pro for Ableton Live?

The MC8 Pro doesn’t sync states natively with what’s going on in Ableton Live - I understand there’s a convoluted way to make it happen with like.. 16 (really 8, if you want on/off states) functions via the MIDI message converter, but that’s super limited and annoying.

Is there just a normal script or something I can download that makes this work both ways, properly?

All I want it to do is have the states of some things synced properly, ie mute states on some tracks or loopers, looper states ie recording, not recording, overdubbing, playing, etc - I get that there’s only really 3 states per button on the mc8 pro, that’s fine - it just means using banks so I’ve got a mode for arming tracks etc + a bank for muting tracks = those 16 (really 8) midi message converter slots are gone way before I’m finished setting things up.

I just want it to work with Ableton Live properly.

Unfortunately, I don’t know of any existing Control Surface script to integrate a Morningstar controller with Ableton, which would create the logic necessary to bind the responses from Ableton to toggle the controller’s switches. Until something like that is written, there’s really only uni-directional control, either via keypresses or manual MIDI bindings.

I’ve played around with writing one, so I know it’s possible, but I unfortunately don’t have the time to code one right now. Sorry!

If enough people are interested in it, though, let me know!

Definitely interested in this! I know it’s MIDI remote script based but not sure I know enough Python to actually accomplish myself.

Yeah, it’s definitely doable. I was able to bind a play button and have it two-way sync. It’s just a ton of work regardless of whether you know the python well enough or not.

As has been said in other places, the biggest hurdle to getting a surface script happening is that Ableton and Morningstar simply do not speak the same MIDI language.

To remotely engage/disengage a preset on the MC8 Pro you need to send CC2/CC3 with a value of 0-23 corresponding to the 24 switches across the three pages in a bank, or 127 for all.

Meanwhile Ableton assumes that any MIDI message is to be reciprocated as the same message for MIDI feedback. In fact. The entire message->update state->feedback lifecycle depends on that being the case.

These two schemes fundamentally don’t mesh. You can use the Midi Converter of the MC8 Pro to translate the MIDI from “Ableton” to “Morningstar”. But with only 16 converter slots, requiring 2 for every preset on/off message, you are limited to a single page of presets.

You could use a virtual MIDI bus to translate an arbitrary number of messages. But that only adds complexity and mental overhead to what already isn’t a trivial task.

Without prior knowledge of control scripts or python, I spent a good portion of the last two days vibe-cobbling together a basic script that displays the correct outside behavior for the three basic transport buttons. It achieves that through letting Ableton do the translation work by mutating the outgoing MIDI messages to a format the MC8 Pro natively expects.

To do that I hat I had to create a special Button class that is aware of its “index” for the purposes of feedback and re implement the function responsible for accumulating and sending messages to Abletons C++ engine for broadcasting.

Out of the 72 lines in that script, a good 40 is spent not writing a control surface script, but rather changing how a control script works for simple on/off buttons.

Anyway. Here’s the script again. Maybe someone finds a better solution to this Gemini fueled abomination. It should be expandable to happily sync any number simple on/off presets. I can’t guarantee any more at this point.