It was simply HD16 as master (HD16 won’t work as slave to anything), BB as slave. Zoom got rid of all the midi stuff for some reason after the HD16 so you’ll probably struggle to sync an R24 to anything. I’ve never tried BB as master to anything so can’t comment but others say it works well, however with BB as slave it just slowly drifts out of time and lags slightly behind the master after a while.
@Klink do you still have your BeatBuddy? Please test the new firmware and tell me if this fixes the sync drift problem. Download the new firmware here.
@Klink[/USER] [USER=2798]@further[/USER] [USER=260]@miamigroove Please test the new firmware and tell me if this fixes the sync drift problem. Download the new firmware here.
142 ???
I installed 141 yesterday !
What’s been added in 142 ?
Each time there is an update the version number goes up. Reading the above it appears the only thing that has been added to 1.42 is a possible fix for the “sync drift” problem and is currently being tested by users having this problem.
I have zero sync problems with my Boomerang III
Love it !
Rang III for the win! 
The only thing that makes me a little sad is that I don’t know if Rang would ever be able to accept any special MIDI commands for advanced things like changing the active track.
I don’t see the need for that…
If you want to change track just press the buttons on the Rang.
It’s perfect as is .
I couldn’t be happier with this combo :D:D:D:D:D:D:D:D
Gotta LOVE the Americans :p:p:p
What would we be without them 
In Soviet Russia music writes You 
Thanks David but unfortunately I sold my BB due to the midi slave sync issue so can’t try new firmware. Wish I’d have kept it now but I’ll probably get another one sometime when the exchange rate improves in Australia!
???
Well, that was a joke. Apparently it didn’t hit the spot 
Too bad… we really want to solve this issue. I hope we get some users to test it ASAP…
I’ll test it for you if you’ve got a spare one hanging around you can send me ;):)!
Last night I tried to sync a TC Flashback x4 as slave to BeatBuddy with no luck no matter what I did…I actually thought it was working one time, but my timing must have been oddly perfect haha. I’m going to see about trading up for a Boomerang III. So. Much. Money.
This is not a Beatbuddy issue, this is a Flashback x4 issue - I’ve been trying to get them to work on it for a WHILE now - check out my posts on the Flashback forum, http://forum.tcelectronic.com/topic/17203/pretty-please-with-sugar-on-top-enable-looper-midi-on-the-flashback-x4/ I’m hoping they can do something with their firmware - it seems like it would be a fairly simple fix, since they are midi enabled for the delay, you would think they could enable the looper as well. I’m wondering if Daefactor might be able to help them? I’m posting this same message as a reply to one of his posts.
Unfortunately, I don’t own a Flashback x4 unit. I also don’t think TC Electronic would trust some random guy on the internet like me to fix their problems
Fixing stuff usually requires an access to the codebase, and this is a very touchy question. If it is leaked, a huge permanent damage would be done.
I had trouble last night when I updated the BeatBuddy to 1.41 and the Infinity Looper to Pigtronix latest firmware. In the release notes for the Infinity Firmware, they specifically mention functionality for the BeatBuddy but that it is only confirmed working on BeatBuddy’s latest firmware. The way things look, 1.41 was the latest…that combo made the infinity totally freak out! The infinity was pretty much unusable when it was receiving MIDI messages from the Beat Buddy! I found DavidPackouz 1.42 Firmware and that made everything work Perfectly (phew thank god!), so just my two cents-not sure if 1.42 is a secret right now, but you may want to make it a little easier to find? Thanks for the hard work DavidP! I’m gigging solo with the beatbuddy and the infinity next weekend, so that’ll be the real test!
Sorry, I’ve been out of the “loop” for awhile! I will install the 1.42 fw soon and report back.
I assume your Infinity was reacting to Midi notes for triggering the BB beat outputed by BB, that were “confusing” your Infinity. You can change this behavior by Infinity application - tools - global boot settings - there you can tick a box to make Infinity ignore Midi notes. This will not change Infinitys behavior to it`s Midi messages (like PC for selecting songs or CC messages to remote with Midi Looper), but it will ignore any other Midi notes…