image-et-son
commented
2 years ago There are still corners of the GliGli firmware I have not yet worked through :-) (but not so much anymore). Clock is one such area. And I discovered, that it is already supposed to work as you describe: the speed/data pot selects a clock divider from the following list: {192,168,144,128,96,72,48,36,24,18,12,9,6,4,3,2}
Just a little piece of information. I now need to see where the mechanism goes wrong. Would be good if you could say something about 2.1RC3 while I concentrate on the code.
el-folie
matrix12x
When feeding the tape input with a constant ticking clock source (CR-8000, 8th or 16th) not every single clock pulse leads to an arp trigger. There are drop outs here and there, can´t see a pattern yet.
And the arp speed parameter knob has an influence too: Only on speed 99 almost but not every clock pulse is converted to a trigger impulse for the arp and there are drop outs of pulses. If the speed parameter is reduced to about 80 the arp gets only triggered here and there. Further reduction of arp speed leads to only one arp trigger impulse every few beats and so on. So there must be some dependence of the arp speed and the tape input as a clock source. Maybe there once was the idea to let speed act as a clock divider, but it´s just all over the place without any reliability yet.
(Proposal: It would be nice if the arp speed parameter could act like a divider in midi sync mode, as the midi beat clock is ticking so fast that the arp becomes unusable without a divider option. In Tape Sync mode both a clock divider/multiplier would be nice to tailor the arp speed.)
(I´ll test v2.1rc3 tomorrow to see if it was always like this.) Forgot to type this yesterday, yes, on 2.1rc3 the behaviour is as described above.