Schedules Direct - wrong movie year data?

[daneo]

Hi Sub,

I have a problem on v5 by where the movie year information is incorrect and off by one year - the top image is from my v4 installation, and the bottom is from my v5 setup.

   

The correct date is 2013 - see below from a postprocessing log snip I took last year during a v4 recording session. 

Code:

190524-2305 Postprocesing called with "H:\Recordings\Parker (2013)\Parker (2013).ts"
----------- file parsed with 576 height and 3947353 bitrate
----------- deleting DNR "H:\Recordings\Parker (2013)\"

How can I validate if this is a SD raw data issue compared to some processing when the EPG is populated?

I can provide both DB files if you need them.

Thanks,
 Dane

[mvallevand]

It should be 0101 because it is just year in a date field. Is there time on the v4 version could be utc correction.

Martin

[daneo]

Hi Martin,

you're right - it's off by one hour exactly - pushing the date to the next year.

Top is v4, bottom is v5

   

[sub]

What timezone/country are you in? This is Schedules Direct right?

[sub]

Nevermind - I can see you're in Germany.

[sub]

Is it actually displaying the wrong year anywhere?

It's being stored as UTC. It should be converting it to localtime when it needs to display it.

[daneo]

Hi Sub,

it's writing the files with the name.(date) convention for movies, and all of the v5 movies are being saved with the incorrect year - and it's nuking my recognition scripts for material I already have, as I compare directory names and bitrates to see if I need to keep or delete something.

NPVR v4 records everything with the correct date (not sure if you get the exact release date from SD, or just the year) but v5 is putting the wrong data on the drive.

Regards,
Dane

[sub]

Ah ok I get you. I’ll check it. My epg doesn’t typically have the year available so I hadn’t noticed. I wouldn't have seen it anyway, since I'm in a timezone ahead of UTC.

[sub]

This updated nshared.dll should fix the issue.