EnochLight wrote:To be clear (since some people seem more interested in ad hominems than respectfully discussing subjects like grown ups), Tube D's approach is extremely convoluted, uninspiring, and certainly not good for "workflow". It's essentially treating the loop like an archaic Propellerhead ReCycle REX file and slicing it up with tales. Additionally, this approach does NOT work well for melodic loops, especially loops with strings and other melodic content.
Let's just call it what it is: MPC Live/X's standalone warp (live time stretching) is absolute ass. If enough people make this known to Akai, maybe they'll take it seriously and fix it.
Ahah I totally agree.
I find it funny we debate about warp algorithm on Mpc standalone.
It's very easy: it's a crap.
Not enough cpu for a good one and that's it.
Everybody is aware of this, Akai included.
To have a good warp algorithm, we need a better cpu.
Look at Ableton, and take a look at how much cpu (macbook pro one, much more powerful then Mpc one) is taken by cpu for the standard warp algorithm.
Then switch to the best one, the last one. Very very hungry.
So draw your conclusions.
Mpc standalone warp algorithm is not even at the level of the worst Ableton one, not to talk about PT elastic audio.
We cannot have a good warp algorithm with current cpu in Mpc standalone.
It's just a technical issue.