Closed andimik closed 5 years ago
Any idea what goes wrong here?
I never dealt with this kind of thing when I wrote the plugin (all the plugin does is exchange commands and tuning status with the device, and supply a stream of RDS groups). It would be interesting to see what happens when the device is connected to another form of live input, e.g. a Si470x stick. I suspect it might affect other forms of live input as well.
Just tried the Si4701 stick: here I get proper start and end times. Will try with the SDR on my end.
Indeed, I can reproduce your issue with the SDR, no idea why it is acting differently. @ChristopheJacquet any ideas?
BTW, same with the group analyzer. Si470x shows proper timestamps, SDR shows 4 digits.
Sources internally supply different kinds of timestamps: One is RealTime
(wall clock time, which formats into a nice string), the other is SequentialTime
(basically the number of bits received so far, modulo 10000). The latter is used for file input with no time stamps.
I wrote the SDR source around an existing source for file input, and I was blissfully unaware of the difference then. Events (which bear timestamps of one or the other kind) are just piped through.
I’ll try and fix this by swapping out the events from the SDR source, giving them a proper timestamp.
Fix submitted as pull request #29.
I confirm this works. Sorry for the delay.
I just realized that the time for traffic events is only displayed correctly when using a playback file (see right window: 10:13:26 start and 10.14.24 end). In the live mode with RTL stick the time is a 4-digit number.