ID cannot be triggered by notifications.
I'm trying to build a patch which allows me to set the loop in marker quantized to the nearest beat on the playing clip.
I am getting the 'Setting the ID cannot be triggered by notifications' error message in the Max window.
I have made sure whenever a notification is sent it doesn't set anything else without connecting to a deferlow object, is the correct thing to do? I am still getting the error message.
I've tried your patch and got the error message too, but nonetheless it seems to work as expected.
Maybe in this case the message can be considered just as an "overcautious" warning?
Ah, your reply has saved me a lot of headache.
I was confused with this message as it would not appear every time a notification was sent, I tried to fix it and nothing seemed to work!
Now I know i can proceed, without the fear of it interfering with other parts of my patch.
Thanks Broc!
Is there a strict rule I can follow as to where to place the deferlow objects in the message flow?
I feel like I place them without knowing where they actually should and they are not needed...
For example. A prepend object to a message object, I wasn't sure either to put it before the "prepend" or before the "message".
Usage of deferlow is explained in the 'Live API Overview', section 'Notifications'.
I understand that notifications are created and why a deferlow is used, but I don't quite understand where specifically a deferlow object should be placed in the messaging flow.
Can you advise?
Usually I insert deferlow directly at the outlet of live.observer or live.object that creates notifications.
This way it takes effect on all depending messages.
The technical functioning of deferlow is explained in this article
That explains a lot!
Thankyou