des99

Yes, thirty or forty years ago. In a DAW? No, it's not the same at all. You *should* work with some headroom, and there is no quality or signal-to-noise penalty for doing so, unlike back in the older days. You've turned your volume down. Did you turn up your monitors/headphones to compensate? Humans hear differently at quiet volumes compared to loud. The point is to work at levels in the DAW that make sense, and monitor at levels that make sense. If you need to turn down your mix, but this is too quiet to hear, you need to turn up your monitors to compensate for this volume loss, otherwise you will perceive the mix differently. Note - the reason hi-fi amps had a "loudness" button was to compensate for the loss of bass listening at quiet volumes. This button simply boosted the bass to make up for the perceive lack of bass when listening quietly. Humans are complicated, and music doubly so... 😉

Velocity shouldn't be affected by your mod wheel at all. What I suspect is happening is a MIDI volume issue - ie, your keyboard is sending MIDI volume events to Logic and it's pulling your channel fader down (or changing the internal volume of an instrument). Try using Snoize's MIDI monitor to observe the MIDI traffic to Logic when this happens, and see whether your keyboard is sending a CC #7 event or something else. You can uncheck the preference to allow MIDI CC's to control pan and volume which might help with this case. If you think this isn't the case, and Logic is doing something *actually* with your velocity events, then start with a brand new project (not from any templates) to make sure you have no MIDI processing going on, and see if it still happens...

Ok, so then you just want to use pure MIDI, and *not* the controller assignment system at all. You do not use controller assignments, you record the knob movements as MIDI data, and use the plugin's own MIDI learn system - I think that's what you are saying above... Yes, you haven't correctly learned a controller assignment for the plugin parameter, you've only, presumably mistakenly, learnt to open the controller assignments window. It doesn't really matter what you use to send MIDI CC's, anything that is a generic controller will work fine. I don't use those, but there are a lot of them around. CH was recommending this one recently: https://ghostnoteaudio.uk/products/conductor I'm not sure why you'd need MIDI transform, unless there is no way to change the CC messages the controller sends (but this shouldn't matter with the plugin MIDI learn anyway, it will just learn whatever message that fader sends.)

When you move the knob, what MIDI message is it sending? Can you show me screengrabs of the controller assignments you are making in both cases? Just limit it to one plugin parameter for simplicity. It's possible Logic is overwriting the previously made assignment for that plugin parameter with a new one, but without specifics is difficult to know exactly what's going on...

Ok - in the Mac world, that's called "beachballing", and means Logic is either processing, or is stuck (this basically happens when an application is no longer responding to UI events). It's not clear to me what your bounce settings are - did you try what I suggested, and if so, can you let us know what the results were? This is part of the troubleshooting process...

I'm not sure what you mean by "permanently buffering"... Does changing your bounce settings affect the behaviour? (Ie, a straightforward bounce to PCM, no normalising, don't add to iTunes etc). Or bouncing to a different place?

There is no inherent problem with learning controller assignments from different MIDI controllers, so possibly you are doing something wrong in the process perhaps? Please document what you are doing and what’s not working, and we might be able to help…

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.