danardf

Good news, that is what is expected. And good that you have publish the screenshot: there is no "Device" in the Current Software State. That means the preset is not loaded. There is no errors when that happens, that means you have too "old" AZ Controller for the preset.
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
 

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

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.

Sounds good Azlow

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.
 
 

I have not put the link explicitly, I just wrote Test version from Downloads. So that is at least partially my fault.
Also a error dialog when preset can not be loaded because of version has to be implementers... I obviously never hit the problem myself.
 
On my forum no registration required to see/download anything. Only to post (because of spam...).

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

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

Super!
I have re-uploaded fixed test, "XTouch Test 2" (in the same post).
You should see "Green" and "Blue" now. Please check that colors are also set, not only text.
 
So now, when you know that it works with MIDI->USB, can you check USB directly and MIDI over Ethernet? From everything in the Internet, that is not going to work. But costs not a lot to re-check...

Track 1

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

 
Track 2

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

• Same

 
 

For your information
The XCTRL is available only with Eth and Midi Cable.
Not in USB.
Midi Over Ethernet should not work because i can't set any IP port here and if this one is master or slave.
 
If think that if you need to use XCTRL mode only, then for Eth link, get the socket port for this X-touch using IP address.
 
 

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?