cesipxynic

I have the following chunk of code in a [poly~]:

What comes into the [t l l] is, predictably, an id - in this case, of a parameter. Numerical values (either 1 or -1) are received by the left inlet of [+]. What this is supposed to achieve is control a Live paramter with an endless encoder.

As you can see, there's a [deferlow] involved. Yet in Edit Mode (it doesn't seem to happen while just using the device - but it's very hard to check, since to see Max errors I need to be in Edit Mode) I still get the "Changes cannot be triggered by notifications. You will need to defer your response" error message.

I should addtionally mention that there are 8 of these constellations in the [poly~], which has 128 voices. Yet most of these voices are never really targeted and the [live.object]s and [live.observer]s are instantiated with IDs in only a few voices - I simply need to have the 128 voices since the background need is to address 8 parameters on an Instrument Rack on each Drum Pad in a Drum Rack.

I have the following chunk of code in a [poly~]: 

I should addtionally mention that there are 8 of these constellations in the [poly~], which has 128 voices. Yet most of these voices are never really targeted and the [live.object]s and [live.observer]s are instantiated with IDs in only a few voices - I simply need to have the 128 voices since the background need is to address 8 parameters on an Instrument Rack on each Drum Pad in a Drum Rack.


live-object-throws-changes-cannot-be-triggered-by-notifications-error

Patch looks fine... If you only ever see it in edit mode, perhaps it's some strange interaction whilst in edit (wouldn't be the first!)

You can check the max window when not in edit mode by right clicking the device name area. Most of the time, adding a deferlow before the live.remote that triggers the notification is enough.

[live.object] throws "changes cannot be triggered by notifications" error