des99

By delete, do you mean delete the tracks in the main window? All the audio files you've imported are still referenced in the project, regardless of whether they are used in the main arrangement. You could just pack them into a folder, then you've got one item to move, and no bouncing or new audio files to deal with. Ok, so you've now *added* another 18 audio file references to the project, so your project contains all the original audio files, and the new ones you've made by bouncing. Sure - all the audio files the project uses will be copied to the project folder/package. If you don't want the original audio, you'll need to remove the unused ones, or ones you don't want anymore, from the project audio window, so the project just references the 18 new bounces you made. Remember, there is a distinction between the files you've imported into the project, versus which ones are actually currently in the arrange window. If you import 100 audio files, but only put one in the arrange window, the project still refers to those 100 audio file assets, unless you remove them from the *project*, not the arrange window. The Project Audio window is where you manage the audio files referenced in the project, and has a bunch of tools to do things like "delete unused audio" (ie, delete audio file references that aren't used in the arrange page) and other useful management things. Be careful before you delete stuff that you didn't mean to delete, though! For the last point - keep the Logic project at the sample rate of your audio - 48KHz.

I know you're a bit late to the Apple silicon game, as we've been talking about this for years now (welcome! It's good here! 🫠), but one of the first things I realised when I got my M1 Pro MBP, was that Apple silicon performed differently to a decade or more of previously held understandings (and I was one of the first to start posting about this). Previously, on my Intel Mac, I'd generally run a mid, safe-ish but reasonably performant buffer of 128. If I needed something to be lower latency (eg, tracking a guitar through an amp sim), I'd drop it down as low as I could get for that task, but 32 for me with a high plugin load was marginal. And then, as the project got bigger and we progressed to the mix stage and weren't tracking any more, the buffers would go up to give more performance overhead for large amounts of tracks - 512 or even 1024 etc. That's the way most people tended to work, depending on their systems. All of that went out the window with Apple silicon. On these machines, they perform *better* at lower buffer sizes, and actually perform *worse* as you increase the buffer (I did a bunch of tests to verify). This means that for the most part, you can drop the buffer the 32 samples, and then just forget about it - and that's pretty much what I've been doing since. Good that your e-core worries and that video that confused you that we all dismissed a bunch of times here turned out to not be a problem after all, like we were saying. 😉 Yes, these machines are phenomenal, and my MBP is by far the best computer I've ever had. And the fan has only ever turned on once in the few years I've had it, doing some large render process. And never with Logic. (Due to the power envelope on these machines, and confirmed by Apple, the CPU alone doesn't pull enough power to even bother the fans to turn on, even with all cores maxed. It's really when you hit the CPU *and* the GPU hard, that the fans wake from their long slumber.) Enjoy! 👍

Nope. I love mine. If you're just doing some email and surfing tiktok, then sure, it's overkill. If you're actually *doing* anything with it though, you'll benefit from the increased power in many ways. However, I do think large amounts of RAM (at the prices Apple charge) *is* overkill for many folks. Unless you're regularly doing hybrid cinematic movie scores with templates of five hundred+ tracks of sampled instruments available, 16GB is generally fine (I've not really had any problems, and I do *everything* with my machine), and 32GB gives plenty of room to stretch your legs. Any more than that is, imo, overkill, without a specific use case...

So either something is sending MIDI to Logic (it's common for instance for controllers to have knobs/sliders/wheels that send spurious data, even when not being touched), or something in Logic is resetting these. What did Snoize tell you - this will show, or rule out whether it's your keyboard sending MIDI to Logic that's doing it...

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.