2012-10-01, 07:17 AM
(This post was last modified: 2012-10-01, 07:28 AM by johnsonx42.)
Sorry, didn't catch this during pre-release... note crazy end-times of all completed recordings. It looks like they've been converted from UTC twice... -7 hours to get from UTC to PDT, and -7 hours again to get to the displayed time.
[ATTACHMENT NOT FOUND]
(edit: to be clear, the displayed times are correct on Pending and In-Progress recordings. only once they're completed does the end-time go wacky)
(edit 2: out of curiousity I looked in the database, and found that for all recordings completed with 2.5.9, the start_time is in UTC, but the end_time has been changed to my local time (PDT))
[ATTACHMENT NOT FOUND]
(edit: to be clear, the displayed times are correct on Pending and In-Progress recordings. only once they're completed does the end-time go wacky)
(edit 2: out of curiousity I looked in the database, and found that for all recordings completed with 2.5.9, the start_time is in UTC, but the end_time has been changed to my local time (PDT))
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV