• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Two Audio Units with the same View class. Only one shows in DAW.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Two Audio Units with the same View class. Only one shows in DAW.


  • Subject: Re: Two Audio Units with the same View class. Only one shows in DAW.
  • From: Admiral Quality <email@hidden>
  • Date: Tue, 28 Nov 2017 18:22:49 -0500

Have Apple ever explained why there's no namespace feature to avoid
this nonsense?

And yes, any UUID should do. A suitably long hash of the current time
is probably a fairly safe bet.

- Mike/AQ

On Tue, Nov 28, 2017 at 6:18 PM, Brian Willoughby
<email@hidden> wrote:
> Hi Jeff,
>
> If your script can run on the user's target system, then it could scan all
> existing plugins for conflicting names. That way, even a poor quality random
> number generator would work just fine.
>
> I get the impression, though, that your script runs in the build environment,
> so there's probably no way to know what other plugins might be installed when
> the plugin is actually used. If your replacement name is long enough to allow
> for a good UUID, then it should still work, but as you say it needs to be
> guaranteed unique across all possible build systems.
>
> Brian
>
>
> On Nov 28, 2017, at 2:03 PM, Jeff McClintock <email@hidden> wrote:
>> What I've resorted to at the movement is a script to modify the wrapper
>> binary by search/replacing the Objective-C class name with a randomly
>> generated name. For this to work, the replacement name must be exactly the
>> same number of characters as the original name. Also the random number
>> generator needs to be high quality to ensure two plugins don't end up with
>> the same class name. *Seems* to work fine so far, even if it seems like a
>> nasty kludge.
>>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Two Audio Units with the same View class. Only one shows in DAW.
      • From: Brian Willoughby <email@hidden>
References: 
 >Two Audio Units with the same View class. Only one shows in DAW. (From: "Jeff McClintock" <email@hidden>)
 >Re: Two Audio Units with the same View class. Only one shows in DAW. (From: Brian Willoughby <email@hidden>)
 >RE: Two Audio Units with the same View class. Only one shows in DAW. (From: "Jeff McClintock" <email@hidden>)
 >Re: Two Audio Units with the same View class. Only one shows in DAW. (From: Brian Willoughby <email@hidden>)

  • Prev by Date: Re: Two Audio Units with the same View class. Only one shows in DAW.
  • Next by Date: Re: Two Audio Units with the same View class. Only one shows in DAW.
  • Previous by thread: Re: Two Audio Units with the same View class. Only one shows in DAW.
  • Next by thread: Re: Two Audio Units with the same View class. Only one shows in DAW.
  • Index(es):
    • Date
    • Thread