Charles Baker

Noticed that some published m4l patches(notably monomeemu launchpad monome emulator) that use js LiveAPI are failing now that I have changed to Max6 for my m4l ... the issue is where it calls to gather array of control devices: the orig js getDevices/count calls are to a toplevel API object, but in all non-js m4l API example patches, we query the path obj for list of extant devices...am I just missing the doc I need to read to understand this issue? (like docs for the js wrapper for LiveAPI?)

I want my monome emulator back. What da heck did I do to it? ;-)...

Thanks for any input.
CharlieB
cfb
aka
j2k


max6-changes-in-liveapi

I find there are a lot of conflicts with updated abstractions, doesn't help in the slightest when none of the changes have been documented, it should at least be backwards compatible, not at all impressed!

Darren, The updated abstractions you talk of, are these updated M4L abstractions or general Max abstractions. I've just stumped up for the 6 upgrade and am wondering if I should stick to 5.19 for M4L applications. It would be a pity because the 6 upgrade is great but I have a feeling official support within M4L is a very long way off.

JM
------------
http://soundcloud.com/leftside-wobble


I believe the official word is that sticking to 5.1.9 as your M4L editor is the safest bet until a new version of M4L is released.

Cheers Stringtapper, I understand the official word but was wondering which abstractions had been changed in 6 undocumented. I've already made a couple of devices using Gen abstractions which sound fantastic and I only changed the Max path to 6 (within Live) whilst designing those devices. In general I use 5.19 but I was trying to gain further insight to S4racen's comments as I know him to have a fairly deep knowledge of M4L in particular.

Ah so, I was wishful, but... I too have been itching to host some Gen work in m4l...well, it was worth a try.

Will wait for now, given little choice. :-)

Ah so, I was wishful, but... I too have been itching to host some Gen work in m4l...well, it was worth a try.
Will wait for now, given little choice. :-)

We absolutely support the use of Max 6 for MFL. Go for it.

I'm sorry to hear that there has been some confusion with some abstractions. If you feel like it, please detail them for us in support so we can try and figure out what happened.

We actually tried to introduce nothing new at all, but it may be that some fixes or changes slipped by.

We actually tried to introduce nothing new  at all, but it may be that some fixes or changes slipped by.

I am loath to publically query about specific code issues in another user's software: I will isolate a specific ? in code and 'genericize' it before posting the question. After day job. :)

the JS->LiveAPI issue us the only thing I've seen since going to Max6 for M4L...

I am loath to publically query about specific code issues in another user's software: I will isolate a specific ? in code and 'genericize' it before posting the question. After day job. :)
the JS->LiveAPI issue us the only thing I've seen since going to Max6 for M4L...

Did anyone ever find a resolution to this issue? It seems like a lot of patches have been broken due to this.

It would be great if someone could point out the differences between the getdevices/count call in Max 6 as opposed to what was possible in max 5.

It would be great if someone could point out the differences between  the getdevices/count call in Max 6 as opposed to what was possible in max 5.


Max6 - changes in LiveAPI?