Comment "timestamp" from API different from "Frame" in downloaded CSV

Got it. I asked our devs and they responded with:

“yes, ultimately the front end player and backend have to independently calculate the frame position based on the DB timestamp_microseconds value. I did a bunch of testing to minimize these off by 1 errors, but the truth is that the rounding errors from two different systems that handle numbers (as floats or decimals etc) will cause this kind of issue.”

1 Like