> On 01.10.2015, at 18:27, Olivier Tristan <[email protected]> wrote: > > 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... >
I managed to get my stuff to work. First of all apologies to Logic. It indeed does not treat this warning as error, so I was mistaken. I got the idea from your post on the JUCE forum. Turns out Logic still loads plugins that produce warning #140. I also have been able to get rid of the warning for my plugins. What I needed to do was rebuild the XCode project from scratch.. or maybe my clean builds just weren’t as clean as they should be. In any case I created new project files that compile with XCode 6, use SDK 10.10 and deployment target 10.6. The built plugins no longer produce the warning and validate and work fine in Logic. So things are good for me. My plugins do access the file system during validation, but that does not seem to be a problem. I have to load some setting files and an initial preset that can be largish (can include samples), but that does not lead to problems. Unfortunately that means the problem has to be somewhere else for you. _______________________________________________ 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]
