Already a qualifying Patreon member? Refresh to access this content.
2 thoughts on “Loopop’s MIDI Morph Station”
Nyx
I’ve not been able to get this to work with a Korg Nanokontrol 2. No MIDI devices are showing in the inputs or outputs on my Windows machine. Unsure if I’m doing something wrong? Have tried refreshing the page after plugging in the device, have also tried having it plugged in before opening the page.
Are other programs seeing the controller? Are you using Chrome or Edge? I tested it on those and it works. I asked AI for other ideas:
Based on my research, this is a well-documented Windows-specific issue with Chrome and WebMIDI, not a bug in your app. Here’s what’s likely going on:
The most common cause on Windows: Some USB MIDI devices on Windows are only discoverable by WebMIDI in Chrome if they’re already in use by another application This is because the default Windows USB MIDI driver doesn’t support multi-client access — Chrome can’t “see” the device unless something else has already opened it.
Here’s what to try, in order:
1. Check Chrome’s MIDI permissions — navigate to chrome://settings/content/midi and make sure the site (or file:// if local) isn’t blocked. You should also see a small MIDI keyboard icon in the address bar when the page loads — if the icon has a red X, click it and select “Always allow” for full MIDI device control.
2. Make sure the device shows up in Windows at all — open Device Manager and look under “Sound, video and game controllers” for your MIDI device. If it’s not there, it’s a driver issue, not a browser issue.
3. Try opening the device in another app first — open a DAW, MIDI-OX, or any MIDI utility so the device is “active,” then reload the page. The default Windows 10 USB driver is not multi-app capable, so some devices need to be opened by another application first to become visible to Chrome’s WebMIDI.
4. Check for manufacturer drivers — if your MIDI controller has dedicated Windows drivers (rather than relying on the generic Windows USB MIDI class driver), install those. Devices with their own multi-client drivers tend to work much more reliably with WebMIDI.
5. Restart Chrome completely — sometimes Chrome caches the MIDI device list from startup. Close all Chrome windows and reopen.
Unlock with Patreon
I’ve not been able to get this to work with a Korg Nanokontrol 2. No MIDI devices are showing in the inputs or outputs on my Windows machine. Unsure if I’m doing something wrong? Have tried refreshing the page after plugging in the device, have also tried having it plugged in before opening the page.
Are other programs seeing the controller? Are you using Chrome or Edge? I tested it on those and it works. I asked AI for other ideas:
Based on my research, this is a well-documented Windows-specific issue with Chrome and WebMIDI, not a bug in your app. Here’s what’s likely going on:
The most common cause on Windows: Some USB MIDI devices on Windows are only discoverable by WebMIDI in Chrome if they’re already in use by another application This is because the default Windows USB MIDI driver doesn’t support multi-client access — Chrome can’t “see” the device unless something else has already opened it.
Here’s what to try, in order:
1. Check Chrome’s MIDI permissions — navigate to chrome://settings/content/midi and make sure the site (or file:// if local) isn’t blocked. You should also see a small MIDI keyboard icon in the address bar when the page loads — if the icon has a red X, click it and select “Always allow” for full MIDI device control.
2. Make sure the device shows up in Windows at all — open Device Manager and look under “Sound, video and game controllers” for your MIDI device. If it’s not there, it’s a driver issue, not a browser issue.
3. Try opening the device in another app first — open a DAW, MIDI-OX, or any MIDI utility so the device is “active,” then reload the page. The default Windows 10 USB driver is not multi-app capable, so some devices need to be opened by another application first to become visible to Chrome’s WebMIDI.
4. Check for manufacturer drivers — if your MIDI controller has dedicated Windows drivers (rather than relying on the generic Windows USB MIDI class driver), install those. Devices with their own multi-client drivers tend to work much more reliably with WebMIDI.
5. Restart Chrome completely — sometimes Chrome caches the MIDI device list from startup. Close all Chrome windows and reopen.
Let me know how it goes!