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!