Basvlk

Hi - I'm sharing an abstraction which I hope is useful for others (and of course I'd love to get feedback)

Assuming that live.remote and live.observer are quite resource intensive, and you may not actually use them all the time. While keeping your M4L devices loaded you may temporarily want to switch the resource intensive objects 'off'.

In my case: I'm building a remote controller with different screens, when screen2 is visible I don't need M4L to be updating controls that are invisible because they are on screen1: It's a waste of resources.

As far as I understand from the documentation, sending an 'Id 0' to the right inlet of an M4L object switches them off (kind of).

The attached abstraction does just that: Switching off ('TOGGLE' inlet '0') passes on an 'id 0' ot the outlet and switching on (toggle '1') passes on the live path - or re-sends the buffered path. If the path was changed while the patcher was 'off', the new path is sent out when you switch it on again.

Assuming that live.remote and live.observer are quite resource intensive, and you may not actually use them all the time. While keeping your M4L devices loaded you may temporarily want to switch the resource intensive objects 'off'.
In my case: I'm building a remote controller with different screens, when screen2 is visible I don't need M4L to be updating controls that are invisible because they are on screen1: It's a waste of resources.

As far as I understand from the documentation, sending an 'Id 0' to the right inlet of an M4L object switches them off (kind of). 

The attached abstraction does just that: Switching off ('TOGGLE' inlet '0') passes on an 'id 0' ot the outlet and switching on (toggle '1') passes on the live path - or re-sends the buffered path. If the path was changed while the patcher was 'off', the new path is sent out when you switch it on again.


Sharing: On/Off switch for M4L objects