Ableton Forum

I have it on very good authority that the ONLY reason plugmod still shows up at all in 5 is to throw out less errors when people try to open old patchers. The Live API is the way to go for such things. While I agree that it could perhaps be easier, it's what's going to be in the initial release (and...

Your comments might be more usefully directed to the persons who made and support the CNMAT objects. In the case of non-vanilla (third-party) Max objects, that's always best *unless* you can provide us with specific examples where those objects fail and you believe that the reason for that failure i...

As the filenames might suggest, a max patch (*.maxpat) and a M4L device (*.amxd) are two completely different beasts as far as loading into Live is concerned. If you own Max, you can always open the file from within the Max edit window. There are no plans to support dropping Max patches into a Live ...

It's not a bug, and there's no secret workaround. It was done on purpose in order that the dials would be the same size as the "real" Live UI objects. We'll log it as a longer term request, though.

Or you could do what I do without even giving it a thought: create
a new blank device of whatever type you want, then copy and paste
the patch bits between windows. Does that seem unneccessarily difficult?

The easiest way to convert your plug-ins in a way that supports Automation stuff is to use the Live UI-versions of objects like knobs/dials/sliders/numboxes and to use the objects' Inspectors to set the Initial Enable attribute [put in a value, too, of course]. The name you use as the "Long Nam...

While the help files (when they're present, of course) contain lots of useful examples of how the object is commonly used, the Reference is the final correct and complete description of what any Max object does - keeping that in mind will serve you well in the days to come. You can also see relevant...

Oh - my colleague Emmanuel reminds me that one can also keep an eye on tempo using the live.observer object, since the Life Object Model stuff lists tempo as something that can be set and also observed (I'm so used to using the transport object that it remains a bit of a habit). here's how you'd do ...

There are the in-progress versions standard Max refpages available for the live.path, live.object, live.observer, and live.remote~ objects already there. There's a linked page from the live.path refpage that contains descriptions of the Live Object model. You access refpages by clicking on an object...

Since Max's sense of "musical" time is derived from the Live application, take a look at the Max transport object. I think it'll be of some use to you. You can use the live.path, live.object, and live.observer objects to do things like setting tempo from within Max. Copy this stuff (includ...