You will need to defer your response.
Hi,
like a lot of LOM user I get the classical error " live.object: Changes cannot be triggered by notifications. You will need to defer your response."
I found this article and tried to use [defer] [delay] [pipe]https://cycling74.com/articles/event-priority-in-max-scheduler-vs-queue
But I still get a nice feedback, even when the patch is not in edit mode.
What can I change ?
All test I did remains unfortunately unsuccessful
insert defer instead of pipe.
I tried [defer] between the [live.observer] and the [live.numbox] but still get the same error message
In fact when I'm connecting the [live.observer] to the [live.numbox] it works fine, but I get this error message ?!
If you're still working on this and would like a second set of eyes feel free to share the patch. It's hard to know exactly what's the flow path.
Usually [deferlow] works more reliably than [defer]. The issue isn't the changing the value of live.numbox, the issue is the "set value $1" message to the live.object. Hence the error message: live.object: Changes cannot be triggered by notifications.
Hi,
happy to see that people get interested with this question !
I gave a try still stuck with this problem
Sorry I just saw the patch now.
Here you go:
No more "You will need to defer your response" error. Only a warning because live.numbox will actually output its value before live.object knows what's the id. you can fix that by applying a gate that only opens after the patch is loaded, which you can know via the live.thisdevice object.
Best,
OCH
a lots of small difference, have to do some test to understand how they modified the behavior
hope it helps someone one day :)
a lots of small difference, have to do some test to understand how they modified the behavior
hope it helps someone one day :)
what?
inside the live.observer you add value
Basically you need to ensure that in one Max message chain of operations you don't observe and set the API at the same time.
yes, I guess that in a perfect world this should be possible.
A "perfect world" where you could perform two operations "at the same time" would, most likely, not have computers in them. :-)
If notifications could trigger the API and vice versa, it would be quite easy to make Live lockup by creating endless loops. They (Ableton) have gone to great pains to ensure that can't happen.
@max maybe this is a solution !
@Iain Yes I get it
I'm not sure if this has been mentioned in this thread, but if you swap out Live API observing for plugsync~ in your patch anywhere (which depends on what you're observing) that can make a big difference. Plugsync's output is not considered a notification in this sense.