<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I’m assuming all it does is divide by 12 to get a 16th note. <br><br><div dir="ltr">Benjamin Tremblay</div><div dir="ltr"><br><blockquote type="cite">On Dec 18, 2021, at 3:53 PM, Pete Hartman <pete.hartman@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 18, 2021 at 2:15 PM Benjamin Tremblay via Synth-diy <<a href="mailto:synth-diy@synth-diy.org">synth-diy@synth-diy.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
2) I wish I understood the theory of clock multipliers. I have seen code that measures the period between clock pulses and dead reckons the double-time pulse as an average of the recent periods. But why? Why can’t I just fire another extra HIGH-LOW pulse whenever I get a MIDI clock event? Why does timing of the extra ticks matter? I’m assuming 48 PPQ divides the clock down to individual sequencer steps on the KPR-77. As long as the divided clock is coming in on the beat, what does it matter if some of the synthetic pulses are a little off? (They’re just shadows of the main tempo clock). It’s not like the KPR-77 is inferring something or trying to calculate BPM from the external clock… So… Anyway I just wish I knew what I was aiming for, and then maybe I could hit the target.<br></blockquote><div><br></div><div>One suspects that most people are trying to write a general purpose converter. E.g. you could run those 48ppq out to some other module, like an analog sequencer, and it would keep time. I'm not familiar with the KPR-77, but I'm also slightly puzzled by the idea that some piece of gear would require 48PPQN but not care about the timing of half of the pulses.</div><div><br></div><div>Pete </div></div></div>
</div></blockquote></body></html>