I’m creating an independent iOS utility app that will allow us to extend the MIDI implementation of the CQ mixers. This will eventually include controlling absolute FX delay time, SD playback and file navigation, FX in/out, Listen, Phantom power, gain, custom midi channels and other things that are currently missing in the CQ. All midi mappings will be configurable by the user. The app will be free.
I will soon be looking for enthusiastic beta testers. Will you join?
Do you have some hidden NRPN for FX parameter ?
Hidden, not sure what you mean. But yes, Emellan (the app) allows setting FX delay times using NRPN!
Edit: I think you are asking if I discovered some undocumented MIDI implementations in the mixer. If so, the answer is no. Emellan is not communicating with the CQ using MIDI at all.
Ak ok, so you are using TCP frame for non midi parameter.
I thought maybe you had discover somme hidden NRPN 
Correct. So Emellan is providing a much richer MIDI implementation for the CQ by acting a MIDI to TCP bridge.
What confuse me is your screen capture showing « NRPN1 » for the FX time parameter.
It cannot be midi.
I think it confuses you because this is the new functionality my app brings. It IS MIDI because Emellan is creating that new NRPN capability. Here is a sketch:
I am also developing a something to control non midi parameter but I am focusing more on a solution that would work with Stage traxx 3 on ipad.
Currently I am capturing all parameter’s TCP frame with wireshark.
Tedious but encouraging job.
So we are partly doing the same job, from the protocol reversal perspective. My app will of course work with StageTraxx, as that is just another MIDI controller. Are you imagining some other way of integrating with ST?
Don’t know yet but maybe midifire, I need to look at it.
ST3 send midi command to midifire, and midifire translate into TCP frame to the CQ.
How your app will manage the HEX to MS conversion (little endian) for FX time parameters ?
For example, if I want EASYVERB Delay time of 500 ms, do I need to enter 500ms somewhere or just the raw frame (f4 01)?
I’d be impressed if you could pull off the protocol using MidiFire. 
The decimal value of the NRPN is directly translated to milliseconds. I will probably also support creating mappings with a predefined delay time, which can then be triggered with a note on midi message or similar.
Well didn’t even tried yet.
I was just wondering if using an extra app to bridge midi from ST3 to TCP frame was relevant. I am already using 2 app with my Ipad, ST3 and LoopyPro at the same time.
Yes an Ipad could handle a third app running behind. But this is not something I like very much…
And I believe that I could already achieve the same result using Mixing station ( linking MS controls to incoming TS3 midi command)…
Why reinventing the wheel…
So I have deviate from the initial project.
I’ll be using an ESP32 to do the bridge:
-ST3 send midi to ESP32, ESP32 translate to TCPFrame and send them back to the CQ in Wifi.
The advantage is that the ESP32 can also be used to add physical control like a footswitch or a pedal for non midi CQ controls.
Testing are going well and I can up to now control any non midi parameter of the CQ with a button or a potentiometer.
Next step is to make the ESP32 listen or receiving the midi from ST3…
The main thing about my approach that sets it apart from Mixing Station and your ESP32 is that it will be free and that I aim to support everything MixPad can do.
Of course.
And needless to say that I’ll be happy to beta test it of course.
We will for sure gain knowledge from each other.
For example, I am working to set an external tap tempo for TAPDELAY FX.
The average time (ms) of 3 press on a button (ESP32) will be convert in hex figures and sent via wifi to the CQ in a TCPFrame.
This is very precise and working just great.
How would your app proceed ?
Same principle. But translation from NRPN to the TCP message.
NRPN → Emellan → CQ
I will go for a DIY project pedal board, ESP32 based, with some footswitch and some expression pedal input.
I would like it to be collaborative so I’ll create another post soon for it to receive users input and wishes.
Enough for my project here (sorry to have jeopardise you initial post), let’s go back to your amazing app.
