Hello,

All three codes, Manufacturer, Type and SubType, have the same specific rules 
about the characters. All upper-case (or maybe all lower-case) are reserved by 
Apple, but anyone can request and register codes that are mixed case. Apple has 
never allowed non-printable control characters so you will have to work within 
that restriction. As someone on the internet described it, you have (126-32) 
choices for each byte of the four-char code. So, you can't use 0x7f "delete" or 
any control character.

I assume that you're already using one of the defined Type codes.

Your SubType can be "anything" within the generic restrictions from Apple.

p.s. I may be forgetting some details, but my understanding is that you need to 
register with Apple for a (free) Creator Code (which is a Manufacturer Code in 
AudioUnits). Not sure whether you've done that yet.


On Mar 3, 2021, at 05:41, audio boy wrote:
> So I have successfully migrated from the res based entry point to the
> plist/factory method.
> 
> However, I have hit a glitch in that the subtype in our plugins were
> all numeric values (matching the VST ID).  Apparently this is not the
> correct way, but it was working (as the subtype codes are all just 4
> byte CC's.  With the plist method, it seems you can only use a 4
> character string.  This now means Logic won't recognise the plugin.
> 
> Worst case this could be 'solved' by renaming the bundle / bundle id
> etc, but does anyone happen to know of a way around this?

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]
  • SubType in plist audio boy via Coreaudio-api
    • Re: SubType in plist Brian Willoughby via Coreaudio-api

Reply via email to