Recordings have wrong time

[dvasco]

When I setup my xmltv file years ago while using GBPVR I used +0000 for the offset time. When I upgraded to NPVR I used the same xmltv setup. Now if I import the recordings into a new install of NPVR the time of the recordings is off by 6 hours. What can I do to correct the times of the recordings?

Thanks in advance.

[Kiwi]

When I setup my xmltv file years ago while using GBPVR I used +0000 for the offset time. When I upgraded to NPVR I used the same xmltv setup. Now if I import the recordings into a new install of NPVR the time of the recordings is off by 6 hours. What can I do to correct the times of the recordings?

Thanks in advance.

U can try to edit the xmltv file to the appropriate times before importing the file.

[dvasco]

Then I would have to do that for the start and end time for about 100 files. There's no way to bulk change the times? I am a bit confused on why the times are the same in the original system as a new install on another but the original system knows to subtract 6 hours and the new install doesn't know to do that for the imported files.

[sub]

How exactly are you trying to import these recordings?

NextPVR is based on UTC, where as the old GBPVR software used local times. For the most part it should handle the conversion automatically if it knows the recordings being imported are from GBPVR.

[dvasco]

I should included the following statement in my original post "After upgrading from GBPVR to NPVR the correct times were maintained" It is only when I do a fresh install of NPVR on a new system and I import the recordings from an existing install of NPVR.

Would tricking NPVR into thinking the recordings are from GBPVR fix the recordings times?

[BrettB]

How exactly are you trying to import these recordings?

Are you, by chance, using Vidimport to create the import file? It does not generate the recording times properly for NextPVR's import files unless your local timezone is UTC+0 because it uses the local timezone not UTC for the times in the generated .xml file.

[dvasco]

I use the import recordings option in the Settings menu of NPVR and I point to the recording-backup.xml file from the old NPVR.

[sub]

Are you sure the timezone is set correctly on both PCs? ie, the one that originally exported the file, and the new one trying to import.

I've not seen any reported issues with importing recordings-backup.xml from NextPVR

[danorum]

Are you sure the timezone is set correctly on both PCs? ie, the one that originally exported the file, and the new one trying to import.

I've not seen any reported issues with importing recordings-backup.xml from NextPVR

I just had this happen to me when I was moving files from one drive to another. I used the export from the menu in NextPVR, did a find/replace to change f:\ to g:\ in the xml file, and then did an import (on the same computer). The result was that the recording time is "off" on the imported ones.

This isn't a huge deal for me, because I won't key off the time recorded much anyway. Just wanted to report it.

Dan

[danorum]

I did some more debugging on this and I think I see what is happening. If I look at a recording that has not been imported (recorded since I switched drives), I see similar times in the recording object and the recording cached event details. Both of these show times in UTC. However, if I look at one that has been imported, the recording.CachedEventDetails are in UTC, but the recording.starttime and recording.endtime are in my local time.

I wrote a .NET console app to get recording info. 2585 was recorded after the import and the rest are imported shows. I did delete a bunch of rows, but they all showed the same thing. The details from the guide are correct, but the start and stop time of the actual recording have been stored in "local time".

I may try writing an app to clean this up as long as recording.StartTime and Recording.EndTime are writable, which I think they are.

EDIT - It was writable, so my code checked to see if there was more than 5 minutes difference between the recording start time and the guide event start time and if so, I added 5 hours (because of my time zone) to the recording.StartTime and recording.EndTime and then called recording.save(). Now all my recordings show the correct time in NextPVR. The exported XML looks correct with all Z times, so it is probably code in the import that is changing it to local time.

Dan

Code:

OID,recording.StartTime,recording.EndTime,CachedEventDetails.StartTime,CachedEventDetails.EndTime
2666,9/8/2015 6:59:00 PM,9/8/2015 8:02:00 PM,9/9/2015 12:00:00 AM,9/9/2015 1:00:00 AM
2665,9/8/2015 7:59:00 PM,9/8/2015 9:02:00 PM,9/9/2015 1:00:00 AM,9/9/2015 2:00:00 AM
2664,9/8/2015 8:59:00 PM,9/8/2015 10:02:00 PM,9/9/2015 2:00:00 AM,9/9/2015 3:00:00 AM
2663,9/8/2015 10:34:00 PM,9/8/2015 11:39:00 PM,9/9/2015 3:35:00 AM,9/9/2015 4:37:00 AM
2662,9/9/2015 1:59:00 PM,9/9/2015 3:02:00 PM,9/9/2015 7:00:00 PM,9/9/2015 8:00:00 PM
2585,9/10/2015 3:34:01 AM,9/10/2015 4:39:00 AM,9/10/2015 3:35:00 AM,9/10/2015 4:37:00 AM