Post
by tomz » Sat Feb 16, 2013 3:48 am
Plugin Delay Compensation, basically ableton has audio compensated correctly (it seems, go check their forums, this shit goes nuts over there) but midi and the visual aspect of the software isn't compensated. So for example, load LFOTool or one of those kind of plugins in a channel after a vst that induces latency and you'll see it doesn't work properly.
Automation isn't compensated either so you're blind automating, if you have plugins that add latency, where you draw your automation lines won't be where the automation actually is being done, because this isn't compensated in Live, it may be silly when you're just starting a project, but it really fucks up when you have loads of channels already.
Also the interface isn't compensated so you can't edit audio properly when you have plugins that add latency, if you try it yourself you'll see it. Add a sample, and load some vsts that add latency on it, then hit play. You'll see that the bar (the vertical one, the one that indicates song position) passes over the sample and when it shouldn't be playing anything it still is playing the sample... total workflow killer.
According to Ableton this happens cause they prioritize the "Live" aspect of it, and they do this to reduce latency when monitoring (so you can play live), that's what they'll tell you. The truth is, they don't want to add a "production mode" and a "live mode" in order to fix this, because they just don't know how to do it, the code is a mess, lots of old code going around and they lost programmers that left onto bitwig.
Just look at the update, they just added Max4Live into ableton, thats it. The automation curves work like shit from what i've read, they're really bad, and the audio to midi is bad too, it cant get even single notes correctly (you'll do it quicker by ear), and the CPU usage is even higher on 9.
Hope bitwig destroys them for not giving a fuck on their customers.