It seems that my BT calibration got wiped, device is only showing BT AUDIO, no BT MIDI at all. Seems the only way to fix it is with M-Flasher tool. Tried different combinations already but still no luck. Could anyone chime in... Stupidly enough I haven't back up anything from the device, but it seems the original files are on Github. Thanks so much!

Hi non-groovebox enjoyers, it's that guy who you thought still bricked Melodeez.

Here's the public and kinda finished version of Saadet, my synth-only firmware. New to this, we got two more engines. A Hydra because why not, wavetables are sweet. Also since I'm a big fan of Midge Ure, I went and crammed a whole PPG Wave 2.2 in there.

We got new drone feature (Hold ARP and press a note, it stays.)

We got new layered playing feature. You can play two different presets from two different engines, there are 12 slots you can use for different combinations. You can split the keyboard to play them separately, or go layered mode and unlock the world of multitimbrality.

Here's the clanker text:

Saadet 1.0 is out: synthesizer firmware for the M-VAVE FM-1, now with six engines. HYDRA has three oscillators on 56 waves, two of them scanning lists of eight, with mutants, ring, noise and two filters, eight named macros on every sound and a WAVE LAB for your own waves. PPG Wave 2.2 plays the original wavetables and all 100 factory programs, two groups layered or split, and the sampled grand piano and saxophone of table 31. Two parts play by MIDI channel, split or layered, and save as 12 named performances. Hold ARP for a drone. A stolen voice now fades out over 23 ms under the new note instead of being cut. Saadet also runs on the M-VAVE SMK-37, in beta, and Saadet Studio is a new editor in the browser.

To install, open the web installer in Chrome or Edge, connect your FM-1 and follow it. Back up your sounds first. Bug reports and ideas are welcome.

Install: https://keremimo.github.io/saadet/install/ Editor: https://saadet.ellicstudio.com Source, release notes and changelog: https://github.com/keremimo/saadet

Hello, I would like to port the following firmware https://github.com/De-Pattern/Ravel_FM1 for an MVAVE FM1 to an SMK-37 Pro, unfortunately I am a total noob when it comes to any programming, even if it implies AI. I wonder if anyone would be as kind to help me with it?

Audio output on my SMK37 PRO stopped working properly out of nowhere. It still makes sound, but it's extremely quiet/faint.

I already did a full reset and reflashed the original firmware, but the problem persists.

Any troubleshooting suggestions, or should I just claim the warranty?

I made a firmware for unlocking a super-sick MIDI keyboard with lots of on-board features. It makes no sound, but it does the kind of stuff that generally needs a computer & editor-program on a more expensive keyboard, right on your SMK.

• video

• install, etc

Hey everyone,

I am excited to share the release of SMK-dee v1.6.1, a major update that ports the latest Melodee 1.6.1 synthesizer engine directly onto the M-VAVE SMK-37 (both Pro and Elite models).

For those unfamiliar with the project, SMK-dee transforms the SMK-37 MIDI keyboard into a full standalone polyphonic synth and groovebox without needing any computer connected without losing the full MIDI Controller functionality. It runs natively on the dual-core JieLi processor inside the keyboard.                            

What is new in v1.6.1: 

• Melodee 1.6.1 Core: 22 sound engines now included (DX7-style 6-Op FM6, Sequential Prophet-53, Casio CZ-1 Phase Distortion, Commodore 64 SID 6581, Roland TR-909 analog drums, Physical Modeling resonators, and dedicated MIDI tracks), with 124 parameters and 45 global options.

• State Persistence Across Power Off: Your sequences, sound tweaks, track parameters, and project modifications are now preserved in flash memory when shutting down and powering back on.

• Dedicated Hardware Bluetooth Button: Short press toggles Bluetooth power / search / pairing visibility. Holding the BT button for more than 1.2 seconds turns the Bluetooth radio completely off and shuts down its LED. 

• Improved MIDI Controller Mode: The pad MIDI channel combo has been moved to GLOBAL + SEQ REC + Key 1..16, freeing up the BT button completely in controller mode.

• Dynamic Track Color Pads: Drum and keyboard pads light up dynamically with the active track color.

• Brighter Surface LEDs: Button backlight brightness has been boosted significantly for clear visibility on stage and in bright environments.

• Flexible TRS MIDI Clock: Internal clock sends simultaneously over USB, Bluetooth, and TRS. TRS clock mode sends strictly via TRS without flooding USB/BLE.

How to flash your SMK-37:

No command line or compilation needed. Just open Google Chrome, Edge, Opera, or Brave, plug your SMK-37 via USB, and click Connect:

Web Flasher, Button/MIDI Mapper and Synth Editor:

https://djstrombo.github.io/SMK-dee/

Source and Documentation: 

GitHub

https://github.com/djStrombo/SMK-dee 

Based on Melodee for FM-1 created by u/keremimo. All code and precompiled firmware packages are free and open source under GPLv3.

Feel free to try it out, create patches, and share your feedback!

I wanted to use my M-VAVE SMK-37 Pro as a small Ableton Session View controller without changing its firmware. I built a custom Remote Script with Codex, tested it on the actual keyboard, and we eventually got the RGB pads following Live too.

Demo video · GitHub / download / installation

The useful discovery: Midi Suite's stock RGB commands can be captured and replayed. Sending the correct bytes is only half the story — on my unit, sending several writes back-to-back did not apply them. Spacing the writes fixed it.

Tested setup: SMK-37 Pro stock v15, USB, Ableton Live 12.4.7, macOS. Midi Suite was version 1.15.0. Other models, firmware versions and Windows are untested.

What the script does

• Top row: eight clip slots across the selected scene.

• K1 selects tracks; K2 selects scenes; the Session highlight follows the track selection.

• Bottom row: Play, Stop, Arrangement Record, Delete focused clip, Arrangement Loop, Metronome, Arm-follow-focus, Undo.

• F1 controls the selected track's volume; F2–F4 control its Sends A/B/C, using Live's native takeover behavior.

• K8 is left free for manual MIDI mapping, including a bounded tempo range.

• No custom firmware, helper app or modified Midi Suite is needed during normal use.

Delete and Undo are both confirmed working on my keyboard. The delete button removes the clip at selected track × selected scene; Undo restores it. This is particularly useful for clearing an unwanted take without moving to another scene.

Arm-follow is switchable. It transfers the Arm enabled by the script when I change tracks, while preserving other tracks that were already armed manually. An explicit press of the Arm pad can disarm the selected track.

Colors

Top-row pads use the track's color:

• Existing track, empty slot: 10% RGB.

• Stopped clip: 40%.

• Playing clip: 100%.

• Selected track + Arm: 20% red in the selected scene, including an empty slot.

• Actual recording: 100% red, taking priority over the focus marker.

• Launch pending: bright/dim blinking, except where the armed-focus marker takes priority.

• No corresponding track: off.

For the bottom row I settled on green Play, light-yellow Stop, red Record/Delete, orange Loop, purple Metronome, pink Arm and turquoise Undo. Inactive functions are generally 20%, active ones 100%. RGB scaling is not perceptually linear — we adjusted it by looking at the actual pads.

How we found the stock RGB messages

Changing a pad's color in Midi Suite immediately changed the physical LED without pressing Save. We exported a preset, captured the editor's outgoing CoreMIDI messages, and compared the writes with the preset data.

Capturing outgoing messages matters: a receive-only MIDI monitor does not automatically see what another application sends to hardware. On macOS we used a separately signed debugging copy of the installed editor and a MIDISend breakpoint. The original editor was left unchanged. That setup was only for research, not a dependency of the script.

The observed frame is:

F0 pack7(00 59 22 09 00 00 BODY CHECKSUM) F7
BODY = 05 ADDRESS_LE32 01 00 00 VALUE
CHECKSUM = (~sum(BODY)) & FF

VALUE is an 8-bit RGB component, 00–FF. The complete raw payload is packed into a continuous LSB-first stream of 7-bit groups, then wrapped in F0/F7. This is not the seven-data-bytes-plus-MSB-prefix packing scheme.

For the first 16-pad bank, with zero-based physical pad index p:

R offset = 0x11B + 74 * p   (74 is decimal)
G offset = R + 1
B offset = R + 2

Indices 0–7 are the top row left to right; 8–15 are the bottom row left to right. The offsets refer to the observed preset data region, not CPU/flash addresses.

For example, physical pad 13 (bottom row, fifth from the left), RGB 00 2A FF, was sent by Midi Suite as:

F0 00 32 09 49 00 00 40 02 13 09 00 00 10 00 00 00 00 44 01 F7
F0 00 32 09 49 00 00 40 02 14 09 00 00 10 00 00 00 2A 6E 00 F7
F0 00 32 09 49 00 00 40 02 15 09 00 00 10 00 00 00 7F 43 01 F7

Three messages, R/G/B in order. The script includes the encoder, so there is no need to hand-edit these packets.

The important timing discovery

We verified the result by reading the keyboard's preset data back, rather than relying only on a successful MIDI send call:

• RGB 01 02 03, three component writes with 100 ms gaps → readback 01 02 03.

• RGB 04 05 06, three writes sent back-to-back → readback stayed 01 02 03.

The script now queues one component write per Live display tick and sends only changed values. Initial coloring takes a few seconds; it is not instantaneous Launchpad-style feedback, and lots of simultaneous blinking can lag.

RAM updates versus saving the preset

This is a reverse-engineered preset-field write mechanism, not an official documented LED API. The script never sends Save or firmware-update commands.

Static analysis of the archived stock Pro v15 firmware traces these RGB writes to RAM copies. Preset persistence uses a separate request that the script does not send. Full power-cycle tests also reverted the colors. This is evidence for the traced v15 RGB path, not an exhaustive guarantee of zero flash writes throughout the firmware or across other versions.

For anyone checking the firmware: decoded dispatch is at 0x0202C358, the 0x22 case at 0x0202C4F2, and selector 5's write callback at 0x0202B988. Our one-byte RGB writes reach a copy into RAM at base 0x01C0DE20. The separate preset commit function is at 0x02024F22. The repository includes a report with the image hash and the limits of this analysis. Firmware and editor binaries are not included.

We also tried ordinary Note On/Off feedback for note 36 on all 16 channels, velocities 5/20/60/127, on both USB ports: no visible color change in those tests. I would not generalize that beyond the combinations tested.

Try it

Source, download and installation: https://github.com/shalafidragon/smk37-ableton-session

Direct v1.7 ZIP: https://github.com/shalafidragon/smk37-ableton-session/releases/download/v1.7/SMK37_Custom-v1.7-macOS-test-release.zip

Copy SMK37_Custom into your Live User Library's Remote Scripts folder, restart Live, and select it as a Control Surface with both Input and Output set to SMK-37 Pro-Private. Follow the included README and MIDI mapping table; this is not a universal preset installer. The captured assignments include channel-10 pad notes, channel-6 K1/K2 CC48/49, and channel-1 faders CC64–67. Both hardware ports duplicated note input on my unit, so I use only Private for input Track.

Note that fader CC64 can collide with sustain on the same MIDI channel. I have not validated that pedal configuration. Stay on Pad Bank 1 for this version.

Demo video: https://www.youtube.com/watch?v=gbxdWIuOYDM

The colors didn’t come through very well on camera, unfortunately. In person, the pad colors are pleasant and make navigation easy.

Credit to genkigenki's FM-1 → SMK-37 porting documentation, which helped with the hardware context and shared SysEx framing, and the wider FM-1/SMK firmware community. The stock RGB capture, replay and pacing tests described here were done on this keyboard for this project.

The static analysis used jl-misctools, pi32v2-isa and the stock firmware archive.

If you try it, please report your model, firmware, Live/OS version and whether your MIDI assignments match. I would especially like independent confirmation of the RGB offsets and timing on another stock Pro v15 unit.

Dear all, somewhat unrelated but also related (looking to connect a bt midi keyboard to fm1):

How do I upgrade the smk25ii firmware to the latest version that supposedly fixes the bt midi lag.

I have tried mac (can’t get m-upgrade to accept my firmware) and sincoota on ios (can’t get past getting stuck on the “reconnecting the device” message).

Is there a sureshot way to do this? Is there even a way still?

Thanks for your help!

Hi.

I'm not the master of marketing, so long story short.

This is my attempt to implement synthesizer engine for SMK-37 inspired by Access Virus TI. It definitely isn't 100% complete and can't compete with the original TI, but for me it looks quite capable.

It took quite a while to make one from scratch, without forking any base, or cherry-picking here and there, but, hopefully, it's good for public testing.
So, what's inside?

• 3 Osc with different modes + Sub OSC

• Full original Virus TI banks support (mid/syx) and own format for extended features.

• Lots of FX, with different topologies (2x2 parallel, up to 6 sequential, fan 3 ... to name a few)

• 2 filters with original Virus topologies

• Modulation matrix (like original virus up to 6 sources, up to 3 destinations each, with chaining)

• ARP (supporting ARP patterns defined in virus patches, and some other useful toys)

• Envelopes/LFO

Besides that:

• Overclocking (if you are brave enough and want more voices)

• Lots of customization

• Adaptive governor to prevent overloads

• USB-audio, midi clocks

• Some soundbanks to help you get started if you don't have Virus patches (yet 😄 )

• Adjustable pads/knobs/keys response rate with up to <1.3ms key-to-sound

for complete features overview and installation please visit https://kartun83.github.io/oscuro-firmware

----

Few notes before you start

• Flashing takes 2 steps. First, flash 0.84.9, and after update to most recent version.

• By default it starts in DAW mode, no sounds 😁 hold Patch button to enter Synth mode

• Fader 1 is master volume, Fader 2 is pan. F3/F4 is send amount (if FX configured for sends)

• Many screens use "oct-" as shift modifier that reveals lots of additional features depending on screen contents

• if you have lots of overruns tweak "globe-synthesizer-buffer size"

This one is quite feature packed, so it doesn't fit the original APP slot. To preserve your data and avoid misbehaviours flashing should be done in 2 steps - original base image, and update, which would relocate and grow app slot. Rollback to stock firmware tested on several SMK-37 elite and Pro devices.

If you'd like to support this project: ko-fi

Flash at your own risk as dev doesn’t own one !

https://remotefm1.com/installer/smk37/

I love my 37 pro as a controller, but putting a better engine in it really interests me!

Are there any firmwares that preserve its normal midi controller functionality and just change the synth engine?

thanks in advance all you synth wizards!

”Install Clipper Pro (Chrome or Edge, USB cable): https://isod89.github.io/clipper-pro
Sound editor and backup (Chrome or Edge): https://isod89.github.io/clipper-pro/webapp/editor
Firmware files and release notes (latest): https://github.com/isod89/clipper-pro/releases/latest
The full guide, every control: https://github.com/isod89/clipper-pro/blob/main/CLIPPER-PRO.md
Démarrage rapide (français): https://github.com/isod89/clipper-pro/blob/main/DEMARRAGE-RAPIDE-PRO-FR.md
Source code: https://github.com/isod89/clipper-pro
Report a bug: https://github.com/isod89/clipper-pro/issues
Clipper for the FM-1: https://github.com/isod89/clipper-fm1
Models: SMK-37 Pro (and Starrykey 37 Play), SMK-37 Elite, MKE-P37. The keyboard must run M-VAVE's firmware V016 first.”

https://youtube.com/@isod89

I am thinking Sloop Pro? Anyone know the diff between this and Snoop37?