This would probably not be the way it works, the Aeros would have to do the following:
Record the first track> Instantly divide that track based on time signature > Tell the BeatBuddy the Tempo> BeatBuddy starts immediately
Notice that’s a lot of things to happen in less than a quarter of a second, maybe less than an eighth…
We will have to look into it a lot, but the Aeros will also need to be able to be Master and also send tempo/time signature info.
That being said, an auto-record function would probably start off as an internal function and then we will probably move on to expanding it’s ability (once stable) to incorporate the BeatBuddy seamlessly.
A lot of things have to be done before we can even get there, namely the MIDI implementation on the Aeros so that it can be Master as well as slave, as well as the beat clock; and also the auto-quantize function.
So this may not be coming all too soon.
I don’t believe there is any hardware in the BeatBuddy that is reading incoming levels in a way that it can be turned to useful tempo data. I can ask. Most likely, the BB will have to behave as I stated above, as slave to the Aeros. How well will this work? Not sure, will be an experiment, we may have to fumble around with how often the BB is syncing to Aeros tempo, possibly incorporating smaller, finer levels of subdivision so that even if beat one is a few ms off on BB it resyncs before you reach beat 2. This is probably no small feat!
It’s an interesting idea, that way once a threshold is reached, it’s as if a record command was sent and will start recording on the following measure. And the forgiveness lag (if Aeros was told to playback and not record) would make sure if within 300ms of beat, it will still be recorded.
I don’t know if we would outright trash the set count in, but it’s an interesting expansion to the feature.
There’s a lot of ifs here but I know we are interested in looking into it.
