Jarrett Confrey

I noticed that the Node.js version bundled with Max is 16.6.0

Node.js 16.x is scheduled for end of life on 2023-09-11

https://github.com/nodejs/release#release-schedule

https://nodejs.org/en/blog/announcements/nodejs16-eol

Node.js 18.x is the current Long Term Support version but goes into maintenance on 2023-10-18

Node.js 20.x is the current version and will become the new Long Term Support version on 2023-10-24

I realize that the node.script object has node_bin_path and npm_bin_path attributes I could use to update my version but I think it would make sense to update the version of node bundled with Max to 20.x

I noticed that the Node.js version bundled with Max is 16.6.0

Node.js 16.x is scheduled for end of life on 2023-09-11

https://github.com/nodejs/release#release-schedule
https://nodejs.org/en/blog/announcements/nodejs16-eol

Node.js 18.x is the current Long Term Support version but goes into maintenance on 2023-10-18

Node.js 20.x is the current version and will become the new Long Term Support version on 2023-10-24

I realize that the node.script object has node_bin_path and npm_bin_path attributes I could use to update my version but I think it would make sense to update the version of node bundled with Max to 20.x

I noticed that the Node.js version bundled with Max is 16.6.0

Node.js 16.x is scheduled for end of life on ... 

bundled-nodejs-version-end-of-life-on-2023-09-11

this is correct, I don’t have an ETA or too much detail right now but we’ll be looking into this for a future update alongside supporting modern module loading that is required by some npm packages. 

In the meantime we recommend using node_bin_path and npm_bin_path as suggested to change the version of node if required. 

Thank you 

Bundled Node.js Version End Of Life On 2023-09-11

Jeff Griffiths

, Max 8.5 ( the version embedded into Ableton Live 11 ) bundles nodejs 16.6, which has been unsupported and has not had any security updates since September 2023. If you intend to build applications in m4l that use node.script, you should be aware of two key issues that affect your ability to support Ableton Live 11 going forward:

1/ node ships with openssl, and the version 1.1.1 of openssl that ships with node 16.6 is no longer supported since Sept 2023. At the time I assume Max 8.6 development was the focus of the team so they decided not to update the embedded version of node in Max 8.5. 

If you use node inside Ableton for networked applications, your applications have known security vulnerabilities.

2/ when nodejs 16.6 was deprecated in Sept 2023, the npm ecosystem moved quickly to drop support for this version, quickly rendering many useful packages as incompatible with Live 11. You will quite often get errors like this:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @sveltejs/kit@2.5.17
npm ERR! notsup Not compatible with your version of node/npm: @sveltejs/kit@2.5.17
npm ERR! notsup Required: {"node":">=18.13"}
npm ERR! notsup Actual:   {"npm":"7.20.3","node":"v16.6.2"}

I contacted cycling '74 support directly and they clarified that they have no plans to update the node version in Max 8.5. They suggested I upgrade to Live 12 to benefit from Max 8.6 and node 20, which I will probably do, because my project is focused on directly embedding web servers and apps inside max for live. If you are working on similar projects, 

you should probably only support Max 8.6 going forward

. This also means dropping support for Ableton Live 11 users, which I had hoped to avoid.

I am concerned that c74 didn't move to update Max 8.5 in Sept 2023 though - at the time Max 8.5 and Live 11 did not have newer versions available and they continued to ship and sell Max and Live with a deprecated version of node with known security issues.  They were notified immediately of the issue but waited instead for the release of Live 12 and Max 8.6. Nodejs 20 will continue to be 

As discussed in another post, Max 8.5 ( the version embedded into Ableton Live 11 ) bundles nodejs 16.6, which has been unsupported and has...

psa-using-nodescript-in-live-11-should-be-avoided-especially-for-networked-applications

PSA: using node.script in Max 8.5 and  Live 11 should be avoided, especially for networked applications

Felon

I have an issue on a new Windows computer that I am setting up for a patch that works perfectly on another machine. When I try to use some basic NodeJS communication with the PC (through child- process), I have an error message sayin' that the script (or the program ?) doesn't have the right access: it lacks privileges. 

//--------------------------------- PING ------------------------------------

maxApi.addHandler('ping_out', function() //

var exec = require('child_process').exec;

exec("ping -c 1 localhost", function(err, stdout, stderr) {

//------------------------------------------------------------------------------

The node.js debug tool says (in french) => "Access Denied, option -c requires admin privileges". 

I installed everything like before, with normal Max settings. I didn't encounter this issue with other computers.

Sorry if it's a really simple thing to solve, but maybe other users will have to deal with that.

Hello team,

I have an issue on a new Windows computer that I am setting up for a patch that works perfectly on another machine. When I try...

how-to-give-nodejs-scripts-admin-privileges

How to give NodeJS scripts admin privileges ?

woyteg

long time max user, experienced python user and novice in java script here.

I seem to experience some kind of memory leak when repeatedly accessing a dict through js. The attached patch tries to replicate my issue with minimal code. In reality i am building some sort of sequencer and dont plan to query the js object every millisecond but this seems to replicate/isolate the issue nicely.

Hope some of you find my mistake obvious and its not an actual bug. 

outlets = 1
var dict = new Dict('testing');
keys = dict.getkeys();
function bang(){
	keys = dict.getkeys();
	foo = dict.get(keys[0]);
	outlet(0,foo);
	return
}

{
	"test" : [ 1, 2, 3, 4, 5, 6, 7, 8 ],
	"test2" : [ 9, 8, 7, 6, 5, 4 ]
}


Hi,

long time max user, experienced python user and novice in java script here.

I seem to experience some kind of memory leak when...

memory-leak-when-accessing-dict

Memory leak when accessing dict

Robert Rapp

Hello, I am currently work with rnbo.js to develop a small webapplication. 

I create two audio elements and use them as AudioElementMediaSourceNode to connect it to the RNBO Patch. 

In my lifecycle hook of my Vue component I call within the beforeMounted function the createDevice of the rnbo lib and then I heard the first time a glitch. After couple of seconds I can recognize another glitch in the audio. 

Is this an known Issue? And if yes is there a possibilty to avoid the glitching while creating the RNBO Device? 

Hello, I am currently work with rnbo.js to develop a small webapplication. 


I create two audio elements and use them as...

audio-glitches-right-in-the-beginning-every-time-i-create-a-rnbo-device

Audio glitches right in the beginning every time I create a rnbo device

I have a simpler select option dropdown HTLM element from a site on jweb. But the Max Application crashes when the dropdown menu is clicked on some of the PCs. Can someone please let me know if there is a way to fix it? The app is built for Windows.

Hi there,

I have a simpler select option dropdown HTLM element from a site on jweb. But the Max Application crashes when the dropdown menu...

basic-lessselectgreater-option-from-web-on-jweb-crashes-max-application-862

Basic <select> option from web on jweb crashes Max Application

Jared Bennett

I'm trying to make a super simple js script in Max to make an 

 object of variable length depending on the list input to the js object. I've done some js things before in Max (and not in Max!) and feel relatively secure with in, so either I'm missing something super obvious or something doesn't work in a logical way!

unp = this.patcher.newdefault(1000, 1000, "unpack", 0 0 0);
unp = this.patcher.newdefault(1000, 1000, "unpack", "0 0 0");
unp = this.patcher.newdefault(1000, 1000, "unpack", "0&nbsp0&nbsp0");

However, the first option throws an error (js: autounpack.js: Javascript SyntaxError: missing ) after argument list, line 14), and the second and third options reproduce exactly what is written including the quote marks, which means the unpack object is created with only one outlet (and isn't super useful!). I've also tried this with the 

If anyone could tell me what I'm missing so I can stop banging my head against a brick wall that would be amazing!

Hi everyone,

I'm trying to make a super simple js script in Max to make an unpack object of variable length depending on the list input to...

newdefault-argument-issues

newdefault argument issues

hal bay

There is a crash bug with %100 reproducibility. Any Max4Live device with jweb (Chromium Embedded Framework) in them, if initiliazed at launch, for example while opening a recent set, will cause ableton main thread to crash with the stacktrace below. If the device is loaded on a track after ableton is initialized, they don't cause crash. you can try this open source device, 

, for quick reproduction; or make a new Max4Live device with jweb in it and save with it on any track and close/open that set afterwards, and smile at your crash :}

Version: 11.3.3 (2023-05-23_d46a6d1068) (11.3.3 (2023-05-23_d46a6d1068))

Date/Time: 2023-11-28 03:27:32.4749 +0100

Anonymous UUID: 4C2C9CF9-EE2F-C7A7-00C9-482BCA460703

Sleep/Wake UUID: F9175B31-D182-4989-88F1-1972EC4996C0

Crashed Thread: 0 MainThread Dispatch queue: 

Exception Codes: 0x0000000000000002, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5

Thread 0 Crashed:: MainThread Dispatch queue: 

0 Chromium Embedded Framework      0x1a43c6749 uhash_compareUnicodeString_69 + 993465

1 Chromium Embedded Framework      0x1a43c584d uhash_compareUnicodeString_69 + 989629

2 Chromium Embedded Framework      0x1a43d888d base::mac::CxxPersonalityRoutine(int, _Unwind_Action, unsigned long long, _Unwind_Exception*, _Unwind_Context*) + 46957

3 Chromium Embedded Framework      0x1a3f98501 _TIFFSwab64BitData + 3361665

4 Chromium Embedded Framework      0x1a403c636 __gxx_personality_v0 + 399606

5 Chromium Embedded Framework      0x1a401ce9b __gxx_personality_v0 + 270683

6 Chromium Embedded Framework      0x1a401cb81 __gxx_personality_v0 + 269889

7 Chromium Embedded Framework      0x1a07774a9 cef_initialize + 265

8 MaxPlugLib      0x11e05db52 CefInitialize(CefMainArgs const&, CefStructBase<CefSettingsTraits> const&, scoped_refptr<CefApp>, void*) + 114

9 MaxPlugLib      0x11dc84810 max_cef_startup + 1648

10 MaxPlugLib      0x11dc82902 cweb_new(symbol*, short, atom*) + 34

11 MaxPlugLib      0x11de0974a typedmess_fun + 394

12 MaxPlugLib      0x11de22c99 object_new_typed_flags + 601

13 MaxPlugLib      0x11de9c869 jpatcher_newobject + 649

14 MaxPlugLib      0x11dea5858 jpatcher_pastefromdictionary + 1256

15 MaxPlugLib      0x11dea4cc1 jpatcher_fromdictionary + 2481

16 MaxPlugLib      0x11de971b5 jpatcher_new + 3413

17 MaxPlugLib      0x11de0974a typedmess_fun + 394

18 MaxPlugLib      0x11de61f43 jpatcher_load_fromdictionary_namespace + 515

19 MaxPlugLib      0x11de621d5 jpatcher_load_frombuffer_namespace + 421

20 MaxPlugLib      0x11de603d9 lowload_jpatcher_frombuffer + 137

21 MaxPlugLib      0x11de6024b lowload_jpatcher_fromamxd_data + 1083

22 MaxAudioAPIImpl      0x11a0260db pluginterface_createjpatcher + 267

23 patcher      0x11a210a0d WiresPrivate::mfl_device_createjpatcher(WiresPrivate::_mfl_device*) + 461

24 patcher      0x11a20a22d Wires::CreateDevice(char*, int, int, char*, int, host_DeviceRef*, plug_DeviceRef**) + 861

25 Live      0x106717c12 0x103fcf000 + 41192466

26 Live      0x10670e6e1 0x103fcf000 + 41154273

27 Live      0x106742f4f 0x103fcf000 + 41369423

28 Live      0x1067430f0 0x103fcf000 + 41369840

29 Live      0x106745eb1 0x103fcf000 + 41381553

30 Live      0x105033e77 0x103fcf000 + 17190519

31 Live      0x106745b95 0x103fcf000 + 41380757

32 Live      0x106745794 0x103fcf000 + 41379732

33 Live      0x1067380e1 0x103fcf000 + 41324769

34 Live      0x105c03094 0x103fcf000 + 29573268

35 Live      0x105c02ce6 0x103fcf000 + 29572326

36 Live      0x105c02e66 0x103fcf000 + 29572710

37 Live      0x106a7f7cb 0x103fcf000 + 44763083

38 Live      0x1051dc788 0x103fcf000 + 18929544

39 Live      0x104f14581 0x103fcf000 + 16012673

40 Live      0x104f140df 0x103fcf000 + 16011487

41 Live      0x105129a33 0x103fcf000 + 18197043

42 Foundation      0x7ff8097ec716 __NSFireTimer + 67

43 CoreFoundation      0x7ff80893c2e8 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20

44 CoreFoundation      0x7ff80893be63 __CFRunLoopDoTimer + 807

45 CoreFoundation      0x7ff80893ba89 __CFRunLoopDoTimers + 285

46 CoreFoundation      0x7ff808921dc9 __CFRunLoopRun + 2206

47 CoreFoundation      0x7ff808920ec1 CFRunLoopRunSpecific + 560

48 HIToolbox      0x7ff8123a2f3d RunCurrentEventLoopInMode + 292

There is a crash bug with %100 reproducibility. Any Max4Live device with jweb (Chromium Embedded Framework) in them, if initiliazed at launch, for example while opening a recent set, will cause ableton main thread to crash with the stacktrace below. If the device is loaded on a track after ableton is initialized, they don't cause crash. you can try this open source device, Magenta Studio, for quick reproduction; or make a new Max4Live device with jweb in it and save with it on any track and close/open that set afterwards, and smile at your crash :}

Any ideas?

Translated Report (Full Report Below)
-------------------------------------

Process:               Live [90557]
Path:                  /Applications/Ableton Live 11 Suite.app/Contents/MacOS/Live
Identifier:            com.ableton.live
Version:               11.3.3 (2023-05-23_d46a6d1068) (11.3.3 (2023-05-23_d46a6d1068))
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2023-11-28 03:27:32.4749 +0100
OS Version:            macOS 13.6.1 (22G313)
Report Version:        12
Bridge OS Version:     8.1 (21P1069)
Anonymous UUID:        4C2C9CF9-EE2F-C7A7-00C9-482BCA460703

Sleep/Wake UUID:       F9175B31-D182-4989-88F1-1972EC4996C0

Time Awake Since Boot: 220000 seconds
Time Since Wake:       227978 seconds

Crashed Thread:        0  MainThread  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process:   exc handler [90557]

External Modification Warnings:
Thread creation by external task.

Thread 0 Crashed:: MainThread Dispatch queue: com.apple.main-thread
0   Chromium Embedded Framework   	       0x1a43c6749 uhash_compareUnicodeString_69 + 993465
1   Chromium Embedded Framework   	       0x1a43c584d uhash_compareUnicodeString_69 + 989629
2   Chromium Embedded Framework   	       0x1a43d888d base::mac::CxxPersonalityRoutine(int, _Unwind_Action, unsigned long long, _Unwind_Exception*, _Unwind_Context*) + 46957
3   Chromium Embedded Framework   	       0x1a3f98501 _TIFFSwab64BitData + 3361665
4   Chromium Embedded Framework   	       0x1a403c636 __gxx_personality_v0 + 399606
5   Chromium Embedded Framework   	       0x1a401ce9b __gxx_personality_v0 + 270683
6   Chromium Embedded Framework   	       0x1a401cb81 __gxx_personality_v0 + 269889
7   Chromium Embedded Framework   	       0x1a07774a9 cef_initialize + 265
8   MaxPlugLib                    	       0x11e05db52 CefInitialize(CefMainArgs const&, CefStructBase<CefSettingsTraits> const&, scoped_refptr<CefApp>, void*) + 114
9   MaxPlugLib                    	       0x11dc84810 max_cef_startup + 1648
10  MaxPlugLib                    	       0x11dc82902 cweb_new(symbol*, short, atom*) + 34
11  MaxPlugLib                    	       0x11de0974a typedmess_fun + 394
12  MaxPlugLib                    	       0x11de22c99 object_new_typed_flags + 601
13  MaxPlugLib                    	       0x11de9c869 jpatcher_newobject + 649
14  MaxPlugLib                    	       0x11dea5858 jpatcher_pastefromdictionary + 1256
15  MaxPlugLib                    	       0x11dea4cc1 jpatcher_fromdictionary + 2481
16  MaxPlugLib                    	       0x11de971b5 jpatcher_new + 3413
17  MaxPlugLib                    	       0x11de0974a typedmess_fun + 394
18  MaxPlugLib                    	       0x11de61f43 jpatcher_load_fromdictionary_namespace + 515
19  MaxPlugLib                    	       0x11de621d5 jpatcher_load_frombuffer_namespace + 421
20  MaxPlugLib                    	       0x11de603d9 lowload_jpatcher_frombuffer + 137
21  MaxPlugLib                    	       0x11de6024b lowload_jpatcher_fromamxd_data + 1083
22  MaxAudioAPIImpl               	       0x11a0260db pluginterface_createjpatcher + 267
23  patcher                       	       0x11a210a0d WiresPrivate::mfl_device_createjpatcher(WiresPrivate::_mfl_device*) + 461
24  patcher                       	       0x11a20a22d Wires::CreateDevice(char*, int, int, char*, int, host_DeviceRef*, plug_DeviceRef**) + 861
25  Live                          	       0x106717c12 0x103fcf000 + 41192466
26  Live                          	       0x10670e6e1 0x103fcf000 + 41154273
27  Live                          	       0x106742f4f 0x103fcf000 + 41369423
28  Live                          	       0x1067430f0 0x103fcf000 + 41369840
29  Live                          	       0x106745eb1 0x103fcf000 + 41381553
30  Live                          	       0x105033e77 0x103fcf000 + 17190519
31  Live                          	       0x106745b95 0x103fcf000 + 41380757
32  Live                          	       0x106745794 0x103fcf000 + 41379732
33  Live                          	       0x1067380e1 0x103fcf000 + 41324769
34  Live                          	       0x105c03094 0x103fcf000 + 29573268
35  Live                          	       0x105c02ce6 0x103fcf000 + 29572326
36  Live                          	       0x105c02e66 0x103fcf000 + 29572710
37  Live                          	       0x106a7f7cb 0x103fcf000 + 44763083
38  Live                          	       0x1051dc788 0x103fcf000 + 18929544
39  Live                          	       0x104f14581 0x103fcf000 + 16012673
40  Live                          	       0x104f140df 0x103fcf000 + 16011487
41  Live                          	       0x105129a33 0x103fcf000 + 18197043
42  Foundation                    	    0x7ff8097ec716 __NSFireTimer + 67
43  CoreFoundation                	    0x7ff80893c2e8 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
44  CoreFoundation                	    0x7ff80893be63 __CFRunLoopDoTimer + 807
45  CoreFoundation                	    0x7ff80893ba89 __CFRunLoopDoTimers + 285
46  CoreFoundation                	    0x7ff808921dc9 __CFRunLoopRun + 2206
47  CoreFoundation                	    0x7ff808920ec1 CFRunLoopRunSpecific + 560
48  HIToolbox                     	    0x7ff8123a2f3d RunCurrentEventLoopInMode + 292
49  HIToolbox                     	    0x7ff8123a2d4e ReceiveNextEventCommon + 657
50  HIToolbox                     	    0x7ff8123a2aa8 _BlockUntilNextEventMatchingListInModeWithFilter + 64
51  AppKit                        	    0x7ff80b9bd25c _DPSNextEvent + 858
52  AppKit                        	    0x7ff80b9bc106 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1214
53  AppKit                        	    0x7ff80b9ae788 -[NSApplication run] + 586
54  Live                          	       0x105128dd1 0x103fcf000 + 18193873
55  dyld                          	    0x7ff8084ed41f start + 1903

There is a crash bug with %100 reproducibility. 

crash-at-launch-with-any-max-for-live-pluging-with-cef-in-them-percent100-reproducibility

Could you file a bug report here? Be sure to include all versions of the software you are using (Live, Max, etc), your Support Info from Max, and if you are using the bundled Max or a newer version. Thanks!

I will file a bug report there, as I could just reproduce it on 3 different computers( 2 macOS and 1 windows) with official and simple node4max express example from there.

I just clone the repo, open .maxproj, export max4live device(with server.js and node_modules embedded or not embedded both crashes),

then load created .amxd on a track, save the set and close ableton. when opened back, load the recent saved set and the same crash with same stack happens

Crashing here also on Macbook Pro Ventura 13.5.2

Crash at launch with any Max For Live device with jewb(CEF) in them, %100 reproducibility

attila

Hi all, I'm working on a project involving Node for Max and struggling to get a basic non-trivial patch running. 

Correct me if I'm wrong, but even with a custom @node_bin_path Node binary specified it seems like the node.script node process manager object in Max is hardcoded to import user scripts using the outdated CommonJS `require('xyz')` syntax.

Max.app/Contents/Resources/C74/packages/Node

The README states that Node v16.6.0 is used internally. In Node.js v12.17.0 and above it's possible to use dynamic imports. A compromise could be:

// if package.json nearest to the user script has type: 'module'

import(process.env.SCRIPT_PATH).then(() => {

These days, a number of package dependencies are being published in ESM-only formats. The broader implication is that it's not always feasible to convert an entire script to CommonJS. A modern Node project often comes with additional complexity, especially if there's Typescript transpilation or bundling involved. Often there are packages involved with add-on Node-API binaries (`.node`) that cannot be bundled and need to be marked as runtime externals (in my current case, one that's adding WebRTC support for Node). 

Is there a currently preferred workaround or consideration for this? It seems like I would have to resort to some kind of a Max for Node proxy to exchange messages with a locally running, completely separate node process.

Hi all, I'm working on a project involving Node for Max and struggling to get a basic non-trivial patch running. 

Correct me if I'm wrong, but even with a custom @node_bin_path Node binary specified it seems like the node.script node process manager object in Max is hardcoded to import user scripts using the outdated CommonJS  `require('xyz')` syntax.

In `/Applications/Max.app/Contents/Resources/C74/packages/Node for Max/source/lib/nsRunner.js`:

// Kick off things and load user script
require(process.env.SCRIPT_PATH);
loadedSuccessfully = true;

The README states that Node v16.6.0 is used internally. In Node.js v12.17.0 and above it's possible to use dynamic imports. A compromise could be:

// if package.json nearest to the user script has type: 'module'
// or the script file ends with .mjs
import(process.env.SCRIPT_PATH).then(() => {
  loadedSuccessfully = true;
})
or something less hacky.

These days, a number of package dependencies are being published in ESM-only formats. The broader implication is that it's not always feasible to convert an entire script to CommonJS. A modern Node project often comes with additional complexity, especially if there's Typescript transpilation or bundling involved. Often there are packages involved with add-on Node-API binaries (`.node`) that cannot be bundled and need to be marked as runtime externals (in my current case, one that's adding WebRTC support for Node). 

Is there a currently preferred workaround or consideration for this? It seems like I would have to resort to some kind of a Max for Node proxy to exchange messages with a locally running, completely separate node process.

support-modern-esm-imports-in-node-for-max

To save some hours in case anyone finds this thread — I was able to get a typescript + ESM project running in Max via esbuild bundling to commonjs and an unexpected hack to mix import/require. The latter is required for interaction with the Max API.  

// build script
esbuild index.ts --platform=node --bundle '--external:max-api' --format=cjs --outfile=./index.js
// index.ts
import esmOnlyDefault from 'esm-only-package'
import commonJsDefaultViaEsm from 'cjs-only-package' // ES Modules imports are static
const maxAPI = require('max-api') // CommonJS imports are dynamically resolved at runtime 

Hi!
Thank you digging and sharing this solution with the community.
I'm interested in this but I confess I don't have enough flexibility to understand your approach.
Could you possibly add more information on how to implement this?
I'm trying to test this library:
https://www.npmjs.com/package/hdsp2

Consultant, City Manager, and Governor appointed @AmeriCorps Commissioner focused on strengthening communities and planning the next outdoor adventure.
Michael Grayum

Thanks for pointing this out and providing a workaround. It seems to in fact point towards a limitation in the way we are currently loading the process shell on the Node / JS side. 

I’ve filed a ticket and we’ll be looking into this. 

Thanks
Florian

Is the best way to get notified about the state of the support of modern esm imports subscribing to this thread?
I have a bunch of projects that I could finally integrate fully in max without having to use external scripts sending OSC to max once esm imports are possible.

Also very interested in this functionality if it hasn't already been handled.

Support modern ESM imports in Node for Max

Sean Sanchez

Hi community. I've been working on making a chatbot in Max using two node.js objects. One for the Deepgram API and the other for the OpenAI and Elevenlabs API's. I use a Deepgram.js object to convert speech to text which sends as a message to the elevenlabs-openai.js object which processes the prompt and plays the audio response from max. The problem is that the Deepgram.js object listens to the audio and transcribes it as the next prompt causing a feedback loop. I've tried an option with adding a toggle to turn on and off the recorder library in the deepgram.js object but I'm novice to javascript and couldn't get it to work properly. Any help or suggestions would be appreciated.

Hi community. I've been working on making a chatbot in Max using two node.js objects. One for the Deepgram API and the other for the OpenAI and Elevenlabs API's.  I use a Deepgram.js object to convert speech to text which sends as a message to the elevenlabs-openai.js object which processes the prompt and plays the audio response from max. The problem is that the Deepgram.js object listens to the audio and transcribes it as the next prompt causing a feedback loop.  I've tried an option with adding a toggle to turn on and off the recorder library in the deepgram.js object but I'm novice to javascript and couldn't get it to work properly. Any help or suggestions would be appreciated. 

Hi community. I've been working on making a chatbot in Max using two node.js objects. 

chatbot-with-elevenlabs-responding-to-itself

What you want to achieve is not very clear.
If I get it right, I guess you first say a phrase in a mic, the audio is transcribed by deepgram, which sends the text to elevenlabs_openai, which synthetises audio from it and play it through the speakers, which audio is then captured by the mic and sent to deepgram, and so on. Is this it? 
If so, I guess you indeed want to control when deepgram receives audio from the mic instead of always listening. But I can't tell how to do that without seing your patc and js files. Is the audio captured from within Max directly? Or is it handled by node? 

Also, maybe it's just a design issue: in the context of a chatbot, why would you say something, then hear the computer repeating what you just said but in a synthetized manner?

By the way, I'm quite curious to see how some messages degrades/evolve through many iterations of that feedback loop.


Thanks for your response. The goal is to create a conversational chatbot through Max with little to no manual input. (ie: entering text, on/off controls with the exception of starting the node.js scripts). The audio is captured/handled by node in the maxDeepgram.js object using the recorder library. I'm leaning towards a toggle to pause() or resume() the recorder. I've added the patch and node.js files but you'll need your own keys to try it out. Appreciate any suggestions :) 


According to the recording library documentation, you can pause your recording by calling "recording.pause()" and resume with ""recording.resume()".
You can simply try to declare functions like such: add the following code

maxAPI.addHandlers({
    pause: () => recording.pause(),
    resume: () => recording.resume()
});


in maxDeepgram.js, then, before send your "message" message to elevenslabChatGPT, send the message "pause" to maxDeepgram.js to call that function and actually pause the recording. Then, once the text is played through the speaker,  send "resume" to maxDeepgram.js.

I did not tested this, but it should work straight away.

Cycling '74 Forums

Hi Florian - thanks for the workaround, and your patience. This is a great solution for individual developers using Ableton 11 who want a...

As discussed in another post, Max 8.5 ( the version embedded into Ableton Live 11 ) bundles nodejs 16.6, which has been unsupported and...

Hello team, I have an issue on a new Windows computer that I am setting up for a patch that works perfectly on another machine. When I...

I'm not sure that it's a bug, but I don't think it's specifically related to dictionaries but rather to js in general, in particular with...

Hello, I am currently work with rnbo.js to develop a small webapplication. I create two audio elements and use them as...

Hi FS. To follow up here, I can't reproduce the issue with Max 8.6.2 on macOS and we had addressed this in Would you mind sharing the...

ah! I'd missed that each argument is separated by a comma... absolute rookie error! Thanks so much!

Crashing here also on Macbook Pro Ventura 13.5.2

Also very interested in this functionality if it hasn't already been handled.

According to the recording library documentation, you can pause your recording by calling "recording.pause()" and resume with...