Time incorrect in Preview + Archive playback

[christ]

Hello,

I've got the Lite version working with a couple of cameras now, and it seems to work pretty well.

However, when playing back footage from a camera the seek bar at the bottom is showing the incorrect time (e.g. 07:15 instead of the actual time of 08:15) - something probably to do with DST settings. The Marking module timestamp on videos shows the correct time.

On my server, running the code

Code: Select All Code

sudo dpkg-reconfigure tzdata

I get

Code: Select All Code

Current default time zone: 'Europe/London'
Local time is now:      Wed May 18 08:18:35 BST 2016.
Universal Time is now:  Wed May 18 07:18:35 UTC 2016.


so it looks like the server is set correctly. I just can't find a setting in Xeoma to make sure the seek bar shows the correct time.

Thanks,

Chris

[Admin_N]

Hello Chris,

Could you please contact our tech support via email? We will figure out the solution for you asap!

[christ]

Will do!

[axelderhund]

I have the same problem. Xeoma was working properly before Daylight savings time was in effect. I emailed customer support on 3-16, and recieved the following response.

Hello!
You can check (or manually change) time zone on Server. ‘Marking’ module’s time is taken from Server.
You can also go to Main menu – Remote access – Users and check time zone there.
If you have any questions please feel free to ask, we'll gladly help!

Best regards,
Ksenia
FelenaSoft Support Team

I responded saying that the issue still persists, after confirming xeoma's time zone settings. I never recieved a response from this email. When clicking on Main Menu - Remote Access - Users, I have confirmed that my timezone is set for (GMT-05:00) Indiana (East)
Current time is now 17:05 (5:05p) (EDT GMT/UTC-4)
Right above the time zone setting, Xeoma says "Current time on the server: " and this time is an hour ahead of the current time and says 18:05 (6:05p)
Time marking, and video playback are giving me a time that is delayed, 16:05 (4:05p) possibly GMT/UTC-5??

I have restarted xeoma, as well as my server, and have also checked that the current time on the server is correct. I have also tried US/Eastern timezone with the same result

Ubuntu ~ user $ date
Sun May 22 17:06:17 EDT 2016
Ubuntu ~ user $ date --utc
Sun May 22 21:06:21 UTC 2016
Ubuntu ~ user $ cat /etc/timezone
America/New_York

If I change Xeoma's timezone to GMT-4 Atlantic Time (Canada) then the text marking will now show the current time (17:05), but recording playback is still showing an hour behind (16:05). Without a bug fix, i'll have to change this back to Eastern Time in November to keep Xeoma's text marking correct. (This will not fix the playback module's time)
It appears that Xeoma is unaware of daylight savings time and is not applying the correct time to the time zones. When daylight savings time is not active (November through March), EST is GMT/UTC -5:00. When daylight savings time is active (March through November), EDT is GMT/UTC -4:00.

Is this a bug within Xeoma? Is it an issue with Xeoma running on Ubuntu?

Sorry about the long feedback, I just wanted to provide as much detail as possible. Any help with this bug would be greatly appreciated.

Thanks!

[jrmymllr]

I have the same problem. Xeoma was working properly before Daylight savings time was in effect. I emailed customer support on 3-16, and recieved the following response.

Hello!
You can check (or manually change) time zone on Server. ‘Marking’ module’s time is taken from Server.
You can also go to Main menu – Remote access – Users and check time zone there.
If you have any questions please feel free to ask, we'll gladly help!

Best regards,
Ksenia
FelenaSoft Support Team

I responded saying that the issue still persists, after confirming xeoma's time zone settings. I never recieved a response from this email. When clicking on Main Menu - Remote Access - Users, I have confirmed that my timezone is set for (GMT-05:00) Indiana (East)
Current time is now 17:05 (5:05p) (EDT GMT/UTC-4)
Right above the time zone setting, Xeoma says "Current time on the server: " and this time is an hour ahead of the current time and says 18:05 (6:05p)
Time marking, and video playback are giving me a time that is delayed, 16:05 (4:05p) possibly GMT/UTC-5??

I have restarted xeoma, as well as my server, and have also checked that the current time on the server is correct. I have also tried US/Eastern timezone with the same result

Ubuntu ~ user $ date
Sun May 22 17:06:17 EDT 2016
Ubuntu ~ user $ date --utc
Sun May 22 21:06:21 UTC 2016
Ubuntu ~ user $ cat /etc/timezone
America/New_York

If I change Xeoma's timezone to GMT-4 Atlantic Time (Canada) then the text marking will now show the current time (17:05), but recording playback is still showing an hour behind (16:05). Without a bug fix, i'll have to change this back to Eastern Time in November to keep Xeoma's text marking correct. (This will not fix the playback module's time)
It appears that Xeoma is unaware of daylight savings time and is not applying the correct time to the time zones. When daylight savings time is not active (November through March), EST is GMT/UTC -5:00. When daylight savings time is active (March through November), EDT is GMT/UTC -4:00.

Is this a bug within Xeoma? Is it an issue with Xeoma running on Ubuntu?

Sorry about the long feedback, I just wanted to provide as much detail as possible. Any help with this bug would be greatly appreciated.

Thanks!

What a relief to see others are having this same problem! I've been struggling with this issue for months, well sort of just putting up with it. I also run server on Ubuntu and have the exact same problem, except I'm in Central time. Support 'fixed' it by changing the timezone, then correcting the time, but that's not a long term solution.

From what I can tell, Linux and Windows report timezones differently. Linux seems to report the UTC offset that had to be applied to get the correct time. Windows reports the non-DST time offset, then applies a DST offset after.....meaning that now the server and client are one hour apart according to the reported offsets. The Android client doesn't exhibit this issue, probably because it's essentially Linux.

I'm looking forward to this being fixed as it's existed since I first started using Xeoma 7 months ago.

[jrmymllr]

Any idea when this is going to be fixed?

[Admin_N]

christ, axelderhund, jrmymllr,

We heard your complaints loud and clear and are currently working on the issue. We are planning to release the fix in the next beta version (or the next after it).

Please subscribe to our newsletter to get announcements and list of changes when new versions of Xeoma are released.

[christ]

Thanks!

[jrmymllr]

christ, axelderhund, jrmymllr,

We heard your complaints loud and clear and are currently working on the issue. We are planning to release the fix in the next beta version (or the next after it).

Please subscribe [url=http://felenasoft.com/en/subscribe/]to our newsletter[/url] to get announcements and list of changes when new versions of Xeoma are released.

Just curious how this will be implemented. I personally think the "current time on the server" being corrected for time zone is confusing; I'd expect that to be the server's time. I also think the archive being corrected for time zone is confusing, because if I'm viewing the client from a different time zone, I'd be thinking in terms of what time is it where the server is. An option to completely disable the time zone correction and just use the server's time, if available, is what I'd do if available.

[johnB]

I don't see this issue is solved in the new version: Xeoma 16.6.6.
Anybody already checked this?

[christ]

Yeah, issue still persists in 16.6.6.

[jrmymllr]

So is there a better idea of when the beta to fix this will get released?

[Admin_K]

Hello!

Please note that Lite version has no renewal period.

As for the issue, if you're using Standard/Pro version, you can go to Main menu - Remote access - Users and check time zone there. Then you need to go to Server (if you're connected remotely) and check time zone there.
Make sure that both time zones are equal. Then you can restart your Server part (if you changed anything in Remote access - Users in Xeoma Client) and check archive time. Did it help?

The issue is connected with DST, we're working on improving time zones in Xeoma.

[jrmymllr]

Hello!

Please note that Lite version has no renewal period.

As for the issue, if you're using Standard/Pro version, you can go to Main menu - Remote access - Users and check time zone there. Then you need to go to Server (if you're connected remotely) and check time zone there.
Make sure that both time zones are equal. Then you can restart your Server part (if you changed anything in Remote access - Users in Xeoma Client) and check archive time. Did it help?

The issue is connected with DST, we're working on improving time zones in Xeoma.

I've gone through all that, and I think others who have posted in this thread said they did the same. The times zones are set correctly but I believe it's because of DST and how Linux and Windows handles that differently. I end up with a a 1 hour time zone discrepancy although each OS correctly reports the time.

[johnB]

Hello!

As for the issue, if you're using Standard/Pro version, you can go to Main menu - Remote access - Users and check time zone there. Then you need to go to Server (if you're connected remotely) and check time zone there.
Make sure that both time zones are equal. Then you can restart your Server part (if you changed anything in Remote access - Users in Xeoma Client) and check archive time. Did it help?

The issue is connected with DST, we're working on improving time zones in Xeoma.

This works for me! Problem seems to be solved. Thanks!