RhythmVAE_M4L
RhythmVAE_M4L copied to clipboard
[Windows] node.script: Node script not running, can't handle message midi
Hello Nao Tokui,
I can't run it. And the message is "node.script: Node script not running, can't handle message midi".
I have latest Node.js installed, and Live is 10.1.9; Max is 8.1.3. I clicked the "edit" button of built-in max-instruments and Max 8.1.3 can be launched correctly.
evil,
Did you get this to work? I am running Windows 10, Ableton 10.1.30, Max 8.1.8, getting roughly the same message:
"node.script: Node script not running, can't handle message loadmodel"
Change the node modules folder name from napi-v5 => napi-v3
Have you solved this problem?? Thanks for your advice @mcwebdev
Hello @naotokui Thank you for creating this device!
Unfortunately I am having the same issue as @eviluess Upon downloading I don't seem to have the same files as @mcwebdev so I can't implement his solution. I am running: Mac Osx 10.14.6 Max for live 8.1.7 (I don't own Max standalone. Is this an issue?) Ableton 10.1.3
Is there any other software I'm missing?
I've attached the Max Console messages in this transcript: Nao Tokui M4L_Rhythm Max Script.docx
I'm interested in implementing this for PhD research in Australia. Please let me know if there is a resolution. Let me know if I can help! :)
Thank you for your time!
Hi @Makejorton
Could you try the following steps?
- Open the device in Max in Ableton.
- Find and click
script npm install
button on the top left. (Make surenode.script debug tool
tells youNPM Command Succes
) - Click
script start
- Close the device and Drag & Drop some MIDI files. If the device shows
# of bars in train. data
, then it means everything works fine.
Hope it helps!
Hi @naotokui I'm facing a similar issue trying to run your m4l device. I've followed all the steps mentioned above and also in your last reply here. In the Node.script debug tool: I get the confirmation after pressing 'script npm install', but when I press script start', I get the following error message:
failed to create process. File C:[...]AppData\Local\Temp\MAx64\M4L.RhythmVAE_coll_u153000708\rhythmvae.js not found. Please ensure the path argument to [node.script] is correct and valid
I had tied moving the amxd file from the release folder to the main folder - that caused a bunch of different error messages, so I've reverted. Also changing the foldername of the tensoflow node folder from napi-v5 to napi-v3, as @mcwebdev suggested, didn't change the result.
I'd really appreciate any effort to help solve the issue - your device looks incredible and I'm really keen to play with it.
Hi again, I've tried a few more things to get this device to run, unfortunately without success, so I'd still appreciate any help.
I've went through the installation steps again, made sure that the external Max runtime is set in Ableton, which I seem to have overlooked previously, but the result in unchanged... I open the device, click 'script npm install', which shows a green success message in the node.script debug tool. When I click 'script start' after that, I get an error message though.
node: message Unable to launch process node: details The Node.js native addon module (tfjs_binding.node) can not be found at path: C:\Users\kuhn-\Documents\Ableton\User Library\M4L\RhythmVAE_M4L-0.72\node_modules@tensorflow\tfjs-node\lib\napi-v5\tfjs_binding.node. Please run command 'npm rebuild @tensorflow/tfjs-node build-addon-from-source' to rebuild the native addon module. If you have problem with building the addon module, please check https://github.com/tensorflow/tfjs/blob/master/tfjs-node/WINDOWS_TROUBLESHOOTING.md or file an issue. node: stack Error: The Node.js native addon module (tfjs_binding.node) can not be found at path: C:\Users\kuhn-\Documents\Ableton\User Library\M4L\RhythmVAE_M4L-0.72\node_modules@tensorflow\tfjs-node\lib\napi-v5\tfjs_binding.node. Please run command 'npm rebuild @tensorflow/tfjs-node build-addon-from-source' to rebuild the native addon module. If you have problem with building the addon module, please check https://github.com/tensorflow/tfjs/blob/master/tfjs-node/WINDOWS_TROUBLESHOOTING.md or file an issue. at Object.
(C:\Users\kuhn-\Documents\Ableton\User Library\M4L\RhythmVAE_M4L-0.72\node_modules@tensorflow\tfjs-node\dist\index.js:49:11) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Object.Module._load (node:internal/modules/cjs/loader:822:12) at Function.Module._load (C:\Program Files\Cycling '74\Max 8\resources\packages\Node for Max\source\lib\nsRunner.js:67:24) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:94:18) at Object. (C:\Users\kuhn-\Documents\Ableton\User Library\M4L\RhythmVAE_M4L-0.72\rhythmvae.js:5:12) at Module._compile (node:internal/modules/cjs/loader:1101:14) node: code 6
This is far beyond my paygrade, but I'm hoping that this makes sense to you and that it helps you figure out what's wrong.
Btw, I'm using Windows 10 Home (Build 19044), Ableton Live 10.1.42 and Max 8.1.11