Hi there, we've started encountering this problem where, despite the pupil being very well contrasted with the iris, the detector refuses to look where the pupil is due to the positioning of these boxes you can see in this image. They keep moving on and off of the pupil. Do you know what might be happening and how we might be able to correct for this?

You need to reset the ROI (region of interest). It is set to the bottom half (at least it looks like that)

You can sort of see the thin white box that is the ROI on the edges of that eye image

These two boxes?

They're not the ROI, no

Those boxes seem to constantly be changing position on their own

Unless it's a separate dynamically-updating ROI that moves based on where the darkest portions of the image are or something like that

I checked the ROI you can adjust via the gear at the top right of the eye window, and the ROI boundary points are set to the four corners of the image.

@user-3cff0d there are dynamic rois, yes, but they correspond to the light blue rectangles

@user-3cff0d I have no clue though why the ROI handles would not correspond to the ROI area displayed in your screenshot.

I wish I'd recorded a video of it, but yeah those dotted line boxes were automatically moving and updating themselves

This was with the posthoc-vr-gazer branch of PLC, running from source, and it was running alongside an HMD-Eyes Unity project

Would HMD-Eyes do something like that?

Gotcha

Would that also update the big ROI circles that appear when you go to move the ROI box manually in the eye window?

Because those were still anchored in the corners

(By ROI circles I mean the points that you click-and-drag to adjust the ROI)

Hello! But here's a question. How are the marks synchronized in devices? Is there a synchro block on the "invisible/core"?

Is it possible to get a comparison table?

Analog Timestamps

Hi, I was able to reproduce the issue but unfortunately I was not able to find a stable solution, yet.

Okay. And how is synchronization of streams from three cameras guaranteed: world, eye 1/2? And the synchronization between the stimulus on the screen and the eye camera?

Hello, I have been using your pupil cloud software to analysis some of my pupil invisible recordings and have ran into some issues with the analysis of marker mapper enrichment feature. When I use project events that I created in the video instead of recording.begin and recording.end when I download the results it appears that it just randomly picks a time to start analyzing the data as opposed to the project event that I listed as the from event start. This problem seems to go away as long as I use recording.begin and recording.end as the from event and to event. I was wondering if this is a know issue and that I can be fairly confident in the results as long as I use the recording.begin and recording.end as my settings?

The section.csv file has the correct start time for the chosen project event but data does not show up in gaze.csv or surface_positions.csv until 46 minutes after the start time. I know that there should be data there as when I used recording.begin/end there is data throughout the recording. my project event only cut off 3 minutes from the start and 2 minutes from the end.

the data does end exactly at the end event and has no extra data

will that provide access to the video because it is participant data and the video might have identifing data that I cannot share

identifying*

Hi, I was wondering are there any possibilities for you to add new functionality to the calibration mode so that calibration can be done on multiple screens at the same time (For example, we have three screens and we want to display 5 dots one by one on each screen, or we can calibrate the three screens as a whole)? Or do you have any suggestions on how I could integrate such a feature into the API in an easier way? I'm confused as to where to start with this problem, we only want to use screen markers right now because it is easier and more convenient to be controlled. Thank you for your help!

Thank you! I will try this!

Hi, I am running into issues trying to install from source. Working on a uni project and wanting to build a plugin. Windows 10 install I am continuing to get the following error on setup and I am not sure how to solve it. Worked through the Windows dependencies page word-by-word and still get this trying to start. Any help is appreciated!

player - [ERROR] launchables.player: Process player_drop crashed with trace:
Traceback (most recent call last):
  File "C:\Users\wittw\Desktop\pupil\pupil_jku\pupil_src\launchables\player.py", line 858, in player_drop
    from pupil_recording.update import update_recording
  File "C:\Users\wittw\Desktop\pupil\pupil_jku\pupil_src\shared_modules\pupil_recording\update\__init__.py", line 15, in <module>
    from video_capture.file_backend import File_Source
  File "C:\Users\wittw\Desktop\pupil\pupil_jku\pupil_src\shared_modules\video_capture\__init__.py", line 40, in <module>
    from .uvc_backend import UVC_Manager, UVC_Source
  File "C:\Users\wittw\Desktop\pupil\pupil_jku\pupil_src\shared_modules\video_capture\uvc_backend.py", line 24, in <module>
    import uvc
ImportError: DLL load failed: The specified module could not be found.

I see stuff about DIY eye tracking. Are you able to hook arbitrary cameras up to the Pupil Capture software or do you need to have the Pupil Labs hardware in order to make use of this tracking?

Ok awesome, thanks! I spent some time trying to see if I could make something to connect my cameras through NDSI and I almost have it, but something isn't quite right. My videos will have green/red blocks and stripes flickering over everything when they come through and will intermittently crash the program. I figure it might be easier to just just get it building from source so I can just connect it straight to to the back end