SMK-37 Field Guide Unofficial

When it doesn’t work

Troubleshooting & FAQ

The fixes people need most, in one place. Most problems are one of five things — firmware version, the PATCH button, Bluetooth pairing in the wrong place, MIDI channels, or a charge-only cable.

Last updated

On this page
  1. First, the five usual suspects
  2. Connection
  3. Playing & sound
  4. Apps
  5. Firmware
  6. Still stuck?

First, the five usual suspects

  1. Old firmware. Update to official V016 (2026-08-12); it fixed key lag, dropped notes, pedal and wheel bugs (release notes).
  2. PATCH is off. The internal synth and the audio jack are silent unless PATCH is active (manual).
  3. Paired in the wrong place. Bluetooth MIDI = the _BLE entry, connected inside the app (iPad) or Audio MIDI Setup (Mac) — never in Bluetooth settings.
  4. Channels. Keys send on 1, pads on 10.
  5. Cable. Many USB-C cables are charge-only. Use a data cable, direct to the computer.

Connection

The keyboard shows up in iPad Bluetooth settings but no app sees MIDI.

iPadOS Settings pairs it as an audio device. Connect Bluetooth MIDI from inside the music app and choose the name ending in _BLE. See iPad Pro.

Bluetooth MIDI won’t connect on my Mac.

Use Audio MIDI Setup → Window → Show MIDI Studio → Bluetooth button → Connect, not System Settings. See Mac + Logic Pro.

It connected to one device and now won’t connect to another.

It auto-reconnects to the last host and serves one connection at a time. Disconnect or forget it on the old host (and force-quit Midi Suite) first. On SMK37 OPEN, use FORGET MIDI PAIRS.

Windows doesn’t see it over Bluetooth.

Windows needs Bluetooth 5.0 and M-VAVE’s BT MIDI Connector app (manual). USB is simpler.

Bluetooth is flaky with a WIDI or another third-party host.

Remove old pairings on both ends and use auto pairing (r/synthesizers). A community BLE patch exists for the Pro only.

USB-C is plugged in but nothing appears.

Power switch on; data cable; direct port, not an unpowered hub; on an iPad, charge the keyboard first or use a powered hub.

Playing & sound

Notes lag, or the first notes after a screen change drop.

Fixed in firmware V016 (r/midi thread). For Bluetooth, keep the app buffer around 128 samples; use USB for tight playing.

The pitch or mod wheel drifts, is jumpy or dead.

Keep the wheels at rest when powering on. Firmware from 2026-01-26 onwards has a wheel calibration mode.

I hear two sounds when playing my DAW.

The internal FM synth is answering the keys too. Turn PATCH off, or turn Local Control off (V016).

Loud chords distort.

Lower Volume on the PARA page (K4), or choose a quieter patch.

The arpeggiator won’t switch off / the sequencer won’t start.

Turn the ARP Latch off first. The sequencer won’t start while Arp or Note Repeat is on.

Sustain is stuck or behaves oddly.

Check GLOBE K7 (sustain vs expression). A sustain bug and a mod-wheel hanging-sustain bug were fixed in 2026-01-26 firmware.

What CC numbers and pad notes does it send?

M-VAVE doesn’t publish the stock map. Read it in Logic’s MIDI activity/Event List or a MIDI monitor, or set your own in MIDI Suite. Custom firmwares document their own maps, which don’t apply to stock.

Apps

Koala only plays one sample up and down the keyboard.

Keyboard mode is on: in the SEQUENCE tab, toggle off the piano icon on the left.

Pads don’t trigger in my app, but keys work.

Set the app to receive all channels (pads are on 10), and make sure the pads are in Note mode (not CC/PC) in Midi Suite.

My GarageBand Beat Sequencer pattern disappears in Tracks view.

Record it into a region first (main Record from bar 1), then turn the Beat Sequencer off. See GarageBand.

Recording the internal synth gives silence.

Latch PATCH; select the keyboard as the audio input device; check the sample rate. Fallback: the 3.5 mm output into an audio interface. See Sampling.

Firmware

A flash failed or the keyboard won’t boot.

Don’t flash something else on top. Hold OCTAVE− + OCTAVE+ for 5 s at power-on for update mode, then restore V016 via the SMK37 OPEN workbench, M-UPGRADE or M-Flasher. See recovery paths.

Back on stock firmware, every key plays C and the synth is silent.

The key map was rebuilt without calibration — use SMK-37 Repair with your model’s V016 file, then run wheel calibration.

M-UPGRADE says “Failed to enter upgrade mode!”

Leave the app open, unplug and replug USB, continue (M-VAVE downloads). On a Mac, allow it under Privacy & Security → Open Anyway first.

The workbench or installer can’t see my keyboard.

Use desktop Chrome or Edge (not Safari, Firefox or an iPad), allow MIDI/SysEx access, use a data cable, and quit Logic and other MIDI apps.

Sampler shows EMPTY after installing SMK37 OPEN.

Use the workbench’s “Check / initialize samples” — no need to flash again (README).

Can I flash from my iPad?

No. iPadOS browsers have no Web MIDI, and the official updater is Windows/Mac only. Use a Mac or PC with Chrome.

Still stuck?

Ask with your model (Elite or Pro), firmware version and host in the M-VAVE forum, in SMK threads on r/synthesizers, or on r/MVaveFM1 for firmware questions. More places in the directory.

Sources & links on this page (10)

Page last updated 2026-11-21 · Back to top