Using the DAVIS128 on the USB3 Dev Kit, in windows (10 or 8) using jAER, the rendering, or perhaps the data, is messed up. Chip class DAVIS128 and DAVIS128color both have distinct problems which could, however, be related to an underlying data corruption, perhaps some bit shifting, but the APS images are also corrupted. Using the DAVIS640 on the same MB with everything else identical, there is no problem. Using caer on the same machine, there is no problem. You can replicate this error using, e.g. the Yoga laptop.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using the DAVIS128 on the USB3 Dev Kit, in windows (10 or 8) using jAER, the rendering, or perhaps the data, is messed up. Chip class DAVIS128 and DAVIS128color both have distinct problems which could, however, be related to an underlying data corruption, perhaps some bit shifting, but the APS images are also corrupted. Using the DAVIS640 on the same MB with everything else identical, there is no problem. Using caer on the same machine, there is no problem. You can replicate this error using, e.g. the Yoga laptop.
This has been fixed in SVN. The problem was wrong biases in the DAVIS128 bias XML files.