Mapping 1,000+ Hydrasynth cutoff values using my brain, MIDI, a camera and AI 😁

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! :grin:

The idea was pretty simple:

I developed an app to automate the entire process.

The app automatically:

  1. Sends MIDI commands to step through all 1,025 cutoff values on the Hydrasynth.

  2. My phone record the Hydrasynth display.

  3. AI analyzed the footage and read the displayed values.

  4. AI generates a complete JSON mapping table.

  5. 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? :grin:

4 Likes

Your perseverance is examplary, sir!)

1 Like

That’s pretty cool, but did you try contacting the manufacturer first? sometimes they’re very helpful with stuff like that

1 Like

First of all, I apologize for the length of this post, but I believe the truth needs to be told. Some things simply cannot be explained in a few sentences, especially when customers are treated this way.

ASM – Great Synthesizers, Terrible Documentation, and Apparently No Tolerance for Criticism

I genuinely admire the Hydrasynth. It’s a fantastic instrument, designed by engineers who clearly know what they’re doing.

Unfortunately, I can’t say the same about ASM’s technical documentation or their attitude towards customers who ask for it.

Trying to get proper information about MIDI implementation, SysEx messages, parameter structures, and advanced integration is an exercise in frustration. Information that should be readily available is either missing, incomplete, or unnecessarily difficult to obtain.

Why on earth should customers and independent developers have to spend countless hours reverse-engineering a commercial product just to understand how it communicates?

But here’s where things get truly ridiculous.

I actually raised these issues directly with ASM on their own official forum. And how did that discussion end? I GOT BLOCKED.

Yes, you read that correctly.

Instead of having a constructive discussion about improving technical documentation, the conversation ended with me being blocked from their forum.

What an extraordinary way to treat someone who is genuinely interested in getting more out of their product!

I’m not asking ASM to redesign the Hydrasynth, give away proprietary source code, or perform miracles. I’m asking for proper technical documentation so that musicians and developers can integrate the instrument into their own systems.

Is that really such an unreasonable request?

Apparently, asking difficult questions about documentation is more troublesome than addressing the documentation itself.

Here’s a suggestion, ASM: Instead of blocking customers who raise legitimate concerns, try listening to them.

Your engineers have created an outstanding synthesizer. It’s a shame that the documentation and my experience with your customer communication fall so far below the standard of the instrument itself.

A company should welcome technically curious customers. These are the people who develop tools, build integrations, share knowledge, and help extend the useful life of your products.

Alienating them is not just disappointing. It’s incredibly shortsighted.

Great hardware. Poor technical documentation. And in my experience, an absolutely appalling way of handling criticism.

ASM, you can block a customer from your forum, but that doesn’t make the underlying problem disappear.

Perhaps it’s time to spend less effort silencing criticism and more effort providing the technical documentation your customers deserve.

And now we have the Leviasynth. A technological miracle – but where is the documentation?

4 Likes

@Electrolove , no worries: in a couple of month I am sure someone will vibe-code a couple of dozens of new FWs for ASM synths, and the AI will also create detailed manuals along the way!)

Just kidding, but this type of behavior is in my view totally unacceptable for any manufacturer, let alone for the manufacturer of inspiration and creativity aimed products, which synth are by nature)

2 Likes

Had no idea they were that bad.

1 Like

Someone posted having a similar experience with ASM a while back on gs

1 Like