Re: Major Problems With Live 11
Posted: Wed May 12, 2021 12:12 pm
Ableton already separates vst2 and vst3 in the plugin browser and are scanned separately too. I haven't come across any problem plugins yet.
Well, YOU can tell Live to do so... just go to the plugins' Preferences tab.Dandy Dust wrote: ↑Wed May 12, 2021 11:32 amWould be great if Ableton Live 11 asked me - for example - which version (vst 2 or vst3) should be used.
Did you send detailed info about this to support@ableton.com ?BloodPremonitions wrote: ↑Fri May 14, 2021 1:57 amI have to say that I have had a fairly horrific time changing over to 11. I pre-ordered and have been wrestling with it since the release, I had issues with the plugin scans/library and still am today. Particularly with AU plugins, which it no longer seems to read at all when I boot a session it disables the plugins, and they are not able to be re-activated. Even if I open that same plugin again and it works. Sessions crashing and also a new problem with the interface that I have not seen anyone here writing about... I've encountered an issue where plugin interfaces, clip view, midi view, etc randomly close.
CPU usage is fine for me, I would even say improved (when I have actually been able to mix), but the interface issue has rendered this program completely unusable for me.
Agreed. Ableton could drastically simplify things but they continue to keep it unnecessarily complex and confusing and then offer no support. Did you see this that I wrote about the whole experience? https://medium.com/the-electronic-music ... 4aa6238b07Dandy Dust wrote: ↑Mon May 10, 2021 7:54 pmOn my wish-list: Ableton Live should have some kind of VST - Interface that structures the scan.
Most incredible: Live 11 produces a new folder called VST3, and suck in there, what ever (also) has a VST 3 version installed...
But many of the VST - plugin depend on their own folder structure... that means they start malfunctioning "looking" for their installation paths and
withdrawing from functioning and authorization... reinstalling them sometimes adds to the mess, since some older installation locations might be involved... (i got several hard disks! because I try to keep the access to .wav - files quick)...
well this is my impression: The update from Live 10 to Live 11 totally confused my more complex VST plugins and no update of Live 11 will ever be able to resolve what has happened through that.
Yes. Firstly, check this out - I wrote it after all of the tech issues I experienced on Ableton 10 and 11: https://medium.com/the-electronic-music ... 4aa6238b07oratowsky wrote: ↑Mon May 10, 2021 10:25 pmthis is a mess.
I spend about half my workday every day cajoling it into loading projects by restarting and remaking live sets by dragging tracks one by one because it crashes all the time on every plugin I own.
Support tells me they can't do anything bc 3rd party plugins are causing the crashes.
What am I supposed to do ?
Anyone have any tips ?
Do you know why they install both and not just one?Mark Williams wrote: ↑Wed May 12, 2021 12:12 pmAbleton already separates vst2 and vst3 in the plugin browser and are scanned separately too. I haven't come across any problem plugins yet.
Ditto amigo. I wrote this about the nightmare: https://medium.com/the-electronic-music ... 4aa6238b07BloodPremonitions wrote: ↑Fri May 14, 2021 1:57 amI have to say that I have had a fairly horrific time changing over to 11. I pre-ordered and have been wrestling with it since the release, I had issues with the plugin scans/library and still am today. Particularly with AU plugins, which it no longer seems to read at all when I boot a session it disables the plugins, and they are not able to be re-activated. Even if I open that same plugin again and it works. Sessions crashing and also a new problem with the interface that I have not seen anyone here writing about... I've encountered an issue where plugin interfaces, clip view, midi view, etc randomly close.
CPU usage is fine for me, I would even say improved (when I have actually been able to mix), but the interface issue has rendered this program completely unusable for me.
I found switching from a laptop to a PC tower has helped. I chronicled it all here: https://medium.com/the-electronic-music ... 4aa6238b07bkg2018 wrote: ↑Sat May 15, 2021 4:11 pmHi all,
I have made exhaustive testing and the conclusion is that Live 11 definetely has a performance issue compared to Live 10, not on macOS but on Windows 10.
I won't make a duplicate so you'll find details are in my posts on the other topic here viewtopic.php?f=1&t=242943 .
I'm a great fan of Ableton Live since 2006 (version 6 !), and being a computer programmer since about 40 years I tend to study performances in a rather objective and scientific way. The tests I made show a significant difference in performance. But they also show that even a high-end MacBook Pro from 2017 is not at ease with Ableton Live, being 10 or 11. MacOS recent releases eat more and more CPU which is not available for applications anymore.
However I experienced no crash at all, so my guess is that peoples experiencing crashes have issues with third party drivers on Windows 10 rather than with Ableton Live itself.
In case of crash, you should go to the reliability report of Windows (ask cortana or the search input for 'reliability') and check what has crashed, then go to support of the related hardware company.
Just my 2 cents!
The challenge with that is that when you open projects that use 3rd party plugins (it could be very high depending on project), you have disabled plugins that don't re-enable when they work. So you have to manually delete & drag in that plugin. Or is there a shortcut?
No, I'm saying that I disabled and then RE-enabled them, forcing Live to re-scan.luckykat wrote: ↑Mon May 24, 2021 10:48 pmThe challenge with that is that when you open projects that use 3rd party plugins (it could be very high depending on project), you have disabled plugins that don't re-enable when they work. So you have to manually delete & drag in that plugin. Or is there a shortcut?