nuvexport fails to export recordings because of off by one hour starttime

[otto at kolsi dot fi]

For some recordings, nuvexport gives a off by one hour starttime to mythtranscode:

WRONG:
/usr/local/bin/mythtranscode --showprogress -p '0' -c '1004' -s '2007-03-02T21:00:00' -f "/tmp/fifodir_3294/" --honorcutlist >&1

CORRECT:
/usr/local/bin/mythtranscode --showprogress -p '0' -c '1004' -s '2007-03-02T20:00:00' -f "/tmp/fifodir_3294/" --honorcutlist >&1

This seems to be related to daylight saving time. If a recording was made during "winter time" and is tried to export in "summer time" this problem occurs.

All other myth programs, mythweb etc. handle these recordings fine. In DB in recorded table the starttime is the correct one but for some reason nuvexport gives an incorrect time to mythtranscode.

[xris]

Pretty sure I fixed this a couple of months ago. It's actually a feature lacking in perl. The workaround was to use mysql for time calculations instead of the proper perl module.