Using the Axoloti as a 1-in, 1-out MIDI Interface

#1

Just wondering if it's possible to use the Axoloti's DIN MIDI ports to have the computer communicate with external hardware via USB.

If possible, I could add two extra DIN ports to the iConnectAudio4+. Any ideas?

#2

It should be possible. Someone in another thread was talking about forwarding MIDI data from the USB device port to the host port with a script, and that script could probably be modified to pass data from the USB device port to and from the MIDI DIN ports. I haven't been able to get it to work yet though.

#3

Can just patch it up I think? MIDI input to MIDI output object.

#4

I read in the other thread that doing it that way causes latency issues or something. I don't know the specifics but I'm pretty sure that either Johannes or TechnoBear would know.

#5

Hmm, I wonder if this could be used for MIDI Merge. I have a controller going into MIDI-in and a computer forwarding MIDI in through the USB. Merge both and send them out.

#6

No, using a midi/in/script is the only way to get it right.

I don't expect Axoloti to contribute significant latency.

There is a risk of overflowing buffers when merging dense traffic into DIN midi. Axoloti does not do midi thinning automatically.

related thread: https://sebiik.github.io/community.axoloti.com.backup/t/axoloti-as-a-midi-usb-host/290

#7

Right, thanks everyone. Reading the other thread as well, I think this could be another awesome use scenario for the Axo. But I would need full MIDI support (inc. Sysex) to properly "talk" to the hardware, so here's hoping that someone will take the time to script it :smile:

Cheers!

#8

Sysex messages are ignored by by the firmware, can't be fixed with a simple "script", and I have no short-term plans to develop support for sysex, sorry.

#9

Noted. Getting notes and CCs through is quite good, and will work for many of the synths. I'll try the script in my setup, thanks for pointing it out.

#10

Just a small 'note' , you can send sysex via the api (currently USB host only), just not currently receive ... receive could be added easily enough ( it would be low level)
However these is no 'object' support , and it would be tricky to add a generic object

Frankly, the best way to deal with this low level sysex support is in a dedicated object (axo) for each 'controller' , it's more efficient and also can deal with quirks of each controller - which means it's easier for an 'end user' to use.
... This is exactly what I was doing with the ableton push.