Ableton LIVE 10 ... Officially Announced. (plus: Buy LIVE 9 now with 20% discount, get LIVE 10 free)

[Spencer Maddox]

If that is fake that is a well done fake...
It appears one of them is on a lanyard...like the kind you would wear at a Convention....like LOOP!
IDK...just me speculating. But it makes sense!

[jonljacobi]

If they are fake, then Ableton should copy them. Nice stuff.

[Daags]

BO SELECTA !!

Saw this on Reddit earlier...not sure if it's legit, but I have no reason to believe that it isn't:

[Daags]

found another pic ... probably from the same user

[antic604]

[loungepanda]

You guys suck at linking



That alignment with the 9 and the 0 is making me nauseaus

[Uriel Anthony]

Just want to say while it's true some M4L patches has high CPU usage and that usually tends to result in instability, the real reason is actually that those patches are simply badly written resulting in unnecessary CPU cycles and those really adds up if the patch is complex.

I know this because I write my own patches or modify/optimize others that I've downloaded to use. Believe me, I've come across quite a bit of great M4L patches but with inefficient code on the net. Remember, M4L is really just a very small part of the whole larger Max community, which in there you seldom hear about users complaining about high CPU usage or instability because they are all coders who knows how to fix it or seek out help within the community.

That said, I think M4L still has its appeal but probably more for power users who knows how to write/edit patches rather than for normal users who just download patches to use. Besides M4L isn't just about modulations, it can so do much more and that is the biggest reason why I didn't jump ship over to BW.

P.S. My only issue with M4L is that it isn't multi-touch capable but again neither are Live.

[antic604]

Just want to say while it's true some M4L patches has high CPU usage and that usually tends to result in instability, the real reason is actually that those patches are simply badly written resulting in unnecessary CPU cycles and those really adds up if the patch is complex.

I know this because I write my own patches or modify/optimize others that I've downloaded to use. Believe me, I've come across quite a bit of great M4L patches but with inefficient code on the net. Remember, M4L is really just a very small part of the whole larger Max community, which in there you seldom hear about users complaining about high CPU usage or instability because they are all coders who knows how to fix it or seek out help within the community.

That said, I think M4L still has its appeal but probably more for power users who knows how to write/edit patches rather than for normal users who just download patches to use. Besides M4L isn't just about modulations, it can so do much more and that is the biggest reason why I didn't jump ship over to BW.

P.S. My only issue with M4L is that it isn't multi-touch capable but again neither are Live.

Oh, I think everyone knows that! The main complaint is however, that you need to actually run whole MaxForLive if you want to use *simpler* Max devices like the LFO or Envelope Follower, whereas they could easily been "compiled" to be a native Live devices. As you say, leave MaxForLive for those that actually want to tinker with stuff, but those devices that are already there should be somehow exportable to native format or at least run on some M4L Lite, which doesn't have the editor, scripting, is sandboxed, etc.

Hope v10 delivers (some of) that!

[mcbpete]

Yeah that'd be ace - It takes just as long for me to load the standalone Max application from scratch than it does to just employ a simple .amxd on my set (as presumably the first time you load any m4l devices it does in fact just launch Max in the background) so some sort of trim 'read only' Max Lite would be great

[keel]

There is rumours that Ableton have decided to make Live more like Live performance software and not so much production DAW. And because of this, many well known producers have decided to move away from Live. If the host future is more to Live performance, that makes sense then.. But dunno, rumours are always rumours..

[Harry_HH]

There is rumours that Ableton have decided to make Live more like Live performance software and not so much production DAW. And because of this, many well known producers have decided to move away from Live. If the host future is more to Live performance, that makes sense then.. But dunno, rumours are always rumours..

This statement/rumour sounds bad - and it is incorrect in that way that Live already is "not so much production DAW" and "more like a live performance software". I.e. Ableton don´t have to make it lean to that directon. But if this rumour is true, it will not only lean but fall to that directon, and I have to move to the Cubase (which UI is awfull).

[Riansky]

There is rumours that Ableton have decided to make Live more like Live performance software and not so much production DAW. And because of this, many well known producers have decided to move away from Live. If the host future is more to Live performance, that makes sense then.. But dunno, rumours are always rumours..

I don't think that will happen tbh. Yes they are making it more for live performance but I doubt they will ditch the "DAW side" of Live in my opinion. They have to much of a big audiance using Live for production. If anything I've seen well known producers move from other DAW's to Live. But as you said, rumors are always rumors.
Anyway,
What are you hoping to see in Live 10 feature wise ?
I'm hoping for a slightly better GUI, Automation snap to grid, groups in groups, maybe some comping features (which I highly doubt) and some work on MIDI functions, they are pretty limiting tbh.

[whyterabbyt]

Oh, I think everyone knows that! The main complaint is however, that you need to actually run whole MaxForLive if you want to use *simpler* Max devices like the LFO or Envelope Follower, whereas they could easily been "compiled" to be a native Live devices.

well, no. There's no such thing as 'easy compilation' from generic MAX patches to native code.

[Harry_HH]

It may a bit late to put out wishlists for the Live 10, because decisions for that have been made for it 3 years ago. I wrote one to these threads back when the Live 9 was launched, it includes among others better MIDI editing, better piano roll/editig, better automation editor, vst3 support + many small improvement type better tempo automation editing. In my long list is notation-feature integrated to the MIDI editing, but I guess that will be pure fantasy in Live´s case.

[ghettosynth]

Oh, I think everyone knows that! The main complaint is however, that you need to actually run whole MaxForLive if you want to use *simpler* Max devices like the LFO or Envelope Follower, whereas they could easily been "compiled" to be a native Live devices.

well, no. There's no such thing as 'easy compilation' from generic MAX patches to native code.

Yes, but in fairness, I think that antic meant that there's no reason that the devices could not have been coded, and consequently "compiled", as native live devices. Of course, "no reason" is an overstatement, but, I agree with the sentiment that Ableton should have already developed some more efficient native devices for those common cases.

What I'd really wish that they would do is release an SDK so that other people could create native devices. It's one of the few platforms where it matters.