Hello, I am trying to run the Pupil Labs Neon on a desktop to eliminate the delay when transferring data via the API from a smartphone. When I run the software from the Pupil GitHub repository, the Scene camera connects successfully, but the Eye cameras do not. When I click on the 'Neon sensor module' directly, an error message appears, stating it is "already used or blocked" (as shown in the attached picture). How can I solve this issue? Thank you.

great, thank you for the update.

Hi, I had a question about post-hoc eye-tracking. I just made a recording with the pupil-core camera in the 120 FPS (400, 400) resolution mode. Before I made this recording, I checked the lighting in Pupil Capture. I noticed the pupil tracking here was perfect. After making the recording and reconstructing the video as a .avi file, I then fed it into a Python script that I have written, using Pupil Labs detectors library to extract the pupil from this playable video. Here, I found the performance much worse than what I saw live. I was wondering if anyone had any thoughts on how to improve this? I'm also open to improving the conditions of my image as well. Here is a sample image with poor pupil detection

Hi @user-cdcab0 Can we process additional LSL streams we have recorded using Pupil Capture using Pupil Player? I have an extra event marker stream coming from MATLAB that I have recorded simultaneously with pupil and gaze data. I wanted to plot it over the gaze data and use it to parse the gaze data into trials or epochs. Additionally we would also like to process this data along with EEG we have collected. Can the pupil recordings be integrated into brainstorm or EEGLAB?

Hi @nmt @user-cdcab0 We wanted to reduce the size of Pink dot with yellow border showing fixations and eye postion on the pupil capture screen, so that we can see more exactly where the participant is gazing. How can we do that?

Hi everyone, I ran a test using the real-time-blink-detector with a NEON recording (https://github.com/pupil-labs/real-time-blink-detection) and noticed that, ( besides taking quite a long time to finish analyzing the recording), it also detected many more blinks than what the Neon Player reported. My question is: is the blink detection algorithm used in Neon Player the same as the one used in the real-time-blink-detector? Thanks a lot!

Hello! I have another question about this. In the gaze.csv file, the eighth column is the blinkID (which corresponds to the one in the blinks.csv file), but at those indices there are also gaze_x and gaze_y values in pixels. Are those values generated through some kind of interpolation? Maybe something done by the AI algorithm? With the Pupil Core, I found it useful to have the confidence value. I had considered using the eyelid aperture measurement, but in all my recordings this information is NaN. Many thanks for your help!