search

docb / dbRackSequencer

GNU General Public License v3.0
18 stars 6 forks source link

PwmClock - BPM (V/Oct) input doesn't accept clock signal from "Midi > CV module" #22

Closed anyway closed 7 months ago

anyway commented 1 year ago

The "BPM (V/Oct) Input" of "PwmClock" does not accept the clock signal from the VCV Rack module "Midi > CV". The clock rate jumps around like crazy. My DAW (Bitwig) is set to 110 BPM in this case. I also tried different CLK/N divider settings with the CLK/N output... to no success.

Is there anything special that needs to be considered for synchronization? With Impromtu's "CLOCKED" it works fine.

grafik

My System: dbRackSequencer 2.2.2 VCV Rack Pro 2.3.0 MacOS 12.6 MacBook Pro M1 Max

docb commented 1 year ago

hi, thanks for reporting. the BPM input of PwmClock does only support BPM CV and no clock signal. The origin reason is that PwmClock is designed as one of many building blocks for using VCVRack without a DAW. However i did not try this in production but at least you can use start stop of midi-cv to start and stop PwmClock. This should be accurate for a while if BPM is set to the DAW tempo. To automate setting the BPM you can use the mini Clocked as shown in the image: image Note that because of the higher bpm resolution the BPM will wobble between 134.99 and 135.01 in this example.

I will think about supporting clock sync in future versions. Best regards

anyway commented 1 year ago

Thanks for your fast reply, explanation of the problem and the patch as a workaround. Now I understand.

To get your workaround to work, Impromptu's CLKD needs to have "BPM out is CV when ext sync" set in the settings so that BPM no longer jumps in PwmClock.