How to handle missing plugins that aren't missing

Discuss music production with Ableton Live.
Post Reply
mxcreep
Posts: 15
Joined: Thu Feb 08, 2018 9:00 pm

How to handle missing plugins that aren't missing

Post by mxcreep » Sun Mar 10, 2019 7:29 pm

Hi,

I got my hands on a nice tutorial for producing uplifting trance, containing some video's and a project file.
The tutorial is a bit older but still very interesting. After watching some video's I decided to load the project file and do some exercises.

The guy in the video uses mostly Serum, a plugin I have... However after loading the project file all Serum instances where disabled. Live couldn't find the plugin. Propably since my Serum is a 64 bit plugin and the original in the project file was 32 ? I'm guessing this by the way.

I opened the .als file from the project after unzipping it in an xml editor... Searched for Serum, found it.
Did the same with a new project file where I loaded Serum in a midi track, searched Serum, found it.

The naming and identification in the xml file is clearly different between both... So I'm not surprised Live can't find the VST...

Here comes the big question, besides the VST itself the project also contains the settings / preset of the VST... But when I swap out the original Serum and replace it with mine, the preset/settings are lost.

Does anyone now a trick to tell Ableton my Serum can replace the old Serum without loosing all settings ?

I could think of one solution myself but I'm not sure if it'll work... Editing the original project file and replace all Serum references... Shitty job to do but can be done for one project file. However, a nicer solution would be very welcome.

By the way, nice stuff those .als files... Theoretically you could program a complete song in xml, load it in Ableton and hear it for the first time... Pretty geeky right ;)

Post Reply