![3929281619_b4be4197df[1] 3929281619_b4be4197df[1]](http://createdigitalmusic.com/images/2009/11/3929281619_b4be4197df1.jpg)
Max for Live is a fantastic product that treads on genuinely new ground. Its level of integration with the user interface and operation of the host reaches a new high, it comes with a rich selection of instruments, effects, and tools to use as examples, and, in combination with Max 5’s re-vamped interface, makes a comfortable development environment. It does all of this inside a host that, true to its “Live” name, provides a unique workflow.
But Max for Live also comes with some significant strings attached, and it confirms some of the disadvantages to Max as a proprietary, vendor-specific development solution for music and performance. That means that it’ll be a superb choice for certain applications, but will fail to be a viable option for others.
Technology is about trade-offs; understanding those tradeoffs is essential to making informed decisions. There’s never a “right” choice; only a right choice for you. I think the music tech community will embrace Max for Live, but it’s also important to have alternatives. The DIY creative music community likely won’t – and certainly shouldn’t – simply make Max for Live and Ableton Live its tool for everything.
In summary:
1. Max for Live doesn’t have a free run-time, which means it’s not your best option if you want to reach a wide audience with your creations.
2. Max is no longer an option for people wanting to develop plug-ins for multiple hosts, a change that didn’t go over well with all developers partly because it was only revealed after Max 5 and Max for Live.
3. Jitter output is crippled in Max for Live if you don’t also own Jitter.
4. Max isn’t an open source tool, which has practical implications, including -
5. You’ll want to choose something else if you’re interested in mobile music making.
You’ll want to weigh these options when considering Max for Live, even before considering the technical specifics of the tool. You may determine it’s still the perfect tool for the job, or you may not; it should simply be part of your equation.
These aren’t entirely black and white issues, so I’ll be specific:
/* Buy links if custom fields not null and not in cat or search results */ ?>
/* End Buy links if custom fields not null and not in cat or search results */ ?>