FOVE SUPPORT CENTER

Recording data (Eye/Head)

Comments

2 comments

  • Official comment
    Avatar
    Jeff

    The new version of the FOVE Unity Data Collector on GitHub has a mode to collect at 120hz:

    https://github.com/FoveHMD/UnityDataCollector

    It uses threading and the fove_Headset_waitForNextEyeFrame() api released in SDK v0.16 to do the frame limiting to the camera frame rate.

    Note: frames do not always come in at a consistent 1/120s, but you will receive 120 per second (as long as your machine can keep up). Latencies vary due to USB data transfer, windows preemption, etc.

     

    (this response copied from similar question https://support.getfove.com/hc/en-us/community/posts/360013858314-Increase-amount-of-data-captured-by-eyetracking)

    Comment actions Permalink
  • Avatar
    Jeff

    Hi Jon,

    The headset location is given in the pose every frame. Should be a simple change to add it to the CSV. Let me know if you need help.

    As for 120, Unity is synced to the screen, which runs at 70. So the data collector needs to be threaded separately to receive the full frame-rate, which presents it's own challenges.

    We have a simple C++ example which writes data the full frame rate here: https://github.com/FoveHMD/FoveCppSample/blob/master/DataExample.cpp

    I plan on updating the Unity data collector after the next plugin update comes out (which wont be until next year as the holiday season is happening).

    Note that you can run multiple clients at once, so if you need you can run a C++-driven write-csv type program while running content from Unity.

    0
    Comment actions Permalink

Please sign in to leave a comment.