The furthest I've gotten thus far is producing clicks at different amplitudes. A first click for pitch (low amp=low note/high amp=high note), a second click for velocity (higher amp=higher velocity) and a negative click for note off. I'm guessing this might be the way to get it done, but so far it's not so reliable and wonky.

I'm going to keep working on this strategy, but I'm still curious if someone solved this already and if I'm on the right track or if there's a more effective way.

By the way, most of my processing is done in gen~ to get sample accurate measurements.

Hope someone has some insight :)

Cheers!

What is the problem with the midi port on the stage box ? Is it dependant on X32 midi settings , which could be causing the troubles ?

Midi is a simple square wave pulse sent at 38400 baud, I guess I/O capacitors on both stage box and console would degrade the midi signal. I mean in case you want to use audio I/O to send midi

The midi port on the stage box works, but with a lot of latency, shifty rates and it only receives data on the first 3 midi channels so i'm guessing they only designed it to work as a remote for the mixer.

Indeed I want to try to use an audio I/O to send midi. Just pitch and velocity data and if possible polyphonic. I'm guessing it takes a bit of creative coding, but I was hoping someone already tackled a similar puzzle before I'm trying to reinvent the wheel.

http://www.96khz.org/oldpages/midiasaudio.htm

Found this, but still a bit in the dark as to what it means. Still quite a noob on a lot of subjects :P

Thanks for the reply, it's much appreciated :)

midi -> rtpmidi interface -> mix with the audio in a network switch -> only one ethernet cable -> unmix with network router -> X32 / midi? but complicated, >USD 500 for gear, and it might not even work to mix things since rtp midi is not an IP protocol.

You might be better off using long midi cable. Maybe at the end a little current booster, but with a good cable it should not be necessary. If someone can make din to xlr connectors for you, you can test that using standard balanced mic cables. I would solder pins 2 & 3 together, and use pin 1 (shield) as 5v. That would cause least current loss. ------- Midi inputs are run through optocoupler. Trouble using long cables is that current might drop because of cable resistance, and optocoupler would not trigger. On sender side, 5v and data signal are connected via 220 ohm resistors, signal is high when quiet, low on pulses. input side also 220 ohm inserted at opto input. that limits the current to +- 11 mA without cable taken into calculation. Depending on opto used, that might drop too low with long cable and thin wire. ------ It would be a simple thing to measure the cable resistance, add that to 440 ohm and calculate the loss.

I must add a word of warning : you should not connect midi connector to XLR input of any stage box or mixer. If someone turns Phantom Power On, it would distroy midi out circuit at least, and maybe much more in the keyboard.

As Roman proposes, I do use a iConnectivity interface with RTP on stage connected to a Mac over an ethernet cable. The ethernet connection is shared with a Dante setup and it seems to work reliably so far. So there is only one cat5e cable between the stage and the sound booth. Dante is supposed to work on a regular ethernet network, but I don't know for the X32.