![]() ![]() Why? Because in the end, we find features in the beta that we don’t want to give up. By the time that software becomes public, what you’ll find is that beta users are almost all using the beta builds for their work – even their essential work.Ībleton of course have screaming notices telling you not to use pre-release Live software for your day job, because it may not be stable. Now, beta testers are usually closer to the company (as certified trainers, for instance), but very often the beta users are disappointed with releases in early builds. This is not just my perspective you can watch it happen with beta testers. ![]() So I find that Live updates normally get some disappointment at first … until people dig in and find out what actually changed. What you do get is a lot of small changes bundled into big updates, and a lot of additions that had been requested a long time, but implemented with real care. But it does mean that you don’t always get constant updates packed with features or radical changes. The upside of that is, it’s very rare they’ll touch stuff you like. There’s a sort of a cycle that happens with Ableton Live updates. Wait, no, this is actually a huge upgrade. It may not seem radical at first, but it does three things enthusiasts may appreciate – it gives you stuff you asked for, it’s more creative to work with, and it’s got some serious nerd candy.
0 Comments
Leave a Reply. |