I have a Keystation Pro 88. Had it since 2009. It has done this twice. Both times I just reset all settings on the keyboard to factory, and that resolved it. No idea how that happened, and I absolutely detest their now non existent “support.” And don’t get me started on theur audio interfaces…
1 Like
Haha. That’s the one. I might have tried resetting it but once it did that I figured it was done and just got another one. Or a Williams which never did it. My ARTURIA Keylab has never done it. My friend Tim Ryan was the owner of M-Audio and he treated me like gold. And his customers and employees. But once he sold the company things got wonky. I loved all my M-Audio gear - Delta 1010’s, Flying Cows, Tampa, etc.
2 Likes
Ha! Delta-1010. Those were the days! (… of early surround, in my case 
…)
2 Likes
Once mine dies, I’ll get getting an Arturia controller. The Mini I have is stellar
1 Like
I had a Novation Nocturn keyboard when I started getting wonky pitches, but it’s possible that other brands than M-Audio might also be susceptible to the same pitch problems, or that there’s more than one way for that to happen.
1 Like
I had three of them! going lightpipe into my RME HDSP 9652 for 24 inputs. Sounded great, although not as great as the 2 RME interfaces I got later on.
1 Like
This sounds very very like 44k source (ie the VSTi) playing at 48. The difference is almost a semitone, as you are experiencing, but not quite. Somewhere in the bowels there is a sample rate mismatch. Id bet on it.
The extra measure you are getting on export/import of rendered files supports my theory.
Good Luck
That would be the normal reason. But when an M-Audio keyboard controller goes bad, it simply starts sending out wrong pitch info via midi to VSTi’s. The controller cannot affect audio playback, only midi.
1 Like