Hello,
I use Ableton 12. I am trying to open a track I had made a while back in Ableton 11. I used Analog Lab V on a lot of tracks, and I am finding that the VST tracks are not opening. Ableton will say “The VST plug-in could not be found.” I have Analog Lab V downloaded in VST2, VST3, and AU, and can open them just fine in Ableton, they just aren’t being recognized in my tracks. I know I could replace them but I would loose all of my preset and setting selections. Labs is recognized in the tracks where I used the AU instance, just not the VST2 and VST3. Anyone know why this is happening? And if there’s any way I can restore my old settings?
Thanks!
Hi @jholdn and welcome to The Sound Explorers Forum!
It could be a few things causing this, i take it you’ve scanned and made sure Ableton knows where your plugin directories are?
Have you updated to newer versions of ALV etc since you last worked on the project?
From your post, i’m thinking it’s most likely the latter of the two as there have been some pretty significant changes to ALV over the past few years.
If this is the case you could log in to your account to contact The Arturia support team to see if they MIGHT be able to help.
As an aside, it’s often a good idea to either ‘freeze’ or render a ‘temporary’ version of Virtual Instrument tracks as ‘a safety’ or backup to avoid this type of situation, particularly if you know you’re going to be away from it for a while; it’s something i’ve been doing personally for a few years now for this exact reason, this goes for ALL plugin manufacturers.
HTH!
Ps,
Please make sure to subscribe to The Arturia Newsletter to be the first to know about the latest from Arturia.
Dear jholdn,
I believe I am facing the exact same issue. Could you resolve the this?
I would be super grateful if you could quickly point me in the right direction.
Kind regards
Edit: I fixed it by updating Analog Lab V (which is now called Analog Lab Pro) via the arturia software center, then switching all plugin folders off and on in abletons preferences, doing a deep re-scan (rescan while holding down alt/option) and now re-loading the project / restarting ableton.
I hope this might help someone who is facing a similar issue.
2 Likes
Hi @Voidloop and welcome to The Sound Explorers Forum!
That’s great that you’ve figured out your own predicament, and MANY thanks for posting the update, as you said, it might be useful for others in future. 