des99

If you hover the mouse over your plugins, you'll see how much latency each plugin is telling Logic it needs. Remember what latencies can be compensated for, and what latencies will delay the audio signal to line everything up.

Ok, let us know what happens when you try in a new user account...

Hmm, it seems to be behaving like you have something sending keypress cursor down events to Logic. Try running Logic in a new, temporary user account on your Mac - do you still get the same behaviour? Do you have any software utilities running that might be sending system or key events around the system? Also, please try the suggestion I made above and let me know the result...

It's worth checking you don't have multiple commands assigned to the same keypress, so you're not actually triggering the command you *think* you're triggering, in case that's the issue.

Exactly. Pluginfo is a great tool yes, and recommended. Note that just because a plugin doesn't have an ARM binary doesn't mean it's automatically giving problems. I still have a few Intel-only plugins, and they all work just fine in the current version of Logic - in fact, Logic is architected specifically to allow you to mix both ARM-native, and Intel-only plugins on an ARM Mac running Logic natively. The solution is to identify the plugin causing the problem, and uninstall/reinstall/fix it, and this is true whether the plugin is ARM native or not. *Any* plugin can misbehave, have bugs or get into a crashing state, and this is unrelated to whether the plugin is ARM-native or Intel-only - although of course, the older and more unsupported the plugin is, the higher the likelihood it might not be behaving well on modern systems.

That's faster than my 2011 MBP, with similar specs, and I got plenty done on that in ten years... What do Logic's performance meters tell you is the load problem? That doesn't sound right... What audio interface hardware are you using? Does the same thing happen if you just use the Mac's inbuilt audio?

This article summarises the bulk of places Logic stores content:

Plugins aren't stored in the shared folder. There are precisely two places that macOS lets AudioUnit plugins be run from and that's: /Library/Audio/Plug-Ins/Components (the root level Library), and ~/Library/Audio/Plug-Ins/Components (the Library folder in your user home directory) Some plugins place additional data into the Shared folders, that's an implementation decision by those plugins, and you usually can't change that behaviour, unless there is an option inside the plugin to do that. I suggest you don't randomly start moving bits of plugin installations to where *you* want them, away from where the plugin wants them, otherwise you will likely break things.

Delete the content you don't want (apple loops, sampled instruments etc), and your Logic preferences, and Logic will prompt you to download the "Essential content" it needs to run the next time you run it. Your templates and projects are stored elsewhere on disk, and aren't related to Logic's content. It wouldn't delete the content you've already downloaded, no. No, the validation status of those plugins are stored in your cache, so it shouldn't be necessary to validate them again.

Tip: Posting the readable clear text crash log is a lot easier for us to parse than posting the json-encoded version... Logic is segfaulting, and if it's always doing this regardless of the loaded project, I'd start removing your third-party hardware/software bit by bit until the issue goes away, to try and home in on what's causing the problem.

Choose: Logic Pro -> Control Surfaces -> Bypass All Control Surfaces Let us know if the problem stops, or continues...

No it's not possible, as previewing those loops simply plays an embedded audio file rendered into the Apple Loop. It's only when you drag the loop in, that the required plugins and settings are recalled and loaded (which takes some time).

If you right-click on a category, there is an option to "Remove". If they still won't go, there is a way to manually remove them by editing the tag database, I'll try and dig out the post I originally made about it... Here you go:

The instruments don't need to be moved from the standard instrument locations that Sampler looks in, and are pretty small so it's pointless anyway. The samples those instruments use can go anywhere, although you can alias them from the known sample locations in your user Logic folder if you like, which might help Logic with locating them. Just test with one instrument and make sure after you've moved it's samples it still loads, then you can do the rest.

I don't know Amplitube, but some plugins that have hundreds or thousands of parameters, or where the internal state is not fixed (each patch could load different FX with different available parameters etc)), they don't expose all of them as automatable to the host (Logic) by default - so in those cases, yes, in the plugin you have to say "Make this parameter automatable" and then the host can automate and control that plugin parameter. Kontakt behaves the same way.