ASM Hydrasynth Adaptation? Help

[troach242]

I dont want to derail any important development, but has anyone out there created an adaptation for the ASM Hydrasynth? Their librarian is ok at best and allows no searching or visible categories of presets... Plus, I now have 6 other synths in KnobKraft-orm.. so.. Does someone have some time to help? Thank you in advance for your support of this amazing product.

[markusschloesser]

First I thought why not, but having read https://github.com/eclab/edisyn/blob/master/edisyn%2Fsynth%2Fasmhydrasynth%2Finfo%2Fbugs.txt and https://gearspace.com/board/electronic-music-instruments-and-electronic-music-production/1395298-hydrasynth-patch-editors-sysex-spec.html, it's not for me 😊
Otoh edisyn seems to support it. But maybe @christofmuc can help, he did the FS1R adaptation based on the things already done in edisyn

[christofmuc]

Oh, good to see they have done the reverse engineering now! The base64 thing I had discovered as well, as a friend of mine has a hydrasynth we gave it a try. I even sent an email to ASM, but same result.

With the data from edisyn it should be possible to make an adaptation, maybe the sending requires some additional handshake implementation. Given how unusual the synth is implemented, this is a bit bigger effort and will need some help testing with a real device.

[troach242]

I had no idea about the complexity. I just figured it was a relatively new synthesizer and probably has a really robust sysex implementation. I won’t hold my breath, but I’d be glad to test if someone’s brave enough to figure a few things out and create a framework for me.

[markusschloesser]

There's a "save log" button on the upper right corner of the log window

[troach242]

The adaptation loads and connect to my Hydrasynth. When opening "in synth" and selecting "A" the process runs for a long time.. I just stopped it after several minutes at 5% this time and am attaching the log.
HydrasynthLog..log

[troach242]

Thank you again for your awesome support. Amazing!!

[christofmuc]

Thanks! You attached the message log, there is an additional and in this case more important MIDI log. You can access the MIDI log via the Tab next to the Setup tab. There you can see all MIDI messages sent and received, and it has another save log... button. Can you try the download again, it seems it is generally working but it might only be a minor quirk by now?

[troach242]

I am sorry for the delay. I have been really sick this week.
I am attaching the logs from a test run tonight. Hydrasynth is connected. [Midi] [Import patches from synth]
It runs and runs.. I stopped the process at about 5%
Hydrasynth Info.log
Hydrasynth Midi.log

[christofmuc]

No worries, I was pretty sick, too.

I looked at the log, and there are two things that I see:

1. It seems something is echoing all MIDI messages. I.e. each message that is received is immediately sent, which might throw the Hydrasynth off. I don't know if this is a weird bug in Knobkraft or if some other setup causes this (MIDI-Ox in parallel?). I have to definitely check the source code how this could happen. Interestingly, it does not seem to destroy the communication, because the messages progress as planned.

2. The Hydrasynth needs a lot of messages for one bank. It needs 22 MIDI messages for a single patch, and the bank has 128 entries. We have set a general message delay of 200 ms, which means we can only send 5 messages per second. For a full bank, this means it would take 9-10 minutes best case to download. Did you wait that long? We might accelerate later when we know that in general the download works. You could test modifying the value GENERAL_MESSAGE_DELAY_MILLIS in the adaptation file, it is currently set to 200.

[troach242]

I will check to make sure the echo is not caused by my daw or something else connected in parallel.. I will let you know,

[troach242]

I am attaching a database I set up to grab a bank from the Hydrasynth... I let it run all of the way through.
Hydra_20250324_midi..log
Hydrasynth_TR.db3.zip