Sometimes when a plugin failed validation in Logic (atleast on v9) you can try to validate the plugin in plugin manager a few times and if that not work click reset & rescan selection also a few times and some plugins will be successfully validated..

But some will never be validated so it is better to remove them or click ignore plugin so it want scan it again when load up Logic

 

Last edited: Aug 25, 2015

Zynaptiq keygens work in the first place but then plugins revert to demo and want a new key after a few days. Seems like the machine key frequently changes...

 

Bias if you install hexwars release which dont work on many systems you cant get egg version to work

 

I could fix my AU validation problems where "validate all Au's" dont work (osx 10.11) via this solution: replace the auvaltool binary with the one from OSX Mountain Lion 10.8.3 update. "A fix for an issue that may cause Logic Pro to become unresponsive when using certain plug-ins"

 

Nugen plugs expire after a successful authorization with the latest R2R keygen. Tried AAX, VST and AU. OS X 10.9.5
thanks anyway for the amazing job you guys did.

 

DON'T INSTALL EL CAPITAN!!! I just recently upgraded to a MacBook Pro from an older black MacBook that couldn't be upgraded past Lion. Once I got my hard drive set up, all my apps re-authorized, etc., I immediately upgraded to El Capitan without backing up to Time Machine. "What's the worst that could happen?" I thought. "Maybe I'll lose an app or two?" Wrong. About two-thirds of my apps, audio plugs and VIs were suddenly rendered obsolete. Pro Tools 10.3.9, (older) Arturia, my Korg VIs, Sound Toys … the list was long. Some stuff I could upgrade, but the more recent k offerings are a bit slim. At first, as I was going through everything plug by plug and throwing everything in the trash, I thought "Well, I don't use this plug or that VI too much, I can live without it", but I hit a point where the whole idea of upgrading my computer so I could actually run the software I liked was being subverted. Fortunately, I had an older version of my hard drive that I'd never wiped sitting around when I'd upgraded to a larger one. I wound up having to erase my MBP drive via the Lion install disc, reinstalling Lion from scratch and migrating that older drive's info to the new one. Not really ideal, since I'd installed a lot of cool stuff that wasn't even on that older drive onto the current one, and I had to start over from scratch. I'm currently in the midst of re-installing and re-authorizing a shit-ton of software onto the current drive … then, I'll back up the drive to a Time Machine drive and perform incremental upgrades, starting with Mavericks. I'm at least hoping to make it to Yosemite with acceptable losses, but I'm not going anywhere near El Crapitan again. Aside from the forced-obsolesence thing, it's probably the lousiest OS Apple has produced since whatever the hell 10.1 and 10.2 were called. Sadly, I don't think they'll be reverting to a more acceptable OS, so I guess this is the future.

 

no offense iggy, but how could you NOT see this happening? only every dev and thread on this site and others has warned IN ALL CAPS about issues with el capitan..... oh well, live and learn, i'm sorry you have to go through all what you are going through, but this one is a problem that has been known since release of El Crapitan.... not trying to be snarky at all, and your words should be a warning to all... best of luck with the nightmare, and sorry for your time loss!

 

Sorry but in el capitan i have all plug working smooth exactly same way on yosemite without bug

 

FabFilter Pro Q 3 Working for about 30 mins before screeching with a piracy pop up. Have tried removing all library files following their guide but still not working. Are there any hidden license files to know about?

 

This thread is hilarious, it has some oldschool OG's and talks about staying away from the early version of El Cap, which later became one of the most stable OS's. nastalgia

 

yeah, it's a three + year old post...

 

Does anyone have any detail about the updated Arturia 7 Collection being made available for MAC yet?

 

Hi there! Newbie here, so please... don't shoot!

I've downloaded Addictive Drums 2.1.9 R2R and installed alright the standalone app, it works (after some manipulation...), but the audio component doesn't pass validation in Logic Pro X (tried several versions, included the last one 10.4.7). It is a "crashed validation", so that Logic immediately crashed when trying to validate it.
Strange thing is that, if I manually launch auvaltool to validate the plugin, it passes alright!

I've also tried to use the vst via the PluginFlipFlop plugin, with the same result: Logic crashes immediately!

Anyone experienced this?

My system:
MacOs High Sierra
Logic Pro X 10.4.x (but I've tried this also with 10.3.x and 10.0.x)

Thanks a lot!

 

Have you tried Batchmod and worked with the permissions as described in the AD and Addictive Keys thread I believe?

 

Hi sisyphus, I must say that before writing here I've searched in this forum for help and even found some thread dealing with AD2 but no solution. Now I've found that in this very thread there is a possible solution for AD2, in particular for plugins, that is my problem. I've tried to apply that by performing a "sudo codesign..." operation but I receive an error (xcrun: error: invalid active developer path) and can't proceed. Could you help me point in the right direction to find the discussion you were talking about? I didn't find specific AD thread dealing with problems other than PC ones.
As for batchmod, I've installed and found that it does what I've already tried to do myself, that's to say move from com.apple.quarantine the component plugin, but the result was the same.

Any further help would be much appreciated
Thanks a lot!

 

McGralich: I am not on the same OS X as you are, so don't have to deal with quarantining and whatnot as I have "Gatekeeper" off, which IIRC is something you should look into doing, as it sounds like perhaps it is not being installed correctly or all of if it (which is why perhaps it is not seeing the developer path, as well, there isn't one as gatekeeper (system preferences) is on, therefore not allowing certain folder structures or modification to folders in your user library etc...) ...

 

Kontakt 6.4.0 is now giving me grief on Mojave with the 10 days left beta warning?

 

Also I updated serum to 1.3b6 and now it won't take any of the serials -- I even tried deleting the component and vst files and reinstalling an earlier version but same problem.
How would I go about ununstalling Serum properly so I can re-install successfully?

Thanks!

 

No thoughts on these 2???

 

Blocking Zynaptique with a Firewall solves the Problem.
Karl