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

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

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.

Chatbot with Elevenlabs responding to itself. 

Marc Carlton

I'm having trouble working with dynamically created arrays of buffers in javascript. 

(I am planning on using javascript to iterate through samples in each buffer which is why I'm not using a polybuffer, where I don't believe you can use peek/poke w a polybuffer.)

User drops a folder of audio files on a [dropfile] and I want to create an array of buffers in javascript. does this look right?

var player = this.patcher.getnamed("player");

var waveView = this.patcher.getnamed("waveView");

var filePath = lastAudioFolderPath+audioFile;

buffer_array[buffer_array_index] = new Buffer(audioFile);

post("created new buffer ("+audioFile+") at index ("+buffer_array_index+")");

buffer_array[buffer_array_index].send("replace", filePath);

post("play: "+"Bell.wav"); //testing with Bell.wav audio file

player.message("set", "Bell.wav"); //[play~] called player

Screen Shot 2018-02-27 at 2.55.21 PM.png

I'm having trouble working with dynamically created arrays of buffers in javascript. 
(I am planning on using javascript to iterate through samples in each buffer which is why I'm not using a polybuffer, where I don't believe you can use peek/poke w a polybuffer.)  

User drops a folder of audio files on a [dropfile] and I want to create an array of buffers in javascript.  does this look right?

var lastAudioFolderPath = '';
var buffer_array = [];
var buffer_array_index = 0;
var player = this.patcher.getnamed("player");
var waveView = this.patcher.getnamed("waveView");

function clear(){
	post();
	post("clear");
	buffer_array_index = 0;
}

function setAudioFolderPath(path){
	post();
	post("path_audioFolder: "+path);
	lastAudioFolderPath = path;
}

function load_audio(audioFile){
	var filePath = lastAudioFolderPath+audioFile;
	buffer_array[buffer_array_index] = new Buffer(audioFile);
	post();
	post("created new buffer ("+audioFile+") at index ("+buffer_array_index+")");
	buffer_array[buffer_array_index].send("replace", filePath);
	buffer_array_index++;
}

function play(){
	post();
	post("play: "+"Bell.wav"); //testing with Bell.wav audio file
	player.message("set", "Bell.wav"); //[play~] called player
	player.message("start");
}

I'm having trouble working with dynamically created arrays of buffers in javascript. 
(I am planning on using javascript to iterate through 

dynamic-array-of-buffers-in-js

is anyone creating arrays of JS Buffers?  I would love to see an example.

array[i].send("replace", file);  ///returning errors

I've been working away on this too - I've tried the following:
inlets = 1;
outlets = 1;

function loadBuf1() {
	//method 1 - works 
    buf.send("replace");
}

function loadBuf2() {
    //method 2 - works (with connection to external buffer and prepend replace)
    outlet(0, filePath);
}
function loadBuf3() {
    //method 3 - she no work
    buf.send("replace" + filePath);

}
function loadBuf4() {
    //method 3 - well it as never going to work was it!
    buf.replace(filePath);

dynamic array of Buffers in JS?

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

pseudostereo

The Javascript Math object includes the static method Math.cbrt(), to calculate the cube root.

However, when I try to run a js object that uses this method, I get this error:

js: test.js: Javascript TypeError: Math.cbrt is not a function, line 8

I'm not getting the error with any other Math methods.

The Javascript Math object includes the static method Math.cbrt(), to calculate the cube root.

However, when I try to run a js object that uses this method, I get this error:

js: test.js: Javascript TypeError: Math.cbrt is not a function, line 8

The Javascript Math object includes the static method Math.cbrt(), to calculate the cube root.

However, when I try to run a js object that ... 

no-cube-root-in-javascript

no cube root in javascript?

Trevor being Trevor

I have a max patch that dynamically creates and removes a ton of objects via the this.patcher.newdefault() and this.patcher.remove() methods to essentially build and destroy a dynamic UI via Javascript as needed. The objects are stored in global arrays by type (for example, all the textedit objects) so the functions that create and destroy the UI both have access to them.

It's been relatively smooth. However, as I have continued to build using the same methodology I encounter an odd crash now and then. After troubleshooting, the problem comes down to the use of a this.patcher.remove() in specific instances. Literally, if I comment it out the line(s), the crash does not occur.

If anybody with more knowledge on Max debug output could give any insight into following info I think I could get to the bottom of it. I am happy to provide more info if needed, just wanted to avoid writing a novel of a post.

These are snippets of the Max debug output when running a bunch of this.patcher.remove() methods. I am wondering if the bolded lines are potential issues that are compounding into a crash later.

Looks Normal:
object_unregister: slating unique sym u857004814 for reuse
unregistering: u562004824 in 00000000000B1890. ref count now 0

Should I be concerned?
unregistering: u597005447 in 00000000000B1890. ref count now 0
object_unregister: slating unique sym u597005447 for reuse
object_detach: object 000000002D0E4170 wasn't attached to object 0000000029D6F890 
unregistering: u915005449 in 000000000014C738. ref count now 0
object_unregister: slating unique sym u915005449 for reuse
unregistering: u587005469 in 00000000000B1890. ref count now 0

Another snippet after adding in some lines that makes it crash in certain instances.
registering: u184003150 in 00000000009267B8
registering: u363003151 in 00000000009267B8
unregistering: u512002235 in 00000000009267B8. ref count now 0
object_unregister: slating unique sym u512002235 for reuse
warning: object 0000000027D28780 was freed but was still attached to 1 registered object(s) 
loadbang_clearqueue
loadbang_clearqueue
registering: u176003152 in 00000000008DC8A0

MaxCrashSnippet.png

It's been relatively smooth. However, as I have continued to build using the same methodology I encounter an odd crash now and then. After troubleshooting, the problem comes down to the use of a this.patcher.remove() in specific instances. Literally, if I comment it out the line(s), the crash does not occur. 

If anybody with more knowledge on Max debug output could give any insight into following info I think I could get to the bottom of it. I am happy to provide more info if needed, just wanted to avoid writing a novel of a post.

These are snippets of the Max debug output when running a bunch of this.patcher.remove() methods. I am wondering if the bolded lines are potential issues that are compounding into a crash later.

I have a max patch that dynamically creates and removes a ton of objects via the this.patcher.newdefault() and this.patcher.remove() ... 

need-insight-on-crash-and-debug-output-for-this-patcher-remove

Following up on this post, I ended up doing a full rewrite to address various growing pains and this issue resolved thankfully. However, two things I wish I would of known...

gc() - appears to call JavaScript garbage collection, there isn't much documentation on this function specifically, but seems to be a known technique on the forum. I call it after the user does full removal of all the dynamically created objects.

In a different thread a user recently posted that there is a way to print the stack trace using:  

var err = new Error(); 
post(err.stack + "\n");

Need insight on crash and debug output for this.patcher.remove()

Monib Ahmed

Hi, I'm trying to load some external JS libraries. Can you advise me what is the recommended way of doing this?

I've tried including the paths in Files Search Path, and the paths are showing up

MacOS:/Users/monibahmed/node_modules/lodash

MacOS:/Users/monibahmed/node_modules/lodash/fp

But the following post "undefined" in the console:

Hi, I'm trying to load some external JS libraries. Can you advise me what is the recommended way of doing this? 

I've tried including the paths in Files Search Path, and the paths are showing up

MacOS:/Users/monibahmed/node_modules/lodash
MacOS:/Users/monibahmed/node_modules/lodash/fp

var lodash = require("lodash");
post(lodash.VERSION+'\n')

Hi, I'm trying to load some external JS libraries. 

loading-lodash-or-other-external-js-libraries

Welcome to EORC™ Transform your home into a cozy oasis with our stunning collection of premium rugs, now available at your fingertips with just a few clicks. Discover the perfect rug to elevate your space and make a statement in any room, all from the comfort of your own home with our EORC Home
Area Rug

Load it by message:[script npm install lodash] and use in JS by const _ = require('lodash')
Seems to work fine here.


Hi, yes the node.script object works fine with Lodash, but not the js object?

Ah, no. [js] and [jsui] are strictly limited in scope.

Thank you! I guess I’ll start using node. 

Loading lodash or other external JS libraries

This is fun one. I wrote some code for a device that uses the Task Object. Everything works as expected when I use my device in Ableton 10. However, in Ableton 11 on both Windows and Mac it appears to stop functioning.

For context, here's the quick breakdown of how the code works...

Now after debugging for a while, this what I found. The Task function runs successfully "once". More specifically, it's called to repeat x number of times and on the last repetition it triggers the process function again as expected. However, the second time it's called to repeat, it stops just before the last repetition. It fails to call the process function again and everything grinds to a halt. As far as I can tell, this is not an error on my part because the works just fine on Ableton 10 (Windows and Mac). I've been looking through the release notes and documentation looking for a clue, but I have not had any luck. Hence, once again I am asking for your help. Maybe I should change my name to Trevor being Bernie. Anyway, this forum is full of heroes without capes as far as I can tell, thanks for any insight in advance!

This is fun one. I wrote some code for a device that uses the Task Object. Everything works as expected when I use my device in Ableton 10. However, in Ableton 11 on both Windows and Mac it appears to stop functioning. 

The user triggers an initialization function that sets all the global variables to a starting value and then kicks off the desired process function. 

The desired processing function searches for a desired condition to be true within a data set using a loop to process each piece of data. Each iteration increments the necessary global variables.

When the desired condition is found, the task function is called for a given number of repetitions. 

A flag is set that allows the process function to pause using break or return commands nested in if statements checking for that flag

The Task function runs. When it reaches it's final repetition, it calls the process function again.

This repeats until certain global variable conditions are met.

This is fun one. I wrote some code for a device that uses the Task Object. Everything works as expected when I use my device in Ableton 10. 

ableton-11-appears-to-break-the-functionality-of-the-task-object

i use task often in Live 11.   Impossible to diagnose without code sample which reproduces the problem.

Well let me ask more generally then, how did Ableton 11 affect the JavaScript implementation in Max compared to Ableton 10? Based on what I described, how may that be relevant to my situation? This is the kind of insight I am looking for so I can diagnose the problem. I will work on an isolated code sample. In the meantime, these release note links may be helpful now or for someone in the future...

On my machine
Ableton 10 Max Version: 8.1.11
Ableton 11 Max Version: 8.3.3

Max Release Notes After 8.1.11 up to 8.3.3
http://cycling74.s3.amazonaws.com/support/version_8_2_0.html
http://cycling74.s3.amazonaws.com/support/version_8_2_1.html
http://cycling74.s3.amazonaws.com/support/version_8_2_2.html
http://cycling74.s3.amazonaws.com/support/version_8_3_0.html
http://cycling74.s3.amazonaws.com/support/version_8_3_1.html
http://cycling74.s3.amazonaws.com/support/version_8_3_2.html
https://cycling74.s3.amazonaws.com/support/version_8_3_3.html

Possibly Related Excerpts from Links Above
8.2.0
jsliveapi: eliminate crash when there's no 'this' for operations (the task object uses 'this')

8.2.2
JS Task: fixed issue with creating JS object with task

Kudos for digging up the history.  If you are trying to prove a regression caused by a Max update among those builds the next step would be a binary regression through the builds.

So maybe you'd start with Live 10 but linking Max install of 8.2.1 and see if it happens.  Then move newer to newer or older builds based on those results to isolate where the behavior change was introduced.  This is truly tedious and potentially very unrewarding,  but it can also be super helpful to the devs to have that kind of information.

Truly tedious and potentially very unrewarding,  but it can also be super helpful.

I feel like this captures some of the struggles of troubleshooting haha. I may have to do that to get the bottom of it. However, I just got it working by creating a fresh Task object right before I call the repeat function. Not sure why this works, but this is the only change I made...

In Live 10
//global declaration
var myTask = new Task(taskFunction, this);

//Then when the process function needs to call it for x number of repeats
myTask.repeat(x);

In Live 11
//global declaration
var myTask = newTask(taskFunction, this);

//Then when the process function needs to call it for x number of repeats
myTask = new Task(taskFunction, this);
myTask.repeat(x);

nice you found a workaround. If you’re going to do it that way you probably want to call Task.freepeer() before you re-assign myTask to the new Task.  I think that will allow the previous task to be garbage collected.

Cycling '74 Forums

Hi Ben, thanks for the fast reply.

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

I've been working away on this too - I've tried the following: inlets = 1; outlets = 1; var buf = new Buffer("outsidejsui"); function ...

Hi Jarret, 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 ...

Got it. Too bad, but thanks.

Following up on this post, I ended up doing a full rewrite to address various growing pains and this issue resolved thankfully.

Thank you! I guess I’ll start using node.

Okay here was my strategy to deal with Live changing my dynamically created object's colors. Set up a live.colors object to bang a message ...

FWIW the least painful solution seems to be to use scale(2, 2) when when drawing the cached image (on a 2x-sized canvas) and then ...

Yeah, that's inefficient and precludes the use of the same child dictionary being modified from multiple places in the UI, among other ...