[SOLVED] Bug in Max4Live API tools

Learn about building and using Max for Live devices.
lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

[SOLVED] Bug in Max4Live API tools

Post by lalo » Fri Apr 01, 2011 1:07 pm

UPDATED 04 april 2011.

problem solved i have to delete an old version of js32mt.dll wich was located in my windows\system32 dir.
i deleted it.
now i can see the MaxAPI paradise workin' as it should do!

thanks to everybody helped me to solve this stuff

all the best

a.




hi.
when i open any lessons and/or any davice related to API Tools i can't get any values in the track/device/parameter fields of any API tool and the arrows in the 3 fields are just grayed out and i can't select anything

i've installed and authorized Live 8.2.2 and Max 5.1.8 ( latest non beta versions ) and Max4Live pack report to be 2.1

any clue?

thanks

a
Image

Uploaded with ImageShack.us]

Uploaded with ImageShack.us
Last edited by lalo on Mon Apr 04, 2011 11:08 am, edited 1 time in total.

TriangelKlang
Posts: 21
Joined: Fri Nov 20, 2009 11:45 am

Re: Bug in Max4Live API tools

Post by TriangelKlang » Fri Apr 01, 2011 8:29 pm

Same Here

Yes I have a Max License

Yes I've tried that way

after I did a repair Library

Vista Home Premium 2Quad 2,33GHz 3,00 RAM

All the Best

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Fri Apr 01, 2011 11:49 pm

TriangelKlang wrote:Same Here

Yes I have a Max License

Yes I've tried that way

after I did a repair Library

All the Best
same here. i tried a lib repair but nothing...
i'm on win xp pro sp3 . intel centrino dothan 2.0 ghz with 2 gb ram

abstractblack
Posts: 3
Joined: Fri Feb 06, 2009 6:14 pm
Location: Chicago

Re: Bug in Max4Live API tools

Post by abstractblack » Sat Apr 02, 2011 1:53 am

i have the same problem on a MacBook Pro 15" OS 10.6.5 from early '10 with full authorization of Suite 8 and Max for Live and I get nothing listed in the umenu windows of the Max Api Ctrl1LFO and Envelope follower, haven't gotten pass these as far as API devices go. What gives? I click list, click drop down arrows and nothing. Where are the special magic instructions on this? Do I need to load something first, do a head stand, keyboard kick flip? I've had problems with the umenu in other people's devices like Ms Pinky as well. My Cindy Lauper sampler could use this fix...


and i was just about to propose marriage to ableton live, she'll have to be fixed before we hitch...
8O

abstractblack
Posts: 3
Joined: Fri Feb 06, 2009 6:14 pm
Location: Chicago

Re: Bug in Max4Live API tools

Post by abstractblack » Sat Apr 02, 2011 2:15 am

tried to edit Max Api Ctrl1LFO and that attempt crashes Live every time. and my Live Reports apparently have uncleanable viruses such that I can't even send them through to Ableton.

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Sat Apr 02, 2011 7:49 am

so we have a problem here :?:
too bad is week-end...i guess we have to wait 'til monday. :cry:

...let's do some music and/or enjoy the sunshine ( almost summetime wheather here in center-north italy...at least we still have a very few good things in this country :roll: )

willum070
Posts: 4
Joined: Thu Nov 05, 2009 2:38 am

Re: Bug in Max4Live API tools

Post by willum070 » Sat Apr 02, 2011 11:52 pm

I am having the same problem. I am running Live 8.2.2/Max 5.1.8 on Windows 7 Pro 64. When I open the Max API Ctrl1LFO.amxd for editing I get these errors:

js: LiveAPI: requires patcher argument
js: LiveAPI: requires patcher argument
js: LiveAPI: requires patcher argument
js: M4L.chooser.js: Javascript TypeError: api.menudata has no properties, line 603
js: error calling function bang

My guess is that the first three correspond to the Track, Device, and Parameter controls. I took a look in the patcher briefly but I think it would require some more in-depth debugging. I might take another look at it later. Glad to know I am not the only one seeing this!

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Sun Apr 03, 2011 12:16 am

hi shelluser.
i've upgraded as the instructions explain.
max for live content is version 2.1.
i've done the library repair but still no entries selectable
in track/device/parameter fields of every i mean every
api related device
all the best

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Sun Apr 03, 2011 12:27 am

ShelLuser wrote:None. I noticed that you already have a Max window open in there; did you already try to edit the M4L device or is this a Max instance which you ran prior to starting Live (in other words: do you also have a Max license?).
i do have a max license and i tried to edit the device after loading it in live.
ShelLuser wrote:What happens if you simply start clean (so start Live, no Max open or so) and then go to Audio Effects -> Max Audio Effect -> Tools -> API and manually pull in "Max API Ctrl1LFO" on your Midi track ?
happens that nothing appears in the 3 fields track/device/parameter and i can't open
the umenu and its arrows are greyed out.
ShelLuser wrote:You obviously get a M4L splash screen, it probably leaves some room open in front of the device but can you click on the white box below "Track" ?
now i'm on ipod. i'll check it tomorrow

ShelLuser wrote:Also; does anything happen if you click on "list" first ?
nothing happens.
thanks

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Sun Apr 03, 2011 10:43 am

ShelLuser wrote:
You obviously get a M4L splash screen, it probably leaves some room open in front of the device but can you click on the white box below "Track" ?
hi,
yes i can click on it...but nothing happens. the umenu does not open.
definetly something wrong here :?:

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Sun Apr 03, 2011 5:49 pm

thanks for the effort man!

here's my result of your procedure

Image

Uploaded with ImageShack.us

jeremydb
Posts: 64
Joined: Tue Jan 25, 2005 8:20 am
Location: Berlin
Contact:

Re: Bug in Max4Live API tools

Post by jeremydb » Mon Apr 04, 2011 7:20 am

ShelLuser wrote:Thanks for testing lalo, this is really helpful!

I come to the conclusion that its now proven that the problem is actually with the javascript file "M4L.chooser.js". The patch gets loaded and initialized ("loaded bang") and eventually you see that the javascript file spits out some kind of information (the 'device' and 'track' stuff) but with many errors. As such it somehow doesn't manage to get all the tracks and devices.

That is the reason why your umenu's don't work: they don't get filled with usable data because the javascript file doesn't work.

And because this test patch contains everything (frozen device and I also told the 'bpatcher' object to embed stuff) path problems are out of the question.


My conclusion: the M4L.chooser.js script has one or more bugs.

I have little experience with javascript, so unfortunately this is where my capacities come to an end. But hopefully someone from C'74 can shed more light on this.


In the mean time I kinda wonder why they resorted to javascript whereas the native Max environment could have provided the same kind of information (all tracks and all devices).

If time allows next week I'm going to see what happens if I replace their javascript code with a native patch of my own.

Still; I think we have provided a lot of information which C'74 should be able to use to get their fingers behind the problem.
Thanks for the information. We're looking into the problem.

As for why we "resorted" to Javascript: the JS interface is a) somewhat easier to use, since we have basically combined the features of live.path, live.object and live.observer in a single JS Object, b) more maintainable when designing complex behavior, and c) more efficient -- changing the "Poletti Chooser" from a Max to a JS backend sped up device load time by something like 7x.

Of course, if you don't like JS, or don't speak JS, there's nothing inherently wrong with using the Max objects for these tasks. I personally find certain programming concepts like iteration easier to manage in a procedural language such as JS.

jeremydb
Posts: 64
Joined: Tue Jan 25, 2005 8:20 am
Location: Berlin
Contact:

Re: Bug in Max4Live API tools

Post by jeremydb » Mon Apr 04, 2011 7:26 am

lalo wrote:thanks for the effort man!

here's my result of your procedure

Image

Uploaded with ImageShack.us
The posts in the Max window indicate that the Max object which contains the "definition" of the JS LiveAPI Object couldn't be found or loaded somehow.

Can you please look in your Max application folder (usually at c:/program files/cycling '74/max 5.0/), inside the "Cycling '74/jsextensions" folder, and let me know if there is a file called "jsliveapi.mxe"? If not, could you please search your hard drive for this file and let me know where it is (if it is there)?

Thanks
Jeremy

lalo
Posts: 55
Joined: Tue Feb 10, 2009 3:47 pm

Re: Bug in Max4Live API tools

Post by lalo » Mon Apr 04, 2011 8:36 am

jeremydb wrote:
The posts in the Max window indicate that the Max object which contains the "definition" of the JS LiveAPI Object couldn't be found or loaded somehow.

Can you please look in your Max application folder (usually at c:/program files/cycling '74/max 5.0/), inside the "Cycling '74/jsextensions" folder, and let me know if there is a file called "jsliveapi.mxe"? If not, could you please search your hard drive for this file and let me know where it is (if it is there)?

Thanks
Jeremy
hi jeremy,
yes i have the jsliveapi.mxe inside c:/program files/cycling '74/max 5.0/Cycling '74/jsextensions folder.

hope we get it solved soon :)

a.

jeremydb
Posts: 64
Joined: Tue Jan 25, 2005 8:20 am
Location: Berlin
Contact:

Re: Bug in Max4Live API tools

Post by jeremydb » Mon Apr 04, 2011 9:05 am

lalo wrote:
jeremydb wrote:
The posts in the Max window indicate that the Max object which contains the "definition" of the JS LiveAPI Object couldn't be found or loaded somehow.

Can you please look in your Max application folder (usually at c:/program files/cycling '74/max 5.0/), inside the "Cycling '74/jsextensions" folder, and let me know if there is a file called "jsliveapi.mxe"? If not, could you please search your hard drive for this file and let me know where it is (if it is there)?

Thanks
Jeremy
hi jeremy,
yes i have the jsliveapi.mxe inside c:/program files/cycling '74/max 5.0/Cycling '74/jsextensions folder.

hope we get it solved soon :)

a.
OK, I think I know what the problem is -- jsliveapi was (probably) accidentally compiled in such a way that it requires Microsoft's .NET framework installed. I don't see the issue on my machine because it's installed as part of the development tools I use. I'm investigating and will post a link to a new build shortly, assuming that this is the problem.

jb

Post Reply