Connection to OpenSongApp with a WIDi Jack

Hi im seeking help to control the OpenSongApp, in my tablet, with my MC6 Pro, as with my bluetooth Donner pedal. I did tried to use note on for c3 without succes. Any recommedation on this matters?

The following is what OpenSongApp require for connections:

Receiving MIDI messages

OpenSongApp will only listen for MIDI notes (sent using Note on/off) from another device - this is used to listen for MIDI foot pedals. The actions you can assign for different notes received are set on the foot pedal settings page.

Scroll to the pedal 1 and click on the button (by default it will be set to KEYCODE_DPAD_LEFT and MIDI note C3). It will then say ‘Waiting for button’. Tap the desired button on your foot pedal and it will be assigned as pedal 1. Choose a short press/tap action and an additional long press action. Repeat this process for each button on your foot pedal.

If the WIDI Jack is connected to the MC6 PRO 3.5mm MIDI ports, just check the that the physical switch on the WIDI Jack is set to Type A. By default, it is set to Type B.

Hi James!! Yes it is connected to the 3.5mm midi port, and it is in type A! I already changed it. I just try with a press action for note on to C3, velocity 0, opensongapp midi channel 8, but it did not work.

Hi James. The configuration to control the software OpenSongApp with the morningstar is finish. Now I am in the move to resolve why the midi command to control the beatbuddy from the app on my tablet its not working. Is there something special that should be configured to allow the communication from the tablet on the 3.5mm port to the beatbuddy on th dim5 port? Is it posible to monitor the communication from the tablet to the beatbuddy through the morningstar?

Assuming that the WIDI Jack is receiving the MIDI messages from your App, then what you’re trying to do is to pass the incoming MIDI on the 3.5mm MIDI INPUT port out to the DIN5 MIDI OUTPUT port?

If so, you just need to route it as such:

Thanks James, i really appreciate your help and advice!!

Your correct, and thats what i did!! So my problem should be that the WIDI is not receiving, or the beatbuddy is not responding, and theres where my second question is relevant… Is it possible to look, or monitor to see wheres the problem so i can fix it? Any advice to dealt with it? Whats monitor in the editor? Just the actions from the morningstar, as press, releases,…? It was posible to get to the app from the morningstar, but not to get to the morningstar from the app… Im in a one way communication… Maybe i can try with another android app…

In the Editor, select “MIDI monitor”. Have a read of that section in Editor User Guide (Version 1.3.6) - it will show you what MC is sending when you press footswitches

Yes, thank you. But my problem comes when a signal is coming to the morningstar from a tablet app. How do i know if it is really entering the controller from 3.5mm port to get through to a beatbuddy in dim5? Is it posible to monitor that, or just whats pressed on morningstar footswitches? Is there another method to check or monitor that?

You can route the incoming messages from the 3.5MM MIDI IN port to the USB port and then check the MIDI Monitor:

Hi James.

I followed your advice and the following appeared in the midi monitor:

MIDI Data

Timestamp Midi Type Data 1 Data 2 Channel
2025/02/16 18:58:18:888 SysEx 127 127 1
2025/02/16 18:58:18:887 Control Change 107 73 1
2025/02/16 18:58:18:887 Control Change 106 0 1
2025/02/16 18:58:18:886 Program Change 2 1
2025/02/16 18:58:18:184 Control Change 32 13 1
2025/02/16 18:58:18:153 Control Change 0 0 1

The visual result was; seeing my morningstar switching from current (in use) bank to empty bank 3, w empty preset.

After switching back the 3.5MM MIDI In - Thru To DIN5

The beatbuddy respond selecting the corresponding song, but the behavior of switching the morningstar from current (in use) bank to empty bank 3, w empty preset remain. This test was for an specific song (song=No longer slaves/Drum kit=Worship Kit).

MIDI Data
Timestamp Midi Type Data 1 Data 2 Channel
2025/02/16 19:13:12:975 SysEx 127 127 1
2025/02/16 19:13:12:975 Control Change 107 73 1
2025/02/16 19:13:12:974 Control Change 106 0 1
2025/02/16 19:13:12:958 Program Change 2 1
2025/02/16 19:13:12:249 Control Change 32 12 1
2025/02/16 19:13:12:186 Control Change 0 0 1

This test was for an specific song (song=Majesteit/Drum kit=Standard Pro with Bass).

2025/02/16 19:18:58:444 SysEx 127 127 1
2025/02/16 19:18:58:443 Control Change 107 73 1
2025/02/16 19:18:58:442 Control Change 106 0 1
2025/02/16 19:18:58:423 Program Change 20 1
2025/02/16 19:18:57:499 Control Change 32 59 1
2025/02/16 19:18:57:456 Control Change 0 0 1

This test was for an specific song (song=strumtest2/Drum kit=cajon with bass).

In this ocassion the morningstar switch to bank 21, preset w.

Can you help me to understand whats happening?

How is the morningstar responding (reacting) to a command thats supposed to go through to another port. First to usb, then to dim5, but the morningstar is responding with a bank change?

Hi,
if you look at the data you’ll find

If the MC is set to Midi channel 1 this will cause it to jump to bank 21 !

It’s possible to change the MC’s Midi channel in ‘controler settings / general’