|
|
Feb 11, 2012 at 5:05am
live.object: Changes cannot be triggered by notifications, from mouse click
Hi,
I’m getting the
live.object: Changes cannot be triggered by notifications
error, when I use the patch below to change a device parameter in M4L: a toggle object is used to control the change, so there are no notifications involved at all (to my understanding). This occurs frequenty–perhaps one in twenty clicks–but not all the time. I am using a deferlow object, as suggested by the docs, even though it should only be necessary when a notification is triggering the change.
Has anyone any ideas why I’m getting this error?
Thanks,
Aengus.
Copy all of the following text.Then, in Max, select New From Clipboard.
----------begin_max5_patcher----------
477.3ocwUssabBCD8YyWgkUejhvboA5a86nJB4EOYiiXsQ1FxlFk+8fsWXS1
jMkpts4EK7YFFNyYtviQHxF0dvPveG+SLB8XDB4gb.nC2Qjcr8scLi2MhDtW
s4NRbvjE1a8vb3FP2ote1vMJo0H9E3LRoIoGfkC6DxNv5iE8HnZvdJZ.x9PO
DnGgfu9fodls8VgbaiFZsAqzxouAtpJoLFWl4dlVmjt7FBtmkSL+q4kujiR1
Ne7I+PKXcDmgmhhbGwqTP1AFCaK7FEw.V7Hqa.veg9mnJYWbUorHorNsphFi
uJ0KMW89RCMO+xpMV01scKRyeSwWHsqHSCmYoymueRtTN5Y5oTzB5FPx1z4+
VoWvV.AepJW7YU7qJck85hrXbwwNfhOtCHq5x1Abl0EchQHYxfirepyFzrvh
i5Es5b6MnY0efzbvhgMB7lPh0vrVsXyfMrfEsnPHRSOnMBiEjsg70i6k1YA1
SgIcRd55Yep3vespaTC514DeoThOlJbvXERlUnjuxqorBSW75VAmCdGlK.bg
wMavO+vwpYjax62yH2RnW30+RF49WvJknz+SRT9JXzIzd8DJzTw56Gc8egX5
4xzP6cJs652h8WExvUeDIZXTL6edjKZOE8rMIVtV
-----------end_max5_patcher-----------
|
|
|
Feb 11, 2012 at 10:41am
In my experience that error message may also appear in situations not strictly related to notifications.
So it would be helpful if you provide some more context, ie. a complete reproducible example.
|
|
|
Feb 11, 2012 at 1:56pm
I’d be happy to–do you mean a complete Live set too? That’s surely the only way an example could be complete…?
|
|
|
Feb 11, 2012 at 2:34pm
Ideally you would attach a Live set (zip) reduced to relevant devices with instructions for reproducing the issue.
The zip file should also contain all used non-factory components, in particular M4L devices.
|
|
|
Feb 15, 2012 at 5:06am
Now that I attempt to do so, I’m afraid I cannot reproduce this error in another live set. Since I can’t upload the set in which I saw the problem initially, I’ll have to abandon this enquiry for now (I worked around the issue by using live.remote~ in the other set).
|
