Ableton Live 9.2 MIDI remote scripts source code

[julienb]

I (FINALLY) got time to decompyle all Ableton Live 9.2 MIDI remote scripts for your pure pleasure

You can find them there:
https://github.com/gluon/AbletonLive9_RemoteScripts

The (UNOFFICIAL) Live Python object documentation


You can also find on my website these 2 links at the top of the page there

[regretfullySaid]

Thanks!

[irrelevance]

Thanks julien

[Airyck]

This is great! Thank you so much for your work, your timing is impeccable!

[Raztua]

thanks julien,

That's a wonderfull job!

[hacktheplanet]

This is great, you are great.

The VCM600 scripts didn't work right away for me, so I did some debugging.
The log (~/Library/Preferences/Ableton/Live 9.2/log.txt) recorded this:

Code: Select all

8800 ms. RemoteScriptError: raise index in range(len(self._track_eqs)) or AssertionError

8800 ms. RemoteScriptError: TypeError
8800 ms. RemoteScriptError: : 
8800 ms. RemoteScriptError: exceptions must be classes, instances, or strings (deprecated), not bool

Here's the script from the VCM600/MixerComponent.py that threw the first error:

Code: Select all

def track_eq(self, index):
        raise index in range(len(self._track_eqs)) or AssertionError
        return self._track_eqs[index]

I know very, very little Python, but after some light reading it seems that the syntax was incorrect for the version of Python Live 9.2 uses. Using 'assert' instead of 'raise' solves the problem and the script compiles properly:

Code: Select all

def track_eq(self, index):
        #raise index in range(len(self._track_eqs)) or AssertionError
        assert index in range(len(self._track_eqs)) or AssertionError
        return self._track_eqs[index]

If you find that these scripts don't work right away, it may just be due to syntactical errors!

[hacktheplanet]

While I'm thinking about it, does anyone know how to use __timer_count?
I'd like to do some timer based stuff, and time.sleep(x) sleeps the whole thread of course.

[irrelevance]

Just tried the moving the decompiled vcm600 scripts into remote scripts folder and live 9.2 had no problem (re)compiling them.

[infinitystairs]

Hi Julien, I think something is broken in Live 9.7.2 with the decompiled midi remote scripts I downloaded from the Master branch at your GitHub repo.

When I place them in my MIDI Remote Scripts folder and launch Live, almost all of the controllers are missing from the list.

Similar issue was reported on GitHub:
https://github.com/gluon/AbletonLive9_R ... /issues/32

I (FINALLY) got time to decompyle all Ableton Live 9.2 MIDI remote scripts for your pure pleasure

You can find them there:
https://github.com/gluon/AbletonLive9_RemoteScripts

The (UNOFFICIAL) Live Python object documentation


You can also find on my website these 2 links at the top of the page there

[pottering]

Those decompiled scripts are NOT for users to download and install, because they are THE SAME SCRIPTS THAT ALREADY COME INSTALLED with Live, so no need for anyone to do that.

[infinitystairs]

pottering, what do you mean these scripts already come installed? On Mac, Live 9.7.2, I have the compiled .pyc framework files. I want to study the decompiled files. I can't find a 9.7+ version.

Those decompiled scripts are NOT for users to download and install, because they are THE SAME SCRIPTS THAT ALREADY COME INSTALLED with Live, so no need for anyone to do that.

[pottering]

pottering, what do you mean these scripts already come installed? On Mac, Live 9.7.2, I have the compiled .pyc framework files. I want to study the decompiled files. I can't find a 9.7+ version.

Those decompiled scripts are NOT for users to download and install, because they are THE SAME SCRIPTS THAT ALREADY COME INSTALLED with Live, so no need for anyone to do that.

I don't know how Julien Bayle decompiled them, sorry.

I just did a test here with a 9.6 script from github in Ableton Live 9.7.2, and it compiled the .py into a .pyc just fine (Ableton found it).

Did you change the folders name when dropping them inside "MIDI Remote Scripts"?
Did you drop just the scripts, outside the original folders?

You can't just change the folder name or remove the script from inside it, the scripts have to be inside that folder (that usually has the same name) or you have to edit the references inside the .py file.

Otherwise, asking Julien Bayle seems to be the only way, at least for now.