Can't Skip After v2.5.9->3.1.1 Upgrade

[Braklet]

Migrated from v2.5.9 to 3.1.1 using the general MSI package, and then applied the NPVR 3.1.1 R1 rollup.

Most functions seem to work well, and I find the new OSD TV Guide super useful (thanks!).

However, a couple of basic play functions that I have come to rely on either don't work at all, or are very fragile. I'll focus on skip in particular since I see what appear to be identical errors in the npvr.exe front end.

I can initiate play on normal recordings, but any time I try to mess with skip functions, either short (via >> IR remote key) or long (via ->| IR remote key), NPVR pops up an unhandled exception with a "divide by zero" error. When this happens, the only recovery is to kill the npvr.exe process completely, I've found no other alternative.

This is really bad during chase play, where I simultaneously play a file that is currently recording. Popups are always unhandled exceptions with divide by zero errors.

Last night I captured npvr.exe log data from one such event where I played a normal, completed recording. I then attempted to skip 50 minutes ahead with my usual technique on the IR remote: 5, 0, ->| . This immediately brought forth the unhandled exception/div0 popup. I extracted the corresponding log entries and attached them to this posting.

I'm a little surprised I wasn't able to find similar reports in the forae... hope I'm not out here on my own with this one.

Let me know if I can extract any additional information. Thanks!

[Braklet]

By the way, this HTPC is running 32 bit Win XP SP3. v2.5.9 worked beautifully.

[Reddwarf]

Does it work if you use keyboard instead, ie ctrl-right/left arrow and ctrl-f/r?

[Braklet]

Does it work if you use keyboard instead, ie ctrl-right/left arrow and ctrl-f/r?

Won't be able to try this for a few hours, but I'll see.

[Braklet]

My gut feel is that this is not an IR remote interface problem since most of the other buttons function as they did with v2.5.9.

Here is a log extract from my attachment which appears strange to me:

Code:

2013-12-11 22:31:41.704    [DEBUG][1]    OnKeyDown() called: {CTRL}Right, Control
2013-12-11 22:31:41.704    [DEBUG][1]    GetDuration returning 0
2013-12-11 22:31:41.704    [DEBUG][1]    User is trying to skip.
2013-12-11 22:31:41.704    [DEBUG][1]    Current position is: 5.6528754234314
2013-12-11 22:31:41.720    [DEBUG][1]    Asking for position: -2
2013-12-11 22:31:41.720    [DEBUG][1]    Pause()
2013-12-11 22:31:41.751    [DEBUG][1]    SetPosition(-2.000000)

If you look earlier in the attached log you'll clearly see evidence of button pushes for "5" and "0" . Ctrl-right should skip forward, but position "-2" sounds backward. Anyway, NPVR.exe knows I'm trying to skip around in the recording but coughs up the unhandled exception/div0. Guessing that something is broken in the timing calculation?

[johnsonx42]

yes, not sure how you're getting it to try skipping to position -2, and your duration is showing 0. That's clearly the source of the resulting div0 exception, but I don't know what could lead to that in the first place. You're the only one having this problem, so clearly it's something to do with your system... but what?

There were some changes to the way timing is calculated in 3.1.1, so I'm going to start by surmising that somehow one of your files didn't get updated so one side of NPVR isn't matching up with the other side. Try uninstalling 3.1.1, then wipe out your C:\Program Files\NPVR directory. Then re-install 3.1.1 and the R1 rollup (shutdown the recording service in between, as the installer starts it for you), and see if it still happens.

[mvallevand]

I'd start with this

Timing.info reports duration 0ms

You might need to delete the timing file and if necessary see what writeTime creates.

Martin

[Braklet]

Oh heck, never like it when I'm the only one seeing a problem.

If file detritus could contribute to the problem I'm more than willing to attempt an uninstall/delete/install cycle, but in this case what's the best way to preserve my settings? I know I tweaked a lot of stuff manually in order to preserve my analog recording profiles. Just copy out all the *db3, *xml files, reinstall and copy them back?

Or is it enough to do as Martin suggests and delete "timing.info" ?

Thanks for thinking about it, at least.

[johnsonx42]

deleting the timing.info (and optionally writing a new one with WriteTime) will fix the one file, but it seems all your files are being created with bad timing.info. If sub were around he could write a patch to reject ridiculous timing.info data (like duration=0ms) and revert to calculated position info, but I think he's still away on business for a few more days at least.

so I'm suggesting a possible fix to the root of the problem, martin is suggesting a fix for the resulting symptoms. Both are probably needed, and certainly the results of deleting the timing.info for a file and then playing it would indeed confirm that the transport stream in the file is ok so we're just dealing with timing data issue.

As to the re-install procedure I suggested, it won't affect your data or settings as I only said to wipe the program directory, not the data directory. It will just lay down a fresh copy of all programs and .dll's.

[Braklet]

deleting the timing.info (and optionally writing a new one with WriteTime) will fix the one file, but it seems all your files are being created with bad timing.info.

OK, now I'm definitely outside my comfort zone. Is timing.info an attribute of each recording, an entry in npvr.db3, or a separate file? This is the first I've heard of WriteTime, too; is that a separate utility, on the Wiki, or ... ?

As to the re-install procedure I suggested, it won't affect your data or settings as I only said to wipe the program directory, not the data directory.

Gotcha, I just spaced out on the different directories; that's actually closer to my comfort zone. Will have to fiddle around with this tonight & see where I end up.

Kinda sucks being the only one with a problem. Thanks again for the help.