The last thing we try is one of the first things we would have tried, if only we had some reason to think it was the source of our trouble; such as it being obvious to somebody else.
After spending yet more blood, sweat, tears, time, and money (don’t ask) in troubleshooting this, it seems this might be solved.
I have not reinstalled BB into my full-blown MIDI setup yet, but here’s what I have done using the test setup from above:
- Ableton Live 10 Lite over USB to Behringer UM404HD as an interface, out to BB, then out to D-05.
I had thought MIDI-MERGE is the most flexible setting, to be able to pass note data from the DAW and send note data originating from BB should that be desired at some point.
- Change BeatBuddy MIDI-OUT Output Type from MIDI-MERGE to MIDI-THRU.
Also works if MIDI-OUT Output Type is set to MIDI-OUT.
This only works because clock signal is entirely separate from note data and is not dependent on channel settings.
I knew that, but apparently clock signal is not only sent through BB, but BB also generates its own signal (or it somehow loops internally) and as a result, adds that to what it sends out and screws everything up.
I do not think BB is the only device out there that behaves like this. It’s just something I was unaware of.
So, here’s hoping this simple fix remains effective once the entire network is put back together. And that others might benefit too.
By the way, I’ve determined that BB’s failure to start drumming in response to my standard notation programs is the fault of those programs, not BB’s fault.