First of all, congratulations for your implementation of the Autoquantize! It has made me dust off the Aeros and start really using it. The routing options for the click are great and very useful to combine with the loop sound to guide a drummer. Some people have mentioned clicks at double time or half time but that is to be expected if the computed bpm falls outside of the 40-300 bpm range.
But with Autoquantize, with length=Auto I do have a question:
Suppose, for example, that a piece, musically 4 measures long, lasts 12 sec. The computed bpm could be 80 bpm (think of Hey Jude) and the click bpm would exactly correspond to the intended musical beats.
But a faster piece, musically 8 measures long could last the same 12 sec and could be computed at 160 bpm, and correspond to the intended musical beats. What would the algorithm do?
The point here is that BOTH fit the 40-300 bpm range. If the algorithm chose 80 bpm for the fast one, clicking at half time it would be less bothersome, but if it chose 160 for the slower piece, that would be slightly more annoying. What would the algorithm do. choose the one closer to the middle of the range, absolutely or percent-wise. or some other criteria?
Next for me would be to interface with my friend’s Beat Buddy, but before I want to be absolutely sure of how the Aeros does things. Again congratulations!