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.
(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))


Reply With Quote
