Right on, Luke. I really like the way you broke this down into the 3 groups. I wonder what previous versions would reveal if looked at like this? Also, some of these 'blank page' features are building blocks to other performance and transformative features. Features don't exist in isolation. Often, feature Z needs a foundation of feature A and scaffolding of feature B to function properly. As for accessibility -- accessibility helps us ALL, even the non-impaired, whatever that means, we all have our challenges.
When i see clip automation at the top of the list i am asking myself how many of the voters actually know that Ableton lets you midi map the clip gain. The best is, its not specifically for a certain clip, once you mapped the clipgainslider no matter which clip you selected for doing this, you will always control the gain of the currently selected clip, for me this is way more convenient than use up and down arrows while holding down a shortcut to change in 0,5 db steps like in pro tools. It works best with endless encoders, so you have no value jumps etc.
Agreed. I'm not an expert but even I recognize that the permutations of the relatively simple control structures provided in Live allow for powerful control.
Only ever buy software for what it can do for you today, not for what you think it should do tomorrow, otherwise you will be constantly disappointed. I will treat the cost of the Live12 update as basically buying 2-3 years of continued updates, which works out way cheaper than the yearly support plans for a certain other DAW.
Software devs gotta eat, and I’m down with paying them whatever model they follow. I agree that grumping about what might come later can’t be good for your music-making now.
The feature I would like to install is users understanding that their personal wishes are not requirements for software developers to live up to. The language around this is just so silly. “Embarrassing”? “Abysmal”? It’s like a pissing contest for whiny children, who can use the largest words Ahem. End of rant
All that is written down in the EULA, in the paragraph "Complexities in the Calimero Complex Approach". A snippet: "The desire to instill a realistic understanding among users that their personal preferences are not obligatory directives for software developers is rooted in promoting a more balanced and respectful interaction."
dude, everyone knows that if you’re having cpu issues with $200 worth of plugins then you should replace them with $12,000 worth of hardware synthesizers. no need to bring class into this.
Very interesting, I have to agree with the community I reaaaaally wish they had bounce in place and freeze groups, two hugely important things for mixing that would save a LOT of time and are honestly super easy to code up. Kinda weird not to get those done.
and here is the thing about the "fix your cpu usage", i do disagree with you on that. when you are very far into a mix and everything is how you want it and then you run out of CPU it is not practical to just go back and redo the mix with less CPU. if you need the freeze stuff you need to freeze stuff and IMO its totally reasonable to want that to be easy. Love your channel tho, just found it and its very cool.
@@synthseeker Fair enough. I'll stand by my claim for the time being, for freeze groups at least. IMO we're talking about a for-loop over existing freeze functionality. I'm a pro developer and IMO that sounds pretty easy given what they have right now. Maybe I misunderstand something about their situation, that's fair, but given my understanding it doesn't seem like a huge ask.
As a software developer, I myself have always said that not paying attention to accessability is saying a big FU to 20% of your possible audience. Of course ... I don't need it for now, but a lot of people do. And as I'm getting older I do notice my eye sight is getting worse so I do appreciate improvements on that side.
Yet, in a very Ableton way - you can scale the interface, but the preferences panel... Noooooo... so off to zooming into the screen for me. These are those small things that show that the design is lacking.
Super pumped for 12 upgrade. When I saw the accessibility update, it made me proud to support Ableton even though I don't need it. Excited for new built in midi tools.
I start use Ableton live lite 4 and trust me you would not complain at what it's become. You don't buy any one instrument that can do everything, and it's good to have limitations. In live lite 4 to have more that 6 tracks i have to bounce tracks together like bass and drums on one track, left and right guitars on track two and so on. This would teach me more about where to sit everything into the mix
You’re completely right in your analysis about use cases for Live. I uses it almost entirely for orchestral writing you could remove session view and audio warping from Live and I wouldn’t notice. Not a single one of those features from the Reddit list is a thing I care about - doesn’t mean they aren’t valid requests, just that to assume they’re universally requested features is wrong. I’d give my first born to be able to edit CC1 automation and velocity without having to switch views
Because it’s original purpose was to be an excellent tool for performing live. And unironically, it still is an excellent tool for performing live. None of that has changed. However, its overall goals and capabilities have broadened in scope significantly.
It's funny how different DAW customers are complaining about stuff other DAWs have while forgetting what they do have. I primarily use Bitwig now because I like it's feature set the best, but it has gaps that I've occasionally missed from Live and Studio One. A lot of these features could only be dreamed about pre-computer recording era. DAWs are incredibly cheap for what you get so I don't get the complaining. Don't like/need the new version? Don't buy it. Or use more than one, and use the one needed for the moment. I don't think there will ever be just one DAW to rule them all.
Yes and yes. DAWs are cheap comparing to a 2" Studer, yes, but the times have changed and I don't think it's wise to criticise users for complaining AND implying that the young ones have it easy, because we had to rub two stick together... I'm 95% on Bitwig as it looks and feels like Live done properly and I've never been involved in demanding or requesting any features, however I do understand why people compile lists of features they'd want to see. It is called customer feedback and companies who do not listen eventually shoot themselves in the foot.
I have no insight into that specifically for Ableton but I’d be surprised if that was the case. It has not been my observation generally across the DAW landscape. How do you know? :)
The level of eye-rolling in response to complaints is related to the rage enclosed in the complaint messaging. That’s all. But taking user feedback is good and Ableton certainly does do that (re:centercode) as companies should. However taking feedback and prioritizing features are separate things and raging that a feature request has not been responded to doesn’t help.
The Bounce in Place or to a new track, or the lack of it, is embarrassing - truly. Live reminds me of many other dinosaur softwares that instead of being re-written for contemporary computers are being kept alive by adding features and not in order of the user base requests. I'm not going to mention, but have a look ant newer, efficiently coded daws, where nobody has issues with the CPU overloads etc. Live needs to be properly updated, code up.
Embarrassing? Not at all. That doesn’t even apply to a software project as large as a daw. Go ahead and mention those “newer, efficiently coded daws, where no one has issues with the CPU overloads”…I’m curious which daws avoid being crushed under the weight of stacked vsts. If that’s a thing I’ll switch immediately!
I agreed with a lot of your video but your Bounce in place argument was weak and single sided. Lots of bounce in place is about audio manipulation and not just about saving CPU. The fact that you have to go through two separate systems and wait for a full freeze and flatten is abysmal in 2023. @@synthseeker
@@synthseeker Do have a look at Bitwig and its memory management. Of course every software can be overloaded, no doubt, but in daily use you'd be surprised. Oh, it also can the seeming impossible "bounce in place", or to a new track, which doesn't destroy the MIDI... MUST BE VOODOO of some kind. And I'll stand by the "embarrassing" statement. Having to Copy a track (if future changes are possible, which is always), Freeze a track, then Flatten... yeah, just the steps you have to take stink of 1994. And considering it is No. 1 request by the dedicated and committed users to be ignored by the programers is embarrassing, if not insulting. I never expect my hardware or software to anything differently to what it does now, my response is a rant on your rant only. You know what Live reminds me of - Akai Force. Seemingly all cool with bells and whistles yet somehow dated, dusty and weird. I've been involved in AKAI's "fight club" and all feedback goes into the too-hard basket and new bells and whistles are added in hope that users mesmerised by new and shiny things will forget that the basics are dated and often ridiculous.
Fair point. I can see the inconvenience of the current freeze options being painful for anyone who does so often as part of their workflow. But there are other ways to setup a project in Live if your workflow revolves around repeated printing of audio. The anger at inconvenience is still not appropriate IMO. “Abysmal” is a bit strong? “F*cking annoying” may be better. :)
@@synthseeker BTW, did you know that a newly and efficiently coded DAWn releases the CPU in between notes in a sequence, so other process are not interrupted? It can be done, but the designers and managers need to *want* to do it, instead of saying "Freeze the track if your computer starts smoking..." Don't make me nerdy, or I'll run comparative tests... :)
