For quite some time my default clock is docB PwmClock. I like the PW, the swing, the number of outputs, everything.
But … I’m experimenting with tracks changing the tempo occasionally due to CV to the BPM input. PwmClock is total chaos. My drumtrack is failing for a few seconds. It’s not the case with Impromptu Clocked that handles these BPM changes nicely. Is there a way around with PwmClock?
@docb: would it make the transitions/calculations smoother if the BPM is rounded to an integer?
yes i recognized it also if i turn the BPM knob. the BPM goes crazy for some seconds…
I use this clock regularly. I’m pretty sure the ‘chaos’ during BPM changes is not avoidable.
It’s just the structure of this module. No, I don’t think that staying to whole integers will smooth it out. Also, if you modulate the Run on/off, that is not stateful and you get a reset effect every time it turns back on.
It’s a great clock as you know, but I think these limitations are hard-wired as a tradeoff to the variable pulse width.
more likely the clock multipliers go crazy? Previous post pointed out that clocked has variable PW and doesn’t do this.
it is currently not designed for that usecase. please create an issue on github.
A related issue for pwmclock. I use PAM Sync: ALM - ALM-PG001 Pam Sync to send DAW clock and run info to clock modules like Impromptu, which works fine, but pwmclock does not stay in sync. Here’s I’m sending BPM to pwmclock from Clocked, which is receiving clock from PAM Sync hosted in the same DAW, but pwnclock goes out sync every few seconds. Run input on/off is working fine.
Currently PwmClock runs most accurately (for an arbitrary amount of time) all internal clocks in sync from start, as each clock only relies on the sample count since the start is triggered (which is the reason for the problem stated above – if the bpm is changed, the point in time of clock beats since start may change drastically). So in this case i also could say the other clocks run out of sync with PwmClock as PwmClock is the most accurate clock ;-). However, PwmClock is not designed yet for syncing with other clocks.
