There is no plan at the moment to support that. With the way the metronome is implemented, it will just cause significant headaches and potentially performance issues, as the metronome tempo that is being received could constantly jump up and down 1 bpm, requiring a new audio file to be generated over and over. Obviously I could implement all sorts of optimizations to try to cache loops at different bpms to account for this, but I really don't want to try to take on all that work unless a large number of users indicate they need this capability. Part of the reason for all this complexity is I wanted to ensure the metronome is incredibly accurate over long periods of time. I had to do extensive work to make sure there was no variance in the metronome even if it is played for 30 minutes straight. I tested this against a real metronome sitting next to the tablet to be sure. Previously, I was dynamically generating audio on the fly for the metronome, but none of the available audio frameworks on Android or Windows were accurate enough over time - there would start to be small variance, and it would be worse on older devices or devices with slow processors. So instead I had to go with an approach of generating an audio file that contains one measure of audio for the metronome, and I loop that audio file with an audio framework that is designed for high-performance and accuracy.
Mike
Mike