@erkme73
UI3 only shows the real world timestamp if the length of the video file matches the duration that
Blue Iris reported for the clip. This condition exists because a common configuration of BI (the default configuration, actually) is to combine multiple motion-triggered recordings into one clip, causing the real world timestamps to be absolutely unpredictable for any given location on the seek bar. The intent is to only show these timestamps when they are guaranteed to be accurate within a few seconds.
Assuming you are recording continuously, this
should not have been a problem, so lets see if we can figure out what happened.
I see both your clips you screenshotted are less than 8 hours in length. This suggests those clips were still open for recording. I could see UI3 getting out of sync in this case and thinking it needs to suppress the real world timestamp when it really doesn't need to. Does the timestamp appear reliably for older clips?
It would be helpful if you went through several clips and noted 3 things:
1. Duration shown in the clip list.
2. Duration shown in the seek bar after opening the clip.
3. Whether or not the real-world timestamp is appearing.
If the #1 and #2 values are very far apart, then the real-world timestamp is supposed to disappear.