Logic Pro & Studio One detect the "Enable Midi Input FX" enabled plugin as a different plugin

[A Former User]

I compiled an fx plugin with Enable Midi Input FX is disabled. I used it in some Logic Pro projects.

Then I compiled another plugin version with Enable Midi Input FX is enabled.

The Logic Pro / Studio One don't recognize the new compiled plugin on the DAW project. and it gives "Plugin is not found" error. The new compiled plugin's Name/Plugin Code/ Bundle Identifier...etc everything is the same.

The New compiled Plugin is shown as "MIDI-Controlled Effect".

Is this normal? What can we do about it if the users previously made some projects?

[A Former User]

@Steve-Mohican Any ideas?

[d.healey]

If you use AuVal you can see all of the plugins on your system and the various codes/names etc that the system is using for them. Might point you in the right direction.

[orange]

@Steve-Mohican

Have you checked the Plug-in Manager in Logic?

If you've enabled the Enable Midi Input FX, the plugin type will change from "effect" to "MIDI-controlled effect". I think this is the reason that you've lost the backward compatibility with this type change. Even if the plugin name is the same, since the type is different, Logic will scan the plugin as a different unit, so the previous version (effect) couldn't be found now. I am not sure if it is a bug though.

AFAIK, it happens in AU plugins only, but I might be wrong with this.

[A Former User]

@d-healey said in Logic Pro & Studio One detect the "Enable Midi Input FX" enabled plugin as a different plugin:

If you use AuVal you can see all of the plugins on your system and the various codes/names etc that the system is using for them. Might point you in the right direction.

Yes I use it, the plugin passes the validation and it works in the DAW. But the plugin can't be found in the previous DAW projects.

[d.healey]

@Steve-Mohican I wasn't suggesting you use it to validate the plugin. Auval can also be used to list every AU plugin on your system along with their codes, it might show that the wrong code has been associated with the plugin.

[A Former User]

@orange said in Logic Pro & Studio One detect the "Enable Midi Input FX" enabled plugin as a different plugin:

@Steve-Mohican

Have you checked the Plug-in Manager in Logic?

If you've enabled the Enable Midi Input FX, the plugin type will change from "effect" to "MIDI-controlled effect". I think this is the reason that you've lost the backward compatibility with this type change. Even if the plugin name is the same, since the type is different, Logic will scan the plugin as a different unit, so the previous version (effect) couldn't be found now. I am not sure if it is a bug though.

AFAIK, it happens in AU plugins only, but I might be wrong with this.

Yes! This is the cause, Thank you so much Great Find! I compiled the plugin again with Enable Midi Input FX is set no, the plugin is opened in the DAW project again. Yuppies!

[A Former User]

@d-healey There is no wrong code. Everything is the same but with only "Enable Midi Input FX" difference.