Why are there no 'MIDI' LFOs in Live ?!?
-
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
Why are there no 'MIDI' LFOs in Live ?!?
...this is a long story. I try to make it short.
First of all, we (Ableton) would want to have modulation devices like LFOs in Live too. So, why the are we not doing it ????
The reason is a technical reason that leads to a conceptual problem, and we need to
solve the conceptual problem, which is very tricky, first. Then we can address the
technical problem, which is a huge effort. It's basically rewriting an important part of the engine.
So, you want to ask what is the problem? The problem is the ambiguity between
automation data, which is e.g. the parameter changes you can record in the arranger, and modulation data, which is the clip envelopes.
In the current internal data structure, each parameter can be controlled by exactly
one automation and one modulation. The automation is always directly the
movement of a 'knob' in the pannel, and this movement can be created by a
moving a knob with the mouse, or by an automation curve in the arranger, or by a
midi mapping, or by a macro control. The modulation which currently only can be
provided by a clip envelope belongs to that parameter and is independent from the
automation. The point where these things come together is the parameter itself.
When we invented the clip envelopes for Live 3 this structure seemed to be a good
concept, since the user does not need to do anything but drawing a clip envelope,
and he/she still can change the parameter that is modulated and there is no further understanding needed.
A better system from a todays perspective would allow any parameter to be
controlled in a relative or absolute fashion by many sources, and therefore allow for things like:
-automation of parameters within a clip, and not just modulation.
( -> automation recording not just of MIDI CCs but all parameters from within a clip )
-more then one modulation source per parameter ( -> LFOs !!! )
-control of a single parameter from various sources with variable curves. ( e.g. macro controls )
This sounds all very exciting, and would improve Live dramatically. However, it
would be the one single most complex re-design of the software since version 1.0.
It would change not only the way the engine handles automation data, but would
also require new interface strategies. It raises questions like: Is there automation
in the clip or in the arrangement or both? If so, which one wins if you move/delete
things? How to visualize multiple modulations? Can an LFO be modulated by itself?
What happens at overdub, ... and many more little things that can drive you nuts
if you sit in front of a whiteboard and try to solve them...
We planned to address the automation story for Live 7 but we had to realize that it
would be too risky at that time, and there were too many open questions. We are
still continue thinking about it, because it is obviously very very desirable.
However, it might turn out that the changes would be so drastic that it would be
impossible to open older documents in that new version and things like that.
Things we simply cannot do anymore, too many users rely on us.*
We could find a it-somehow-works solution for the LFO idea. But it would be a
dirty hack, and would make it even harder to finally come up with a better solution
for all the above mentioned wishes.
So, at the current state of affairs, it is not too likely that the LFOs will come soon.
Now you can hang the messenger,
Cheers, Robert.
*as a side note, this happens to a lot of companies: Mac OS 9 had to die because
there was no way to maintain and improve it anymore. Protools has this huge
legacy of the TDM hardware, that makes it hard to re-write the audio engine
without making customers who payed a gozillion for their old systems totally
mad...
First of all, we (Ableton) would want to have modulation devices like LFOs in Live too. So, why the are we not doing it ????
The reason is a technical reason that leads to a conceptual problem, and we need to
solve the conceptual problem, which is very tricky, first. Then we can address the
technical problem, which is a huge effort. It's basically rewriting an important part of the engine.
So, you want to ask what is the problem? The problem is the ambiguity between
automation data, which is e.g. the parameter changes you can record in the arranger, and modulation data, which is the clip envelopes.
In the current internal data structure, each parameter can be controlled by exactly
one automation and one modulation. The automation is always directly the
movement of a 'knob' in the pannel, and this movement can be created by a
moving a knob with the mouse, or by an automation curve in the arranger, or by a
midi mapping, or by a macro control. The modulation which currently only can be
provided by a clip envelope belongs to that parameter and is independent from the
automation. The point where these things come together is the parameter itself.
When we invented the clip envelopes for Live 3 this structure seemed to be a good
concept, since the user does not need to do anything but drawing a clip envelope,
and he/she still can change the parameter that is modulated and there is no further understanding needed.
A better system from a todays perspective would allow any parameter to be
controlled in a relative or absolute fashion by many sources, and therefore allow for things like:
-automation of parameters within a clip, and not just modulation.
( -> automation recording not just of MIDI CCs but all parameters from within a clip )
-more then one modulation source per parameter ( -> LFOs !!! )
-control of a single parameter from various sources with variable curves. ( e.g. macro controls )
This sounds all very exciting, and would improve Live dramatically. However, it
would be the one single most complex re-design of the software since version 1.0.
It would change not only the way the engine handles automation data, but would
also require new interface strategies. It raises questions like: Is there automation
in the clip or in the arrangement or both? If so, which one wins if you move/delete
things? How to visualize multiple modulations? Can an LFO be modulated by itself?
What happens at overdub, ... and many more little things that can drive you nuts
if you sit in front of a whiteboard and try to solve them...
We planned to address the automation story for Live 7 but we had to realize that it
would be too risky at that time, and there were too many open questions. We are
still continue thinking about it, because it is obviously very very desirable.
However, it might turn out that the changes would be so drastic that it would be
impossible to open older documents in that new version and things like that.
Things we simply cannot do anymore, too many users rely on us.*
We could find a it-somehow-works solution for the LFO idea. But it would be a
dirty hack, and would make it even harder to finally come up with a better solution
for all the above mentioned wishes.
So, at the current state of affairs, it is not too likely that the LFOs will come soon.
Now you can hang the messenger,
Cheers, Robert.
*as a side note, this happens to a lot of companies: Mac OS 9 had to die because
there was no way to maintain and improve it anymore. Protools has this huge
legacy of the TDM hardware, that makes it hard to re-write the audio engine
without making customers who payed a gozillion for their old systems totally
mad...
-
- Posts: 3604
- Joined: Fri Jun 04, 2004 2:57 pm
- Location: The south east suburbs of Malmö, Sweden.
Best thing I've read all day, *cheers*
roach- the other white meat
http://www.themenacetosobriety.com/blog/
MBP, Live Suite, and lots of nice analogue gear.
http://www.themenacetosobriety.com/blog/
MBP, Live Suite, and lots of nice analogue gear.
+1Lo-Fi Massahkah wrote:Ah. We love it when you get technical.
Or is it just me?
Seriously, I love that you come on here and actually explain things. In an honest and straight forward way.
Cheers,
.m
Love this company!
Too bad it can be implemented soonish.... but hell..it's not like the most necessary thing
Last edited by lola on Tue Sep 30, 2008 6:53 pm, edited 1 time in total.
-
- Posts: 4357
- Joined: Fri Oct 14, 2005 1:29 am
- Location: The Ableton Live Forum
-
- Posts: 3604
- Joined: Fri Jun 04, 2004 2:57 pm
- Location: The south east suburbs of Malmö, Sweden.
Uhu...!? On that note...Tone Deft wrote:now, about that Cycling 74 announcement...
Jazzmutant are promising clip names on the Lemur from v2 (that'll go into beta in about a week). In my mind, that would only (?) work with OSC support from Live - so maybe something is happening on that front in Live 8.
.m
Thanks so much for taking the time to explain things to us....a huge step in the right direction. Now you'll have even more heads working on this problem! This conceptual barrier has come up before in the discussion of the relationship between session and arrange, so it seems to be holding back more than just a single feature implementation. As a customer, I would rather wait longer for a new version or pay more, than for Ableton to not address this barrier in the near future. I loved the feeling I had in Live 3, that anything was possible and the only limit was my imagination...the feeling that Live could do far more than it was even intended to do. I want to have that feeling again, and for me that would mean being able to route anything to anything else, record anything I want, and feed it all back into itself.
That being said, I would be pretty happy if there was a just a MIDI device that sent out CC data according to an LFO that I could then route back into Live using MIDI-yoke. Not ideal, but it would sure help me pull off some things I've been wanting to do.
That being said, I would be pretty happy if there was a just a MIDI device that sent out CC data according to an LFO that I could then route back into Live using MIDI-yoke. Not ideal, but it would sure help me pull off some things I've been wanting to do.
nah, I don't think that's what he said at all.nowtime wrote:@Robert
Am I hearing you say that there will probably never be automation recording in clips because the engine overhaul would most likely make all old sets non-functional?
notice the underlined and bold segments.Robert Henke wrote: We planned to address the automation story for Live 7 but we had to realize that it
would be too risky at that time, and there were too many open questions. We are still continue thinking about it, because it is obviously very very desirable.
However, it might turn out that the changes would be so drastic that it would be
impossible to open older documents in that new version and things like that.
He's saying it's very tricky and that's why it takes time, they must dodge some very nasty obstacles, that means trying a few different plans and seeing what is best. It may be that it needs a "year zero", but that would be the worst case scenario, it may be that one of their alternative plans may bear fruit.
Hats off to Robert for telling us what's going on.
Lo-Fi Massahkah wrote:Uhu...!? On that note...Tone Deft wrote:now, about that Cycling 74 announcement...
Jazzmutant are promising clip names on the Lemur from v2 (that'll go into beta in about a week). In my mind, that would only (?) work with OSC support from Live - so maybe something is happening on that front in Live 8.
.m
Nah, they just hacked one of the API projects or did one themselves.
Its possible to get clip names right now over OSC or Sysex...
What isn't possible is displaying more then 8 pieces of dynamic text on a lemur V1.6.
-
- Posts: 2846
- Joined: Sat Sep 25, 2004 6:37 am
- Location: Chicago, IL
- Contact:
-
- Posts: 3604
- Joined: Fri Jun 04, 2004 2:57 pm
- Location: The south east suburbs of Malmö, Sweden.
-
- Posts: 11426
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
I might be reading too much into this, but it seems like the re-write it if ever happens would also solve the 128 parameter limit? If so, I personally vote for a TDM/OS9 slash and burn style rewrite! (as Angstrom pointed out IF it's necessary)
It's not like you guys have ever made it impossible to use older versions on the same computer, hell even at the same time.
It's not like you guys have ever made it impossible to use older versions on the same computer, hell even at the same time.
-
- Posts: 4357
- Joined: Fri Oct 14, 2005 1:29 am
- Location: The Ableton Live Forum
It also sounds like it would solve recording clip envelopes.Machinesworking wrote:I might be reading too much into this, but it seems like the re-write it if ever happens would also solve the 128 parameter limit? If so, I personally vote for a TDM/OS9 slash and burn style rewrite! (as Angstrom pointed out IF it's necessary)
It's not like you guys have ever made it impossible to use older versions on the same computer, hell even at the same time.
Professional Shark Jumper.