2011-03-06, 06:17 PM
Sub, I suspect the Timing.Info is not always correctly reporting the time and allow precision skip on time points, and in addition the total running time seems off.
You did add a patch that tries to correct for timeline problems http://forums.nextpvr.com/showthread.php...post398751 but it I guess it only relates to comskip and not resume etc. I note from that thread that you don't think it is a problem but I do trust the comskip times as being the most accurate times we have.
In an unrelated thread on NMT skipping I was noting that the NMT was finding (based on the actual PTS) a 5 second difference on skips based on a requested time. Roy has done some further investigation http://forums.nextpvr.com/showthread.php...post405904 and really looks like NPVR perhaps because Timing.Info is wrong is not showing the correct time.
I don't see any gap on my recording but I get nearly pin point jumps so it is difficult to argue with your conclusion, but something is causing differences.
Martin
You did add a patch that tries to correct for timeline problems http://forums.nextpvr.com/showthread.php...post398751 but it I guess it only relates to comskip and not resume etc. I note from that thread that you don't think it is a problem but I do trust the comskip times as being the most accurate times we have.
In an unrelated thread on NMT skipping I was noting that the NMT was finding (based on the actual PTS) a 5 second difference on skips based on a requested time. Roy has done some further investigation http://forums.nextpvr.com/showthread.php...post405904 and really looks like NPVR perhaps because Timing.Info is wrong is not showing the correct time.
I don't see any gap on my recording but I get nearly pin point jumps so it is difficult to argue with your conclusion, but something is causing differences.
Martin