Constantly getting errors when starting M4L Granulator II

Milo Brown's icon

Hey guys,

I'm not too familiar with Max For Live, and I don't really understand most of the terminology behind it, so I figured you guys would be able to help me with this problem I've been having inside of Ableton Live 11.
I keep getting this weird error message every single time I open Granulator II inside Ableton that just repeatedly says:

"jsliveapi: Changes cannot be triggered by notifications. You will need to defer your response."

Also, I saw in another post that unchecking "ShowErrors" in the About section of the device could be a potential fix for a similar issue, but it's already turned off on my end, so I don't really know what to do from here, unfortunately.

Granted, I can still use the device normally with no issues, it's just more of an annoyance than anything to have this window pop up every time I open the device. Any idea on what I can do to fix this? Thanks in advance.

Namakemon's icon

I don't see those errors here, tried to load several ways (clean default, .adv preset, within .adg Rack preset), even with the audio engine off, it doesn't show those errors.

That error is mentioned in the docs.

My computer is not the fastest and my files are in a non-SSD drive, maybe your computer loads AMXD much faster, fast enough to trigger order of operations errors (which don't appear in my slower computer)?

Milo Brown's icon

I think the issue was somewhere within my project. I started a completely new blank project and there were no errors. Not sure what the actual issue was though.