Question

I'm shocked and surprised that this hasn't been reported.

For me this is a major workflow killer of the FP8 and 16

This problem occurs in Studio One so i'm not sure its the same in other DAWs

Add a Vst2 instance of a  third party plugin, hit Edit Plugins and map the faders and buttons to the Faderport, now if you have the VST3 version of the same third party plugin add it. What i would expect to see happen is that the mapping would automatically be mapped to the VST3 version of the plugin.

Its not, and here is the major workflow killer, you have to remap the faders and sends to the VST3 version.

This is duplicating work and is a time waster.

Can Presonus look to implement a mapping system that maps the faders and buttons to both formats of third party plugins when its the same plugin.

As a test i tried it the other way round. I started with a third party VST3 plug, mapped it, then pulled in teh VST2 version. Same problem, both had to be mapped individually.

Answer 1

Its the same problem with all Waves plugins, you have to remap all the mono instances separately from stereo ones!!!

Answer 2

Hi Stew,

The reason you have to re-map for vst2 and vst3 separately is that they are two different plugins.  Vst2 and vst3 use different dll's for each one.  They even get stored in different place, iirc.  (They are on my system anyway.)

The real question is why are you using both plugs?  There's no need to.  For example, blacklist the VST 2 and keep the vst3 active in your plugins list.  Or vice versa.  Just don't use both vst3 and vst2 versions of the same plugin.

However, in my experience, you can't map all plugins to the faderport anyway.  E.g. Izotope plugs don't allow mapping.  (Ozone for example)

The Maag E.Q (included in the Studio Magic bundle) will allow mapping.  I have only ever set  that vst once and now it's set for everytime I drop the plug onto a track.  I do find it hit or miss with third party plugs, but I tend to use only native S1 plugs for my jobs.