I think this view misses the point slightly. Max was built on collaboration. The open source ethos is a core part of what has made it a success so far. Already in the library on your site there are modified devices being shared (the PeakMod device being one example). This is a good thing as long as credit is always given and the modifiers have collaboration as their main motivation.tempus3r wrote:This is exactly what I would do if I were Ableton.3dot... wrote:I think a 'runtime' should be included in the suite...
the edit button should cost the extra 299...
(either way .I'm getting it...)
I think eventually they will need to go in this direction. When talking to some max developers about http://www.maxforlive.com one of the things people say is that they would only share their devices/patches if users could NOT edit them.
Some people worry that users will take their devices, change them slightly, and repackage them as their own. If/when we see people starting to charge for their devices this issue will come up often. If there was an ability to share a device that could not be edited, and have any user run that for free, it makes potential business models based on M4L a lot more interesting.
Free runtime with Suite with no edit button ftw!
At the same time I believe developers should have the option to bring devices to market that are locked down. If developers are going to bring unique products to market they 1.) deserve to profit from their efforts and 2.) need to have a large enough market of potential customers to make their efforts worthwhile. Many Live users are only interested in accessing new devices not creating their own and $299 is a high price for this (the number of bundled devices are irrelevant if you are only interested in using 1 of those devices).
Max For Live is going to be a success, I'm pretty certain of that. The question remains as to whether it can break out of the coding community and create an viable economic ecosystem of it's own. IMHO the current pricing model severely limits this from happening. Having said all this I'm pretty certain C74 and Ableton have discussed this at length and maybe the don't believe the product is mature enough at the moment to support a runtime as well as the main product.
Whatever the answer, all I do know is that I'll be purchasing the M4L at launch and hopefully utilising it with a spirit of collaboration.