Thank you very much for your post, although we did not immediately reply we were watching it closely.
This issue should be fixed without the workaround now!
The reason this started happening is the Aeros was updated to never lose count to avoid a bug reported to us that Aeros would not always reliably start back following the right count if stopped and restarted many times while BB remains playing back.
The bug reported here is caused by the lack of a logic for devices sending only clock and not Start commands.
The Aeros will now start immediately and be synced to the incoming MIDI clock if no MIDI start was sent. The Aeros refers to the incoming clock, it does not “follow” the clock, this allows it to be started immediately without any lag even when receiving clock.
We understand this breaks from the MIDI convention, we are going to experiment soon with changing both the BB and Aeros to follow the general MIDI Start spec behavior.
Thank you for reporting and your patience!