Open nitin710 opened 4 months ago
Describe the bug the LslMarkerSourceTimestamp and LslLocalTimestamp columns in parsed data are zeros, even with a marker generator present.
LslMarkerSourceTimestamp
LslLocalTimestamp
Expected behavior those columns should contain the extrapolated LSL time.
Additional details
Looking at the raw data files Looks like the source of the problem is the raw data. Looks like the TX packet is for some reason also containing the original LM packet, instead of just having the TLxLC and LCxLM timestamps. Link to relevant code in 1.9.0-alpha Link to relevant code in v1.8.4
TL
LC
LM
To Reproduce Steps to reproduce the behavior:
Describe the bug the![image](https://github.com/EmotiBit/ofxEmotiBit/assets/31810812/c1dcc357-0f1a-4c3c-8c79-9146479800c6)
LslMarkerSourceTimestamp
andLslLocalTimestamp
columns in parsed data are zeros, even with a marker generator present.Expected behavior those columns should contain the extrapolated LSL time.
Additional details
Looking at the raw data files Looks like the source of the problem is the raw data. Looks like the TX packet is for some reason also containing the original LM packet, instead of just having the![image](https://github.com/EmotiBit/ofxEmotiBit/assets/31810812/70a9157d-ea28-4846-b4a8-4dd9c3d6d289)
TL
xLC
andLC
xLM
timestamps. Link to relevant code in 1.9.0-alpha Link to relevant code in v1.8.4To Reproduce Steps to reproduce the behavior: