10-19-2020, 11:51 PM
Hi All, thanks to your suggestions the mystery is unveiled. I was sending the clock to the NDLR 5x times too many, however some of the maths is still off. See below.
Bitwig's master clock was 100, and the clock reading on the NDLR was 600.
By default, Bitwig sends the clock to all devices, which means also all of NDLR's USB ports, so, in Bitwig, not in NDLR's boot menu, I turned off 3 out of 4 clock sendings and the new clock went down from 600 to... 200! (see the configuration here https://imgur.com/UxlkOS6 ). Why not 300?
Next, I turned off also sending clock on USB 1... and NLDR was still receiving clock!
So I've realised that to control the NDLR I was using Bitwig's "HW instrument" tool that was sending its own clock too (see https://imgur.com/xZ1pSct ). I've turned that off, and the clock on the NDLR now matches the DAW.
Still, why was the clock 600 and not 500 in the first place? That remains a mystery.
Bitwig's master clock was 100, and the clock reading on the NDLR was 600.
By default, Bitwig sends the clock to all devices, which means also all of NDLR's USB ports, so, in Bitwig, not in NDLR's boot menu, I turned off 3 out of 4 clock sendings and the new clock went down from 600 to... 200! (see the configuration here https://imgur.com/UxlkOS6 ). Why not 300?
Next, I turned off also sending clock on USB 1... and NLDR was still receiving clock!
So I've realised that to control the NDLR I was using Bitwig's "HW instrument" tool that was sending its own clock too (see https://imgur.com/xZ1pSct ). I've turned that off, and the clock on the NDLR now matches the DAW.
Still, why was the clock 600 and not 500 in the first place? That remains a mystery.