Hi, when I load the old project sometimes they says its missing plugins. I open the track and theys greyed out with the no way to auto-replace with the updated vst3 version. then I try to drag and drop updated vers vst3 over the vst2 it wont do its just adds it next to the missing plugin

 

good question. I recently had the same issue and never did find a "swap" solution

 

Not a swap as i know off . One of my big annoyance with ableton is vst , in general is crap compaired to cubase , scan takes for ever ,starts default on start up so you have to stop scan , used to be able to stop that but they removed that in a update and say if you got a hundreds / takes forver .

 

No and it sucks! There should be a vst2 -> vst3 tool in Ableton im not sure how other DAWs do this and some vst3s might not be exactly the same like their vst2 version but at least have a wizard that does try???? Should work without problem for 99% of the plugins anyway.

Loading time on my avarage PC with almost 400 plugins is excellent, takes a few seconds to open Ableton and scan is in background, but only if you install a new plugin anyways. What exactly is the problem with the scans?

 

It does sucks because I encounter these problem more now with so many updates I only can reinstall old vst2 version and try to copy over setting or save preset to rearrange to new folder so now need to keep 2 version for backup. Does the new Ableton 12 handle this different? I cant try the demo right now

 

For this reason I still keep a few of my essential plugins in vst2 installed as well, the synth I use almost exclusively and my favorite effects.

That way I have to dial in all eq and most stuff again but at least the basic synth and delay stays the same. Not ideal but what to do...

 

There is a way, but honestly it’s such a pain that I don’t think it’s worth it -- I'll share it here anyway.

.als files are basically gzipped XML. Inside that XML there are elements called <VstPluginInfo>, where Ableton stores all the info about a particular plugin in that project.

For example: let’s say I have an old project that’s missing the VST2 version of The Legend. I load the VST3 version into the project, then I open the .als file with 7-Zip, extract the XML, edit it in a text editor, and replace the relevant parts. After that, I drag the edited XML back into the 7-Zip window to overwrite the original.

Example:

VST2 (missing):
<VstPluginInfo>
<Path Value="C:/Program Files/Steinberg/VSTPlugins/Legend.dll" />
<PlugName Value="Legend" />
<UniqueId Value="1163154006" />
<Buffer> [BINARY PARAMETER DATA] </Buffer>
</VstPluginInfo>

VST3 (present):
<Vst3PluginInfo>
<Path Value="C:/Program Files/Common Files/VST3/The Legend.vst3" />
<Name Value="The Legend" />
<Uid> [4 FIELDS] </Uid>
<ProcessorState> [BINARY PARAMETER DATA] </ProcessorState>
</Vst3PluginInfo>

In this particular case, it’s easier because both versions of the plugin share the same UniqueId.

The key here is that the binary parameter data is actually compatible between the VST2 and VST3 versions of this plugin. So I just copied the <Buffer> data into the <ProcessorState> field.

So basically what I changed was:
- Plugin type: VstPluginInfo > Vst3PluginInfo
- Path: .dll > .vst3
- Preset type: VstPreset > Vst3Preset
- Added VST3-specific fields (Uid, DeviceType)
- Updated browser path and device ID

As I said, it's a pain, and kinda messy, but it works... "sometimes" lol

 

Last edited: Sep 28, 2025 at 11:22 PM

What about BlueCat´s Patchwork?

 

It can't retrieve a DAW projects' plugin saved state, if you had the plugin inserted directly in your project. Only if you started out with it loaded via Patchwork.