You know James Holden? An artist who plays Modular live with drummer and percussion. At least I want the others to dictate tempo before my parts join, and once I’m in, the others can adapt to my tempo, that is now hopefully close to the original tempo. I want to be able to sync my system to a live band without having the rest of the band members locked to my tempo. Because no Matter how accurate your tapping is, two machine will drift out of sync after a short time because you'll never tap as accurate as required and the clocks them self won't be either. Why do you want / need something like that? I hope you don't want to sync several machine this way. Is this possible to set up or am I dreaming here? If it could also send a reset on the 8th tap and start the clock on the 9th it would be awesome. What I dream about is a module sophisticated enough to take, say 8 taps and make a educated guess out of the average of how it is going to continue. Just be a hair off, and the tempo generated is 10% faster or slower than the actual tempo. In my opinion this is not enough to make a reasonable calculation of the actual tempo. Most devices that does tap tempo seems to pick up the tempo within three taps. I’m looking for a good way of accurate tap tempo. are all eurorack modules that accept user programs. something like teletype, ardcore, terminal tedium, ornaments crimes, daisy etc. your idea about a sync input and a trigger to unmute the tap tempo clock out is a good idea but you need someone to program that into some module. in your case you want exactly 8 steps of averaging which can be programmed in software but it will have the incorrect speed if you tap 7 times. if you have averaging, you also make a compromise that you will need at least 3 taps because of the averaging. the only chance at getting it right is to do averaging if you know the music is constant tempo. if the speed of the music is constantly increasing them the average will always be incorrect. averaging seems fine in theory but it is also bad. ![]() this is why the module needs to have a lower bound for BPM. ![]() if you have the perfect simple math formula then it would be 2 BPM. ![]() if you tap 3 times, wait 3 minutes, tap 3 times again. software does not know if you will tap 3 times or 30 times so it assumes that you may or may not tap again. it also can't update in real time because the transition would not be smooth. the tap tempo software needs to have an upper and lower bound.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |