• 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: About AUValidation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: About AUValidation

  • Subject: Re: About AUValidation
  • From: Olivier Tristan <email@hidden>
  • Date: Thu, 01 Oct 2015 18:02:28 +0200
I was able to remove the warning by moving to the factory version
https://developer.apple.com/library/mac/technotes/tn2276/_index.html

Please note that you need to fill correctly the plist.

You can put a breakpoint in the Entry and Factory functions and see which one is called by the AUValidation tool in your case.

As soon as I export the factory function, fill correctly the plist, the new factory function is called.


Still I wasn't able to check under Logic X with El Capitan.
Following Blue Cat post, the issue might not be related to this warning though.

Are we sure that Logic X treats warnings as error in its validation process ?

2015-10-01 17:49 GMT+02:00 Adrian Pflugshaupt <email@hidden>:

>> For me changing the base SDK and using XCode 7 is not enough unfortunately.
>>
>> I build Juce based plugins and they get the same warning.
>>
>> However I think there’s a shimmer of hope coming from Juce. If I build the Juce Demo Plugin with XCode 7 it does successfully validate and still contains the rez stuff and CA_USE_AUDIO_PLUGIN_ONLY is not set and all the normal CoreAudio files are built.
>>
> Looks like Juce does an equivalent of CA_USE_AUDIO_PLUGIN_ONLY.
>
> Check JUCE_DISABLE_AU_FACTORY_ENTRY at the bottom of juce_AU_Wrapper.mm
>

I see that, but what I am also seeing is that without changing the code builds I do with XCode 7 sometimes produce the warning #140 and sometimes they don’t. I managed to get builds to work and break by changing seemingly random configuration choices. As I am absolutely sure I am not using the Component Manager, I think this is just a weird warning coming from some even weirder compatibility issue in the system. Currently I hope it is related to the c++ lib and SDKs used. After reading all the new posts, I’ll try using older SDKs now. I used 10.10 and 10.11 so far and am getting these weird very mixed results. Btw. how do you get 10.8. installed in XCode 6?

In any case it does not really seem to be related to how the AU is configured, but changing the configuration still seems to trigger the error.

So if you’re luckly your exisiting AUs just keep working and if not… well then you’re in my situation.

The whole situation would easily be solved if Logic stopped treating this warning as an error which is is not. After all my plugins work just fine on El Capitan, they don’t fail validation but sometimes produce a weird warning.
 _______________________________________________
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



--
Olivier Tristan
Research & Development
www.uvi.net
 _______________________________________________
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
References: 
 >Re: About AUValidation (From: Blue Cat Audio Dev <email@hidden>)
 >Re: About AUValidation (From: Olivier Tristan <email@hidden>)
 >Re: About AUValidation (From: Adrian Pflugshaupt <email@hidden>)
 >Re: About AUValidation (From: Olivier Tristan <email@hidden>)
 >Re: About AUValidation (From: Adrian Pflugshaupt <email@hidden>)

  • Prev by Date: Re: About AUValidation
  • Next by Date: Re: About AUValidation
  • Previous by thread: Re: About AUValidation
  • Next by thread: Re: About AUValidation
  • Index(es):
    • Date
    • Thread