Hello:

I have just completed the first X-Touch Mini and AAO tutorial "How To" video [X-Touch AAO (Axis and Ohs) Lesson 1) and everything worked fine except the actual X-Touch Mini device didn't control anything! So, I went back to the first X-Touch Mini Tutorial (X-Touch Mini Initial Set Up) and discovered that there was a difference in the initial setup of the device. In the AAO tutorial, the Global Channel was set to 10; I have been using (as it came out of the box and with SPAD.neXt) Global Channel 1. I made up a screen shot of each but couldn't paste it into the topic!

So, my question is: Where does AAO software specify the Global Channel - there is no mention of it the manual (at least that my search engine could find)?

I could use it this way but it would mean that if I wanted to go back, every time I did that I would have to reconfigure the X-Touch.

Thanks in advance.

UPDATE: Sorry - it made no difference - so, there is something else not connecting the X-Touch to AAO!

 

 

 

Edited January 24, 20242 yr by The Artful Dodger

The Global Channel is of no consequence in AAO, it doesn't matter what value you set there. Mine is set to channel 1 too, as this is the Behringer default (I often reset the device to factory default)

1 hour ago, The Artful Dodger said:

there is something else not connecting the X-Touch to AAO!

Sorry, no idea. This just works. You did activate the MIDI devices in AAO and you can see it in the dialog? (Menu hardware)

My bet would be on SPAD as the cause. If it is running at the same time, I suppose that nothing will reach AAO (and vice versa, depending on which app is started first?)

In general, one should not run several software apps at the same time that do essentially the same thing. My advice would be to make your decision for one app of this type and stick with it.

Edited January 24, 20242 yr by Lorby_SI

I followed the video exactly. Everything worked on the Desktop FIP but nothing happens with the X-Touch. No, SPAD is not running - that was the decision I made a couple of days ago - I'm moving everything from SPAD to AAO. But, of course, I need to get the X-Touch speaking to AAO. Tomorrow I am going to re-do everything (for the third time) and maybe find the error. One of the problems is that the video was made a year ago and the files have changed! But, I will try again - it must be something I'm doing because I can see that it works in the video. I will report back!

Thanks for your help - I really appreciate your reaching out to me!

13 hours ago, The Artful Dodger said:

I followed the video exactly. Everything worked on the Desktop FIP but nothing happens with the X-Touch.

Sorry, but I have no idea what video you are talking about. Lorby does not make tutorials or anything like that, I only made a handful of advertising videos, many years ago. And what is "the Desktop FIP"?? Are you talking about the X-Touch gauge made by a fellow simmer going by the label of "Funatic"? If that is the case, I'm out. You will have to ask the author directly, he is not affiliated in any way with LWR Inc. and we have had no part in the development of that gauge.

I'd suggest that you test the MIDI as it is supposed to be used - as a bare bones input device in AAO. Enable the MIDI devices in the Hardware menu, then add a new button and press/move something on the X-Touch - it should be picked up on the "Add Button" dialog in AAO. Then you know that it works. You may have to reset the X-Touch device to factory default using the button combo, because I know that Funatics X-Touch gauge changes the operation mode on the device.

Edited January 25, 20242 yr by Lorby_SI

Finally, I figured it out. But first I took AAO out of the system and brought up SPAD because I knew that SPAD recognized various button presses; when I did, the X-Touch worked as always!

So, I had narrowed it down to something in AAO. I decided to completely remove everything from AAO and start over. So I had to look to find something to click that will remove everything from AAO to make it virgin again (I never found that control, by the way, and it might be something to consider in a future update) but while looking I found "MIDI devices enabled" unchecked! I didn't even know about that 'switch'! That was the problem! So, may I make a suggestion: When the X-Touch Template is loaded, it should 'set that switch to on'; of course, it wouldn't force it to stay on so, while debugging, someone might want to disable it but at least start with it on!

Again. thanks for your help.

6 minutes ago, The Artful Dodger said:

I didn't even know about that 'switch'!

Twice in this thread I pointed you at the "Hardware" menu and the MIDI items in there.

Quote

You did activate the MIDI devices in AAO and you can see it in the dialog? (Menu hardware)

Quote

Enable the MIDI devices in the Hardware menu,

 

Edited January 25, 20242 yr by Lorby_SI