Hi,

I'm using AAO for various things in my setup, and it's a God-send. I couldn't find any contact for Lorby, so I don't really know how to make a suggestion, so I figured I'd throw one up here.

For the Saitek/Logitech G Radio Panel:

1) Truncate the 1 of all frequencies on 8.33kHz-spacing. It's always a 1, so I'd rather see "23.455" than "123.45" while not rotating.
2) Hard? Fast rotation of the knob - at least the one scrolling through decimal places - speeds up the seeking. Going from .550 to .000 is a lot of turns.

I think number 1 would be the easiest and biggest improvement for my part. Anything I'm overlooking with my suggestion?

 

2 hours ago, Articate said:

I couldn't find any contact for Lorby

Last page of the user manual

2 hours ago, Articate said:

Going from .550 to .000 is a lot of turns.

You could switch to 25Khz spacing (hold down the swap button for more than half a second) for faster scrolling, then switch back and do the fine tuning?

Or put the Radio Panel into MIDI mode, then all input events go through the AAO button assignments.

Edited March 22, 20233 yr by Lorby_SI

7 minutes ago, Lorby_SI said:

You could switch to 25Khz spacing (hold down the swap button for more than half a second) for faster scrolling, then switch back and do the fine tuning?

Or put the Radio Panel into MIDI mode, then all input events go through the AAO button assignments.

Thanks for the reply! I really love your work. Yeah, I don't know the structure of the events that fire, but I imagine that it would be quiet some work to implement at "user scrolling fast" state based on turn speed, so I didn't necessarily think that would be easy. Is there anything via MIDI that could support that? Otherwise I guess I'd be equally far with MIDI.

 

Do you feel the ability to permanently truncate the 1 to be an undesired feature? Maybe I'm not an experienced enough pilot yet, but I feel I lose a bit of overview without the full frequency shown, I guess for if I have preselected a frequency and want to verify that as I'm called for a frequency change. I just imagine the 1 would always be redundant information. But, I don't want to neither feature creep or bloat your software, so merely a suggestion, and thanks again for the response!

8 minutes ago, Articate said:

Is there anything via MIDI that could support that? Otherwise I guess I'd be equally far with MIDI

The point of the MIDI mode is that AAO handles the input from the SaitekPanles the same way as any other (joystick, MIDI etc.) button. And that includes the fast turn option. But you have to (re-) create all button assignments for the panel manually, in MIDI mode the panel is nothing but a button box with no inbuilt functionality.

11 minutes ago, Articate said:

permanently truncate the 1

I will add a checkbox for that on the Saitek config dialog.

"undesireable" - no. But it will cost me about a 100€ to do it (programming + documentation) and yours was the only request ever about the matter. The fast turn implemented specifically for the radio panel will probably be between 500 and 1000€ in cost (for an equal number of customer requests). So I am reluctant to go there, sorry.

2 minutes ago, Lorby_SI said:

The point of the MIDI mode is that AAO handles the input from the SaitekPanles the same way as any other (joystick, MIDI etc.) button. And that includes the fast turn option. But you have to (re-) create all button assignments for the panel manually, in MIDI mode the panel is nothing but a button box with no inbuilt functionality.

I will add a checkbox for that on the Saitek config dialog.

"undesireable" - no. But it will cost me about a 100€ to do it (programming + documentation) and yours was the only request ever about the matter. The fast turn implemented specifically for the radio panel will probably be between 500 and 1000€ in cost (for an equal number of customer requests). So I am reluctant to go there, sorry.

 

Ah, I haven't fiddled with the MIDI, yet. Seems I have what I'll need there, then! As for the suggestion, I didn't intend to mean that I feel this should be implemented by my suggestion alone. I'm a developer myself, so I respect both the technical debt features could include, and a wish to prevent endless feature-creep. I would be very happy if it was added, of course, but by no means do I intend to posit that my suggestion is simply so good that it has to be implemented. If it's a feature that makes sense and more people want, then it'd be cool, but so far I'm simply happy you took the time to respond!