Hi

I got an X-Touch Mini to use with MSFS and got it to work, and I'm even managing to get some basic scripting to work.

I decided to get a second X-Touch to expand my options, and then more out of interest, I got one of these devices

summina MIDI Controlle Mixing Console with 43 Buttons 8 Knobs 8 Push Buttons BT Connection Battery/Type-C Power Supply USB MIDI Controller Mixer for Most Electroacoustic Instruments : Amazon.co.uk: Musical Instruments & DJ

to see if it would also work. It does but the knobs need changing from "CC" to "CW" to make them continuous.

Once I added the third device, the X-Touch Minis stopped working, I think because their device IDs had changed when the third device was added. I see in the release notes for v4.5.0 a comment saying "Change: Added sound device mapping to numerical IDs" and wondered if anyone knows how this is implemented. I found an option that seems to move all assignments to a particular device so I wonder if that is it, or is there a way to lock a particular device to an ID to prevent the assigned device from changing?

Andy

 

1 hour ago, Andy TF said:

Change: Added sound device mapping to numerical IDs" and wondered if anyone knows how this is implemented.

This has nothing to do with MIDI. This mapping is about the actual sound hardware used for playing sound files and the text-to-speech features in AAO.

MIDI devices get their IDs from the Windows MIDI subsystem. AAO doesn't have any special mapping logic in that area. The question is why the OS decided to change the IDs. Are you quite certain that this is really the case? Could there be interference from the new device, for example blocking/exclusive access to the MIDI IN channels?

Edited December 13, 20241 yr by Lorby_SI

The IDs do seem to be changing. I can't work out how to post an image from my PC into this forum but with two X-Touch Minis plugged in, AAOs shows MIDI IN with IDs 1 to 3 and MIDI OUT with IDs 4 to 7. With the three controllers plugged in, AAOs shows MIDI IN with IDs 1 to 5 and MIDI OUT with IDs 6 to 11. The MIDI OUT assignments are very much changed (affecting LED commands for example). One of the X-TOUCH MINIs moves from ID 7 to ID 11.

In testing the above, I looked at a plane that I set up yesterday to use the X-Touch. In the "Change Button Assignment" screen, the Device showed as "X-TOUCH MINI # [1]" and the Assigned button/key as "CHN: 11 EVT: 2003 TURN_LEFT". After the testing, the Device had changed to "SMC-MIXER-Bt # [2]" with the assigned button/key unchanged. 

If this had been set up with the SMC device, the assigned button/key would be different - for example "CHN: 1 EVT: 3031 TURN_LEFT".

 

 

 

 

16 minutes ago, Andy TF said:

The IDs do seem to be changing.

No need for screenshots, I understand what you are saying. I just don't know what to do about it. I'm not sure that a mapping, like I do for the sound devices, is even possible.

Please send an email with your proof of purchase to the support email address (address is on the last page of the manual). Please include the AAO Startup log file from C:\Users\...\AppData\Local\LORBY_SI\LorbyAxisAndOhs<simname>