Node: Unable to launch process manager
Have had all patches with Node for Max (including one I am working with, based on Twitch Plays Max which includes the tmi library) break completely several times recently. I'm on Windows 10.
On opening a patch, the Max window sometimes prints " Node for Max: unable to launch process manager"
and when running a node.script, no message comes up when sending a start message, but other messages (including stop) produce "node.script: node process manager not running"
I thought I had fixed this problem twice by playing with the PATH/environmental variables, which got it working for a session on two separate occasions. And yet, next time I open Max....same thing! It happens in all the Node example/overview patches as well.
Has anybody dealt with this before? It's strange that it doesn't work now, as my Node installation is definitely in PATH. (Strange that this fixed it even temporarily)
Thanks for any help!
Please get in touch with our support as this is likely something specific to your setup and we'll need to know more details. As a sidenote - Max ships with its own Node and NPM binaries so it doesn't require you to have / add that into your PATH.
Thanks
thanks a lot Florian, I have sent an email already and was asked to send on the support information, waiting to hear back now. looking forward to resolving this.
In the meantime I found a way to work around this by recreating the script in Python and using udpreceive in Max... works equally well, although harder to share the patch with someone else this way.
The weird thing is that I was able to replicate this on a second laptop which has a pretty much fresh installation of Windows and Max.
Hi Sebastian,
just following up here as I'm still curious what might cause this and would like to help you resolve the issue. Not sure what "fresh installation" means in detail but I'd just like to make sure that there isn't something that is getting in the way.
One additionally helpful step we could take is to have Node For Max generate a Debug Log. You can enable this in the Max preferences in the Node For Max section by ticking the checkbox and ensuring a filename and folder is set.
You might have to restart Max but once you instantiate a node.script object or just open the helpfile, there should be a log file being put in place. If that's the case it would be great if you could send this with your support communication.
Thank you again,
Florian
Hi Florian, Sorry for the slow reply!
Just now, I did a clean install (i.e. deleted the Cycling74 folder from AppData/Roaming folder and then reinstalled). Also updated Max to the new version 8.1.10 - still have the same problem.
I just turned on the Node debug log and set location to my desktop, and it just doesn't make a log at all- it's like Node is just not working at all. Have tried with my patch, node help files etc.
I just double checked the patch on my laptop (the one with the fresh installation) and my patch + Node help files are now working there on the laptop... All that has changed with that laptop is that it's possibly had a windows update: but the desktop has been through two or three windows updates during all of this which have not changed anything.