Every device may have a completely different mechanism to control the tempo (could be the MIDI timing clock message, a control change message, a system exclusive message, etc). Adding a way to insert the tempo as a value into any kind of MIDI command is not a trivial thing at all. The UI will not support that at all in its present state, and there is no where in the database for me to store that information at present. The MIDI logic is also not designed at the moment to pull values dynamically from other fields in a song (it expects constant values that were already assigned), so that would then require even more changes in the logic. I'm not even sure exactly how I would want to present that as an option to the user in the current UI, but even if I do make changes for that, then I have to make those UI changes on every platform and in the companion app. So this is not a small request that I can just slip into an update.
I should also add that inserting the tempo into a control change message requires splitting it up between the two fields, as they are limited to one byte (0-127). The implementation of that could also potentially be different with every MIDI device. I originally said I planned on adding something specifically for BeatBuddy, as I have documentation on what is expected with that device. Adding a solution that works for any device doesn't seem feasible to me unless they all use the exact same approach for setting the tempo.
Mike
I should also add that inserting the tempo into a control change message requires splitting it up between the two fields, as they are limited to one byte (0-127). The implementation of that could also potentially be different with every MIDI device. I originally said I planned on adding something specifically for BeatBuddy, as I have documentation on what is expected with that device. Adding a solution that works for any device doesn't seem feasible to me unless they all use the exact same approach for setting the tempo.
Mike