Electron not detecting Keppy's Synth as a possible MIDI output?

[FireController1847]

Now I don't know if this is an issue with Electron or Keppy's Synth, but I came here first (because loopMidi shows fine). When running the test code below:

navigator.requestMIDIAccess().then(midi  => {
  for (const item of midi.outputs) {
    console.log(item[1]);
  }
}).catch(console.error);

If you run it in Google Chrome, you'll see that Keppy's Synth shows up as an option (so does loopMidi for me). But if you run it in an Electron app, say, Discord, by pressing CTRL+SHIFT+I and then pasting it into there, you'll see the only outputs available are loopMidi if you have it, but no Keppy's Synthesizer.

[KaleidonKep99]

It's up to the app developer to disable certain MIDI support functions in the Electron engine.

[FireController1847]

What? That's not the issue lol. First, I am the app developer, second, the issue is that it doesn't show up at all in Electron while it does in Google Chrome.

[KaleidonKep99]

Well, you didn't specify you were the developer. 🤔 Chromium had issues with MIDI devices, and they fixed them recently, after some Nightly builds.

Maybe Electron is using an oudated release of Chromium, I'm not sure.

[FireController1847]

Yea, sorry about that lul.

I'll bring up an issue in https://github.com/electron/electron/ referencing this one to see if it's an issue there.

[KaleidonKep99]

Also take a look at this, it might help the Electron team: https://bugs.chromium.org/p/chromium/issues/detail?id=672793

[KaleidonKep99]

Anything new about it?

[FireController1847]

No, this bug still seems to be there. No responses on the electron issue either.

[KaleidonKep99]

👀

[FireController1847]

It got tagged, hopefully will be fixed eventually.

[KaleidonKep99]

I'll close this, since it's not an issue with Keppy's Synthesizer itself. Let's see if the Electron team updates their CEF build... 🤷‍♂️