lid55
MidiFire Beta
Posts: 68
|
Post by lid55 on Jan 24, 2017 20:27:02 GMT
Hi nic, I was wondering if you could help shed some light on a particular issue I've run into.
Multiple MIDI messages sent via a single key press of the SoftStep, that work fine going directly from the UA22 interface into LoopyHD, do not work as intended when taking the route UA22 > MidiBridge > LoopyHD.
So, in analyzing it, it's even a problem if just 2 CC messages are sent simultaneously. If I send a single CC message, all works as it should.
Now I know there's a potential workaround for this: building all the multiple messages within MidiBridge. And I might just do that, but I do have many of these simultaneous commands, so I was hoping there was another solution.
Any ideas?
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 24, 2017 20:47:46 GMT
Hi lid55, I (soon will) have sent you a PM with instructions on how to get MidiBridge to generate developer trace which might assist in identifying what is happening. I have a couple of ideas, but the trace should help steer me in the right direction. Regards, Nic. |
|
lid55
MidiFire Beta
Posts: 68
|
Post by lid55 on Jan 24, 2017 21:54:12 GMT
Ah, sorry about this! I should have known to try and entirely power down and restart everything. It works! I was messing about for a few hours this morning, trying different routings, SoftStep programmings, including MIDI Clock, so... I guess something really messed up, but I tried so many things I have no idea what caused it. Could a looped routing cause something that persists like this? Well, anyhow, I'm just glad it seems to be working now. Also, I know how to send a trace if needed. Thanks Nic.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 25, 2017 9:50:58 GMT
Hi lid55, Hard to know without seeing the trace, but generally a looped routing would be painful until the loop was broken and then everything *should* return to normal. However, maybe Loopy has smarts to detect looping (hehe) and does something. If it happens again, I'd be happy to examine any trace you might generate. A common issue is where an app receives multiple messages from CoreMIDI bunched together in a single packet. Not all apps handle this case and maybe this was happening, but just a guess. If the path from input to output in MidiBridge does not have any modules configured on it, then any multiple-message packet is passed directly to the output. If there *are* modules configured then the packet is split into separate messages (by MidiBridge) and passed to the output one by one. So, if you see this happening again, try enabling an Event Filter that passes everything on the UA22 input which will force the messages to be split. Regards, Nic. |
|
