New Feature: a professional tool

Share what you’d like to see added to Ableton Live.
Mint Puma
Posts: 3
Joined: Sun Sep 04, 2022 6:37 pm

Re: New Feature: a professional tool

Post by Mint Puma » Mon Sep 05, 2022 9:55 pm

I think this a privacy law thing.

The way it is now proves by itself the user her/himself sent the data voluntarily.

Same reason you have to manually accept cookies in every bloody website you visit.
Every other software developer provides a way to opt-in.

jacobeen3006
Posts: 3
Joined: Sun Sep 04, 2022 9:03 pm

Re: New Feature: a professional tool

Post by jacobeen3006 » Tue Sep 06, 2022 2:06 pm

pottering wrote:
Sun Sep 04, 2022 11:22 pm
jacobeen3006 wrote:
Sun Sep 04, 2022 9:15 pm
Ableton 11 crashed 3 times in this year. Running 377 hours until now. Just stats…
Yeah, Live saves crash data in folders for each version (Users > AppData > Roaming), it is pretty visible here how much less crashes there are since Live 9.

For me each Live 10 and 11 version progressively reduced crashes and bugs in a perceptible manner.

Had more than 3 crashes this year (14 here, 2 per month, I use Live daily, even weekends), but less than I used to for sure.

Also, that list of bug fixes someone posted is from the Beta version, not the actual full release.

https://www.ableton.com/en/release-notes/live-11-beta/

https://www.ableton.com/en/release-notes/live-11/
Dont take me wrong, everyone demands fixes from Ableton cause no one wants to use anything else :) its a great tool. Btw beta surprisingly works well better

Machinesworking
Posts: 11551
Joined: Wed Jun 23, 2004 9:30 pm
Location: Seattle

Re: New Feature: a professional tool

Post by Machinesworking » Tue Sep 06, 2022 8:22 pm

goose3000 wrote:
Mon Sep 05, 2022 2:28 am
Bitwig and Reaper both have sandboxing. That’s besides the point- it’s highly requested and invaluable as a feature. Especially when you consider a major selling point of Live is performing live. Legitimately, consider a scenario where a plugin crashes in a performance; how irreparable that is to the show. Better to not risk the using the plugin at all (not a solution…)
It is absolutely 100% the solution to not use crashing plug ins during live performances. In fact Bitwig and Reaper will not entirely save a performance with sandboxing otherwise.

You're calling a feature invaluable that only a few DAWs have. Reapers implementation BTW is 100% setup to force you to use it only for crashing plug ins you're aware of, it's really pretty bad as mentioned here by other forum members. Personally I didn't even know Reaper could do sandboxing because checking that box in previous versions made Reaper eat as much CPU as Live etc. which defeats the purpose of using that Excel spreadsheet of a DAW. So now it's hidden in a right click menu and you can only select it individually, which means you would spend a couple hours doing so with my collection.....

I'm not at all saying it's not a great feature, but we do absolutely nothing positive by calling a DAW unprofessional because it doesn't have a feature we want. Bitwig IMO remains the only DAW that does this feature decently, and it was literally built with the feature in mind. Plug ins will still hang in Bitwig BTW, nothing is 100% effective, besides isolating the offending plug in and using it sparingly in production and not while performing.

Post Reply