Project Info - Version Number

[HISEnberg]

My assumption about the Project Version (so the version you assign in the project settings, typically formatted as 1.0.0) is that different "versions" of the same plugin (so same plugin code) should load just fine. So if I distribute an updated version of the plugin (1.0.1), the user should be able to replace their existing version of the plugin with it and it should open in any previous projects they were using the plugin with.

However, I'm getting some users saying it isn't being properly recognized specifically in Logic. It's being seen as a "new" plugin. I notice there is a warning in the project settings (but this is almost the opposite issue):

Be aware that some hosts (e.g. Logic) are very picky when they detect different plugin binaries with the same plugin version.

I'm wondering if I am missing something here or why the plugin isn't being detected properly, I always assumed it was the Plugin code that mattered not really the version number. What's the proper procedure here? Do you instruct your users to remove older versions of the plugin? Anyone else have this issue?

[d.healey]

@HISEnberg your installer should overwrite or remove the old version.

[HISEnberg]

@d-healey thanks that makes a lot of sense, I’ll try adding that to my installer scripts.

Is that how you release updates of your plugins?

Have you seen this issue before? I’m noticing in my ProTools sessions that the new version of my plugin is launching fine so it seems specific to Logic. I’m going through my GitHub repository and I’m not seeing any other changes in the project settings other than this and one other flag (force mono to stereo). Am I correct in thinking that all the DAW ought to care about in this case is the Plugin ID?

[Christoph Hart]

@HISEnberg if you change the name of your plugin binary this will also cause issues.

Have you tried refreshing the AU cache or killing the AU registrar process, then restart?

[d.healey]

@HISEnberg said in Project Info - Version Number:

Is that how you release updates of your plugins?

Yeah the installer just overwrites the old version. As Christoph mentions, everything else must be exactly the same (plugin name, code, company code, etc.) only the version number changes.

[HISEnberg]

@Christoph-Hart I gave this a shot but this wasn't the solution. It's my mistake.

@d-healey you are exactly right.

Basically for anyone who ends up here I recommend looking at and comparing the Info.plist that is part of the .component bundle. In my case I had changed the company code and this is why the plugin wasn't being recognized properly. Strange I couldn't find this in my Github commits but my issue had nothing to do with the version number.

Thanks both for your responses!