Recording start time is off for some archived shows

[will]

Hello,

I moved some TV recordings to a different drive so I could archive them and free up recording space. The shows I moved had a 5 minute padding on the end of each recording. So if the show aired at 9pm it would record from 9 to 10:05pm.

However, once I moved the show to a different drive, SageTV now shows it as having the five minute padding in the beginning. So the show's recorded time is 8:55pm to 10pm. The entire show is there and I just have to rewind five minutes to start at the beginning but it seems odd.

Does anyone know of a way to fix this or know what caused it?

[graywolf]

I would be interested also.
Happens for all our recordings that have padding also (at start and/or end) since they record on the sagetv pc then get moved to unRaid box

[EnterNoEscape]

I think when it doesn't have any better clues about start time, it goes based on the creation date of the file.

[BobPhoenix]

This problem (feature?) has existed since at least v6 SageTV for me.

[Fuzzy]

Originally Posted by EnterNoEscape

I think when it doesn't have any better clues about start time, it goes based on the creation date of the file.

Sort of.. It think it uses the files lastmodified, and sets the end of the airing to that time. This explains why the end of the recording is lined up with the end of the airing, and the beginning floats 5 minutes earlier.

[wayner]

I think it also likes to use the creation date of the file regardless of whether it has other metadata. I have a process where I archive shows externally from SageTV using Handbrake, but I was keeping the file ID number in the filename which was allowing it to keep the metadata. But it was giving me timeline issues until I added some code to change the file creation time on the archived file to be the same as the file creation time on the original SageTV file.

If anybody wants to they could play around with this by changing the file creation time in Windows - but I think you need a utility to do this as it isn't possible, or at least not easy to do, in Windows or from a CLI. I am not sure how to do this in Linux - maybe with chattr?

[graywolf]

Linux it would be the touch cmd
Would have to look up the syntax

[wayner]

Originally Posted by graywolf

Linux it would be the touch cmd
Would have to look up the syntax

Touch changes the last accessed property - I don't know if it can also change the file created property.

[graywolf]

Checked. The touch cmd can modify the access (last time read), modify (last time content modified), or change (last time file metadata changed [ie permissions])

Maybe sagetv linux uses the modify date/time. Just a guess

[Fuzzy]

Originally Posted by graywolf

Checked. The touch cmd can modify the access (last time read), modify (last time content modified), or change (last time file metadata changed [ie permissions])

Maybe sagetv linux uses the modify date/time. Just a guess

Pretty sure it doesn't matter windows or linux, the Java File object only has a method for returning the lastmodified time, so I'm pretty sure that's what sage uses no matter what platform it's on. I don't think actual created time is used for anything. (it can be done via readAttributes, but it is more complicated, and I don't remember seeing that anywhere in seeker.java, or anywhere in sage at all).

[will]

Originally Posted by Fuzzy

I don't think actual created time is used for anything. (it can be done via readAttributes, but it is more complicated, and I don't remember seeing that anywhere in seeker.java, or anywhere in sage at all).

Hmm, what if we removed the metadata from the file completely. The timeline should work fine then, correct?