|
|
Post by baldeagle on Nov 3, 2013 2:00:07 GMT
I am trying to use MidiBridge to remap midi commands on hard synths and am experiencing some latency and dropped midi events. Are there some settings that might help? Here is my configuration.
iPad 4 and Griffin StudioConnect with Lightning.
M3 connected to Midi In via MOTU Midi Express XT
Prophet 12 connected to Midi Out via MOTU Midi Express XT
MidiBridge Interface connecting StudioConnect In to Studio Connect Out
No active MidiBridge modules
No other active iPad apps
So with this setup I'm basically using the M3 to control the Prophet 12. There is some latency but more important are the dropped midi events. It usually drops the note off event resulting in hung notes but also sometimes drops note on events. Is MidiBridge capable of operating like this or is it really intended to control midi within the iPad using only one in or out at a time?
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Nov 3, 2013 9:07:59 GMT
Hi baldeagle,
Virtual MIDI was added to MidiBridge a while after hardware CoreMIDI, so no, it isn't intended to control internal MIDI only.
With no modules on, MidiBridge blindly routes the data it gets (ie. it does not look at the packets before routing) so in this mode, latency is in the sub/low-milisecond range as it passes through. It is also designed to route between multiple interfaces. The routing code is very tried and trusted and extremely stable, and although I would never say never, the chances that MidiBridge is dropping/delaying events itself is fairly slim. ;-)
If you are experiencing unacceptable latency and dropped events it could be that there is a routing loop in your system (unlikely, but can't be ruled out) or that the issue lies elsewhere. Given that that hardware unit is having to process incoming/outgoing streams pretty much simultaneously does make me wonder whether the problem lies there. I have never used one of those myself so don't have any first-hand knowledge about how well they perform.
It's easy for me to say all this, but the proof is in the pudding. Could I suggest you email me directly about this (please include a screenshot of the MidiBridge main Interfaces page with your routings) and I will get you to access the routing stats MidiBridge keeps and then if you are willing try to capture some development trace I can take a look.
While I am not ruling anything in/out I also suggest you might like to try connecting the M3/Prophet directly to the Griffin unit and leaving the MOTU out for now. Any difference?
If you happen to have a different iOS compatible MIDI device, maybe you could try that and eliminate the Griffin as the source of the issue?
Regards, Nic.
|
|
|
|
Post by baldeagle on Nov 4, 2013 18:52:05 GMT
Problem solved. It turns out that some of my gear was sending out massive amounts of midi timing events which ultimately caused the Griffin Studio Connect to overflow and drop events. MidiBridge was working flawlessly and processed all the data that was thrown at it, no latency and no dropped data.
Many thanks to Nic for all the effort he put into solving this issue. It wasn't even a MidiBridge problem and most companies don't provide the level of support that Nic did even when it is their problem.
|
|
