2013-12-13, 02:01 PM
Well folks, I uninstalled NPVR, deleted Program Files\NPVR, and reinstalled. This might have affected things but the problem still occurs occasionally, especially during Chase Play. Reproduced multiple times and every time I got similar events in npvr.log, so the attachment above that shows "Timing.info duration 0ms" and "skip to -2 position" still applies.
I also ran the problematic recording that sparked this thread through VideoReDo remux, which "fixed" the problem for that file only. So there may well be some goofy issue with my TS mux platform or something similar.
Might have to wait until sub comes back to provide an expert opinion, but what are the differences between v3.1.1 and v2.5.9 in regard to timing calculations? I'm hoping someone can explain how Timing.info does its thing.
I really don't want to switch front ends but I might give XBMC a try just to see if it acts differently.
Thanks again!
I also ran the problematic recording that sparked this thread through VideoReDo remux, which "fixed" the problem for that file only. So there may well be some goofy issue with my TS mux platform or something similar.
Might have to wait until sub comes back to provide an expert opinion, but what are the differences between v3.1.1 and v2.5.9 in regard to timing calculations? I'm hoping someone can explain how Timing.info does its thing.
I really don't want to switch front ends but I might give XBMC a try just to see if it acts differently.
Thanks again!