And making great stuff if your channel is any indication. :) subbed!

me too😂

@@synthseeker ☺️ thanks!

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.

Ableton 12 Lite is going to be LIT ! ! ! !

Do what feels right. ;)

Thanks Brian, the creative material chain is additive at the start then folds back on itself. :)

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.

Rawr! 🔨

Laughter is the best medicine, sandboxing VSTs is gooderer. Instruments releasing the CPU between notes - even better.

Agreed.

To be clear “trash” denoted poor quality software, not vsts as a whole.

I’m starting to need it. Time for a bigger monitor. Soon. :)

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.

@@iqnill I agree 100% ... even some of the VST's don't have a scaling interface, although I 've noticed a lot of them are starting to implement it.

@@synthseeker with a 34 inch widescreen, I don't really have much room to go bigger here.

lol my sympathies. :) as for non scaling ui…progress is slow but there *is* progress.

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.

All good thanks for commenting in a reasonable way. :)

I’m not sure I agree with the “super-easy to code” part but I can recognize the need you have.

@@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 much as can be. I haven’t heard of any new features that works on 3 and not 2.

Thanks for being an example of the “blank page creator” case. :)

@@synthseekerto be honest, I do spend a most of my time staring at a blank page wondering what the hell I’m going to create :-)

do you know why its called Live....??

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.

Same here!

Well…actually I might need it soon…accessibility. 🤓

Hello old-timer! :)

@@synthseeker hello my friend, well said about people who have limitations and Ableton trying to bring them in.👍

free upgrade to live lite 11

@@russ254 I have the suite version, but started on 4 lite years ago.

"unpropitiously grievous" ;)

@@synthseeker eloquently retorted, mon frère

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."

Ha! Nice try. :) Who is Live 12 for again?

So many memories of Acid Pro…

🙏 ;)

Sure…if people didn’t already have multiple options for CPU management. Yet they are still raging over lack of convenience. Their rage is irrelevant.

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.

​@@russ254Ouch you got me with that one. Over $10K in synths and I am just here to gloat at DAW users

@@wrenchposting9097 GOTCHA !

I hope not, competition drives innovation. :)

@@synthseeker Not at Ableton, they covered their windows with newspapers and pretend there's no competition.😁

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.

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... :)