How do I connect MacBook Virtual Pipe Organ to Teensy

How do I configure the organ to connect to MidiFire? The organ Input and Output Midi Ports only show Network Session 1 and Teensy Midi, which I check both. What I observe using Midi Monitor on my MacBook is that the organ responds to message From Session 1 (inputs from my iPad) and outputs responses To Session 1, including the specific 39 byte SysEx I want to send to Teensy. My MidiFire Sources and Destinations are Network Session1, MidiFire, and Teensy MIDI. Nothing indicates the organ specifically.

I have 3 configurations in my scene: MidiFire to Teensy; Network Session 1 to Teensy; and Network Session 1 to MidiFire. All have Event Monitors. None respond to the organ generating midi messages to Network Session 1 as observed in Midi Monitor. Network Session 1 outputs to both Teensy and MidiFire when the iPad triggers the same button on the organ (but not MidiFire to Teensy configuration). But the 39 Byte SysEx and any other organ output is not routed to MidFire or Teensy.

Loopback did not work. I am getting frustrated. I monitor midi messages using Midi Monitor and at Teensy input using Teensy's Serial Monitor. I am able to receive midi at Teensy generated by my iPad and a keyboard, but not the organ. MidiFire responds to output from the iPad and the keyboard, but not the organ.

I configure the organ Midi Output Ports to Session 1, the Keyboard, and Teensy Midi. The only output from the organ observed on Midi Monitor is to Session 1, which is not received by MidiFire.

So while I successfully route midi from my iPad to Teensy using MidiFire, I can't route from the organ. It's as if the organ ignores any output port selection except Session 1.

Is this something you can help me with?

Even when I activate Loopback, it only works with my iPad. No response when I select the equivalent button from the organ. I try to activate Teensy from the organ Midi Port Output, nothing appears at the Teensy input nor at Midi Monitor. I was able to set the organ to use the test button and did receive the message in Teensy and Midi Monitor, but not in MidiFire nor pressing the button outside of test. Strange behavior. I am attaching a screenshot. The leftmost window is the readout from Teensy. One Test: send 'on' from the organ Setup created 2 Teensy messages. The window to the upper right is Midi Monitor, which does show 2 messages To Teensy Midi. Lower right is my Midi Network Setup. For Session 1 I have the iPad (2) as a Participant at Port 5006. I tried all sorts of combinations.


Maybe there is a way to do what I want in the iPad? I have the Stream Byter Plugin to MidiDesigner Pro but have never used it. I know the 39 byte SysEx message is appearing at the MDP input. Can I use the Plugin to route the SysEx to one or more buttons or pickers in MDP and all other midi messages are received by all other MDP buttons that are set to Midi Receive? Alternately, detect and output the 39 byte message and route it to teensy for decoding the individual bytes?

There are 2 functions I am trying to implement with the Teensy (probably need 2 Teensy's).

1. Use external pushbuttons to generate midi messages that can be received by the organ. I have this working using MidFire connecting Teensy to Network Session 1.
2. Decode bytes 20, 21, and 22 of the 39 byte SysEx message from the organ. I modified a Teensy Sketch that sends the data to a Display and initially added print statements to monitor the input. That part works fine for messages from the iPad, but not from the organ.

Any ideas?

The screenshot shows the results of my clicking the Test send on with <all enabled ports> selected. I show the other choices I could select.

What I tried is to activate the IAC Driver in Midi Studio and set IAC as an Output in the organ. I could set it in MidiFire and it responded and routed messages to Teensy. It routes CC messages and 5 byte SysEx messages. But IAC does not route the 39 byte SysEx message, which is routed only to Session 1. Is there a way to trigger Session 1 to output to Teensy in MidiFire?

In the screenshot, only IAC responds and the connection to Teensy functions properly. The StreamByter only allows SysEx messages to pass through.


I tried Teensy selected in the organ Output Ports. But again, I can only send SysEx to Teensy using the test function. Using the normal buttons only outputs to Session 1.

To use the StreamByter plugin, I would need to detect the 39 byte message and output it to Teensy. Is that possible?

I feel extremely embarrased about wasting so much time. I do want to thank you very, very much. There are 2 LCD Panel selections under 2 different menus in HW. I selected the wrong one all along, which is why the test worked but the button on the organ that generates the SysEx I want to process in Teensy did not. But not all was lost. Loopback still doesn't work but IAC Driver does! I am able to select output of the message to IAC Driver and MidiFire responds as desired.

In MidiFire I route IAC Driver Bus 1 to an Event Monitor to Stream Byter to Event Monitor to Teensy MIDI. 

But now I have another problem. The Stream Byter using the following code filters CC messages and passes the 5 Byte SysEx to Teensy but not the 39 Byte.
    # block non-sysex
    if M0 != F0
        block
    end

Below is the Midi Monitor readings for the 5 byte and 39 byte midi messages.


The 5 Byte starts with F0 70 and the 39 Byte begins with F0 7D. I define the 70 and can set it to another other value. 7D comes from the organ and I can't change it. So I think the best option is to pass only the F0 7D and block all others.

Again, Thanks
Don