<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 2 Feb 2021, at 10:31 am, Didier Leplae via Synth-diy <<a href="mailto:synth-diy@synth-diy.org" class="">synth-diy@synth-diy.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div class="yahoo-style-wrap" style="font-family:verdana, helvetica, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false" class="">I am currently working on a delay module using a PIC uC to control the delay time so adding in a tap function. </div><div dir="ltr" data-setdir="false" class="">Thus far, I have the PIC measuring the time between two consecutive taps to determine the delay time. But it occurred to me that sometimes when I use a tap tempo, I tap multiple times with the assumption that the multiple taps are averaged. </div><div dir="ltr" data-setdir="false" class="">Does anyone have an opinion on which is the more sensible or accepted way to do this? </div></div></div></div></blockquote><br class=""></div><div>I always tap along to the track for a few seconds, and try to stop as soon as I think I’m very close, because I assume only the last two taps would be measured. I wasn’t aware of the use of ‘averaging’ in these types of circuits</div><div><br class=""></div><div>A</div><br class=""></body></html>