Thanks, but in my case I got the pain from the beginning. First of all I've got the error message in node.debug, which says "Process terminated due to an uncaught exception, missing values for outlet call". Then I couldn't find an information about how to setup the project, whether I need to use specific version of node.js or not, or should I make "npm init" in my project folder, if I don't use external libraries. The most discouraging thing is that even in minimal code only with max-api import and maxApi.post() I get errors
This is great! Any chance the patches used in this video will be made available? I have never interfaced Java with Max, so any help would be greatly appreciated. Node seems like it will be the most useful way for them to communicate - looking forward to this feature!
@@dude837 well, there's a "max-api" node module, and maybe a Max4Live one as well. Can't imagine why there wouldn't be. In which case I'm not quite seeing the point of using the old js scripting.
Node for Max really lets you connect Node to Max, but there's not much in N4M itself for controlling Max. Sure, you can send messages and print to the console, but you can't do stuff like create and connect objects. That's why I say "this is what the JS object is for". We could write a "max-for-live" Node module, but it's not in the works currently.
@@dude837 fwiw I'm way more of a js than Max person, but contemplating getting back to Max. I'd see myself wanting to make M4L devices that lean quite heavily on LOM and probably with as much on the js (preferably node) side as possible. I guess I'll understand a bit better the context of the different execution environments as and when I get around to digging in. Is Node running in an independent process per max node object? Any differences in overheads of getting data in and out etc?
Been having a lot of fun with node 4 max. Great introduction. Thanks for sharing!
Super excited about this node.js integration. Nice overview thanks.
exciting stuff, can't wait to see what people come up with!
Thanks, but in my case I got the pain from the beginning.
First of all I've got the error message in node.debug, which says "Process terminated due to an uncaught exception, missing values for outlet call". Then I couldn't find an information about how to setup the project, whether I need to use specific version of node.js or not, or should I make "npm init" in my project folder, if I don't use external libraries.
The most discouraging thing is that even in minimal code only with max-api import and maxApi.post() I get errors
Holy crap. I guess it's time to buy that upgrade.
Hi, I want to learn Max and start working with the project. Let me know any tutorials for this.
Good to know about node!
How did you connect your phone to n4m.squiggle?
This is great! Any chance the patches used in this video will be made available? I have never interfaced Java with Max, so any help would be greatly appreciated. Node seems like it will be the most useful way for them to communicate - looking forward to this feature!
Hey, thanks for watching! The github repo mentioned near the end of the video will eventually contain a version of all of the patches we used here.
Wow, this is so so so cool!
great - any chance of the shown examples getting uploaded to the github?
Absolutely! Should be up soon.
The examples have been added, check out the updated repository.
So can you or can you not script Max or the Live Object Model etc from a node script?
You cannot, or at least not without some extra work. That's what the JS object is for.
@@dude837 well, there's a "max-api" node module, and maybe a Max4Live one as well. Can't imagine why there wouldn't be. In which case I'm not quite seeing the point of using the old js scripting.
Node for Max really lets you connect Node to Max, but there's not much in N4M itself for controlling Max. Sure, you can send messages and print to the console, but you can't do stuff like create and connect objects. That's why I say "this is what the JS object is for". We could write a "max-for-live" Node module, but it's not in the works currently.
@@dude837 ok, thanks for the info.
@@dude837 fwiw I'm way more of a js than Max person, but contemplating getting back to Max. I'd see myself wanting to make M4L devices that lean quite heavily on LOM and probably with as much on the js (preferably node) side as possible.
I guess I'll understand a bit better the context of the different execution environments as and when I get around to digging in.
Is Node running in an independent process per max node object? Any differences in overheads of getting data in and out etc?
sister of the sam!
awww i love dogs !
It's really "happy patching"