Live 11.1 on Windows 10 - VST issues?

[DJ Tequila]

I've installed Live 11.1, but it doesn't give me access to a large number of my VSTs.

Firstly, I'm getting an error on ValhallaRoom (an alert pops up after Ableton loads), and I can' use it. It's still working nicely on v11.

Secondly, I'm using shortcuts a lot in my VST folders. Installers can install to some random places, and some don't even give you the option to pick a VST folder. I ended up pulling them across to a workable VST folder via shortcuts, which also helped with categorisation.

Thirdly, I'm using an option in the options text file to prevent VSTs loading on launch. I only add VSTs rarely, and I'd rather scan the folder by hand when I make a change, rather than every time the DAW opens. I know the task has moved to the background, but this just means the system will be janky until it completes. It's better than not being able to use the program until the scan is complete, but still not ideal.

So I guess I have some questions.

- Is anyone else getting VST errors in 11.1? Especially ValhallaRoom?
- Is anyone else using shortcuts? Is 11.1 finding them for you?
- Is there no way to prevent a VST scan on launch any more?

Or does anyone at Ableton have any official answers and advice on these points?

[DJ Tequila]

I guess, depending on any answers I get, I have a couple of feature requests:

- Either re-enable shortcuts (if they've been disabled) or allow multiple custom VST folders.
- Re-enable the option to disable plugin scan on launch, unless there's some replacement.

[desertrogue5150]

I'm having cpu overload issues due to some of my vst's not working right. 4 track project with a few plugins on like soothe2...skyrocketing my cpu hardcore style. I usually run bigger projects and video edit on this windows pc. It happened when i updated to 11.1

[Dean Corrie]

On my desktop Windows 10 PC, I'm getting all my Softube VST3 plugins (Time and Tone Bundle and Dirty Tape) giving errors on scan and failing to appear. Rescanning I sometimes get some to appear then other times not. Never had them all successfully scan together. Tried a few times. Only Softube VST3 plugins seem affected.

On my Windows 10 laptop, I didn't have either my iLok or eLicenser connected, so Live 11.1 threw up all sorts of errors with VST2 and VST3 upon initial load. Check that out properly later.

Yet to update the Studio Mac.

[jsn]

Yes, I am having lots of issues as well. It was so disheartening that I just went back to 11 for now. Nothing on my template master is recognized. Not a good start. Let's hope this gets resolved quick-like so we can work with the cool new features (and good fixes)

oh, ignore my sig. not uptodate

[DJ Tequila]

Not just me then. Any of you using Windows shortcut files to organise your VSTs?

[wabbyboy]

I am having the same issues with shortcuts. On Windows 11 though

[josefreak]

I was just about to post the same question. Many of my shortcuts (collections) are gone, several of my vsts aren't loading, and my default template is broken. Can someone offer some insight as to what has changed?

[TheCoil]

It's inexplicable why they would take away 2 features that are intrinsically important to many of our workflow and setup, i.e. not letting us use the txt file that disables startup vst scan and taking away the ability to use shortcuts to additional vst folders. Was this really something they needed to kill? v11.0.12 was running great for me with these features enabled so I can't see why this would be a necessary development in a new version.

[jsn]

Not just me then. Any of you using Windows shortcut files to organise your VSTs?

Hi, I am not sure, but if that be the case, then it is the install process which caused that and I imagine(?) the developer had their reasons for doing this(??) but I know nothing about that side.. I manually choose the Same VST directory for every VST I have. My thinking is such that if everything was fine in 11.0 then this is on Ableton to provide a fix or information about how to proceed. I've been reading some discussion here today (not online often) about moving the actual vst file (as you suggest, i suppose there are some devs who use 'shortcuts') to the directory chosen in the preferences. The issue here, and the reason i chose to simply stay with 11, is that this seems a temporary solution and that any updates would involve jumping through these hoops again. I'll just wait for a proper fix or other information from this company or one/several of the devs. I don't find it my responsibilty to go through a support process when so many experience the same dilemma. This is why I started always installing major releases beside one another versus replacing the prev version. I have too much at stake. So,again, I hope a FIX will arrive. I am curious at which point in the beta process for 11 that this changed -or- if this was just something that reared its ugly head as the copany assembled the final release??? This is one incentive to joining the beta release group perhaps, so one can reap the benefit of the features and fixes should the 'final' release magically break things when it lands...as seems to happen more often lately. And I don't think ill of the company for the issues which are widespread IF there is some Effort in informing the affected groups of a fix or being prompt in releasing a patch. 11 works fine for me for most of my needs so I am in no rush. Let's hope for some understanding from Ableton's end, in some form regarding the issue (ignore the sig. logging off again)

[MichaelAbletonForum]

I reported this bug while the beta phase. It has been validated and logged as bug. But it is still not fixed, so that I could not go further with tests or using the new Live Version.

Its possible to copy every plugin to one folder, but if you have a large amount of plugins or more than one DAW or Host, that's not a possible way because you will destroy your setup.

My second try was to reduce the path toVST2s only 2 targets by replacing VST2 by VST3. But it was a mess because some main features in VST3 implementation are still missing. I wrote support ticket, the answer was use VST2 instead of VST3

I worte a lot of email, created support tickets, I've talked with steinberg developers, made feature suggestions wrote in user groups etc. At the end I gave up.

For me working with plugins is still a main feature of a DAW, I use some DAWs, Live, Cubase, Maschine, Reaper, WavLab... only in Ableton Live i have such problems using plugins. The base implementation within Live is still not the best (Midi Channel Routing always channel 1 etc) But with these additional issues, in my opinion Live becomes the DAW with the worst VST implementation .

[Mark Williams]

It's inexplicable why they would take away 2 features that are intrinsically important to many of our workflow and setup, i.e. not letting us use the txt file that disables startup vst scan and taking away the ability to use shortcuts to additional vst folders. Was this really something they needed to kill? v11.0.12 was running great for me with these features enabled so I can't see why this would be a necessary development in a new version.

The options.txt file was not officially supported nor an official feature.

[jsn]

I reported this bug while the beta phase. It has been validated and logged as bug. But it is still not fixed,...<snip>

Thanks for sharing that info about the beta, Michael. As you are a part of the beta group, do you see Any discussion of this being looked into?

[Tarekith]

It’s being looked into.

[travismc1]

I had this problem on my main workstation. I have Arturia V-synth collection (updated to whatever the current version is). Piano V2 is the name of the VST in my default live set... I also have Guitar Rig 5 on one of the tracks. Neither of these could be found by Ableton 11.1. When I went to preferences, the "scan" was still scanning.... seemed like a long time to keep scanning... watched for a minute or two. It never quit "scanning". I deleted the offenders from the template. Saved. Closed, then opened. Went to PREFERENCES - rescanned the VST 2 folder, it quit. I had to reset and rescan the VST 3 folder (it had been changed by install, I just caught that.) Then I put those two VSTs back into my "default" template... saved as default template ... No more problems last night... have not rechecked today yet.