Yeah, read it as 4ms per row at first. Should be fine for general use, and rather impressive as is :)

I read it first as 4ms per row, but yeah 4ms per scan wouldn't be too bad. There is of course additional time taken for communication etc, which might take another 4-10ms, which could make it almost a frame behind. Not terrible still.

Valid point! Might still be able to get a speed up if you can write and import your own C code though.