i lol'dhoffman2k wrote: M4L has the advantage that we can make more elaborate workarounds than we already have to do using Live normally.
accessing devices inside a rack
Re: accessing devices inside a rack
Re: accessing devices inside a rack
I'm paraphrasing this following statement, because I heard it in person many years ago and don't recall the exact wording. But Gerhard Behles once stated: "Our users shouldn't have to resort to workarounds. If a large number of people resorts to a specific workaround, we should look into making it a feature."fisk wrote:i lol'dhoffman2k wrote: M4L has the advantage that we can make more elaborate workarounds than we already have to do using Live normally.
That should give you a better idea of why I appreciate M4L. People can actually work together to implement a feature into Live. If enough people actually resort to a "nasty" workaround. It shouldn't take much to either persuade Ableton or Cycling that "people demand feature X". They're users too after all.
Re: accessing devices inside a rack
maybe.
altho tbh i can't see Ableton going for prog changes, they seem adamant that racks are better. i've now seen several forum posts that indicate their position on that. prog changes are spiky, i can see their thinking, but there's a shade of arrogance there as well. they could let the users choose.
after all we can select buffer sizes.
altho tbh i can't see Ableton going for prog changes, they seem adamant that racks are better. i've now seen several forum posts that indicate their position on that. prog changes are spiky, i can see their thinking, but there's a shade of arrogance there as well. they could let the users choose.
after all we can select buffer sizes.