Playback zero length during recording

[sub]

Ah, yes - now you mention it, I think there was. ceandra, do you have the latest patches installed?

[ceandra]

sub:

I got patches "NPVR 3.1.1 Patches R1a.zip"

However, it looks like nshared.dll did not copy over (in use by another process). Seems like I tried even with services stopped. I'll have to try again after tonights' recordings are done, a few hours (3 hours from now).

Would that have the fix?

Chuck

[ceandra]

OK, I got nshared.dll to update by stopping service. Rebooted the machine after just for good measure. Recording started, within first 2-4 minutes I check, and same result. o:oo:oo on right, increasing number on left.

Let me know if I don't have the right patches.

Chuck

[ceandra]

BTW, if I go in through the web page from another computer and "play" the in-progress recording, it plays fine (in VLC), can move slider to anywhere I want. So it does not seem to be an issue with the ts file.

Chuck

[sub]

If those patches don't help, then it's probably a different problem. We'll probably need to revisit it in a few weeks when the next release is out.

[mvallevand]

The fix was in the writer not NShared. You'd need to check Timing.Info to see if it is a new problem.

Martin

[ceandra]

Searching a bit, I found this:
http://forums.nextpvr.com/showthread.php...-1-Upgrade

Looks like it was a similar problem to mine. IN this thread, the OP was asked:
After updating from 2.5.9 to 3.1.1, did you perhaps reintroduce the older version of npvr.db3?

I have to say that I used the external tool to get my recording information from gbpvr tonpvr. Is it possible this results in a corrupt/old db3 file? If so, what shoudl I try?

How do I check timing.info?

Thanks all for the quick attention!

Chuck

[ceandra]

OK, figured out timing.info from that other thread. dir/r did not work, but opened current ts file (still recording) in notepad. Here is the first bit of the timing.info:

0,0
859,2180800
1719,3647200
2594,5113600
3453,6467200
4312,7896000
5203,9287200
6078,10791200
6953,12332800
7828,13836800
8687,15303200
9547,16882400
10406,18461600
11281,20078400
12156,21620000
13031,23161600
13891,24665600
14750,26244800
15609,27711200
16469,29403200
17328,30982400
18187,32674400
19047,34366400
19906,35870400

So, it appears to be a different issue, as timing info is not zeros in col 1.

Verified the file is still growing, and the problem still exists.

Chuck

[ceandra]

Sub:

I finally upgraded to the late March 2014 version, anticipating doing some debugging. However, the issue is gone. It was still definitely a problem prior to the update, as I tried "chase mode" for today's NASCAR race. Now, at least with "quick record", the problem appears gone, on both HD and SD recordings. I will keep an eye on it, but it looks to be resolved.

Chuck