Forums > Max For Live

Intermittent Error: "Changes cannot be triggered by notifications"

May 17 2013 | 9:53 am

I’m getting intermittent errors enabling/disabling the mute on track 0 while setting up my first patch.
Does anyone know what is going on with this?




  1. ScreenCapture


May 17 2013 | 9:53 am

The error message is:

live.object: Changes cannot be triggered by notifications. You will need to defer your response.


May 17 2013 | 10:44 am

This error occurs when you are trying to make a change to live whilst processing a notification from live, which is not possible. its indicating the you need to defer the update to live and let the processing finish (or it’s a bug in your code)

I can’t see how this can happen from the patch you’ve posted above – is that it or is there more?

May 18 2013 | 5:16 am

defer/deferlow may help

May 28 2013 | 9:07 pm

im having the same trouble.  but defer/deferlow doesn’t help.

this creates problems with push and control surfaces.  because i have to use live.object to watch the buttons, and they then drive downstream interations with the api- like enter notes into clips.

does anyone know how to get around this problem?

May 29 2013 | 12:32 am

can you post the portion of the patch causing the issue?

Viewing 6 posts - 1 through 6 (of 6 total)

Forums > Max For Live