MIDI Controller Keyboard “Missing” in DP

[Dave Connor]

Not sure what happened but DP no longer sees my controller. If I open a stand alone program like Kontakt it sees my keyboard fine, so it isn’t the OS (Ventura on a Mac Studio M2, DP 11.23.)

Is there a way to rescan or something so that DP will find it? Everything looks ok in the Bundles window. The keyboard shows there. I thought about reinstalling the keyboard’s driver (Korg Kronos) but I don’t think that’s the problem.

I am getting asked to remap MIDI assignments upon opening but the Korg isn’t available, just Netwok and ipMidi. I have a feeling the answer is simple but I don’t know what it is.

Thanks for any help!

Dave

[James Steele]

I'm guessing it's connected via USB? Do you see your MIDI Controller Keyboard when you open the Apple Audio MIDI Setup app? You can try to rescan there. Or if you see it and it's greyed out, delete it and then do the rescan.

[Dave Connor]

USB yes. I've been checking Audio/MIDI and all has looked well but I'm probably going to do exactly as you suggest. I've left it alone because the apps in stand alone see the driver fine - but not DP so I'll delete the driver in audio MIDI.

Thanks.

[James Steele]

USB yes. I've been checking Audio/MIDI and all has looked well but I'm probably going to do exactly as you suggest. I've left it alone because the apps in stand alone see the driver fine - but not DP so I'll delete the driver in audio MIDI.

Well I hope that works. I was just taking a shot in the dark there, but if other apps "see" it in their setup, I can't explain why DP doesn't.

[James Steele]

I wonder if it's possible that you might have enabled Multi-Record in DP or maybe some kind of input filter. I hope someone else can jump in here soon.

Do you have MIDI Monitor? https://www.snoize.com/MIDIMonitor/

It can be helpful sometimes in these situations. If your standalone apps "see" your keyboard, then it does indeed sound like something is going on within DP.

[Dave Connor]

Here's what's interesting: I can open other older projects in DP and everything works fine. So I must have done something within this project to cause the problem. I'm going to look into your idea about accidentally filtering something or anything else that could be the problem. I've been toggling multi-record just to look at what's available (that's where the Korg is greyed out and "missing.")

I appreciate your help!

[Dave Connor]

To round out the picture, here are some things that might be helpful to others, as well as explain why stand alone apps are working with the Korg but not DP presently. Korg does NOT recommend using their driver on later Mac OS'. They recommend using the native Apple USB driver. So I'm wondering if the Apple driver is what's working with Stand Alone instances of Kontakt. Korg recommends uninstalling their driver but I haven't been able to get that to work. On top of that, the MIDI side of Audio/MIDI is hanging sometimes when opened, with a dialogue warning about recent changes made to the MIDI configuration being a problem, and deleting and reinstalling drivers (or something like that.)

I'm looking at this as a problem that's been lurking with the Korg driver issue. Going to call MOTU tomorrow and see what might be done to get DP to either see the Korg driver or whatever solution they suggest. I may be wrong about a lot of this but hope to find out.

Thanks again James, it's nice to be able to come here for help.

[Dave Connor]

Sorry I didn't get back with a final report. I worked late into the evening when I posted all the above (and James was kind enough to offer suggestions) and did everything I could think of to solve the baffling issue. I've been slammed trying to makeup for a lost day ever since.

It seemed like I did everything 20 times with no luck. In the morning I turned things on and everything worked fine. I'm convinced that the Korg Driver was the issue and I simply was unable to delete it. As it turned out, there are different versions of the Uninstaller with one designed for later Mac OS'. It may have been that I came late to that but still: none of the uninstallers actually deleted the driver from the Audio/MIDI app and I did do restarts after each deletion. The driver still shows there now. So whatever ghosts I was dealing with, the heads-up is to steer clear of Korg MIDI drivers in later model (ARM) Macs and OS'.

[James Steele]

I'm glad you got it sorted. I don't know if the driver is one of those kexts (kernel extensions), but I know there have been times where they only way I could delete something was to boot with the Recovery partition and do it via Terminal. Don't quote me on that. It's a hassle and it's scary because you delete the wrong stuff in Terminal booted from the Recovery partition and you mess stuff up. Glad it's working now.

[Dave Connor]

Yes, I guess we've all heard of using the terminal to delete stubborn things and the perils of doing that. What's interesting is that the Korg *audio driver* was causing me all kinds of misery a while back since the OS saw it as a possible output and Sibelius was hanging up on it. I couldn't get Sibelius to open and when it occasionally did, I couldn't change its audio out. That was only solved by a Sibelius update. Naturally I researched and did everything I could to delete *that* Korg driver with no luck. I may be destined for the terminal route at some point to rid myself of all this the Korg mischief.

Thanks again!

[James Steele]

Yes, I guess we've all heard of using the terminal to delete stubborn things and the perils of doing that.

You might be surprised how many people haven't. I've used it once or twice, and both times I was very nervous about it.

[Dave Connor]

I believe you!I think I've done it once and only did it because I was at wits end. Very nervous indeed.