Zebra crashes in Logic X

[stardustmedia]

I still don't see it an issue. Are you that pressed you can't afford an extra 15secs??

The validation happens before th audio engine is loaded. There could be a good chance they would have to shut down and reboot the engine every time they did a scan. I would think that to be more intrusive.

15 seconds? Did you read what I wrote? How many plug-ins do you have? For me, an entire scan takes almost an hour and that if there are no crashes (which, in the majority of times, are just caused by the validator itself, not the plug-ins). And I have to be standing there, stupidly looking, because, if the routine stops for some reason, it will not return until I click somewhere to make it go.

I have almost 300 plugins and Logic 10.2.2 starts in 15-20 seconds.

When I do a clean fresh install of OS then Logic then all plugins. The very first scan of not yet validated plugins takes more time, yes, but that happens only once. Since I don't install 300 plugins at once and scan them in one go, I cannot say how long it'd would take.

However after the first validation, it doesn't validate anymore. Only the updated plugins and that takes usually not more than 2-5 seconds per updated plugin. All other 300 (not updated plugins) are NOT validated again.

So how come you're talking about hours? Does that happen often? Should IMHO only happen once, in the beginning.

[fmr]

However after the first validation, it doesn't validate anymore. Only the updated plugins and that takes usually not more than 2-5 seconds per updated plugin. All other 300 (not updated plugins) are NOT validated again.

So how come you're talking about hours? Does that happen often? Should IMHO only happen once, in the beginning.

No, it shouldn't happen once. It shouldn't happen... period. OR, it should happen ONLY when I need/want.

And it depends what you consider the "beginning". Beginning of what? If you install a new OS (which, in Mac OS, happens more often than it should), you have a new beginning. When you install a new version of something, again, you have a new beginning. When you install a new host, you have a new beginning. Many new beginnings, each with its FULL scan. It's not "just" when you install a new plug-in.

It's not "just" Logic, it's everything - it's the system. Each manufacturer seems to think that the user will only use just one version of one host in one OS forever.

[stardustmedia]

No, it shouldn't happen once. It shouldn't happen... period. OR, it should happen ONLY when I need/want.

I see, yeah maybe there should not be any validation. I cannot talk about that, I'm no expert. From a user's point of view, I don't really care. Because it's really really fast on my system.

And it depends what you consider the "beginning". Beginning of what? If you install a new OS (which, in Mac OS, happens more often than it should), you have a new beginning. When you install a new version of something, again, you have a new beginning. When you install a new host, you have a new beginning.

Beginning = Format drive, install OS, install DAW (in my case Logic), then install plugins. That's where Logic makes the validation for each plugin, once.
So if you install 300 plugins, THEN launch Logic, it will scan 300 plugins. If you install 5 plugins, launch Logic, it will scan 5 plugins, then install 10 other plugins, it will only scan those last 10 plugins, not the 5 from before.

After an OS update it doesn't do a new validation, or a full scan.

New host/DAW doesn't validate plugins, at least not a Logic update, from let's say 10.0.7 to 10.2.0.
I cannot say what happens when you update Logic from v8 to v10 though.

Many new beginnings, each with its FULL scan.

No, that's just not true, at least for Logic.
If a plugin was updated, Logic validates only this plugin, not all plugins. There is no full scan.

[#rob]

Just guessing here, but if you've upgraded to a new OSX version, then maybe that reset some of the folder permissions or ownerships so that the plugin can't access its resources. Things like GUI graphics and user settings are stored in files on your hard drive, and if the plugin can't access them (any longer) then it may validate in an automated test but crash when actually loading it.

You wrote "original installer", that sounds to me like you downloaded it once and kept that file around, and now you're using it again to re-install. In that case, my first recommendation would be to use the latest official installer from our website. Our newer installers all set the permissions for resource folders as the plugins need them, older installers (I think pre 2015) did not do that, so running an up-to-date installer could already solve the permission issue.
You can find the latest installer here.

If you are using an older installer and insist on keeping that version, then I would recommend to do the one thing that fixes so many issues on OSX already, and that is repair the disk permissions. Apple say that El Capitan keeps track of permissions automatically, that's why repairing them is no longer a function in Disk Utility, but it can't hurt to make sure that service is doing its job correctly.

Open Terminal and enter the following to verify permissions on your system drive:
sudo /usr/libexec/repair_packages --verify --standard-pkgs /

Should there be any suspicious entries, then please enter the following to repair those "incorrect" permissions:
sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

If you need to verify/fix permissions on another drive, just enter the path to it instead of the / at the end of those lines.

Should none of this help, then please do as Urs already suggested and send an eMail to support at u-he dot com so we can investigate this more closely.

[fmr]

Beginning = Format drive, install OS, install DAW (in my case Logic), then install plugins. That's where Logic makes the validation for each plugin, once.
So if you install 300 plugins, THEN launch Logic, it will scan 300 plugins. If you install 5 plugins, launch Logic, it will scan 5 plugins, then install 10 other plugins, it will only scan those last 10 plugins, not the 5 from before.

After an OS update it doesn't do a new validation, or a full scan.

New host/DAW doesn't validate plugins, at least not a Logic update, from let's say 10.0.7 to 10.2.0.
I cannot say what happens when you update Logic from v8 to v10 though.

Many new beginnings, each with its FULL scan.

No, that's just not true, at least for Logic.
If a plugin was updated, Logic validates only this plugin, not all plugins. There is no full scan.

For what you wrote, you know little about it. You didn't even have the experience to install a new version (A NEW VERSION - not an update) of the host. And it also happens when you update the OS (changing version, from 10.9 to 10.10, for example, not 10.10.1 to 10.10.2 - even the numbers you wrote are wrong)). You seem to not have enough experience on the subject to talk about it.

[stardustmedia]

Beginning = Format drive, install OS, install DAW (in my case Logic), then install plugins. That's where Logic makes the validation for each plugin, once.
So if you install 300 plugins, THEN launch Logic, it will scan 300 plugins. If you install 5 plugins, launch Logic, it will scan 5 plugins, then install 10 other plugins, it will only scan those last 10 plugins, not the 5 from before.

After an OS update it doesn't do a new validation, or a full scan.

New host/DAW doesn't validate plugins, at least not a Logic update, from let's say 10.0.7 to 10.2.0.
I cannot say what happens when you update Logic from v8 to v10 though.

Many new beginnings, each with its FULL scan.

No, that's just not true, at least for Logic.
If a plugin was updated, Logic validates only this plugin, not all plugins. There is no full scan.

For what you wrote, you know little about it. You didn't even have the experience to install a new version (A NEW VERSION - not an update) of the host. And it also happens when you update the OS (changing version, from 10.9 to 10.10, for example, not 10.10.1 to 10.10.2 - even the numbers you wrote are wrong)). You seem to not have enough experience on the subject to talk about it.

Keep your tone calm please, even if you think I know little. So now, please tell me exactly which numbers are wrong? And please tell me why you think I don't have enough experience?

Because I know exactly how my Logic reacts, because I see it every day launching. And every week or two I update a plugin. Just recently I updated my MacOS 10.9.5 to 10.11.3 (update, not fresh installation on a formatted drive). And Logic did not validate again all plugins.

And on another computer I really made the experience to install a new version (not an update, so I formatted the drive, booted from USB-drive, and started the OS installation).

That's all I know. Now tell me what's wrong with my experiences, please in details. Superficial offences doesn't help me to understand, what is wrong with my experiences and my knowledge.