You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @c1ngular
Thanks for your interest in the project. Yes, at some point it will be useful to return timestamp as returned by the device. There is so much possible, so little time 😄
Hi @vladimirvivien
I'm also interested in getting the timestamp from the device.
In my application (eye tracking), I'm processing each frame individually and could therefore "live with" storing the last timestamp in the Device struct in device.go. Then I could just read the timestamp from the Device struct for each frame that my app is processing.
Would you consider a PR for this if I implemented that?
I can very understand your time problem very well 😉. I can't spend the time on a fork of my own and would rather contribute to your project. If you have other thoughts on preserving the device timestamp, I'm happy to hear and will consider if I can do it.
i see from ffmpeg v4l2 , it has :
/
#define V4L_TS_DEFAULT 0
/*
/
#define V4L_TS_ABS 1
/*
*/
#define V4L_TS_MONO2ABS 2
is it implemented in this project , i think it might be a useful feature .
P.S. this project evolves a lot since my last visit , great job .
The text was updated successfully, but these errors were encountered: