Strange Playback issues

[SteveTyrakowski]

Hi,

In the last month or so, I have been having consistent problems with recordings from the ABC station in Chicago with ATSC which are stored as .TS files.. I have not made changes to the system that has been working well for years.

I first noticed a problem with the 10pm news broadcasts. When I try to use the skip forward/back buttons on the remote, the video playback freezes. I can press the back button and return to the NextPvr menu so it is not a catastrophic freeze.

I am playing back on a Windows 7 client computer with the recordings on another Windows 7 computer acting as the server. If I use xbmc on the same Windows 7 client, I can play the same file and successfully skip thru it. Also, I have an automated process that transcodes the recordings using Handbrake after they are over a day old into mp4 format at usually less than 10% of the original size. Once it has been converted to .mp4 NextPvr will happily skip thru the files. This problem seemed to affect all files recorded on this channel, but other channels did not have the problem.

That was a minor problem that I was able to deal with, but starting last week, I started having a problem with the daily recordings of General Hospital for my wife. While they had the same skipping problem, they suddenly starting having a problem converting in Handbrake which disrupts my automated process that does the conversions. These General Hospital recordings have been successfully converting five days a week for over a year before this started.

My transcodes are done on an Ubuntu computer using as script and HandbrakeCLI. I tried to process one of the problems files on a Windows box with Handbrake GUI version but it did not give a good error message. It just failed to load the video.

Using VLC I can jump around on the timeline with the mouse OK.

It seems that it is some kind of problem with the timing info that is getting stored. I don't know where I should start trying to diagnose this. I will try to check if multiple tuners are involved. I have 3 internal ATSC tuners as well as an HDHomerun with 2 more tuners.

Thanks for any help or suggestions

[johnsonx42]

what version are you running? with patches? post logs.

[Zeb]

It seems that it is some kind of problem with the timing info that is getting stored...I have...an HDHomerun

In HDHomerun setup, if application NextPVR is selected, try Other: ATSC/QAM instead: http://forums.nextpvr.com/showthread.php...post457164

[johnsonx42]

oh, yeah, I always forget about that. The pid filtering sometimes causes this problem.

[SteveTyrakowski]

In HDHomerun setup, if application NextPVR is selected, try Other: ATSC/QAM instead: http://forums.nextpvr.com/showthread.php...post457164

It looks like the offending recordings were indeed made by the HDHomerun and I did have the application set to NextPvr. I just set it to Other : ATSC/QAM so I will see how Friday's recordings fare.

Thanks for the quick answer, hopefully it does the trick.

Steve Tyrakowski

[whurlston]

We've notified Silicondust about the PID filtering when the application is set to NextPVR. Hopefully they will fix it in the next driver release.

[SteveTyrakowski]

It looks like the offending recordings were indeed made by the HDHomerun and I did have the application set to NextPvr. I just set it to Other : ATSC/QAM so I will see how Friday's recordings fare.

Thanks for the quick answer, hopefully it does the trick.

Steve Tyrakowski

Thanks for the help. That seems to have fixed things. I think I must have set the HDHomerun to be the priority for that channel because I wasn't getting a good signal for it on my other tuners, so that's why it only seemed to affect that one station. The other tuners are normally higher priority and were being used for most recordings.

Steve Tyrakowski