Skip causes fast-forward to the end of the file

[madbrain]

I just installed NextPVR this weekend. I have two Hauppauge cards - one HVR-1800 and one QuadHD, total of 5 ATSC tuners.
I ran into an issue where any skip causes fast forward to happen very quickly to the end of the file.
This is the same with the right arrow or "skip track" media key. This happens inconsistently, but most of the time. Same problem if I click somewhere in the timeline at the bottom. Makes it very hard to use the PVR.

I am using NextPVR 4.2.5 .  CPU is Ryzen 2600. GPU is nVidia GT1030. Windows 10.

I did some google searches before posting here, and found a pre-existing bug that was fixed in 4.2.1 :
From https://www.videohelp.com/software/NextP...on-history :
- fixed issue where sometimes when skipping back during playback, it could start fast forwarding very quickly to the end of the file

What I'm seeing is the same problem, but with skip forward. Maybe only half of the bug was fixed ?


Also, today I installed Comskip . The problem also occurs at the automatic commercial skip. It first skips to the right spot after the commercial, but then plays extremely quickly all the way to the end.

[mvallevand]

If you are new to NextPVR you should be using version 5.

Typically skipping and seek problems can be fixed simply by installing the 32 bit LAV decoders https://github.com/Nevcairiel/LAVFilters/releases and configuring NextPVR to use them

If that doesn't help logs are required.

Martin

[madbrain]

If you are new to NextPVR you should be using version 5. 

Typically skipping and seek problems can be fixed simply by installing the 32 bit LAV decoders https://github.com/Nevcairiel/LAVFilters/releases and configuring NextPVR to use them

If that doesn't help logs are required.

Martin

I did try version 5, but the download link pointed to a beta file. I tried to use it, and it wouldn't detect my 2 Hauppauge devices. I assumed it was a work in progress and downloaded the latest version 4 at that point.

I am using the LAV filters for everything except AC3, as the LAV filters downmix to stereo for AC3, whereas the Microsoft DTV decoder bitstreams AC3 to my receiver over HDMI so I can hear 5.1 in my 15 speaker home theater.

I thought I had attached the logs previously in an update to my post, but that apparently didn't take. Here they are.

[sub]

Does this updated file help?

[Esch]

I made a post on here about a year and a half ago with the EXACT same issue. At the time I felt I was waved off and was told it was my tuner that was the problem and not this program. No one ever mentioned changing the decoders to LAV Filters.

THANK YOU MVallevand for giving the link to those. I switched to LAV and have had zero issues. This has been an ongoing problem for the past year and a half and it has been steadily getting worse as time went on. This fixed my problem. THANK YOU!!!!

Now one question. I'm using 4.2.5. What is different with version 5? I was never given an update warning through the program so didn't know it existed till recently.

[sub]

Now one question. I'm using 4.2.5. What is different with version 5?

v5 is pretty much a rewrite. It's now a multi-platform app, able to run on Windows, Linux, Mac, and Docker (for running on NAS drives etc). The main configuration UI is web based.

[mvallevand]

Now one question. I'm using 4.2.5. What is different with version 5? I was never given an update warning through the program so didn't know it existed till recently.

The main difference is 4.2.5 is the end of the road.  If you are happy with it fine, but don't expect any significant changes or fixes.  There is already a year of development in v5 so in many areas behind the scenes it is better.

Martin

[Esch]

I spoke too soon about the issue being resolved. I had about a week where I didn't have any issues, but now it's back. The decoder setting wasn't the answer, unfortunately. Bah. :/

[Bobins]

This seems to be an issue with LAV decoders and NPVR. I have experienced this issue many times and it also occurs if there's a "blip" in the recorded file data (not uncommon when recording from satellite or internet IP). I'm sure when you try to skip it's probably something in the data flow interruption that's triggering the problem.

If you use the Microsoft decoders it doesn't seem to go into FF but the video may freeze instead.

Regrettably this problem is also present in V5 as Sub says that part of the code hasn't changed much between versions.

I have asked Sub to please look at this again as I know I'm not the only one with this issue.
(see https://forums.nextpvr.com/showthread.php?tid=60458)

[Esch]

When I first started having these issues I was using the Microsoft decoders, then things were great the first week after switching to LAV, but now right back to the same problem. All it takes is a little digital hiccup, and boom, off to the races.