About AU Company and Plugin Codes | AU Stuff | Forum


Please consider registering

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —

— Match —

— Forum Options —

Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
About AU Company and Plugin Codes
February 2, 2015 - 6:05 pm
Member Since: February 2, 2015
Forum Posts: 8
sp_UserOfflineSmall Offline


I'm new to developing AU Plugins and have a question about the plugin and company codes. I understand that these codes are used like a serial number for the plugins? I recall reading or seeing somewhere that no two plugins on a system can have the same codes or it will fail validation? Is this correct?

Can these codes be reused if I don't need the old plugin anymore? For example, I export a compressor plugin while learning with a code COMP. If I make another compressor in the future, and I don't plan to keep the old compressor, can I reuse the COMP code for this new plugin? How does this affect Logic's validation?

As for the company code, I read about having to register/request this code from Apple? Is this for commercial development and preventing conflicts with other developers? I can't find anything else about this.

I'm trying to find out about this before I mess up the use of codes.

February 6, 2015 - 2:48 am
Member Since: January 29, 2017
Forum Posts: 693
sp_UserOfflineSmall Offline

Hi hectorlee

I took some time to consult with a former grad student who is now in the audio division at Apple. He stated that he did not know of a master list of company codes and that the information about registering codes is very old. So, there should not be an issue with that.

However, for the product codes, yes you should create new 4-character codes for each new plugin even if you are going to delete the old one. The reason is that Logic remembers all 4-character codes for anything you've opened in it. And, if your plugin crashes Logic, it will remember this code and never open a plugin with that code, even if the plugin is new and updated (this is one of the reasons you should validate all AU plugins before using in Logic). However, if your COMP compressor works without crashing, you can reuse that code for a later compressor. My own rule is to just make a different code for each version - CMP1, CMP2, etc...

- Will

February 18, 2015 - 5:48 am
Member Since: February 2, 2015
Forum Posts: 8
sp_UserOfflineSmall Offline

Thanks Will! I was having trouble confirming those information online as well. Seems that the links for registering developer codes are already offline.

Interesting point about codes and crashing logic. I only read about Logic caching the plugins using the codes and version numbers. So if you reuse a code but have a lower version number than the cache then the new plugin will not be reloaded. Now I understand the reason for validating it outside of Logic. I have been launching Logic and letting it validate itself. Thanks for the helpful information.

Forum Timezone: America/New_York

Most Users Ever Online: 152

Currently Online:
3 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Chaes: 56

Skyler: 48

StevieD: 46

Derek: 46

Frodson: 45

Peter: 43

TheSmile: 43

Nickolai: 43

clau_ste: 39

jeanlecode: 37

Member Stats:

Guest Posters: 2

Members: 784

Moderators: 1

Admins: 6

Forum Stats:

Groups: 13

Forums: 42

Topics: 850

Posts: 3372

Moderators: W Pirkle: 693