Midi Keyboard issues on new session

[paul_g]

I have an Akai MPK 249 connected via USB to my Mac. I can open up a session I just finished, and my keyboard will trigger midi sounds from a plugin on an instrument track.

I created a new session, created an instrument track, put the same plugin on the track and nothing. I can see the midi messages getting sent in the midi session of the transport window in Pro Tools.

I ensured Instruments are visible on the top of the Mix window track, I set the values to the same as the working session. I checked midi levels, I unplugged the keyboard, I rebooted the Mac. Nothing. Yes, I ensured the instrument track had record enabled, just as the other session worked during my test.

Any ideas?

[paul_g]

So I had an older session called Test Template. I opened that up, created an instrument track and it works perfect. That session was created on October 10, prior to me upgrading from 2023.12 to 2024.10.1, so I suspect there is an issue with creating a new instrument track and getting a midi keyboard to generate signal to the plugin. The plugin I'm using is x-pand, so it's a native Avid plugin.

I'll open a case... At least I have an older session to use as a template that seems to work. Thank fully!

Case Number is: 04904213

[FunkzzaJ]

Hi Paul!

Im not an advanced user, but some simple things to check:

I'd check midi settings in prefs. Maybe changed from 23.12 to 24.10. Perhaps the track must be selected.

I'd use minigrand for troubleshooting, as it it possible to click pianokeys on the gui (or use the pro tools virtual keyboard)

[basslik]

Did you figure it out?


Same here.


I'm using a midi controller, Ensoniq ASR. The piano roll is showing every key I hit on the midi screen and it's doing it's thing visually.


It's a stereo instrument track I created and used a grand piano in the insert,

Shows the usual tiny piano keys and it shows the key I hit. I can't hear anything when playing whether rec. armed or not, and don't see any metering on the fader at all.

Although if I record something, without hearing or seeing any metering, it does record and play back what I played and it also shows the midi notes being played?

I know it's something not turned on I suspect because if I use the user songwriter template, it works as I remembered it.


I fell like a dunce (LOL). But I do live recordings, and never midi.


Worst case scenario, I can import the audio into another clean songwriter session template, but I'm going to loose all my set setting for the audio tracks.


Thank you for your time. __________________

[K Roche]

Originally Posted by paul_g

So I had an older session called Test Template. I opened that up, created an instrument track and it works perfect. That session was created on October 10, prior to me upgrading from 2023.12 to 2024.10.1, so I suspect there is an issue with creating a new instrument track and getting a midi keyboard to generate signal to the plugin. The plugin I'm using is x-pand, so it's a native Avid plugin.

I'll open a case... At least I have an older session to use as a template that seems to work. Thank fully!

Case Number is: 04904213

I have almost the exact same system (See my studio system below) and use the Akai MPK 249
So the behavior and wording changed Now I went from PT 2024.3 to 2024.10.1 and from OS Ventura - OS Sequoia 15.1.1

In PT "Settings/Preferences". Midi Tab > Basics > make sure "Midi Input Monitoring follows selected track"--- is highlighted
If it is then the other new behavior is that as soon as you highlight and select an instrument track the (I) button will highlight green

Note I have also had to (several times ) unplug the USB connection on the Akai and plug it back in

Also Note that because of a different issue with my Avid Carbon when I upgraded to PT 2024.10.1 I ended up having to trash my PT Preferences.
I do not know if that is something you need to do but I thought I should note that I did and now my Midi seems to working as expected

[paul_g]

Originally Posted by basslik

Did you figure it out?


Same here.


I'm using a midi controller, Ensoniq ASR. The piano roll is showing every key I hit on the midi screen and it's doing it's thing visually.


It's a stereo instrument track I created and used a grand piano in the insert,

Shows the usual tiny piano keys and it shows the key I hit. I can't hear anything when playing whether rec. armed or not, and don't see any metering on the fader at all.

Although if I record something, without hearing or seeing any metering, it does record and play back what I played and it also shows the midi notes being played?

I know it's something not turned on I suspect because if I use the user songwriter template, it works as I remembered it.


I fell like a dunce (LOL). But I do live recordings, and never midi.


Worst case scenario, I can import the audio into another clean songwriter session template, but I'm going to loose all my set setting for the audio tracks.


Thank you for your time. __________________

No, I didn't figure it out, however it just started working as normal mysteriously.

Originally Posted by K Roche

I have almost the exact same system (See my studio system below) and use the Akai MPK 249
So the behavior and wording changed Now I went from PT 2024.3 to 2024.10.1 and from OS Ventura - OS Sequoia 15.1.1

In PT "Settings/Preferences". Midi Tab > Basics > make sure "Midi Input Monitoring follows selected track"--- is highlighted
If it is then the other new behavior is that as soon as you highlight and select an instrument track the (I) button will highlight green

Note I have also had to (several times ) unplug the USB connection on the Akai and plug it back in

Also Note that because of a different issue with my Avid Carbon when I upgraded to PT 2024.10.1 I ended up having to trash my PT Preferences.
I do not know if that is something you need to do but I thought I should note that I did and now my Midi seems to working as expected

That's interesting, because for some unknown reason it's now working fine. I can either use X-Pand, or EZKeys 2, and all the functions work as normal.

I did check the settings you mentioned, and the MIDI Input Monitoring flows selected tracks was "unchecked".

Are you saying I should have this preference selected? (checked)?

FWIW, I got a response from Avid, they wanted to connect, but I told them it's now working. So Don't know if we need the case open or not.

[paul_g]

Originally Posted by K Roche

In PT "Settings/Preferences". Midi Tab > Basics > make sure "Midi Input Monitoring follows selected track"--- is highlighted
If it is then the other new behavior is that as soon as you highlight and select an instrument track the (I) button will highlight green

I see what that option does! That's slick!! I like it! Thanks for pointing that out. I guess all is well, because I've done 5 or 6 tests, closing PT, reopening, creating new test sessions and everything works. And yes, early on in my troubleshooting, I trashed prefs, tried new ports on the Mac, different USB, etc..

Thank you for this.

[K Roche]

Originally Posted by paul_g

I see what that option does! That's slick!! I like it! Thanks for pointing that out. I guess all is well, because I've done 5 or 6 tests, closing PT, reopening, creating new test sessions and everything works. And yes, early on in my troubleshooting, I trashed prefs, tried new ports on the Mac, different USB, etc..

Thank you for this.

Glad its working... Yes I always have that selection checked

[basslik]

That preference option is not on the midi page. That's weird.


Man I'm stuck. I'm on Sonoma.


"Midi Input Monitoring follows selected track" is not there?

[massivekerry]

Originally Posted by paul_g

No, I didn't figure it out, however it just started working as normal mysteriously.

Ok. I hadn't wanted to reply, because I thought you might have a different issue. But this does happen to me occasionally. Sometimes I'll be chugging along, and then suddenly the MIDI is showing up, but isn't passing through to the VI. Re-launch or re-boot generally fixes it. Sometimes it happens with audio signal routing through busses as well. But it is infrequent, and as I said, a re-launch or re-boot usually fixes it. Wish I had a better answer.