looping device: live.observer creating errors despite using deferlow

Hi there,

I’ve created a device which will play scenes in a loop. I’ve attached an annotated version. I’ll explain how it works in a second.

However the problem I’m having is that despite using deferlow after my live.observer I’m still getting “Setting the id cannot be triggered by notifications. You will need to defer your response.” I only get the error message occasionally. And sometimes, but not always, it seems to create a problem and my patch breaks.

To use the device in Live I create midi clips in the first track. I have one clip for each scene. The clips can be any length but not looping.

When started with the button in the device, the first scene is fired and the device begins using live.observer to observe the playing position of the clip in the first track. Once the end of the clip is reached, I send a bang to the beginning of the device and the next scene is fired. The process repeats.

I have a counter which ensures I’m looping through the first 4 scenes automatically. But I can manually advance scenes by hitting the button. Doing this generally creates the error I mentioned above.

I’ve also read this post and the referenced article: https://cycling74.com/forums/%22setting-the-id-cannot-be-triggered-by-notifications-you-will-need-to-defer-your-response-%22

…but I couldn’t find any practical solutions after doing so.

Do any M4L experts here have advice?

Much appreciated,

Ted