fjgiie wrote:For some reason X runs from 0 to 499 and Y runs from 1 to 374.
In the previous movie there was no X=500 and in this one there is no Y=375.
There is a Y=375 location in this movie so, I have no answer as to why there are no red locator bars for Y.
I guess it’s due to a common programming issue: the pixel coordinates we expect to see are from 1 to 500 in the X-direction, and 1 to 375 in Y-direction, but are probably represented at program-level by arrays, which conventionally start from zero, i.e. 0 to 499 for X and 0 to 374 for Y.
Hopefully the techs can easily sort out the evident inconsistencies you point out.
By the way, on the coordinate issue, as far as I can make out the native movie frames we are sent from the server are in fact sized 512 x 384, but are slightly compacted at browser level to 500 x 375, I presume in order to conveniently correspond with what we have been told are their actual micrometre dimensions.
Quite why the team settled on this extra complication (and hence, though marginal, degradation in resolution) is for them to explain, but might account for the occasional tough power movie that seems to feature a single pixel ‘track’ that flickers in-and-out of visibility according to different depth frames, so providing an unintended give-away! Anyone else noticed this?