chuckebaby
just figured I would throw in my offer if needed.
Not a touch, I use a Mackie MCU (older version) not sure if I can be any help, but if I can let me know.

Thank you for the offer, but original Mackie MCU does not have color display. Nor it speak Behringer protocol.
 
When we advance to the planing what to do with X-Touch (after we test the protocol), you can help with possible behavior changes. Since we are going to significantly modify the plugin or preset, we can also change something in logic as well.

azslow3
.....
In the right lower corner, that should be: 0.5r4b356.
In preparation section, I have mentioned that you need Test version of AZ Controller: http://www.azslow.com/index.php?action=downloads;sa=view;down=28

Sorry, but i never saw the link to download this version in your thread. :(
Maybe should i need to be registered in your forum to see the links.
I'll make some test anyway with this new AZ controler.
 
 

Ok no problem.
 
Now i can see, in the Track 1 Blue|Blue
 
 

Track 1

• TOP
  • Back ground : black
  • Text : Green
• Bottom
  • Same

 
Track 2

• TOP
  • Back ground : black
  • Text : Blue
• Bottom

• Same

 
 

To finish with colors: I uploaded "XTouch Test 3".
Most important is the difference between "White" and "White2". The RE documentation is unclear what it should be. Can you describe what you see (I mean the difference)?
 
For Eth link. I guess people will be more excited in case we can provide network solution. MIDI->USB/Interface has quite some disadvantages. But for that to happened, we need the "protocol" to use.
a) who connects? does XTouch tries to contact "the server" or it should be contacted first?
b) is it TCP or UDP?
c) how they really send the information? May be we can correlate what is going on with MIDI->USB with the binary content of the network traffic. Do you have an experience in network sniffing?
May be you have some links to some discussions?

For the colors, may be we test later. RE documents specify different values for the same color. So I was thinking may be that are grades of it...
 
For preset. I will start with Mackie preset for AZ Controller, way more simple to change. I will map Xtrl messages so we can use normal functions. That can take some time. It can take much less if we do this online or you do this, since you can just touch/press/move/turn some control and press "Assign" while I have to generate all that messages manually... Than I will add colors to the preset.
 
For network we probably can discuss directly on Skype, when we both have time for that...

danardf
Using this console under XCTRL is not useful i guess.

If colors are only possible with Xctrl (and it looks so), there there is no choice.
Functionality will be the same, so till we find solution with direct networking, that is
USB/MIDI over ethernet without colors vs MIDI->USB cable with colors.
I guess that can be useful, but inconvenient.
 
But lets try to understand Xctrl network protocol first, that will see.

Since our test went offline, I want to inform other about the progress.
 
Xctl (the protocol used between X-Touch and XAir mixers, the only known way to set colors on X-Touch display) is understood. RE documentation mentioned before (and not coming from us) describe the protocol when used throw MIDI cables.
 
We have checked that the same protocol is used when devices are communicating throw the network. Communication is technically done with UDP packets on port 10111. These packets consist of binary MIDI data "as is". No headers or separators. One UDP packet can transmit arbitrary (probably there is some limit) number of MIDI messagers, including SysEx messages. X-Touch understand MIDI running status and XAir actively use that.
 
I am going to support the communication in AZ Controller and then create X-Touch preset with color strips.

azslow3
Since our test went offline, I want to inform other about the progress.
 
Xctl (the protocol used between X-Touch and XAir mixers, the only known way to set colors on X-Touch display) is understood. RE documentation mentioned before (and not coming from us) describe the protocol when used throw MIDI cables.
 
We have checked that the same protocol is used when devices are communicating throw the network. Communication is technically done with UDP packets on port 10111. These packets consist of binary MIDI data "as is". No headers or separators. One UDP packet can transmit arbitrary (probably there is some limit) number of MIDI messagers, including SysEx messages. X-Touch understand MIDI running status and XAir actively use that.
 
I am going to support the communication in AZ Controller and then create X-Touch preset with color strips.

Thank you to share your progress.
 
It sounds great man !

Sorry, the plans was changed at the end of the last year... I was about to finish my controller emu (since I do not have them all) and then add XCtl. Went to REAPER (Sonar->REAPER converter) and in slow progress with REAPER controller instead.