You may find nice docs in the decompiled source from the _Generic folder..mdk wrote:same here, docstrings are included.
i used the .deb from here :
http://crypto.riken.go.jp/pub/linux/deb ... decompyle/
if that helps.
Who wants access to Ableton's Python API? .. You? .. Ok!
-
Nathan Ramella
- Posts: 128
- Joined: Wed Jun 06, 2007 10:48 am
-
Nathan Ramella
- Posts: 128
- Joined: Wed Jun 06, 2007 10:48 am
-
Nathan Ramella
- Posts: 128
- Joined: Wed Jun 06, 2007 10:48 am
worth a bump to post a link to MDKs 'patch morpher'
http://www.liveapi.org/forum/viewtopic.php?p=66#66
take any live device such as Operator or Sampler - , tweak the controls and 'store' them as 4 different presets, morph between them using an on-screen track pad.
It works too.
Uses Flash as the interface and LiveAPI (y'don't say!)
http://www.liveapi.org/forum/viewtopic.php?p=66#66
take any live device such as Operator or Sampler - , tweak the controls and 'store' them as 4 different presets, morph between them using an on-screen track pad.
It works too.
Uses Flash as the interface and LiveAPI (y'don't say!)
-
Nathan Ramella
- Posts: 128
- Joined: Wed Jun 06, 2007 10:48 am
H O TAngstrom wrote:worth a bump to post a link to MDKs 'patch morpher'
http://www.liveapi.org/forum/viewtopic.php?p=66#66
take any live device such as Operator or Sampler - , tweak the controls and 'store' them as 4 different presets, morph between them using an on-screen track pad.
It works too.
Uses Flash as the interface and LiveAPI (y'don't say!)
I REPEAT
H O T
Relevence has landed.
remix.net - versus / liveapi / hangthedj / ammobox
I can't get off the ground, errors, crashes, tears, agony...
6.0.3 - 'Visual C++ serious runtime error' when I set LiveTelnet as a Control Surface
6.0.7 - 2 x 'Serious program error Live will shut down' dialog boxes during initialisation on program launch.
Live OSC can be set as a control surface, no problem.
XP Pro SP2
The error is probably between the keyboard and the chair, I'm just not sure where. Latest Python installed.
Flash interface FTW!!!! Can't try it yet, but scene morphing, how cool is that? This is exactly what I was hoping for with the C74 collaboration, users making the tools we've been dying for, rolling out features we never dreamed of.
12/12/07 Live DAWs worldwide gain consciousness and win every music award on their own for all time ever after.
TIA for any tips.
6.0.3 - 'Visual C++ serious runtime error' when I set LiveTelnet as a Control Surface
6.0.7 - 2 x 'Serious program error Live will shut down' dialog boxes during initialisation on program launch.
Live OSC can be set as a control surface, no problem.
XP Pro SP2
The error is probably between the keyboard and the chair, I'm just not sure where. Latest Python installed.
Flash interface FTW!!!! Can't try it yet, but scene morphing, how cool is that? This is exactly what I was hoping for with the C74 collaboration, users making the tools we've been dying for, rolling out features we never dreamed of.
12/12/07 Live DAWs worldwide gain consciousness and win every music award on their own for all time ever after.
TIA for any tips.
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Hi all,
I'm getting Live 6.0.7 quiting with Runtime Error whenever I try to select the LiveTelnet or LiveOSC Control Surface from the MidiSync Preference Menu.
I'm wondering if this is because of the locations I've got the programs installed to.
My Audio Partition is drive D, so Live 607 is in D:\Program Files\Ableton. I've copied the LiveAPI files to \Live 6.0.7\Resources\MIDI Remote Scripts
I've installed Python 2.2 to E:\Programs\Python (this is a partition I use for general programs and data) Python is working fine - I've played with IDLE and confirmed this.
There's no firewall running (Audio PC never goes near the Internet).
I've seen various posts from Nathan where he says Python should be in C:\Python22 - is this essential (and does this assume that Live is installed on drive C: ? It's not in my case)
Any advice would be appreciated - I'm dying to get cracking on this!
i think the only reason why python has to be in that location is that the setup code expects it to be there when it updates the python system path.
try editing __init__.py to reflect your python location and let us know if it works.
LJ- Very cool man, I reinstalled Python to the root on C: (less typing in the future) and it fixed 6.03. 6.07 is still broken until I took the Python scripts out, now 6.07 launches fine, but no Python, no biggie, I only went to 6.07 tonight to get this going. 6.07 is broken with the same script files from 6.03 copied over. Makes sense, maybe I can fix 6.07 by tweaking the right files. It'll make more sense in time.
Either way, 6.03 and I'm on my way. Whoohoo!! 'Simple_OSC_Client' crashes 6.03, maybe I can suss that out.
MANY thanks! If there's anyway I can ever return the favor, please PM me. Thanks again for your always helpful posts.


On to figuring this thing out.
Either way, 6.03 and I'm on my way. Whoohoo!! 'Simple_OSC_Client' crashes 6.03, maybe I can suss that out.
MANY thanks! If there's anyway I can ever return the favor, please PM me. Thanks again for your always helpful posts.

On to figuring this thing out.
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz