More info on this.

It looks like AUValidation do not delete the last plugin instance before
exiting.
Time for Apple dev to use std::scoped_ptr to avoid that kind of issues :)

As I have some static data dtor which rely upon all plugins instance being
deleted, there was some issue.


2015-10-02 12:46 GMT+02:00 Blue Cat Audio Dev <[email protected]>:

> Hi,
>
> I don't think it has anything to do with sandboxing. However it may be
> related to the place where you load the files. Our plug-ins do load data
> from the disk and have no trouble with the validation. I know the new Mac
> OS is more protective about the file system, so maybe you are accessing a
> location that is now forbidden?
>
> I guess your only chance is to attach a debugger and see what happens, as
> it could be anything - when auval changes, it may have an impact on almost
> any part of your code...
>
> Regards,
>
> Guillaume Jeulin
> Blue Cat Audio
> www.bluecataudio.com
>
> Quoting Olivier Tristan <[email protected]>:
>
> I think I have been in the wrong direction all the time.
>>
>> The issue is not this warning, but I suppose some kind of sandboxing now
>> in
>> use in the validation process of Logic X under El Capitan
>>
>> I suppose you are running some kind of inter app Mutex which is not
>> available under sandbox AFAIK.
>>
>> In my case, I open some files on the user HD when the plugin opens.
>>
>> Given this, if this is really the issue, I am definitely in a bad
>> position...
>>
>> and I wonder how any sampler would work...
>>
>> 2015-10-01 9:05 GMT+02:00 Kevin MOLCARD <[email protected]>:
>>
>> FYI, we implement this for several years but still needed to implement the
>>> old Rez stuff to be successfully validated (at least for 10.7).
>>>
>>> On 10.11, we do not get the warning message you pasted but our instrument
>>> are not validated.
>>>
>>> Indeed auval is crashing when validating any of our Audio Unit with the
>>> following message:
>>> libc++abi.dylib: terminating with uncaught exception of type
>>> std::__1::system_error: mutex lock failed: Invalid argument
>>>
>>> This is shown right after :
>>> AU VALIDATION SUCCEEDED.
>>>
>>> Maybe because of this Rez stuff. I'll give it a try and let you know.
>>>
>>> In the meantime, I encourage anybody to fill a bug at
>>> bugreport.apple.com
>>>
>>>
>>> On 9/30/15 7:06 PM, Olivier Tristan wrote:
>>>
>>> More exactly.
>>>
>>> I have never done this
>>> https://developer.apple.com/library/mac/technotes/tn2276/_index.html
>>> So this is maybe related
>>>
>>> Don't fix what ain't broken as they say.
>>>
>>>
>>>
>>>
>>>  _______________________________________________
>>> 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/o.tristan%40uvi.net
>>>
>>> This email sent to [email protected]
>>>
>>>
>>
>>
>> --
>> Olivier Tristan
>> Research & Development
>> www.uvi.net
>>
>
>
>
> _______________________________________________
> 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/o.tristan%40uvi.net
>
> This email sent to [email protected]
>



-- 
Olivier Tristan
Research & Development
www.uvi.net
 _______________________________________________
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]

Reply via email to