des99

It also sounds like a latency issue to me. The meter is reading at the correct time the track Is sending signal through the channel, but by the time the mix is coming out of the main output channel, with various plugins on it, you *hear* it later than it is because of plugin-induced latency, so the audio is out of sync with the meter on the track. Try going into Low Latency Mode, or removing all your master bus plugins and see if it affects the display behaviour.

Your playhead has disappeared because this is drawn with Metal, and your Mac does not support Metal, or the later macOS versions you are running (which all require Metal), and you've patched these macOS versions to run on unsupported hardware. Unfortunately, you won't be able to use Logic correctly on these systems without Metal. Other parts of Logic will also crash without a Metal-capable machine.

If you post the crash report, we might be able to identify whether it's a third-party plugin crashing the project, or whether the project itself is corrupt and can no longer be opened.

Your faders, automation, compression, limiting, saturation, or changing up the sounds and arrangement, editing MIDI data - there are lots of ways to change the make up of your mix. And the more you do, the better you'll get at achieving the mixes you want.

If your peak volume is at the correct level, but your overall "loudness" is quiet, that means your mix is too dynamic - ie, the peaks are much louder than the average signal level. To increase the overall loudness, you need to bring up the volume and bring down the peaks, which could be an arrangement, mix, or mastering issue. In short, to get a "loud" mix, you must mix it that way to achieve it, as just compressing your peaks a lot to obtain the loudness probably won't sound good.

Ok, try downloading the Snoize MIDI Monitor app, and watching the traffic while you play the keyboard, both with and without Logic running. Also try in another host, even a simple one like Hosting AU - does the MIDI playback show delays in either of those, or is it just inside Logic where you observe this delay?

I understand... Yes, which was why I tried earlier to deduce whether the MIDI *event* was late, or whether the MIDI event was on time but the *audio you hear* as a result of that MIDI event was late. You said it's the MIDI event that's late, based on observing the time between playing as note, and seeing it appear in Logic with the transport display MIDI indicator. So if that's true, we're ruling out general plugin latency issues, and focusing on your MIDI traffic. I know it has no output. But do you still see a delay between hitting a note on your keyboard, and the MIDI event being displayed in the transport display under these (simplified) conditions? That's what I'm asking...

Hmm, both are generating MIDI events, and so probably use Core MIDI to deliver them (unless Logic implements the keyboard differently), and if this is struggling with one MIDI device, eevn one that isn't directly sending events, it affects all MIDI delivery. Is your processor/computer bogged down? (Check Activity Monitor for anything using a lot of CPU). Also check Logic's own performance meters just in case it's bogged down too. Select a track set to "No Output" to take any MIDI output or possible feedback out of the equation too, and play your MIDI parts - any difference?

Yes. No, I didn't mean you should learn a new assignment, you said you'd already created assignments, I thought, so I was telling you how to find and edit them (so you could screenshot them for us). When I said when you move the fader, it should select the assignment you've made for it, I didn't say "enter learn mode", as this will not find your previously made assignment, it will create another new one. In any case, that assignment above won't do what you want, as you've assigned the fader (again) to the command "Open Controller Assignments", not to any plugin parameters. And the fact that you are recording MIDI data into a sequencer and can see the CC data means you don't have any working assignments to do what you want. You need to create a controller assignment to control whatever plugin parameters you want for each MIDI fader, so you need to enter learn mode, move the parameter you want to control in the plugin, then move your MIDI control to assign it to that plugin parameter. At that point, the MIDI data generated by the fader won't control anything in Logic other than the plugin parameter you assigned to it.

All my iTunes music is in Music, but I think *playlists* don't translate, so you'll need to decide what to do about that, unfortunately...

It will likely work, but you might as well update Logic in the meantime. Logic updates are free, so you can update to the most recent version your macOS system supports. So I'd suggest you backup your current system (and version of Logic), update macOS, then update Logic from the App Store.

Ok, so the only thing that can cause this is MIDI driver issues or other MIDI feedback routing issues, so I'd start by removing/uninstalling the drivers for the keyboard, rebooting, and reinstalling them.

No problem! If you're still getting strange behaviour, post back and we'll continue to troubleshoot... 👍

If you had copied your preferences from the old machine to the new one, all your old configurations would still be intact - can you retrieve your old preferences from that machine, or your backups? That would seem simpler...

That's normal, the user Library folder is hidden by default to protect it from user tampering. You're looking at the root Library in your screenshot, that's a different location. You need the one that stores your user preferences, which are all stored in your user account folder. You can use Finder's "Go to Folder" option (shift command G) and and type or copy the path eg "~/Library/Preferences/, and it will open a window on that folder. (The "~" is just an short way of saying "/Users/*yourusername*/" BTW)