Well, it works on my older Mac running Big Sur and F26. It might be the M1 processor. Definitely send this in to tech support, because I know there have been other issues. Use the Submit A Request tab at the top of the page.

In the meantime, a Preferences reset might be something to try.

Thanks, Mike. I'll give the Preferences reset a try before I send it on to tech support. (& I'll report back here whether or not that fixes it.)

-Michèle 

Updating this thread so people searching in the future can see the progress. (I always appreciate it when others do that in their threads.)

.

I tried a few things this morning.

1. I verified that the Mac MIDI Audio Setup utility still sees the Xkey. It does.

2. I installed the Xkey Plus app, which is made by CME & designed to configure/update firmware for the Xkey. It does NOT see the Xkey.

3. I tried plugging the M1's power adapter into my hub (USB-A to USB-C) because some people in the Apple forum reported that this made their MIDI keyboards work with their M1s. Neither the Xkey Plus app nor Finale could see the Xkey, and Finale still couldn't open the MIDI Setup dialog box.

4. I tried plugging the Xkey into the USB-C port via a simple adapter rather than a hub. Same results; neither the Xkey Plus app nor Finale could see the Xkey, and Finale still couldn't open the MIDI Setup dialog box.

5. I reset my Finale Preferences. Finale could not see the Xkey & couldn't open the MIDI Setup dialog box.

6. I unplugged the Xkey completely from my system. SUDDENLY, Finale could open the MIDI Setup dialog box. The box remained open when I plugged the Xkey back in, but even though the M1's MIDI Audio Setup utility could see the Xkey, Finale's MIDI Setup dialog box could not. I closed Finale and leaving the Xkey plugged in, reopened Finale. It could not open the MIDI Setup dialog box while the Xkey was plugged in. I repeated this a few times to confirm. 

As long as the Xkey is plugged into the M1, Finale cannot open the MIDI Setup dialog box. 

.

Now I'm going to go send it the issue to tech support, as Mike recommended. I will report back when I have updates to this topic.

Just wanted to update this thread again. Tech support & I are still working on it. They've had me uninstall Finale & re-install it. I've sent them SysInfo files and Plogue logs. No solution yet, but we haven't given up. 

Well, at least they’re working on it!

Since Xkey Plus app still supports MacOS 10.5 and the PPC, I will hazard a guess and suggest that this issue will not be resolved till the app is updated.

I only installed that Xkey Plus app for testing/diagnostic purposes; I don’t really care if it specifically works or not.

But I DO care about Finale working with the Xkey keyboard itself—which does not require the Xkey Plus app, or at least didn’t on my previous MacBook (2015) with Finale 26. That’s what Support & I are trying to solve.

Many devices that supported CoreAudio or CoreMIDI on a PowerPC no longer work. Although the common complaint is the opposite: newer devices that do not work over older MacOS, this issue works both ways. If that's the case, you may be out of luck unless you can get it working through Rosetta 2. It is odd that it shows up in Apple's Audio Midi Setup.app but not Finale. I've never seen this before.

Hmm, 🤔  I'm pretty sure that Rosetta 2 was installed the first day I had the M1 back in January. Is there any reason it might have been uninstalled? or changed? I'll have to look into that. Thanks 🙂

But yes, it shows up in Audio MIDI Setup -- I sent a screen recording to Support with audio to show that it blinks the lights and produces the test tone. It's weird.

I have to say, the biggest complaint I have about the M1 is audio. Audio apps such as Audacity "forget" which input/output to use. Plugging in headphones doesn't turn off the system speakers. Etc. It's weird. 

Thanks for your comments! I will update this thread when I have more info. 

UPDATE: This issue had been solved!

Many thanks to Austin at Support, who was incredibly patient with me -- the only reason it took so long to get to the solution is because I was out of town teaching & couldn't immediately do the things he suggested.

As part of troubleshooting, he had me create a new admin user account & see if it worked with that user, which it did. That meant that the issue was something in a configuration or preference file associated with my usual (admin) user account. He had me create a new MIDI configuration (in the Mac Audio MIDI Setup utility) for my usual user account and try again -- and it worked! WooHoo!

Color me happy. 😀👍

Also: now the Xkey Piano & Xkey Plus apps see the keyboard, too.