The 0.9.40 "sort of" runs here, although not terribly stable. I'm on a MacBook Pro 13" (2012 model, I think).
The server crashes every time it is started up, but on the following (manual) restarts it seems to work -- most of the time.
The first crash usually just reports:
- Code: Select all
**************************************
** The EYE TRIBE TRACKER Server **
**************************************
Version: 0.9.40
[10:33:27.471] INF: Initializing environment
[10:33:27.472] INF: Constructing logfile:
/Users/pgba/eyetribe/logs/20140814114307_7060627573820068203.log
Settings applied:
TCP port: 6555
Connections: local only
Framerate: 30
[10:33:27.486] INF: Initializing the Eye Tribe Server
[10:33:29.352] INF: Eye Tribe Tracker firmware revision is 293
[10:33:29.352] INF: Accessing Tracker device
Segmentation fault: 11
The log just has this at the end:
- Code: Select all
2014-08-14 11:43:09.436|7060627573820068203|I|Validate USB3 host
2014-08-14 11:43:09.436|7060627573820068203|I|Validate camera device stream
2014-08-14 11:43:11.419|5706777682074004294|I|New connection detected [718350090240]
2014-08-14 11:43:11.466|5706777682074004294|I|The device stream has started
2014-08-14 11:43:11.466|5706777682074004294|I|Tracker started
2014-08-14 11:43:11.466|5706777682074004294|I|Creating new connection [718350090240]
I have in a few cases seen server problems on later runs -- which requires killing and restarting the server:
- Code: Select all
[10:33:37.116] INF: Initializing environment
[10:33:37.117] INF: Constructing logfile:
/Users/pgba/eyetribe/logs/20140814114317_7060627573820068203.log
Settings applied:
TCP port: 6555
Connections: local only
Framerate: 30
[10:33:37.126] INF: Initializing the Eye Tribe Server
[10:33:38.813] INF: Eye Tribe Tracker firmware revision is 293
[10:33:38.813] INF: Accessing Tracker device
The Eye Tribe Tracker stands ready!
The Eye Tribe Tracker has been disconnected!
2014-08-14 11:44:17.602 EyeTribe[51147:7703] CameraControl Error: Control request failed: 00000000
2014-08-14 11:44:24.606 EyeTribe[51147:7703] CameraControl Error: Control request failed: 00000000
2014-08-14 11:44:31.611 EyeTribe[51147:7703] CameraControl Error: Control request failed: 00000000
[10:34:51.528] ERR: The Eye Tribe Tracker is not supported!
and the log has this at the end:
- Code: Select all
2014-08-14 11:43:20.926|7060627573820068203|I|The Eye Tribe Tracker stands ready
2014-08-14 11:43:33.202|13530810068463170777|I|New connection detected [718350090240]
2014-08-14 11:43:33.228|13530810068463170777|I|The device stream has started
2014-08-14 11:43:33.228|13530810068463170777|I|Tracker started
2014-08-14 11:43:33.228|13530810068463170777|I|Creating new connection [718350090240]
2014-08-14 11:44:07.574|10816176073546406572|W|The device stream has paused
2014-08-14 11:44:08.575|10816176073546406572|E|The device stream has stopped
2014-08-14 11:44:09.024|10816176073546406572|I|The device stream has stopped
2014-08-14 11:44:09.024|10816176073546406572|I|Resetting the device!
2014-08-14 11:44:09.034|10816176073546406572|W|The Eye Tribe Tracker has been disconnected, waiting for connection
2014-08-14 11:44:09.576|10816176073546406572|I|Validating camera device
2014-08-14 11:44:09.576|10816176073546406572|I|Initializing tracker device
2014-08-14 11:44:09.578|10816176073546406572|I|Setting up device properties
2014-08-14 11:44:24.607|10816176073546406572|I|Setting chosen video format
2014-08-14 11:44:24.608|10816176073546406572|I|Validate camera firmware
2014-08-14 11:44:31.612|10816176073546406572|W|UVC Extensions (tetcode:2258)
2014-08-14 11:44:31.612|10816176073546406572|E|The Eye Tribe Tracker is not supported!
2014-08-14 11:44:31.612|10816176073546406572|E|The Eye Tribe Tracker is not working
2014-08-14 11:44:31.612|10816176073546406572|E|The tracker device has been connected but not working
The UI part often crashes if you let it run for a few minutes -- I have not looked for log files from it, though.
Then a question: The "timestamp" field seems to be from past times

Mine is not in sync with anything I can dream up (dating back to somewhere in 1970), so I guess there is a small bug there also recording the real machine timestamp?
-- Per.