Florian Demmer

With the just released 8.0.3 update of Max 8, Node For Max now supports bundling dependencies (aka the node_modules folder) within Collectives, Standalone Applications and Max For Live Devices. In order to give you a jump start into using this feature, this is a short guide on how to do it.

Let’s assume for the following that we are working on a Project called N4M-Bundler.

We start off by opening Max and creating a new Project using the File Menu called N4M-Bundler. In return Max will show us the Project Window, which can be used to organize the project’s files and contents. Since we don’t want Max to try to organize contents automatically, the first thing we’ll do is disable the “Keep Project Folder Organized” option in the Project Inspector. 

To open the Project Inspector use the Project Settings Menu:

In the Project Inspector disable the option "Keep Project Folder Organized":

You can now close the Project Inspector. We will now use the + Button in the bottom left corner in order to add our main patcher to the project by choosing "Add New File…" and creating a Max Patcher called n4m-bundler.main.maxpat

In order to verify what just happened we can use the Finder (Mac) / File Explorer (Windows) and look at the N4M-Bundler folder in the user’s Documents/Max 8/Projects folder. It should now contain a folder called patchers that includes our freshly created n4m-bundler.main.maxpat patcher.

In order to have a place to organize our content for node.script we will also create a folder called node_content next to the patchers folder. Our folder should look something like this: 

N4M-Bundler/
├── patchers/
│ └── n4m-bundler.main.maxpat
└── node_content/

2/ Adding node_content to the Project’s Search Path

In order make the files in our node_content folder available to the project we need to add it to the project’s Search Path. For that click on the Gear Icon in the Project Window and use choose the "Search Paths" option. Max will open another window that allows you to manage the Project's Search Paths.

Using the + Icon at the bottom left of this window we can add another entry, which should give you something like the following:

Now click the Choose Button in that new line and add the node_content folder we created previously. After that you can rename the entry to Node Content but most importantly you have to enable the “Embedded” option. Your Project's Search Path Window should now look similar to this:

We will now create the simple script for this test scenario. For that open the node_content folder in a text editor of your choice and create a file called n4m-bundler.js with the following content:

const Chance = require("chance");
const maxAPI = require("max-api")
const chance = new Chance();

const generateRandomName = async () => {
        const name = chance.name();
        await maxAPI.outlet(name);
};

setInterval(generateRandomName, 1000);

This uses a package called chance to generate a random name every second and outlet it to Max.

4/ Patching everything together and installing the chance module

We will now edit our Project’s main patcher and install the required chance package from NPM. The simple idea is to show the random name in a comment box. Start off by create a node.script instance pointing to our n4m-bundler.js file. Before we do anything else we will install the chance package by sending a message "script npm install chance" to the node.script object:

Once done you should find a node_modules folder and a package-lock.json in the node_content folder and can remove the message from the patcher. If you like, you can use Finder or File Explorer again to verify that your project directory looks something like this:

N4M-Bundler/
├── patchers/
│ └── n4m-bundler.main.maxpat
└── node_content/
│ └── node_modules/
│ │ └── chance/
│ │ └── *** a whole bunch of files ***
│ └── n4m-bundler.js
│ └── package-lock.json

We will now use the prepend and comment objects to show the generated, random name. And add the script start and script stop messages to control our script:

Clicking the script start message should start the script and show a random name in the comment box every second. You can now stop the node.script using script stop.

We have now all the pieces of the puzzle at hand and can build our project. Choose “Build Application” from the File Menu, make sure the Format is set to Application and proceed. Max should now build a Standalone application containing our Patch, Script but also the chance module as a dependency.

The same would be true if we attempt to build either a Collective or a Max For Live Device.

Feel free to let us know if you have any further questions or feedback on this.

image2.png

image3.png

image5.png

image6.png

image1.png

image4.png

With the just released 8.0.3 update of Max 8, Node For Max now supports bundling dependencies (aka the node_modules folder) within Collectiv

node-for-max-bundling-in-collectives-standalones-and-max-for-live-devices

Thank you for your tutorial, but it seems there is something wrong here.

1. You wrote: "We will now create the simple script for this test scenario. For that open the node_content folder in a text editor of your choice and create a file called n4m-bundler.js".  But in the file listing the n4m-bundler.js file is located in the root project folder N4M-Bundler:

N4M-Bundler/
├── patchers/
│ └── n4m-bundler.main.maxpat
└── node_content/
├── node_modules/
│ └── chance/
│ └── *** a whole bunch of files ***
├── package-lock.json
└── n4m-bundler.js

2. You wrote: "We will now edit our Project’s main patcher and install the required chance package from NPM. <...> Once done you should find a node_modules folder and a package-lock.json in the node_content folder and can remove the message from the patcher." But the node_modules folder is created in the project root folder as well and not in the node_content folder:

├── patchers/
│ └── n4m-bundler.main.maxpat
└── node_content/
├── node_modules/
│ └── chance/
│ └── *** a whole bunch of files ***
├── package-lock.json
└── n4m-bundler.js

So, there is a question: why do we need this 'node_content' folder? Looks like the Node For Max bundling works well without creating the additional folder: add main patcher and js-file to the project and then point to the 'node_modules' folder to the project search path.

Can you, please, bring a little light on this issue?

thanks for pointing this. And yeah sorry, it was in fact a mistake in these ASCII folder structures.

If things work for you without the node_content folder: great! However, we do recommend the usage of a separate folder (node_content in this example) for the node related content in projects. The reasons for that are mostly practical. It's easier to find/navigate the Node related content and we provide a sort of space for npm to do it's disk related work (writing/altering node_modules, creating debug logs etc) in order to avoid having it change the project's root folder. Also in more complex cases you'll be including more user authored JS files for Node For Max  that are required/used for your script. This way adding a folder to the project ensures that they will be bundled as well.

Hope that makes sense? Thanks for following up and pointing out the little issue in the folder structures,

Yes, now everything works as expected. Thank you for this useful tutorial!

Hey Florian,

A very detailed guide, thanks. When i run the script npm install <package-name> in my case, axios, the package is installed and the patch does what it's supposed to do, a http request.

However, my finder does not show any package.json or node_modules created. So the npm is installing the packages elsewhere. This would be a problem for bundling and distribution. Any ideas?

glad it's working for you. In terms of the installation location - it's kinda hard to pin that down given the limited information but I can try.  To make sure you don't have any naming conflicts you can send a reveal message to node.script that should show the location of the file in your Finder or File Explorer. Is there a node_modules folder next to the file that gets revealed? If you are facing a naming conflict, we highly recommend namespacing your files, fe n4mtest.index.js where n4mtest would be the project specific namespace.

Fwiw,  npm install will  extend the dependencies of a pre-existing package.json file but not create one (only the package-lock.json gets created). The minimum requirements are a name and version field (you can learn more about the package.json here):

{
  "name": "mypackage",
  "version": "0.1.0"
}

Hope that helps a bit with understanding the functionality of npm install? Curious to see if there is in fact an issue with multiple files having the same name in your search path or if something else is at play.  Let me know and I'm happy to assist further.

Hi Florian,
Thanks for this, super helpful for what I'm trying to do. I'm running into an error where the node_content folder can't be added to the  application, and I'm not sure why.  The Max Console reads as follows...

Adding file message.mxe64
Adding file prepend.mxe64
Adding file comment.mxe64
Adding folder node_content
Unable to add node_content!
Investigating Audio Status.maxpat...
Saving Patcher Audio Status.maxpat...
Copying External live.numbox
Copying External adstatus
Copying External umenu
Copying External metro
Copying External number
Copying External substitute
Copying External toggle
Copying External pak
Copying External speedlim
Copying External delay
Copying External button
Copying External js
Copying External bgcolor
Copying External universal
Copying External ubutton
Copying External zl
Including File interfacecolor.js
Copying External led
Copying External textbutton
Copying External panel
Copying External spray
Copying External Uzi
Copying External loadmess
Copying External !-
Copying External buddy
Copying External dspstate~
Successfully built project N4M-Bundler to application.

(emphasis mine)

There are no other errors, and the application opens just fine, but obviously can't find the n4m-bundler.js file. I'm running Windows 10, 64 bit.

I'm at a loss as to why this could be happening and I appreciate your help. 

Thanks!
Stepan

Thanks for the reply Stepan. Please get in touch with our support as we might have to get a copy of your project in order to be able to reproduce the issue.

The issue " STEPAN DYACHKOVSKIY " mentioned is solved?
I have the same problem.

Adding folder node_content
Unable to add node_content!

I'm also running Windows 10, 64bit.
Thanks in advance.

I cannot reproduce the issue here on my end. If you still encounter issues with bundling on Windows please get in touch with our support so we can help you in a more detailed fashion.

Just a quick reply for the others having problems to have a working build on Windows (Max 8.1.3/64 bits).
If you try to build the standalone from the project window (menu : "Manage Project > Build Collective/Application..." ) it doesn't work (you should have the message 'Unable to add node_content!' in the Max Window).
If You build using the menu "File > Build Collective/Application..." in the main patcher window, it works flawlessly.

Hi Florian,
Never got a chance to thank you for writing this.
Just a quick note that second picture caption has a typo: Disbale
And I would like to request this information to be added to Max built-in documentation.
(node.script help patch)

@Omar thanks for the pointer, just fixed the typo. AFAIK the info is bundled with the Max application in the Working with Projects, Max For Live Devices, and Standalones. You can find the same content here:

https://docs.cycling74.com/max8/vignettes/03_n4m_projects_devices 

It would seem that this process is broken on MacOS Monterey. Using the node.script "open folder location" icon, it would seem that all of the javascript files are being sandboxed in a directory in the user library, and none of the node modules are being copied over.

Hi Eric,
thanks for the reply. Was this working successfully before on a different version of macOS?

Would you mind getting in touch with our support with a bit more insight on your project, workflow and version of Max that shows that issue in order for us to be able to investigate further if that's a general issue or something specific?

Thanks
Florian


Yes this is an internal application that we’ve been using since 2018 with previous versions of macOS.

I will reach out to the support team as you requested.

I still have the same issue Eric mentioned, Max 8.3 OSX Monterey. The nmp modules are not copied into  the dir Content/Resources/C74/packages/Node\ for\ Max/source/node_modules/ ,  and the package.json (v. 2.0.4)  does not declare them while  they are into the Project's package.json. So that the app tells that the script can't start (not ready).
Is it already solved in some way ?

why don't you copy files manully ?
At same time you could trash unneeded files from the package....


Node For Max Bundling in Collectives, Standalones and Max For Live Devices

Trevor being Trevor

//Some half Pseudocode that hopefully makes sense of my problem
var isNotDone = true;
var waitCounter
tsk = new Task(repeater_function, this)
tsk.interval = 100;

function repeater_function(){
    //do a task eqivalent to sending a note value out an outlet
    waitCounter++
}

while(isNotDone){
    *** a bunch of code ***
    
    if(certain condition is true){
        tsk.repeat(20);
        
        while(waitCounter < 20){
        // do not pass go, do not collect 200 dollars,
	// i.e. do nothing until tsk.repeat(20) is done
        }
    }
    
    ***more code below***
}

I need to delay a series of events, hence the task object, but I also need to make sure the rest of the code waits until that series of events is complete to move on to the code below. Is there a way to do that without creating an infinite while loop as I have done above? I can't seem to find a way to accomplish this at least without a fundamental rebuild of how the rest the code is structured. 

I am willing to use other methods such as Max Externals, but I need to access the Live API. As always, any advice is greatly appreciated!

//Some half Pseudocode that hopefully makes sense of my problem
var isNotDone = true;
var waitCounter
tsk = new Task(repeater_function, ... 

make-javascript-scheduler-wait-until-a-task-object-is-done-repeating

A little tough to answer from the pseudo code since no where do you set the conditions which terminate either of the while loops.

But mainly I think the troubling thing is that in your outer while loop, executing the code inside the “if” doesnt block execution of the “more code below” in the first iteration.  

Scheduling/running the task makes the task code asynchronous, and evaluation of the parent context will continue regardless of the task condition/evaluation.

so put the evaluation of the counting (rather than just the incrementing) inside the task callback. and when the task has been called 20 times, call the ***more code below*** from within the task (or by a function call inside task callback), and cancel the task.   I usually use repeated individual calls to task.schedule(), which you can re-call from within the task callback itself if needed, rather than repeat(), fwiw.  I think for indeterminate duration operations it works better.

Also, Rather than a bool isNotDone you could have an integer for the critical stages:

0 (not running)
1 (initial condition set)
2 (waiting using task)
3 (task is complete)

it would add more clarity to understanding the overall control flow process.

"Scheduling/running the task makes the task code asynchronous, and  evaluation of the parent context will continue regardless of the task  condition/evaluation."

Okay that makes a ton of sense. I have some ideas on how to call the next iteration within task function now. Thanks! I will add more detail to my Pseudocode just to clarify and 'fix' the other things you mentioned. 

//Some half Pseduocode V2
//this is still simplified, but hopefully allows us to focuses on the problem better

var waitCounter = 0;
tsk = new Task(repeater_function, this)
tsk.interval = 100;

function repeater_function(){
    //do a task eqivalent to sending a note value out an outlet
    waitCounter++
}

//the main goal of this loop is look through a list for a set of matches
//and then do something if it finds a match
//I included this while loop in the pseudocode because it makes
//makes calling the code that needs to come after it from within the task function
//not as easy of switch up. I wondered if I needed to something like this
//but wasn't sure until tyler helped clarify some things. Plus the code,
//was working pretty efficiently otherwise so I didn't want to give it up.
//Appreciate the help
 
while(There are still list items to check && there are still things to check for){
    
    //begin checking each item in the list for the first item i am looking for
    
    if(a match in the list is found){
        waitCounter = 0;
        tsk.repeat(20);
        
        while(waitCounter < 20){
        // do not pass go, do not collect 200 dollars,
	// i.e. do nothing until tsk.repeat(20) is done
        }
    }
    
    //increment a counter to start looking for the next thing
}

Make Javascript (scheduler?) wait until a Task object is done repeating

Christopher


I  have pasted together, with all my love, this .js-file to run in node.script. (absolute Javascript rookie).
Via node-record-lpcm16 it accesses the microphone and streams the audio to the Deepgram API. The latter transcribes it and it shall be output as text through node.script’s outlet to MAX. Deepgram takes care of all the parsing and endpoints of speech, good quality stuff!

Running the .js through node in terminal works (therein not running the maxApi-part, of course), but when running in node.script it crashes with the debugger saying:

Error: spawn sox ENOENT
	at Process.ChildProcess.handle.onexit (node.internal/child_process:282:19)
	at onErrorNT (node:internal/chil_process:480:16)
	at processTicksAndRejections (node:internal/process/task_queues:83:21)

I’d be so happy if anyone had any ideas… Or alternatives how to access a microphone for the Deepgram API.

(Of course I have an API key, runninng LTS of node, all the packages are installed – maybe it is some file localization trouble?)

DeepGramSTT.maxpat

STT.js

Hi guys n gals,

 

 

I  have pasted together, with all my love, this .js-file to run in node.script. 

node-script-error-in-speech-to-text-application

I don't know if this is helpful, but I might as well put it out here: I've been working on a similar project in node.js using Vosk, and I'm having a similar experience -- it runs fine in the Terminal, but in Max I'm getting a spawn error for 'rec', which is also part of the SoX package.

I was guessing that it might have been a $PATH issue with SoX, but that looks good on my end, so it might be some other kind of Max/SoX crankiness.

You might want to check your $PATH situation with SoX -- a possible longshot, but worth checking, I guess. Have a look at this thread:

https://cycling74.com/forums/sox-in-node-js

thank you for all the hints, gotta be some Max/SoX crankiness....

And thanks for pointing me to https://cycling74.com/forums/sox-in-node-js. Pulling SoX into the PATH variable at runtime, as pointed out by Florian Demmer, worked perfectly for me – you're a life saver!

Also, I might check out Vosk – my free DeepGram credit is deplenishing rapidly...

I'm leaving the fixed patch here if anyone cares, it's working Speech-to-Text, not fine tuned however...

Chris

Glad to be of help -- unfortunately, still isn't working for me -- I'll have a look at your code though, & see if that helps!

I was looking at Vosk because the dictionary resides on your machine, so no lookup delay....

Hey Christopher,
Being a lazy-ass, I assumed that since $PATH was returning /usr/local/bin (where my copy of sox lives), my script would find it, but forcing it with the split did it! Thanks for inspiring me to get off my ass!

Glad to be of help -- unfortunately, still isn't working for me

Just FYI, I'm having pretty good results with Vosk, especially the larger models. They're a tad slower than the smaller ones, but definitely more accurate... have you checked it out?

Filterlo is a premier online retail company, offering a wide range of refrigerator filtration products. Our goal is to provide customers with the best shopping experience available on the Internet.
Everydrop Water Filter 3 - EDR3RXD1

node.script Error in Speech-to-Text-Application

tiago morais morgado

https://hastebin.com/share/tibipuweza.javascript 
i am trying to invoke objects, by scripting names, and sending them messages inside node.script.
how could this be possibly fixed, optimized, and iterated?
vielen danke/thank you so much/dank je well/merci beaoucoup/muchas gracias/ muito obrigado/grazie mille/gratias tibi valde

https://hastebin.com/share/tibipuweza.javascript 
i am trying to invoke objects, by scripting names, and sending them messages inside ... 

trying-to-invoke-objects-by-scripting-names-and-sending-them-messages-inside-node-script

http://paste.wooledge.org/18771
if you have trouble opening hastebing, here you have another link

Have you checked that this is actually possible? Node.script runs outside of Max in a separate process. It could be, I haven't used in a while so I don't know if this is part of the Node API, but expecting node scripts to be able to do the things that JS object scripts do is a frequent source of confusion and frustration!

trying to invoke objects, by scripting names, and sending them messages inside node.script

John J.A. Jannone

Hey all,
I'm successfully downloading base64 PNG files using an http request, but I can only save them up to about 120x120 pixels. I'm guessing I'm hitting a size limit somewhere in node.js...

const path = require('path');
const Max = require('max-api');
const fs = require('fs');
	
Max.addHandler("png", (data) => {
	var buf = new Buffer(data, 'base64');
	fs.writeFile('image_temp.png', buf,  function(err, result) {
     	if(err) post('error', err); });
});

test.maxpat

Hey all,
I'm successfully downloading base64 PNG files using an http request, but I can only save them up to about 120x120 pixels. 

saving-large-base64-images-with-node-js

Tried this - did not work - maybe I'm importing node:buffer incorrectly? I get "Buffer.alloc is not a function."

const Buffer = require('node:buffer');
const path = require('path');
const Max = require('max-api');
const fs = require('fs');
	
Max.addHandler("png", (data) => {
	var buf = Buffer.alloc(262144, 'base64');
	data.copy(buf, data);
	fs.writeFile('image_temp.png', buf,  function(err, result) {
     	if(err) post('error', err); });

Max.outlet("done");

});


hey John, this n4m code last ran in 2021, but it did write base64 images (coming in from Runway-ML) to disk as png images at 1024x1024. I couldn't tell you everything this code is doing (especially that string replace on the first line), but here it is in case it's useful:

//////////////////// Save base64 image into local disk //////////////////////////////////
function writeBinaryImagesToDisk() {
    // m.post(base64String) //base64 image
    let base64Data = base64String.replace(/^data:image\/\w+;base64,/, '')
        // m.post(base64Data) // remove first part of the string
    let binaryImage = Buffer.from(base64Data, 'base64')
        // m.post(binaryImage) 

    // lodash library enumerate the generated file names
    let imgNumber = _.padStart(count, 4, '0')

    // combine folder and image number
    let imgTitle = `${imgFolder}/image_${imgNumber}.png`

    // write a file with the image name in the folder, where the script is located
    // throws a warning:ERR_INVALID_CALLBACK. Ignore it...
    fs.writeFile(`${imgTitle}`, binaryImage, err => {
        if (err) m.post(err)
        //m.post(`The file ${imgTitle} has been saved!`)
        m.outlet("write", `${imgTitle}`)
    })
    count++
    //if (count <= framePerSecond * videoLength) {
        //setTimeout(generateImage(), 100) // delay time
    //}
}

... 
The above function called here
...

    const data = {
            z: a, //assign the generated latent space vector a to the Z space
            truncation: truncation, //variation in image generations - higher is more random, lower is more similar
        }
        // POST = send data (latent vector)
        // GET = request data (resulting image)
    axios
        .post(postURL, data)
        .then(() => {
            axios
                .get(getURL)
                .then((response) => {
                    //assign the base64 encoded image as string to the base64String variable
                    base64String = response.data.image

                    // call the function to save the base64 image in the png format
                    writeBinaryImagesToDisk()
                })
                .catch((error) => {
                    m.post(error)
                })
        })
        // .catch((error) => {
        //     m.post(error)
        // })

Yes thanks so much Rob! Had to mess with it a bit, but getting all image sizes now!

Saving large base64 images with node.js

klaus filip

i would like to use essentia.js from within max.
searching the forum was resulting in this thread:
https://cycling74.com/forums/timeout-error-in-long-n4m-process
where in a code from Florian Demmer appears essentia.js
i tried a bit from there, but did not get very far, 
except for listing the algorithm names as a proof for essentia.js is loaded.
can somebody please give me a hint where to go from here?
even maybe also sending audio from max?
i attach the basic patch..

Archive.zip

i would like to use essentia.js from within max.
searching the forum was resulting in this ... 

essentia-js-in-node-script

essentia.js in node.script ?

How can I get JSON like this into a dict?

"[{\"title\":\"512-depth-ema.safetensors\",\"model_name\":\"512-depth-ema\",\"hash\":null,\"sha256\":null,\"filename\":\"/Users/johnjannone/stable-diffusion-webui/models/Stable-diffusion/512-depth-ema.safetensors\",\"config\":null},{\"title\":\"v2-1_768-ema-pruned.safetensors [dcd690123c]\",\"model_name\":\"v2-1_768-ema-pruned\",\"hash\":\"dcd690123c\",\"sha256\":\"dcd690123cfc64383981a31d955694f6acf2072a80537fdb612c8e58ec87a8ac\",\"filename\":\"/Users/johnjannone/stable-diffusion-webui/models/Stable-diffusion/v2-1_768-ema-pruned.safetensors\",\"config\":null}]"

I tried several approaches, and eventually made this Max monstrosity to get something that worked (attached), but it seems there's got to be an easier way...

dict-test.maxpat

hierarchical-json-dict

Input of arrays of stuff is a pain.  But life can be much easier if you can do JSON handling in javascript...

That's great - thank you Tyler! I hope the max dict suite will eventually handle hierarchical JSON better, but this will do the trick for now, and I'll study it as well :)

hierarchical JSON -> dict

AudioMatt

So I get that I need to use getvalueof and setvalueof to enable parameter mode correctly in javascript and C.

But now it appears that JSUI reverts to _parameter_type blob every time I open my patch.   This disables most of the stuff associated with it.  What's going on here?

I'm using a copy of the default JSUI dial


EDIT:  Okay I can make it work if I put this in global code:
this.box.message("parameter_enable",1);;
 this.box.message("_parameter_type",1);;
 this.box.message("_parameter_invisible",0);;

but it's still not working in Ableton 10, only in Max

So I get that I need to use getvalueof and setvalueof to enable parameter mode correctly in javascript and C.
But now it appears that JSUI r

-jsui-parameter-only-in-blobs

Could you link me to some information how to use it in C? 

[JSUI] Parameter only in Blobs?

frank desben

Dear all,
I am getting this error message when trying to use the freesound example (from the Cycling74/n4m-examples github page) with node.script:
"node.script: No value for key FREESOUND_CLIENT_KEY in .env file. Please make sure to create a file called .env with a Freesound API Client key."
Can someone tell me how to fix this?
Thank you! Frank

Dear all,
I am getting this error message when trying to use the freesound example (from the Cycling74/n4m-examples github page) with node.s

node-js-freesound

Getting an API key

Before you can do anything with Freesound, you'll need an API key.

Get a Freesound account. It's free. Go to www.freesound.org and sign up.

After you've logged in go to https://freesound.org/apiv2/apply/

Fill in the form to apply for a new set of API keys.

You may notice that Freesound has fewer keys than Twitter. That's because Freesound only hands out client keys, not access keys. So, whereas using the access keys someone could post tweets from your Twitter account, the same isn't true for Freesound.

Anyway, note down the client ID and API key.

In this freesound folder, you should see a file named .env-template. This is an environment file, it contains key-value pairs that other applications, like Node, can load before running.

Duplicate the .env-template file to a new file named .env. It must be named .env, not my.env or anything like that. Fill in this file using the keys you got from Freesound.

You should be all set. Open the Max patcher freesound.maxpat and see!

In my folders I can't find the .env-template file,
is there a place I can download it?

You need to make invisible files visible for the folder in order to see it. On OSX, this is Cmd-Shift-.

Still, not working even after modifying the .env file, i run npm install and everything but the patch can't find anything

hi,
i can confirm, the example is not working.
my .env seems to be ok, the script is not complaining.
i can post my token with maxAPI.post("token", token); 
just before the freesound.textSearch
but nothing comes from response.
instead there is an "err" but without any error-code.


Node.Js Freesound

tyler mazaika

Live objects (e.g. live.numbox) output the rawfloat value out their right outlet.  Is there any way to get this value in JS?  

MaxobjListener listening to "value" gets the value output from the left side, and for my purposes I'd be much happier getting direct access to the rawfloat value without cabling.

Live objects (e.g. live.numbox) output the rawfloat value out their right outlet. 

Cycling '74 Forums

Node For Max Bundling in Collectives, Standalones and Max For Live Devices

why don't you copy files manully ? At same time you could trash unneeded files from the package....

Make Javascript (scheduler?) wait until a Task object is done repeating

"Scheduling/running the task makes the task code asynchronous, and evaluation of the parent context will continue regardless of the task ...

node.script Error in Speech-to-Text-Application

Just FYI, I'm having pretty good results with Vosk, especially the larger models.

trying to invoke objects, by scripting names, and sending them messages inside node.script

Have you checked that this is actually possible? Node.script runs outside of Max in a separate process.

Saving large base64 images with node.js

Yes thanks so much Rob! Had to mess with it a bit, but getting all image sizes now! const path = require('path'); const Max = ...

essentia.js in node.script ?

i would like to use essentia.js from within max. searching the forum was resulting in this ...

hierarchical JSON -> dict

That's great - thank you Tyler! I hope the max dict suite will eventually handle hierarchical JSON better, but this will do the trick for ...

[JSUI] Parameter only in Blobs?

Could you link me to some information how to use it in C?

Node.Js Freesound

hi, i can confirm, the example is not working. my .env seems to be ok, the script is not complaining. i can post my token with ...

Query the rawfloat value of live objects via JS?

Live objects (e.g. live.numbox) output the rawfloat value out their right outlet.