MxDCore is the bridge between Live's Python scripting environment and Max - it's the glue that makes the Live control and feedback in M4L possible. LiveLink MxDCore is an updated MxDCore which improves the performance of this bridge when a large number of M4L live.* objects are being used in the set (upwards of ~150). This will allow general Live operations (e.g. inserting/removing tracks, hotswapping etc) to continue to operate almost at the same speed they do when no, or small numbers, of live.* objects are present. http://www.sigabort.co/livelink_mxdcore.html The initial load of a Max4Live device must activate the bridge in the background but once it's started loading/hot-swapping .amxds works surprisingly fast. Have patience with the initial Max for Live splash screen. I think what comes after is totally worth it.
Hell of a lot of Max devices. I think M4L is one of the coolest things in any DAW, but man, who uses it that much? Still, intersting stuff.
