I’m building my own Master MIDI Clock device and I have a question about MIDI SYNC = ON while Aeros is in STOP Mode. Note that I’m only using the Aeros, not BB, so my questioning might be related to some interaction between these two that I do not know about.
If my intention as a user is to use an External Clock and an external START/STOP command, is there any purpose for Aeros to receive the external clock first? (ie: MIDI SYNC= ON while Aeros is in STOP Mode?) Or is it the same practical result to send in MIDI START and also begin the MIDI Clock at the same time? (nearly the same time … I know). The later is what I’ve been doing with other external clock devices and it has worked fine, but my custom device has the ability to begin the MIDI Clock without sending START … I can keep those actions independent or combine them into one action.
Or to put it another way: with MIDI Clock being received, but the Aeros in STOP mode, is Aeros doing anything other than acknowledging that clock is being received by displaying MIDI SYNC = ON? Is it using that clock in some way while Aeros is stopped to help solidify the playback once it starts? Is it so that Aeros can sync to a clock while also offering the ability to Start using it’s own command instead of an external Start command? (<= if it’s that reason, and it seems likely, I have some other observations about that, but will avoid that discussion for now)
I’m actually not running into any roadblocks, everything is going great with my custom external clock device. I’m really just wanting to understand a bit more about the purpose and intention for MIDI SYNC = ON while in STOP Mode because there might be something about it that will spark an idea or help my device be more future proof.