Plugin code

[d.healey]

@yall In what way will it not work on Mac?

[yall]

@d-healey what I have seen is that even if it is 2 different plugins, it will either find both or just one. if it finds both, it will always open the same plugin as if they were the same. it did that to me under logic only. (logic is very capricious and requires that the plugins are checked). for a plugin that I call "stereo plugin hise instruments" for example, I put the code "Sphi".

[d.healey]

@yall Thanks for the info. I'm experiencing this issue with logic and that confirms my suspicion about the plugin code. I guess there is no way to check if the code I'm using is already used by someone-else's plugin? Like a register for plugin codes.

[Dan Korneff]

There used to be a database to register your code, but hasn't been maintained in years.
There's a VST plugin registration form from steinberg:
http://service.steinberg.de/databases/plugin.nsf/plugIn

From what I understand of AU, the plugin Type, Manufacturer, and plugin code need to be unique. That will limit the amount of possible collisions with other plugin codes.

[yall]

@d-healey I think, but to verify, that the code also corresponds to the name that you give to your projects. your plugin and vst in application support are in a single folder and both folder correspond to plugin. So even if another brand has the same code as you on a plugin, they will be 2 different folders in application support. maybe I'm wrong but a 4 letter code is quite limited anyway

[d.healey]

456976 possibilities.

[yall]

@d-healey It's true that it does a lot of plugin

[gorangrooves]

I think that the issue will likely occur only if another plugin manufacturer has the same manufacturer code and then uses the same plugin code as you. I ran into issues where I used the same plugin code on two plugins and one of them would not show up. So, as long as your plugins all have unique plugin codes, it is unlikely you will run into issues.

[hisefilo]

@d-healey I can remember to change the plugin code on Mac to avoid plugins to load stored data from older versions of it. So it make that plugin unique on your system I suppose. (don't know if 2 plugin form different devs can have same code. I guess yes)

[Frankbeat]

From my experience today, I'd dare to say it has serious relevance for at least some Mac systems (I'm working on High Sierra).

I experienced this weird behavior in Cubase: I had saved a project holding an instance of MyInstrument1. Later I also installed MyInstrument2 on that machine. Then I reopened that Cubase project and now it had an instance of MyInstrument2 when it shouldn't even know of the existence of it.

This bugged me for a day so I decided to have a closer look on the HISE project settings before export. It just felt right to replace Abdc by something related to me. I can't tell if really this was the culprit, but now I have both VSTs to choose in Cubase.

[andioak]

This should be pretty easy to test out. One developer ID with 2 separate plugin codes. A few testers on different DAWs and machines with different OS versions.

I can be a tester on anyone's plugins. Do not, however, have a project ready or a functioning HISE install, cause of a re-installation issue at the moment...

[Soundavid]

The Plugin Code are tied up with the Vendor Id, The code can be the same for two different developers but the most relevant code is the Component Manufacturer.

https://developer.apple.com/documentation/audiotoolbox/audiocomponentdescription/1410471-componentmanufacturer

Apple hasn't maintained this code registration for a long time so the recommendation is using something unique to your company and not using posible used codes like Wavs or Uadc or Demo...

The Bundle Identifier is important too, com.yourCompany.yourPlugin, when you sign two Plugins with the same Identifier could have some issues.

[clevername27]

@d-healey On the Mac side of things, just pick something you think will be unique, and don't worry about it.

[Lindon]

@clevername27 said in Plugin code:

@d-healey On the Mac side of things, just pick something you think will be unique, and don't worry about it.

The Mac side is where the problems are - specifically Logic - which is one of the few DAWS to be rigorous with this Plug-in/vendor code stuff..