Thanks for the extra information.
The wierd thing is that both keyboards have the same problem. There may have been some damage to the older kb, but why does the new kb show the same problem?
Back to something I asked before, we could do with a prog like MIDI-OX, but I don't know if there is a mac version, or something similar. This is a prog that will monitor the midi input that comes into the computer, and show the data on the screen, esp the note number, velocity, etc. Need to know what data is getting there. Is something getting thru? Something maybe, but out of range. If NOTHING shows at all, then there's a problem with both kb, or the cable. If something does come(see data in the posting I referred to earlier) then the problem is how Logic deals with the data. Could be that if the data is totally out of range, i.e. it's a note ## that Logic cannot handle, then Logic just disregards it, but maybe Logic can be set to do something with it.
You might check: https://www.snoize.com/MIDIMonitor/
, although I've never used this.
The intercept prog will also tell us if both kb do EXACTLY the same thing, i.e. info for key #63, or the same damaged data for key #63.
Maybe Garage Band has better rules for handling damaged data, so it can cope with the damage?
I don't know EXACTLY how your kbs work, but when you press a key that will create some sort of signal in the kb hardware/software, and in due course this will be converted into a note, or a midi key ##. hence how the octave shift works, etc. It is NOT an immediate - Press Key --> Midi Note generated.
The exact data that gets to the computer could help!