I'm sick of Ableton crashes!!! And to not know which plugin is giving a crash, searching log.txt files, reaching to Ableton support etc. then even after you learn, it doesn't solve the problem. I bet they have a huge headache every single day from the clients because of these crashes. Please bring this sandbox technology as soon as possible, otherwise you'll see more than 50k people who uses Bitwig. You created Bitwig and you let Bitwig grow with this approach. You're not listening to us. FOR A LONG TIME PEOPLE ARE RECOMMENDING THIS! Bring it asap please PLEASE PLEASE! I don't want to switch DAW. But if this feature will not come soon, I will unfortunately switch the DAW like many other fellow Ableton producers. Because what is the meaning of Ableton if I can't open my ongoing projects, if I can't work on it, right?
Give us the option of operating third party plugins separately!
Bring the sandbox technology!!!!!!!
-
FurkanTopal
- Posts: 37
- Joined: Tue Feb 07, 2023 3:11 pm
- Contact:
-
DerKastellan
- Posts: 6
- Joined: Thu Dec 08, 2022 12:24 pm
Re: BRING THE SANDBOX TECHOLOGY ASAP!!!!!!!
This is the main reason I started spending more time with Bitwig, too.
I'm annoyed that I get surveys asking what I think about AI and yet things existing customers want languish forever and ever.
I'm annoyed that I get surveys asking what I think about AI and yet things existing customers want languish forever and ever.
Re: Bring the sandbox technology!!!!!!!
+1
at least give us a way to see which vst or m4l crashed live.
at least give us a way to see which vst or m4l crashed live.
copy the text, open Live > drag in empty M4L device > open Max editor > paste > save M4L device
https://docs.cycling74.com/max8/vignett ... ng_patches
https://doubleUG.bandcamp.com/releases
https://docs.cycling74.com/max8/vignett ... ng_patches
https://doubleUG.bandcamp.com/releases