I’ve been working on controlling my ASM Hydrasynth from an Electra One, and ran into an interesting little problem.
The Hydrasynth has 1,025 internal steps for its filter cutoff parameter, but the values displayed on its screen don’t directly correspond to the MIDI values.
I wanted the Electra One to display exactly the same cutoff value as the Hydrasynth, including the decimal.
So how do you map 1,025 values without manually writing them all down?
MIDI + a camera + AI! ![]()
The idea was pretty simple:
I developed an app to automate the entire process.
The app automatically:
-
Sends MIDI commands to step through all 1,025 cutoff values on the Hydrasynth.
-
My phone record the Hydrasynth display.
-
AI analyzed the footage and read the displayed values.
-
AI generates a complete JSON mapping table.
-
I use that table to display the correct values on the Electra One.
The cutoff parameter uses NRPN 8232, with values ranging from 0 to 8192 in increments of 8, corresponding to the Hydrasynth’s 1,025 internal steps.
After some experimentation, checking values and figuring out the display’s rounding behavior, we finally got the complete mapping working.
The result?
All 1,025 cutoff values mapped, with the Electra One now displaying the same values as the Hydrasynth, including one decimal place.
And the best part? No need to manually enter over a thousand values!
Sometimes the most interesting solutions come from combining technologies that weren’t originally designed to work together.
MIDI, a camera and AI. Who would have thought? ![]()


