So at first start, it doesn't crash here -- definitely an improvement!
The timestamp field is still horribly wrong It looks like the timestamp value is generated as a readable representation of the same number that is behind the time value -- so it no longer serves it's intended purpose, I think. Should be very easy to fix, I hope.
Also, there is a lot of jitter in the reported (and actual) time between frames: The average update frequency is not 30Hz but something like 26.7 Hz (on my system), averaged over 30 samples. And the inter-frame interval (purely as reported by time) varies a lot; I've seen values as low as 29 mS and as high as 54 mS, but most are in the interval 31mS to 45mS or so.
For now, it is it thus rather difficult to synchronise with other equipment or any presentations.
Hope this can be fixed also?