This kind of thing varies from looper to looper, and I have the same experience as you do with the Aeros (I use a TEMPODE for Clock and Start/Stop). I really don’t think it is how the Tempode is sending Clock, but I could be wrong. I’m basing that on using 3 different loopers and observing how they each work in different ways slaving to the TEMPODE.
If it helps with anyone’s research, this is the behavior of all 3 Loopers that I use (Aeros, 95000, Infinity), and how they are each different in these 2 use cases:
Start/Stop with TEMPODE:
After starting the Tempode and getting a loop recorded in each unit, if I stop with the Tempode, all devices Stop. If I start again with the Tempode:
- Aeros and the 95000 - start immediately at the 1 of their recorded loops. (the preferred way it should work, IMO).
- Infinity - does not Start. It recognizes that the Clock is running, but waits for me to press Start on the Infinity. When I press Start, it will wait until 1 comes around and start with it in sync.
Stop/Start directly on the Unit while TEMPODE remains running
Again, I start Tempode and record a loop in each device, everything is in sync. But now I leave the TEMPODE running and just stop any one of the devices on their own. When restarting the device on it’s own (while the TEMPODE is still running):
- Infinity - same as above. It will wait until the 1 comes around and then start (in this context, this is the way it should work, IMO.).
- 95000 - It will start on the next clock beat from the top of it’s loop, so it’s in sync tempo-wise, but the 1 can be in a new place in relation to any other devices also keeping sync. (I can work with this, I just have to press Start within 1 beat of when I need it to actually start)
- Aeros - It just starts exactly when I step on it and can be off the beat entirely, though in sync tempo-wise. (I avoid doing this because it’s too risky)
I’m not sure about the idea that there is a problem with the Clock stream or that the “1” should be marked in the stream itself. Empirical results have always indicated to me that the concept of “1” is determined by the unit receiving the clock, which is why each device can be set for various Time Signatures, even while receiving the same Clock data. I think the first tick received by a device is the ‘1’, and then the Time Signature set on the device is applied from there. In the case of the Infinity, I believe when I stop just the Infinity (the TEMPODE is still running), it is still receiving and processing the clock and internally continues to recognize where the ‘1’ is. The other devices don’t do that when they stop. The 95000 jumps in on the next clock beat and makes that beat the new ‘1’ and the Aeros just jumps in right away, even if it’s in between beats.