*SOLVED* Nerdseq as Master BPM issues

[XORadmin]

Hi. I am using the Nerdseq as a master clock. I have the 1/16 clock out then going to a Pamela's New Workout. When I press play the BPM detected by PNW is a few BPM off the value inside the Nerdseq. Eg: if I play the Nerdseq at 128bpm, PNW detects 125bpm. If I slow down/speed up the Nerdseq, PNW always seems to be a few bpm off. 

I don't have this issue with other clocks going into PNW (eg: from CVOCD).

I've made a video to demonstrate this - no other modules are used - just Nerdseq and PNW.

https://www.dropbox.com/s/ujywk3u0pstiy3...k.MOV?dl=0

Thanks x

Hello,

I did several tests with different devices and couldn't find any differences with the BPM. I also just made a recording with the scope to be 100% sure no other latencies are involved.
Connected is the Trigger which is 4 on the floor. Clock Out which is 1/16.
Putting both on the (HQ) scope shows both stable and calculating the BPM from it gives the rate of 128 bpm. (here rounded caused by the 2 digits after the dot). I definitely would say that the PNW doesn't calculate the incoming BPM well. In fact, this can be a tricky thing anyway if the clock rate/precision is not high enough.



Calculation is simple:  Measured frequency (here for the trigger) * 60 seconds
Also, when calculating with the clock signal i get same result as you can also see in the scope picture.