ableton: just release the py midi remote scripts

[oddstep]

Hey St8, thanks for the links Nice 1. Respect for sussing it out yourself.

[gusc]

pretty please

[deeflash]

hate to resurrect a year old thread but... PLEASE?? I'm working on customizing my Remote SL setup and it would be so much more helpful to be able to tweak some things in the midi remote scripts...

[oddstep]

Ha. I'd forgotten about this. So in the past year Hanz Petrov basically reimagined the APC using code fragments from 7 combined with an understanding of 8 that he developed from studying partially decompiled pyc files, I emailled ableton asking for the py files for the launchpad and was told that it wasn't going to happen (very nicely of course) and nothing else has changed. Currently NativeKontrol seem to have the ball with the glyph scripts and the launchpad extension.... I'd guess this also built on the same resources that St8 and Hanz worked with.
So what I expected has happened, the python scripts are being worked with and developed. However because these aren't the original ones, there is a lot of trial and error involved in getting anything right.
I will restate my main point. The py files for the launchpad (for example) exist, Ableton have decided to encrypt them prior to their distribution with Live. This makes them harder to customise and probably harder to use in Max. If this was a successfull business strategy I would resent this decision but ultimately accept it. As it is, plenty of people with greater skills than me are currently doing great work developing scripts from the information that is currently available on the internet. What does Ableton gain from this situation?
Ableton, just release the python source code for the midi remote scripts.

[deeflash]

Yes, I agree, releasing the scripts really wouldn't do anything but make Ableton the best software for live control because we could really fully interface with the software however we need to.

The only reason I could see why they don't release the source to the py scripts is they might have some special partnerships with device manufacturers and do not want to mess with that. (could even be a part of the agreements to not release the source.)

[gusc]

Ableton should start to listen to the big guys, like Balmer or Jobs - it's all about developers, developers, developers and of course customers, customers. And the former is the one of the roads Ableton is not willing to go right now, but they should try Actually the magic of software success is not only based on customer satisfaction, it's also based on the 3rd party developers who can develop new stuff and untie your hands from doing everything yourself. Look at the success of VST and ASIO, if those things would be completely closed source from Steinberg, then we would be running Ableton through DirectSound and you would not be able to use your favorite plugins in ableton, in fact ableton live/suite would be quite empty for some of VST junkies

[oddstep]

Developers haven't got an interest in open controller protocols, they have an interest in protocols that they can access... other people don't come into it. The locking up of control scripts in a compiled format is reducing the potential value of both controllers and Live, but helps fuel a market in new plastic goods that implement the same set of framework classes in slightly different ways... with the user unable to influence the relationship between a piece of expensive licensed software and a piece of purchased equipment. Its a really exasperating situation driven by some really low order commercial imperatives and made worse by the fact that people have already proved that opening up of the py code would lead to a more creative use of Live (for instance, apc extensions, ipad controllers).

[Komponist-Kalle]

Please do, abes.

Yes, please, please, please!