Timo Rozendal

max4live seems to demand some extra attention while developing externals, let me illustrate:

I have made a data storage object with notification options which makes it a blend between [value] and [send]/[receive] (it is based on object_register(..) and notification with object_attach(...));

- If I use a send a receive pair between m4l devices I get a latency of about 5 ms, however with a pair of my own objects the latency is negligible, is this because of the m4l specific implementation of send/receive which ensures thread safety? how should I implement this myself?

- how do I observe in my external if the patcher is disabled or not? when I use a send a receive pair between m4l devices and I disable the m4l device with the receive, it will stop sending out data. However, my own object continues to receive data.

developing-externals-for-use-with-max4live

- how to observe m4l device enabling/disabling in an external

- what should I know about m4l's threading model to be 'safe'?

ok, let me put it shorter:
- how to observe m4l device enabling/disabling in an external
- what should I know about m4l's threading model to be 'safe'?


developing externals for use with max4live