Hello ! 

I bought a Behringer X-Touch Mini and am trying to set up the rotary knobs. 

I'll try to understand AAO programming. How did you manage to set the altitude, speed, vertical speed and direction knobs so that they change the value in both directions?

When you add a button, rotate the desired knob in the desired direction and it will show as either a left or right input in the assignment window for that knob. 

Then assign an event to that input in the same window. Filter for ALT, HDG, SPD etc and choose events for DEC (decrease) or INC (increase). 

It is very intuitive once you get the hang of it. 

14 hours ago, Dazzlercee23 said:

When you add a button, rotate the desired knob in the desired direction and it will show as either a left or right input in the assignment window for that knob. 

Then assign an event to that input in the same window. Filter for ALT, HDG, SPD etc and choose events for DEC (decrease) or INC (increase). 

It is very intuitive once you get the hang of it. 

Thanks! I did as you recommended. But my rotary knob always reduces the height. It doesn't matter if I turn it to the right or to the left. How can I make one knob decrease in height when I twist it to the left and increase in height when I twist it to the right? It should be one and the same de rotary knob. Now I can assign a decrease in height to one rotary knob, and an increase in height to another rotary knob. But using two rotary knobs for one function is not correct.

I think I understand the logic. I need to use only up and only down.

2 hours ago, Flying-Hare said:

How can I make one knob decrease in height when I twist it to the left and increase in height when I twist it to the right? I

Left and right turn are separate input events - you need two button assignments, one for each direction. And the app can only decide about the actual direction when the encoder is turned at least two "clicks", due to the way that MIDI works. When it doubt while assigning the event, turn the encoder left and right a few clicks until the app can discern the direction of the turn that you want to assign. Make sure that the encoder isn't right at the edge of its range, or the app may only register the "click". Again, that is due to how MIDI works (the Musical Instrument Digital Interface, which in essence has nothing at all to do with game controllers - AAO is effectively trying to make sense of musical notes data).

9 minutes ago, Lorby_SI said:

Left and right turn are separate input events - you need two button assignments, one for each direction. And the app can only decide about the actual direction when the encoder is turned at least two "clicks", due to the way that MIDI works. When it doubt while assigning the event, turn the encoder left and right a few clicks until the app can discern the direction of the turn that you want to assign. Make sure that the encoder isn't right at the edge of its range, or the app may only register the "click". Again, that is due to how MIDI works (the Musical Instrument Digital Interface, which in essence has nothing at all to do with game controllers - AAO is effectively trying to make sense of musical notes data).

Thanks for the accurate information!   With this, I figured it out. Now I'm trying to get the autopilot on/off button to work correctly. That is, the first press of the button turned on the autopilot, and the second press of the button turned off the autopilot.

That would be a toggle event?

12 minutes ago, Flying-Hare said:

Thanks for the accurate information!   With this, I figured it out. Now I'm trying to get the autopilot on/off button to work correctly. That is, the first press of the button turned on the autopilot, and the second press of the button turned off the autopilot.

Are you using MSFS? If you do, please be aware that with many aircraft (especially addons) the default SDK events won't work. You will have to resort to LVars, HVars and BVars eventually. A couple of the common ones are in the lists of AAO already, but you will need additional resources.

Best course of action is to download script collections from the authors on flightsim dot to. There are talented simmers who already made complete profiles for the Behringer for specific aircraft too. At the very least, you can look for any AAO profile that includes scripts, even when they were made for different controllers (like the StreamDeck). Disregard the assets that you don't need, you only want the scripts files to import into AAO. Scripts are hardware agnostic and they can be assigned to buttons the same way you assign events - they will appear in the same tree list.

Edited January 1, 20233 yr by Lorby_SI

 

Thanks for your reply! I am using MSFS.

I have downloaded the PMDG 700 template and am learning the settings.

So far, I can not set the spoiler to the slider of my device.

In the PMDG script, they somehow overcame the rotation limitation of the MIDI controllers spinning by the handle. I tried to apply this PMDG script for Honda-Jet, but it didn't work for me.

 

Edited January 1, 20233 yr by Flying-Hare

3 hours ago, Flying-Hare said:

I tried to apply this PMDG script for Honda-Jet,

In 99,5% of all cases this will not work. You cannot apply control methods from one aircraft to the next. Especially with MSFS aircraft, there are no standards anymore, every developer does things differently, probably because they can. For us users that means that almost every single item must be figured out individually for each aircraft out there.

Quote

In the PMDG script, they somehow overcame the rotation limitation of the MIDI controllers spinning by the handle.

I'*m sorry, but I have no idea what that means.

Edited January 1, 20233 yr by Lorby_SI

3 hours ago, Flying-Hare said:

So far, I can not set the spoiler to the slider of my device.

That should be an Axis Assignment of the slider to the AXIS_SPOILER_SET Event with Axis Min -16383 and Axis Max 16383.

42 minutes ago, Lorby_SI said:

In the PMDG script, they somehow overcame the rotation limitation of the MIDI controllers spinning by the handle.

I meant that the MIDI controller's rotary knobs have 172 clicks from the left end position to the right end. And in the PMDG script, the heading or altitude knob can be rotated continuously in a circle.

 

 

I found an interesting tutorial video here:

 

 

18 minutes ago, Flying-Hare said:

I meant that the MIDI controller's rotary knobs have 172 clicks from the left end position to the right end. And in the PMDG script, the heading or altitude knob can be rotated continuously in a circle.

In AAO the Behringer Rotary Encoders are treated as "endless" anyway, when used in Button Assignments. That is why you only see "right turn" and "left turn". As Axis they are limited to their range of course, but not here.

Any "tricks" in scripts should be unnecessary. On my computer, I can turn the Behringer encoders round and round, and they always do what they are supposed to (if assigned correctly)

There are other MIDI devices where this is not the case and where the assignments require more work.

Edited January 1, 20233 yr by Lorby_SI

20 minutes ago, Flying-Hare said:

I found an interesting tutorial video here:

This tutorial is for a third party addon to AxisAndOhs...

23 minutes ago, Lorby_SI said:

In AAO the Behringer Rotary Encoders are treated as "endless" anyway, when used in Button Assignments. That is why you only see "right turn" and "left turn". As Axis they are limited to their range of course, but not here.

Any "tricks" in scripts should be unnecessary. On my computer, I can turn the Behringer encoders round and round, and they always do what they are supposed to (if assigned correctly)

There are other MIDI devices where this is not the case and where the assignments require more work.

I finally understood! The knobs should be programmed as buttons. Now everything works out for me. Thanks for your help!