Loupedeck profile dissapearing

[lowdowndan]

I have the Loupedeck live and X-plane 11 and downloaded the profile xp_a300310_midi.lp5 for the airbus 300/310, purchased the inbuilds Airbus 310 and installed the .toml file A310_XMidiCtrl.toml in the aircraft directory (actually all 3 variants).  The loupedeck shows the profile with the buttons, knobs, etc.  X-plane 11 XMidiCtrl plugin pulldown shows that the loupedeck is available and that the airplane profiles is loaded without errors.

As soon as I select the x-plane window, the loupedeck shows what seems to be a default initial profile. Once I select any window outside of x-plane 11, the airbus profile appears again.  When I press a button, the debug log shows that commands are coming from the loupedeck.  

For example: Inbound message from device 'Behringer X-touch Mini' on port '0' :: Status = '176', Data 1 = '5', Data 2 = '119'.

I also edited the device name in the .toml file to 'Loupedeck Live' and it didn't change things...

Any idea of what could be wrong?

Thanks,

Dan  

[Pils]

I doubt the x-touch and the loupedeck are sending the same midi data, you’d have to customise the toml.

[lowdowndan]

Thanks Pils, that would make sense. I will try and understand the differences between the Loupedeck and the Behringer...

[lowdowndan]

O.M.G.. I got it to work!  The profile example had different cc values than the .toml, so I edited a few to match the .toml file and lo and behold, X-plane 11 responded!

One quirk, the cc set function in loupdeck live appears to send two values, you can't send just one.  The first is in a dropdown list, the second is typed by hand.  I assume that the first, having labels, are intended to make selection easier because the labels would guide that value, presumably specific categories of actions, while the second selects values within that action. In the case of CMidiCtrl, the commands appear to use only one of these values, so I selected 127 as the second value and x-plane seems to respond fine. It receives both values but ignores the second.  

Seem right?

Next step will be to modify the spreadsheet that shows the B737 commands and select the cc values, types, and commands it for what I want to do with the Loupedeck, which is to control the knobs of the G1000. I have the Honeycomb yoke and throttle quadrants that work fine for most things, including the autopilot, but controlling the G1000 knobs with head tracking on and in real time (e.g. flying IFR with PilotEdge) is too much of a pain, as is changing comm frequencies. I have been dreaming of control knobs I can program and it seems that I can finally get my way!!!