Hi all, thanks for the suggestions. It’s not currently possible to input external MIDI messages to the apps via Class Compliant devices, but I have logged and will put it forward to the development team in the next dev meeting 🙂
Thanks.
Harry.
Just another suggestion following your comments – not sure on the coding requirements to implement the full protocol for inputing external MIDI messages, but maybe a restricted set of allowable MIDI commands which would cover typical footswitch type operations would help to limit the time to code, debug, etc.
Sorry to hijack an existing thread but I think the people subscribed to this post are likely the best ones to assist me.
I have started on a windows app but am really stuck getting a connection to the desk. I started by working through the footswitch code posted earlier; then I figured out how the windows TCP class works (I can get messages to send from one computer to another and back) but I can not figure out how to communicate with the desk. I’ve spent hours googling and trialling with the tcplistener and tcpclient classes and am going in circles. I also asked A&H for pointers but they couldn’t help. So I would really appreciate any assistance as I’m sure I’m just missing something really basic.
Thanks Owai, appreciate the response! I’ll look through your code tonight and see if I can port over to windows environment. Th db link to your pictures no longer works – could you upload again so I can see what you have done?
So, if I buy this little box, than I can connect QU’s ethernet with ethernet IN on that box, and then connect box with MIDI controller and than mute my FX with pedal – is that possible? In that case, can I also connect ethernet OUT on box with my router so I still can have access to Qu-PAD?
