I investigated a bit further into the grds module. I am not sure what exactly happens, but I confirmed that the clock is fine. The problem is that “grids” itself somehow interprets an input of “16” as the start of a measure. I checked the output of “pg 32nds” and when it says 16, “grids” produces a beat. I quickfixed this by offsetting the output of “pg 32nds” by 16… Of course this fixes the problem only sometimes in my specific configuration. I think syncing the “grids” modules with
master-beats would solve the problem.
The reason the standalone module does not have this issue is probably, that the clock is initialized at the same same time as the grids itself, so it starts at 0. But I am not sure of that.
Edit: I am building a master-beat synchronized version right now.
Also, U-clock says that it send
master-beats, but it doesn’t.