hey there,
i just tried to do some basic stuff with M4L, and get no result of calling the live.path object. are there any restrictions to the demo or is there something that i had to consider during installation/startup? i am running live 8.3 with latest max/max runtime on win7 64 bit with UAC disabled.
thx!
live.path
Re: live.path
ah okay.. problem solved!
i am developing a lot of python scripts, thats why i cleaned up my midiremote scripts folder... and also kicked some library folders like _mxdcore and _generic...
so max4live is basicly nothing else then a connection to python??????
is it then possible to get some accurate python callbacks triggered through max4live??!?! (like i was asking here viewtopic.php?f=1&t=179893 )
btw.. what a forum?! no scripting nerds here?
i am developing a lot of python scripts, thats why i cleaned up my midiremote scripts folder... and also kicked some library folders like _mxdcore and _generic...
so max4live is basicly nothing else then a connection to python??????
is it then possible to get some accurate python callbacks triggered through max4live??!?! (like i was asking here viewtopic.php?f=1&t=179893 )
btw.. what a forum?! no scripting nerds here?
Re: live.path
m4l allows callbacks to the api...
javascript / java (mxj) / and native max patching...
are supported..afaik
timing is slaved to max (within m4l)..
which is tied to the Live transport..
javascript / java (mxj) / and native max patching...
are supported..afaik
timing is slaved to max (within m4l)..
which is tied to the Live transport..

Re: live.path
yep, already did some tests, step sequencer runs smooth now 
