I figured that it might be helpful to give more information. I did not want to be too long winded in the first post, sorry.
Apple, the process of editing the MIDI Environment was so stupid-tedious. It should not be this hard. Would you please fix this? It should pre-populate when a Virtual Instrument is loaded. The maker of this plugin has a MIDI map made. Why not allow theirs to load?
After manually typing in 136 different drum hits (by 2AM), I was ready to work on the track, as the MIDI Map worked!
As I began to edit the cymbals, I realized that I now had a strange, new, phantom cymbal triggering. It was on my SD3 Toms Track. and now, my SD3 toms are gone. I all worked fine before, but oh well, I will just quickly fix it, right?
WRONG!
So I tried to go into my "Sup...Toms" track (Superior Drummer 3, also), but I could not. Why? Well, while I was editing the MIDI Environment, I noticed that the SD3 Toms track became highlighted some how, and now it is not accessable at all.
Disappointed, I just went to bed. Apple did you do this; because, my Apple Watch showed you that I was still up at 2 AM? Was this your way of telling me, GO TO BED? Or did you insert an AI gremlin into Logic Pro that feels that my heavy use of TOMS is too Old School and that the new kids want overbearing HiHats? hahaha
Please help? Anyone MIDI Genius?
This image shows the MIDI Environment with the wiring going from the monitor to the "SupCymbals" track, not the "Sup...Toms" track, which has the issue. it also shows the Mixer window. The track with the issue is the one in the mixer track with the mouse pointer on it. You can see it light grey with no way to edit it.
Apple, I prepared a snippet of the song (16 seconds), too. We are musicians using Logic. I appreciate that you offer us the ability to show a picture, but we should be able to share an audio file of the issue here, too. Just saying...
