Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Problem with Midi Out

Featured Replies

I recently ran into Trouble with my PC, so badly, that I had to do a clean Windows 11 Installation, and of course I had to setup MSFS, AAO and everything else again. This way I unintentionally made an Update of AAO to the latest Version. Due to the new Installation my Midi Device IDs shown in AAO have changed, but that shouldn't be a Problem, I quickly changed all Device IDs in my Scripts and Templates. While all my Templates are now working again, I can't get Midi-Out to work for my X-Touch Mini. The X-Touch Mini is shown with Midi Out Device ID 5 in AAO, it's set to standard Mode, and global Midi-Channel is set to 1 (so everything on Default). But there is no way to light up any LEDs on the Device.

I created what I think is the simplest possible testing Script, without any Condition like this, and assigned it as an automatic Aircraft script to the Default Cessna:

1 (>Midi:5:NoteOn:1:8)

No LED lights up when this Script runs.

Could it be that maybe somethings broken in AAO concerning Midi-Out with the latest Version of AAO?

Edited by theflyguy

  • Commercial Member
1 hour ago, theflyguy said:

Due to the new Installation my Midi Device IDs shown in AAO have changed,

The IDs are set by Windows, not AAO. It is the complete reinstall of Windows that caused this. But you may be able to change those MIDI - IDs, I don't think that there is a "hardware reason" for them.
Did you wipe your system or did you reinstall Windows "in place" (=with the old version still being present)? Maybe it thinks that these are new devices now, and shifted the IDs because of that?

1 hour ago, theflyguy said:

Could it be that maybe somethings broken in AAO concerning Midi-Out with the latest Version of AAO?

Working fine here:
1·(>MIDI:3:NoteOn:1:8)

1. Make sure that your X-Touch is not set to "MC MODE". If that is the case, the little "MC MODE" LED, that is inset on the top right of the device, is on. 
2. >MIDI must be written in capital letters. "(>Midi" is incorrect syntax

If your device is set to MC mode, execute this script to go back to "normal mode":
0·(>MIDI:midioutid:CC:1:127)

Edited by Lorby_SI

LORBY-SI

  • Author
1 hour ago, Lorby_SI said:

2. >MIDI must be written in capital letters. "(>Midi" is incorrect syntax

THAT! I did a search & Replace in my IDE when changing the Device IDs. Obviously I did it right with my Templates, but wrong with the LED Scripts.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.