How have you still not fixed this?
Every so often, I plug in the ROLI again in the hope that anything works better. The setup is still the most painful implementation I can imagine. There are people on Github who came up with a better way of doing the setup, at least, and they cracked that problem two years ago. As for using it with Equator... Sure, I could *play* stuff in if I make the absolute perfect performance, but forget editing the notes or the automations. I'd like to be able to buy other MPE software like Falcon, or at least use MPE with the other VSTis I already own, but that's not on the cards.
I get really sick as an Ableton user of waiting years to get things like VST3, and here's yet another thing to annoy me. How long will I wait for this? A year? Three? Five? Makes me feel like moving on to a different sequencer.
n9 wrote: ↑
Sat Aug 31, 2019 10:44 pm
People inside Ableton have been pretty upfront that implementing MPE means a complete rewrite of the MIDI and MIDI clip components of Live, which is some of the oldest code in the codebase. It is a VERY expensive feature for them to implement because of this and is the kind of thing that could trigger a need to rewrite even larger amounts of code. My theory (as a Product Manager person in software) is that because of this the cost/value proposition of MPE just isn't anywhere high enough to justify the expense in time and money to do that rewrite and so they are waiting until the cost v benefit equation changes to do it....
I can usually see those arguments, but we pay £539 to own Suite. It's a self-defeating argument, how many people seem to want it versus how much it's worth to the company. As long as it's famously borked in Live, you can't really measure the demand or make a cost/benefit analysis. The apparent demand for VST3 was zero until we finally got that support, because it was pointless for Live users to buy the format. As the amount of hardware and software supporting MPE ramps up, and as long as it's a feature Live claims to support, they should... support it
That's the better of the two possibilities I'm thinking of. The worse is that the MIDI code is so central and so old that they have been trying to rewrite it for a couple of years to update it to do a few things, including implementing MPE, and they have been unable to get the work done as changes in that part of the codebase are breaking everything.
We have seen both of these scenarios play out re: MPE on many software projects -- other DAWs, instruments, etc. For example: Omnisphere has a poor MPE implementation because they do not want to rewrite the core engine -- it would cost too much, so they hacked a workaround. Zebra2 cannot be updated to be MPE so they are going to include MPE in the completely rewritten from scratch Zebra3, which Hive was written such that implementing partial MPE spec was pretty easy to do. Live is looking more and more like a Zebra... needing a dramatic rewrite.
Again my 2 cents (someone that waited from 2017 to Jan 2019 for MPE support and then went elsewhere.)
Yeah, good points. Thanks for your reply!