MaxforLive runtime?

[jeremydb]

will there be a separate MaxForLive runtime, which will allow using but not editing Live devices created with maxforlive?

This is not part of our initial plans. As I mentioned on the Max forum, Live users who do not own Max for Live will be able to use, but not edit, Max Devices, if Live is in test/demo mode (just like you can use Operator or Sampler in this mode, but not save, etc.). But the product is really symbolized by the Edit Button, and version 1 is targeted at users who want to engage with what lies beyond it.

jb

I understand how this would make sense from a MAX user/developer's viewpoint, but there is probably a large portion of Live users who have no time/desire/expertise to create or edit their own MAX patches, but who would be very interested in using Live devices made by others. Providing a separate pricepoint-of-entry for such users seems like a reasonable idea.

I get it from both perspectives, although I think that 'longjohns' hit the nail on the head with his response.

In this endeavor, though, I'm just a coder, and I have little or no control over things like marketing decisions and product planning. I personally think that, when you see how a) nice the workflow is, b) easy it is to make even little devices that significantly change the sound and feel of your music and c) well-documented/tutorialed the whole thing is, you'll want to hit that edit button, too!

jb

[Coupe70]

i am a bit confused now - did i misunderstand something ?
or should i read it like this:

version 1 is targeted at users who want to engage with what lies beyond it

[jeremydb]

i am a bit confused now - did i misunderstand something ?
or should i read it like this:

version 1 is targeted at users who want to engage with what lies beyond it

As in, the initial release of the product.

[stringtapper]

Yeah now that I've rolled it around I can't see them making M4L a free runtime because in the end, whether you're interested in patching or not, it's an added functionality. Of course if you buy it and you're not patching I think you've kind of missed the point.

[Coupe70]

well, whatever. what i can say is, i had a close look on max some time ago
and i personally do not need its editing possibilities and i am quite sure
that i cannot afford max for live (the upgrade from live 6 to 8 alone will cost
me 199 euros). but i would love to buy me the one or the other extra
feature for live made with max if it was possible...

[jeremydb]

Yeah now that I've rolled it around I can't see them making M4L a free runtime because in the end, whether you're interested in patching or not, it's an added functionality. Of course if you buy it and you're not patching I think you've kind of missed the point.

And you might really love the devices we're shipping with M4L -- the Step Sequencer, for instance, and maybe having access to that device is enough for you to take the plunge. And not only the device, but the GUTS, too! How cool is it that if the Step Sequencer does 98% of everything you wished it did, that you could pop it open and custom-build that remaining 2% yourself?

jb

[djsynchro]

http://www.ableton.com/extend

It comes with a Step Sequencer, a Buffer Shuffler, and a really cool loop thing.
Once it gets going you can expect a gazillion effects, and there'll be really outlandish experimental things that Ableton wouldn't do as part of the standard Live package. And, they sit in the devices bar with the other Live effects. So depending on the price and the strength of the library as it grows you can decide if you want it or not.

[parma]

desire to not do something you've never tried.

probably if I met you it'd make more sense.

I have tried it though - demoed Max/MSP at version 4. Went through the tutorials, thought it was really cool and there were tons of possibilities and...that's it. It was cool but it wasn't fun for me. I can totally see where someone else could enjoy it though.

I spent this summer (like an hour each night) reconditioning/modifying a Fender Rhodes. My wife couldn't understand why I wanted to spend so much time fiddling around with "that thing". For me, it was one of the most rewarding and fun music related endeavors I've undertaken.

Basically I'm trying to say "different strokes for different folks" (but trying not to say it because I hate that saying)

I was just pointing out that a runtime only version wouldn't be as a big an issue if Max was priced aggressively.

ah - got ya. Yes -if it's priced "nicely" then this whole runtime thing becomes moot for me because even if I didn't initially want to "roll my own" I may sometime in the future and if it's cheap enough then it may be worth it.

Live users who do not own Max for Live will be able to use, but not edit, Max Devices, if Live is in test/demo mode

and that is exactly the way you bastards are going to end up getting my money anyway - show me all the cool stuff I could use without running in demo mode if all I do is hit that purchase button

like I said - I pretty much answered my own question in my first post and the more I think about it and hear what others have to say I can see why there would be no runtime version.

I guess I'll have to wait and see what kind of pre-made thingies are included (or the crazy things users come up with) to see whether or not I'll bite. I'm sure I'll talk myself into it before the night is over!

[Semuta]

Will m4l devices run under rewire? I would assume so...

[Coupe70]

now that the initial question seems to be answered, may i ask
somehting else about max for live (as i know jeremy is reading
this thread) ?

as max for live is kind of limited to the inside of live, what
possibilities are there to communicate with the "outside world" ?

and i think robert henke mentioned that jitter is also included.
does that mean i can produce my live-visuals inside live without
additional visual software ?

[jeremydb]

now that the initial question seems to be answered, may i ask
somehting else about max for live (as i know jeremy is reading
this thread) ?

as max for live is kind of limited to the inside of live, what
possibilities are there to communicate with the "outside world" ?

and i think robert henke mentioned that jitter is also included.
does that mean i can produce my live-visuals inside live without
additional visual software ?

We're not crippling Max's communication with the outside world, to the best of my knowledge. If you want to use a Max Device to convert MIDI or audio into serial port instructions for a robot claw or OSC data over a UDP connection, you should be in business. Same goes for Jitter.

jb

[Coupe70]

mmmh, robot claw....



just one last question:
is it possible to do the things that were possible with the
hacked api of live 7 - read out the position of clips in the
session view, their color, name... ?

i read about live.object, live.path, and live.observer objects,
but don't know what it is.

[jeremydb]

mmmh, robot claw....

just one last question:
is it possible to do the things that were possible with the
hacked api of live 7 - read out the position of clips in the
session view, their color, name... ?

Yep. There are three special objects: live.path, live.object and live.observer which interact with the Live API (extended and documented for Max use). Jan Buchholz's cool APC40 demo at NAMM, which "abuses" the APC as a step sequencer interface, was done with the help of these objects.

The precise feature set and limitations of that API are still unreleased, though, and I don't have more information than that right now. In any case, it's very exciting.

jb

[Coupe70]

thanks a lot jeremy !

going to bed now, there's a lot to dream about...the robot claw.......

[Gurulogic]

My Monome is getting excited...