Patrick Faion

Results 18 comments of Patrick Faion

Note that the large delay is the result of building from source and attaching the debugger in Windows. When starting without the debugger, the delay is orders of magnitude smaller...

Quote @papr in #1870: > The issue is caused if there is no scene image but pupil data that is recognized to be a blink. I'll see if I can...

Indeed it seems we implemented UVC 1.1 from 2005. In 2012 they released UVC 1.5, which includes `3: 'Auto'`. Weirdly there seem to be no versions 1.2 to 1.4. See...

I had a quick look and it seems the USB specification includes an `InterfaceProtocol` for all its interface classes (which UVC is an instance of). Specifically, UVC 1.1 only has...

The question is, if we want to limit our libuvc fork to UVC 1.1 devices, or whether we want to expose this setting to the outside. The second option would...

I tested it with another Pupil Invisible recording, where the surface is close to the edges of the screen, but here I don't encounter the issue. So this might be...

Notes from @marc-tonsen : Actually the 100x1 case is expected since the heatmap has only 1 bin in the y direction. The 1x1 and 1x100 cases are unexpected and are...

While trying to test this I realized that the docs seem to be out-of-date here: https://docs.pupil-labs.com/#libuvc `LIBUSB_LIBRARY_NAMES` and `PTHREAD_LIBRARY_NAMES` do not exist anymore, but are now called `*_LIBRARIES`. Also: cmake...

Another issue with the docs: https://docs.pupil-labs.com/#libusb references building as static lib: ![image](https://user-images.githubusercontent.com/7101194/64699977-404da200-d4a6-11e9-9360-df66df8c6866.png) This will result in the libraries being stored to `C:\work\libusb\x64\Release\lib\libusb-1.0.lib` while the docs reference `C:\work\libusb\x64\Release\dll\libusb-1.0.lib` (dll instead of...