Check out the attached screenshot. This is a problem I occasionally encounter in recorded content, where the timestamps instead of being something sane (and easily manipulated) are these crazy high values.
This seems like the sort of thing Fix Video Timestamps should fix, but it doesn't seem to believe there is a problem, and has no effect.
Where are the timestamps coming from? At first I thought of various power-of-2 overflow scenarios, but that doesn't work. But if you successively divide by 60, 60, 24, 365.25 to get a little over 54.
Bingo. The timestamps seem to be relative to UNIX Year Zero, ie 1-1-1970.
Well that's interesting and all, but the problem still remains. I'm not sure who is generating these (source material? Channels when it encounters weirdness in the source material?)
Either way, can you please modify Fix Video Timestamps so that when it encounters this craziness, it rebases the timestamps to 0, like most Channels content?







