<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="">I'm with Pete. Arguing that "we're doing timing, but it doesn't matter where the pulses fall" seems like a one-way ticket to failure.<div class=""><br class=""></div><div class="">Unless "drunk jazz drummer" is the effect you're after? ;)</div><div class="">
<div><br class=""><blockquote type="cite" class=""><div class="">On 18 Dec 2021, at 21:10, Pete Hartman 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 dir="ltr" class="">Right but where the divisions are going to fall when you're doing an odd divisor that includes a factor of 3 is going to shift around if the pulses being divided aren't evenly spaced.<div class=""><br class=""></div><div class="">I tried to make an ASCII representation to verify this expectation:<br class=""><br class=""><font face="monospace" class="">| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Original pulse train<br class="">| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | evenly divided<br class="">| | | | | | | | | | | | | | | | | | | | | | divide by 3<br class="">|| || || || || || || || || || || || || || || || || || || || || || || || || || || || || || || || unevenly divided<br class="">| | | | | | | | | | | | | | | | | | | | | | divide by 3<br class="">| | | | | | | | | | | | | | | | | | | | | | the even div/3 for comparison</font><br class=""><br class="">Hopefully everyone's email clients can cope with the monospace required to make this obvious.</div><div class=""><br class=""><br class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 18, 2021 at 3:00 PM Benjamin Tremblay <<a href="mailto:btremblay@mac.com" class="">btremblay@mac.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto" class="">If I’m waiting around doing nothing until I count 12 pulses, all that matters is I construct a square wave 12 pulses long.<br class=""><br class=""><div dir="ltr" class="">Benjamin Tremblay</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On Dec 18, 2021, at 3:56 PM, Benjamin Tremblay <<a href="mailto:btremblay@me.com" target="_blank" class="">btremblay@me.com</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class="">I’m assuming all it does is divide by 12 to get a 16th note. <br class=""><br class=""><div dir="ltr" class="">Benjamin Tremblay</div><div dir="ltr" class=""><br class=""><blockquote type="cite" class="">On Dec 18, 2021, at 3:53 PM, Pete Hartman <<a href="mailto:pete.hartman@gmail.com" target="_blank" class="">pete.hartman@gmail.com</a>> wrote:<br class=""><br class=""></blockquote></div><blockquote type="cite" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><br class=""><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" target="_blank" class="">synth-diy@synth-diy.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br class="">
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 class=""></blockquote><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">Pete </div></div></div>
</div></blockquote></div></blockquote></div></blockquote></div>
_______________________________________________<br class="">Synth-diy mailing list<br class=""><a href="mailto:Synth-diy@synth-diy.org" class="">Synth-diy@synth-diy.org</a><br class="">http://synth-diy.org/mailman/listinfo/synth-diy<br class="">Selling or trading? Use marketplace@synth-diy.org<br class=""></div></blockquote></div><br class=""></div></body></html>