Oscuro installer
For the M-Vave SMK-37 Elite and SMK-37 Pro (also sold as the MKE-P37 and the Starrykey 37 Play), over the USB cable. Use Chrome or Edge on a computer, and close DAWs and other MIDI apps first.
Install or update Oscuro
The first install, from M-Vave's firmware, also needs M-Vave's firmware file; the page combines the two on this computer.
When the keyboard already runs Oscuro, app.bin alone is enough.
Choose a release
Install Oscuro: the keyboard already runs Oscuro, and this updates its app.
Install the complete image: for a keyboard that runs M-Vave's firmware (the first install), or to start over. It needs no M-Vave file.
Go back to M-Vave's firmware
Works from Oscuro and from any M-Vave version. If you erased the patch memory for Oscuro's synth, restore your backup first: M-Vave's firmware doesn't bring it back.
If Oscuro refuses to update this keyboard (its flash chip failed Oscuro's write test), "Use M-Vave's updater" restarts the keyboard into M-Vave's own updater and installs the file with that. Oscuro writes nothing to the flash for this. It needs Oscuro 0.21.3 or later, and a keyboard that has run an M-Vave update before.
Send synth patches
Sends .syx, .mid, or .oscbank patch files to the keyboard's synth. The keyboard only takes patches its synth
can play: Access Virus patches need the Viroid build, DX7 patches the DX7 build. Anything else is refused before it is sent.
Showcase banks
Make room for patches
The synth builds keep patches in the keyboard's user memory, where M-Vave's firmware keeps its own data. Oscuro never erases that data on its own, so patches are refused until you do these two steps once.
-
Save a backup
Reads the whole memory into a
.ksuafile, in 10 to 30 seconds. Keep the file somewhere safe: it is the only copy. -
Erase for patches
Clears the memory so the synth can store patches there. Every patch stored on the keyboard is deleted too.
Restore a backup
Writes a .ksua file back and checks it. Do this before going back to M-Vave's firmware, or whenever you want
its data back. It replaces everything in the memory, Oscuro's patches included.
Send a test report
For testers of a test build (_test in the file names, TEST on the About screen). The keyboard counts how fast
keys become MIDI, how busy it is, audio dropouts and failed saves. This reads those counts and saves them as one file to send back.
It only reads: nothing on the keyboard changes. The counts start again at zero when the keyboard is switched on, so read them
before unplugging it.
Watch reads every 5 seconds until you stop it: it records the busiest moments and notices restarts. Other MIDI apps can stay open on macOS; on Windows, close them first.