Ableton Forum

All,

I am getting very busy lately so I have to drop a few things.
I took care of the updates for the APC_64-40 midi remote script since Live version 9.0.1 (begin 2013) and updated it till mid 2014.
Unfortunately I cannot keep on digging it every time Ableton changes the Framework API for a new version of Live.

So time has come to stop with it.
As a last effort, just to give users some time, I made a last update for 9.1.3.
Anyway, this is the *last* update I will make for the script.

The last version produced (compatible with 9.1.3) and the rest of the legacy versions are here:
http://www.fabriziopoce.com/Live9_Script_APC_64_40.zip

PS: I already asked Hanz if he likes to take over from here again. The link to the script from my website is now gone.

Gr
Fab
http://www.fabriziopoce.com

Sad news.
You have made APC40 much more enjoyable/useful toy. I very much thank you for your effort. It's appreciated.

alpertt wrote:Sad news.
You have made APC40 much more enjoyable/useful toy. I very much thank you for your effort. It's appreciated.

I understand. Anyway, the latest code is there for anyone willing to keep it updated after 9.1.3 (till 9.1.3 the included updates should be fine).
Then, you never know. Like I did taking this over from Hanz the last couple of years, someone may have the chance to do the same for the future.

Gr
Fab

I just sold my APC anyway.
Time for some new.
But the long time i used it i always used it with the script.
Thank you and hanz for the good work!!!

Much respect! Thank you for yr work! I use 64-40 always and yr script has really helped me.

Thank you very much for your hard work and efforts! I'd be interested to know if money would make a difference. We could all pitch in!

handsofire wrote:Thank you very much for your hard work and efforts! I'd be interested to know if money would make a difference. We could all pitch in!

No really.

As Python scripts require an update effort every time Ableton makes a new version, it is an endless development cycle, which is unsustainable.
If Ableton would ever commit to a stable and documented Framework API (= supports it and does not turn it apart every time a new Ableton Live version is required) I could rethink of this.
Unfortunately this is not the case right now and no signs of a change are on the horizon (think that changes where needed to the scripts for *every* minor version: 9.0.1, 9.1.0, 9.1.1, 9.1.2 and now 9.1.3).

Again, I asked Hanz if he likes to take it over again. But I think he has the same issues (= lack of time).
The code of the scripts anyway is open source, so everyone in the community can pick up from here.

Gr
Fab

I understand. Thank you, again!

Hanz & Fab, thanks for your work. I've been using APC64 since the beginning: it was one of the important reasons for getting an APC over maschine or other gear (in that time). I understand with the new hardware, Push, awesome max patches that are available...that updating APC64 is time consuming and has less and less added value/userbase.

For me personally it opened up a world of possibilities and first insight of how 'programming' works in Ableton. Thanks for that as well.

And Fab, now i'm at it: cheers from Belgium, your J74 Max Patches are the bomb.

I use this to play in my live performances. I really hope it can be updated, but if not I understand. I'll have to learn python or find another system that works for me. Can you tell me if this will work with Ableton 9.5, or what might need to be changed in order for it to function properly?

The problem is that with 9.5.1, Python will be updated to version 2.7, which will break most 3rd party remote scripts.

Buleriachk wrote:The problem is that with 9.5.1, Python will be updated to version 2.7, which will break most 3rd party remote scripts.

Are you sure this is the case? Because python 2.x versions don't have big differences AFAIK, but python 3.x does.

Python 2.7 broke some of my Native Kontrol scripts.

this script works fine with 9.5.1 betas

f.poce@tiscali.nl wrote: every time Ableton changes the Framework API for a new version of Live.

Any idea why they do this? The idea of an API is to not change it. I can see that if it affects performance or the old structure cause bugs they'd need to change a component of an API in some fashion, but they should be very clear on those reasons and offer update tips. Do Ableton do this?

Is the PyCharm IDE of any use for Live Python (re-)development? What tools do you suggest?