Connect MIDI Device to Eventide Device: How to?

[JCR]

Finally the Bluetooth over MIDI option has arrived in H9 control. But there is no way I can get this to work in the Windows H9 Control v1.6.2 and iOS version v1.6.1.

I want on my iPad the forScore v8.0.1 app to set presets on my H9 over bluetooth. When the iPad is connected with a MIDI cable into the H9 everything works fine.

1. I have enabled "MIDI Over Bluetooth" in MIDI settings

2. I have connected "Connect MIDI Device to Eventide Device" to Network Session 1, MIDI Bride MIDI Port, MIDI Vision MIDI Port and a MIDI Cable into the iPad.

MIDI Vision, when running, captures the PC event, but it never gets to the H9.

Whatever I try, I can't get this to work. How is this suppose to work? My iPad is running iOS 8.0.2.

Please help…

[gkellum]

Are you setting things up in H9 Control, and then exiting H9 Control and opening forScore?  When you close H9 Control unlike most iOS apps, it exits;  it doesn't run in background mode.  So, I'm wondering if this is the problem that you're running into… 

[JCR]

No, I leave H9 control open. I open H9 Control and wait for it to connect to H9 by Bluetooth and leave it as is. I switch to forScore and let it do its thing by showing me the scores and transmit midi messages. But every time I switch back to H9 Control it is showing the H9 is connected message which has to be accepted. Although the two bluetooth leds are lit on the H9 al the time is there a change the H9 Control app looses the connection to my H9 when focus is set to forScore app?

But I can't get it to work on the Windows version of H9 Control either. It connects to my H9 by bluettooth without problems, but whatever midi device I Select I can't get the H9 controlled, just like the iOS app.

[gkellum]

JCR:

Every time I switch back to H9 Control it is showing the H9 is connected message which has to be accepted. Although the two bluetooth leds are lit on the H9 al the time is there a change the H9 Control app looses the connection to my H9 when focus is set to forScore app?

Yes, when you leave H9 Control and go to the forScore app, H9 Control quits.  So, it's no longer listening for MIDI messages from forScore and sending them to the H9.  We intentionally disabled background operation for H9 Control because it was causing strange bugs and there didn't seem to be much reason to enable it since H9 Control starts very quickly.  I guess I'll have to take another look at enabling background operation to see if I can figure out where the problems I saw were coming from.

JCR:

But I can't get it to work on the Windows version of H9 Control either. 

Hm.  It works fine on my Mac, but I don't think I ever tried it on Windows. I'll have to see if I can reproduce the problems you experienced.

[JCR]

gkellum:

Yes, when you leave H9 Control and go to the forScore app, H9 Control quits.  So, it's no longer listening for MIDI messages from forScore and sending them to the H9.  We intentionally disabled background operation for H9 Control because it was causing strange bugs and there didn't seem to be much reason to enable it since H9 Control starts very quickly.  I guess I'll have to take another look at enabling background operation to see if I can figure out where the problems I saw were coming from.

Is there an update in the make that enables H9 control to operate in the background. It would solve my problem on iOS 8.1. Is it an idea to have a separate basic (driver) app just to enable  iOS coreMIDI apps to connect to H9? Something like the new mi.1 connect app for the mi.1 wireless midi connect device.

gkellum:

Hm.  It works fine on my Mac, but I don't think I ever tried it on Windows. I'll have to see if I can reproduce the problems you experienced.

Any luck on the Windows platform? My Windows H9 control does crash every time when controlled by external midi commands. I am using the latest H9 Control versions on Windows and iOS.

[gkellum]

JCR:

Is there an update in the make that enables H9 control to operate in the background. It would solve my problem on iOS 8.1. Is it an idea to have a separate basic (driver) app just to enable  iOS coreMIDI apps to connect to H9? Something like the new mi.1 connect app for the mi.1 wireless midi connect device.

Maybe, it could work that way.  Alternatively, if we could H9 Control run in background mode only if those MIDI features are enabled, that would be another option, but normally, one enables or disables background operation through the apps property file.  We'll have to look into it…

We're hesitant to always have H9 Control run in background mode for all users b/c it's generally speaking just a good thing to let an app quit when you're not using it as long as it can start up quickly again. It's better for stability to have a clean start.

JCR:

Any luck on the Windows platform? My Windows H9 control does crash every time when controlled by external midi commands. I am using the latest H9 Control versions on Windows and iOS.

I tried to set things up on a Windows machine to test this. I was going to route Max/MSP through a LoopBE virtual MIDI port to H9 Control. I launched Max first and routed it to LoopBE. Then I launched H9 Control and it couldn't open up the MIDI port any more to connect to the H9. Max/MSP was locking up all of the MIDI ports. I had to restart the machine so that H9 Control could talk to the H9, but I could never get both Max/MSP and H9 Control working with MIDI at the same time, much less working together. This doesn't happen on Mac…  What exactly were you trying to route through H9 Control on Windows? Maybe, the app you were using was also locking up all of the MIDI ports?

[JCR]

gkellum:

Maybe, it could work that way.  Alternatively, if we could H9 Control run in background mode only if those MIDI features are enabled, that would be another option, but normally, one enables or disables background operation through the apps property file.  We'll have to look into it…

We're hesitant to always have H9 Control run in background mode for all users b/c it's generally speaking just a good thing to let an app quit when you're not using it as long as it can start up quickly again. It's better for stability to have a clean start.

Maybe a separate app to control the H9 by MIDI is the best way to go. That way it does not mess with the H9 Control app in any way. It could be a very basis app that registers the H9 as a virtual MIDI device and stays in the background. It would be great though if such an app would presents itself as an independent virtual MIDI port (like mi.1 connect does) and not, as the current H9 Control, has to be connected to another MIDI port.

gkellum:

I tried to set things up on a Windows machine to test this. I was going to route Max/MSP through a LoopBE virtual MIDI port to H9 Control. I launched Max first and routed it to LoopBE. Then I launched H9 Control and it couldn't open up the MIDI port any more to connect to the H9. Max/MSP was locking up all of the MIDI ports. I had to restart the machine so that H9 Control could talk to the H9, but I could never get both Max/MSP and H9 Control working with MIDI at the same time, much less working together. This doesn't happen on Mac…  What exactly were you trying to route through H9 Control on Windows? Maybe, the app you were using was also locking up all of the MIDI ports?

I can't get it to work on Windows 7 with LoopBE virtual MIDI port too. Nothing happens when sending MIDI messages to H9 Control connected this way. MIDI-OX caputeres all MIDI events just fine though. H9 Control v1.6.2 crashes when connected to my Roland Quad-Caputer UA-55 MIDI port as soon as MIDI messages are send into H9 Control this way and is thrown out of memory, but I don't have to restart the computer for MIDI to work. It happens when trying to control H9 by MIDI-OX program change and CC messages and when my iPad, connected by a MIDI cable into the Roland UA-55 sends MIDI to H9 by using forScore or MIDI Toolbox.

[Author]

Posts