lowdowndan

I applied each Loupedeck encoder to each x-plane knob and direction, so two encoders are needed for each knob, which essentially means one Loupedeck page per x-plane 11 dual knob. Not efficient, but it gets the job done. I have set up all of the knobs I need and will start to "fly" the configuration to see if I work it smoothly and in real-time under "IFR". Still, it would be great to have both incrementing and decrementing on the same encoder.

Hi! I am attempting to implement XMidiCtrl (v1.02) with the Loupedeck Live and X-plane 11/12. I started with 11, had some of the problems I outline below, thought that I would do a clean install, could not find 11 the install file online and purchased/uploaded X-plane 12. The problems seemed to persist between versions, but the details I describe below are for V12. I am attempting to control the G1000 (especially the knobs) using the Loupedeck for IFR. I have no problems (except for 1) with commands (buttons). They work great. The exception is the com flip-flop which has odd behavior, it works once, then the second time resets the frequency to 121.5 (the frequency set when the real button is pressed for more than 1 second), and after that, pressing the button on the screen does a flip-flop but about a half second later, the frequencies flip again without my input and the frequency is set to 121.5. I assume this behavior is related to the internal x-plane clock determining if the press is 1 second or not? The knobs (encoders) are the big problem. They change the respective values (outer or inner knob) but no matter which way I turn the knob, the values increase! Makes changing frequencies and entering data into the FMS difficult! Any suggestions? I can live with the com flip-flop being broken, I have to use it sparingly, but the reason I got the Loupedeck was to control the knobs... Thanks! Dan

Thanks for the info. I am using the loupedeck and sure enough, using the debug mode, the knob values are absolute, not relative, and do not trigger the commands. Do you know how to make the appropriate layer file for loupedeck? The layer files for the Behringer are binary files...

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!!!

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

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