I can play one of the problem files now, but not twice in a row. If I try to play it a second time, after I hit Play, the screen goes black for a half second and then puts me back at the menu. Same as what it was doing before.
If I exit and relaunch NextPVR I can play it again.
I'm heading offline for the evening. If you happen come up with another one to try, I'll try it tomorrow morning my time. I'll test on this client and also find some recordings that don't work on one of my other clients. I'll then test those on the patched client and report back.
There sure are several blocks of empty ts blocks in that sample file ~18k in total. What drivers are you using? I tested a few of my 2.4.x samples from my HDVR and I didn't have any sync errors.
2012-03-25, 01:08 PM (This post was last modified: 2012-03-25, 01:26 PM by smajor.)
That sample was recorded with, 1.6.29294, although the latest is 1.6.29353. Many of the others were likely early 1.6x series going back to 1.5x probably.
Time Warner also compresses the hell out of their signals, I don't know if that's part of it. When you're the only game in town, you can get by with the bare minimum of service. Time Warner excels at this.
mvallevand Wrote:There sure are several blocks of empty ts blocks in that sample file ~18k in total. What drivers are you using? I tested a few of my 2.4.x samples from my HDVR and I didn't have any sync errors.
The patch works. Of the sampling of 5 recordings I found that didn't play, all 5 played just fine on the client.
Unfortunately, trying to play any affected file a second time requires exiting NextPVR and relaunching it. I tried playing around with different decoders to no avail, all of which should be in the attached client/sever logs. The last thing I did was try to play Kitchen Nightmares twice in a row, so you should be able to find that.
Any recording that wasn't a problem can be played over and over again.
You might need to try creating a c:\temp directory, and setting HKEY_LOCAL_MACHINE\Software\NPVR\LogSlipFile=1, then reproduce the problem and post the c:\temp\reader.log
sub Wrote:I can see any reason for it in those logs.
You might need to try creating a c:\temp directory, and setting HKEY_LOCAL_MACHINE\Software\NPVR\LogSlipFile=1, then reproduce the problem and post the c:\temp\reader.log