What to do if plugins are duplicated in FL Studio's Plugin Date Base

What to do if plugins are duplicated in FL Studio's Plugin Date Base

In FL Studio, the plug-in with the same name will be given an underscore (_) + number by FL Studio.

It is a merit and a demerit.

I will explain why this happens and how to deal with it.

Causes of duplicate plugins

If the DLL name is 32bit, 64bit, VST2, VST3, FL Studio will consider it a duplicate and add an underscore (_) + number to the name.

FL Studio is one of the few DAWs that supports both 32bit and 64bit VST plug-ins.

If the developer has the same name for both 32bit and 64bit, installing both will duplicate the name.

If there are duplicates, FL Studio will add an underscore + number to the name of the duplicate plug-in.

The same thing happens when the plugins are duplicated even if they are in multiple folders.

Remedy XNUMX

There is an option to combine plug-ins with the same name in VST2 and VST3, and an option to combine 32bit and 64bit plug-ins, so enable them.

To do this, click "Manage plugins" from "OPTION" in the menu.

plugin managerWill start.

The target options are the red frame below.

I will also post a Japanese translation of the manual.

• Combine 32 and 64 bit versions of a plugin – Create one preset for plug-ins that have both 32-bit and 64-bit versions. FL is Wrapper's "Bit sizeUse the option to decide which version to open.
  • Combine presets for VST and VST3 versions of a plugin – Select this to merge presets for plug-ins with both VST2 and VST3 versions (partial). FL first tries to load the VST3 version.

Then scan again to eliminate the duplication.

VST2, VST3, 32bit and 64bit are all combined as shown below.
(VST3 is loaded)

Priority plugin

If VST2 and VST3 are called when they are combined, VST3 has priority.

If it is 32bit and 64bit, it can be set by each plug-in.

I think most people are using 64bit FL Studio, so 64bit is read as Native.

You can change it with "Bit size" from the gear icon of the plug-in.

You can check which one is currently loaded in the red frame on the left in the figure below.

Summary of measures to be taken when plugins are duplicated in FL Studio's Plugin Date Base

If you can integrate it, it will be quite neat, so it is recommended to do it even if it is troublesome.
(I'm also self-aware because I'm messed up in various ways)

I wanted to write in a little more detail, but the time has run out.

Since I can finally get a lot of time after GW, I will organize various things from that side.