NodeJS not working in macOS Big Sur
Aug 30 2020 | 3:43 pm
I've tested Max 8.1.5 in the latest beta of macOS Big Sur (20A5354i) and the `node.script` object doesn't work:
- Aug 30 2020 | 4:53 pmDid you tested also standalone Node.js?
- Aug 31 2020 | 6:55 amYes, Node works without problems in Big Sur:
- Sep 02 2020 | 9:18 pmSo perhaps the best temporary solution is to use Node.js standalone and communicate with Max via websockets or OSC?
- Sep 03 2020 | 7:24 amWell, I hope there's going to be a fix at some point :)
- Sep 03 2020 | 9:55 pmBig Sur is, as far, available as "beta" so there is a room to fix it on time (I'm not sure on Max or MacOS side). Recently I also started to see the benefits of using Node "inside" Max, and I think it makes a serious advantage.
- Oct 06 2020 | 6:14 pmJust to inform, this is still not working in 8.1.6 and the last version of Big Sur.
- Oct 19 2020 | 8:32 amNode for Max should be working in Big Sur under Max 8.1.7.In general, we don't go out of our way to support prerelease OSs, since they often have prerelease bugs which get fixed before the RC is provided. In this case, though, we were able to identify the problem and fix it in a way which should be both backward and forward compatible.
- Oct 21 2020 | 9:09 pmConfirmed it's working now in Max 8.1.7.
In general, we don't go out of our way to support prerelease OSs, since they often have prerelease bugs which get fixed before the RC is provided.I'm sorry if my message sounded like I was demanding to fix this problem now. I was merely trying to inform about something I noticed, and that will eventually become a problem once the new OS version is released.