MIDI SYNC Question

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.

Through further experimentation I realized that sending MIDI CLOCK without a START command (MIDI SYNC = ON) also sets the BPM of the song automatically in Aeros.

That’s what I was missing. I suppose it’s this way primarily for how BeatBuddy and Aeros can interact, but can also be beneficial for use by other external devices. It was only observable by me once the external device’s clock and transport controls had independence.

(I realize now that sending Clock without Start is also a way to work around the loop length bug I’ve seen in the past … where you had to make sure Aeros was already set to the same BPM as the external clock. I remember MIDI SYNC=ON being discussed in some BB related threads, but I was missing some of the nuance since I don’t use BB.)

Hello there, sorry for the delayed response,

Interesting questions

Yes, the best way to use the Aeros is with a continuous clock source, otherwise you may have hiccups in certain situations. This is why we have allowed the BB to have a setting to send clock even while stopped.

In essence you should be able to get most behaviors to work normally if the device is setting the Aeros to a BPM that is close to the current BPM displayed on the Aeros as it receives that start command and the clock.

My guess is that it could potentially desynchronize in some cases if the tempo change is too extreme and Aeros does not adapt fast enough, but I can’t say for certain. You will certainly lose the ability to set up a recording before the first beat of the measure (which may or may not apply to you).

Yes, we do support the ability to have Aeros “listening” to the clock to keep it better in time and to constantly resync if the BB changes tempo while stopped. This may be more of a solution to a problem when using machines like the BB that have their own playback timing. If the clock source you are using does not actually produce sound or is restricting playback, it likely should cause no issue (other than that possible tempo jump I brought up).

That’s it!

1 Like

Thanks, it’s good to know what the thinking was there even though I had worked it out. It was pretty clear once I got the right kind of external activity happening.

1 Like

My pleasure thanks for the question!