My M4L device functions even though the device is not enabled in Ableton.
My device continues to respond to parameter changes even though the device is disabled in Ableton.
The device reads track information such as track colour and transmits it via udpsend. It also displays these parameters in the presentation of the device. Very strange.
Other m4l devices I have tested are indeed disabled when the device itself is disabled.
For example: I built a test counter which does follow the enabled button of the Live device. I.e it runs when the device is enabled and is frozen when the device is disabled.
Under what circumstances does a M4L device keep running even though the Live device is disabled?
To my understanding, turning a device off only turns the live.objects to their inactive mode and the audio off but everything else works (midi). You can use the middle outlet of live.thisdevice to turn stuff off
Thanks for the tip regarding live.device!
I was using loadbang with delay but this way is more robust.
My device is using LiveAPI with javascript and for some reason an array reference pulls a js undefined error.
By waiting until the device fully loads the error is not seen. However when I open the device for editing the device is reinitialised in such a way as to pull the undefined error. I suppose I will come to understand the underlying cause....
Thanks for any comments.