Skip to content

Releases: labstreaminglayer/App-PupilLabs

Pupil LSL Relay Plugin v2.1

05 Feb 14:49
83e8a92
Compare
Choose a tag to compare

This release adds support for Pupil versions 3.0 and later.

Pupil Invisible LSL Relay v1.0

12 Nov 21:05
b921ee2
Compare
Choose a tag to compare

We are happy to release our second LabStreamingLayer integration: Pupil Invisible LSL Relay. It is a stand-alone application that relays gaze data from Pupil Invisible without requiring Pupil Capture.

Pupil Invisible LSL Relay vs Pupil Capture LSL Relay

Note: Pupil Invisible LSL Relay is not a replacement for the existing LSL relay plugin but an additional LSL application that serves a different use case than the existing LSL relay plugin.

In order to avoid confusion, we have renamed the existing "Pupil LSL Relay plugin" to "Pupil Capture LSL Relay plugin" and have moved it to the pupil_capture subdirectory. Please see the README files for more details.

Data Format

The application opens a single outlet named pupil_invisible that follows the Gaze Meta Data format. Specifically, it features three channels:

  • x: horizontal component of the gaze position, unit: pixels
  • y: vertical component of the gaze position, unit: pixels
  • pi_timestamp: Original gaze timestamp, in Pupil Invisible time (unix epoch by default), unit: seconds

Pupil LSL Relay Plugin v2.0

29 Mar 10:32
Compare
Choose a tag to compare

We are excited to announce the all new 2.0 version of the Pupil LSL Relay plugin for Pupil Capture. It features an unified LSL outlet following the official Gaze Meta Data format. The plugin also synchronizes Capture's own clock with the pylsl.local_clock(). This allows the recording of native Capture timestamps and removes the necessity of manually synchronize timestamps after the effect.

Features

  • Unified LSL outlet, name: pupil_capture
  • Support for official Gaze Meta Data format
  • Time synchronization with pylsl.local_clock()^1
  • Use of Capture's built-in correlation functionality for the generation of binocular data

^1 Caveat: The time synchronization will potentially break if other time alternating actors (e.g. the Time Sync plugin or hmd-eyes) are active. In these cases, it is recommend that the actors follow Capture's clock instead of changing its timebase.