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?