Can I reinstall Version: 5.2.7.220410?

[benhase]

I have Version: 5.2.7.220410 installed on two Windows 10 PCs.
I Installed the latest version on one of the two PCs and I can no longer reliably view my HDhomerunPrime tuner on the newer version 6.x of NextPVR.

I notice three differences:
1. If I select a Channel to view in NextPVR, NextPVR will play video (always on tuner 2 numbered 0, 1, 2) for a few seconds and then stop with a streaming error.
2. If my third tuner (tuner 2 numbered 0, 1, 2) is in use by Windows Media Center (WMC). Selecting a Channel in NextPVR fails (the video stream drops immediately).
3. If I move WMC to tuner 1 (by starting NextPVR before WMC) NextPVR will play video for a few seconds and then stop with a streaming error (like #1).

I'd like to reinstall  Version: 5.2.7.220410 and verify my issues go away.

[mvallevand]

No need, there is a patch for situations where users run two PVR systems against one HDHR and NextPVR can't access the tuner it request.

https://forums.nextpvr.com/showthread.ph...#pid577728

Martin

[benhase]

No need, there is a patch for situations where users run two PVR systems against one HDHR and NextPVR can't access the tuner it request.

https://forums.nextpvr.com/showthread.ph...#pid577728

Martin

Thank you for the patch. I added it to Version: 6.1.1.221106 in C:\Program Files\NextPVR (removing the old NShared.dll) and now I get the old V5 behavior of rotating to the next free tuner on V6.

I have a second problem (I hoped they were related but it appears they are not).
When using the Web App I typically (after a variable number of seconds) I get in RED "Streaming Failed (transcoder exited)" the video freezes and the tuner is deselected.
Most times I don't get the RED error message, just the video freezes and the tuner is deselected
I don't think this happens on the Desktop App (but maybe I haven't waited long enough yet).
The Web App seems to run longer before freezing on 5.2.7.220410 vs. 6.1.1.221106 but I see the freeze on both.

[mvallevand]

You would need to provide the zipped logs creating them just after the problem occurs.

Martin

[benhase]

You would need to provide the zipped logs creating them just after the problem occurs.

Martin

Here are the log files. I ran a test at 4:00pm (16:00) where I clicked on Channels to view the stations.
I started with 659-CLEO which doesn't seem to fail, then switched to 229-CNNHD which failed.
Then I went back to 659-CLEO (okay) then back to 229-CNNHD (failed).
Then back to 659-CLEO (okay) then to 240-FNCHD (which failed).
Then back to 229-CNNHD (failed) then to 240-FNCHD (failed).

This looks like the typical error:

#EXTINF:4.170833,
../temp/CNNHD-7ec2d5890ca64ce09cc93ba399e258ac3.ts?sid=3f826feb-9360-4d6e-8ace-b9cc23a05abe

2023-01-21 16:03:28.809 [DEBUG][36] Got request [::1]: /temp/CNNHD-7ec2d5890ca64ce09cc93ba399e258ac3.ts
2023-01-21 16:03:29.319 [DEBUG][57] [FFMPEG]: frame= 1553 fps= 79 q=38.0 size=N/A time=00:00:27.57 bitrate=N/A speed= 1.4x   
2023-01-21 16:03:29.436 [DEBUG][57] [FFMPEG]: [hls @ 0260d280] Opening 'C:\Users\Public\NPVR-Data\web\temp\CNNHD-7ec2d5890ca64ce09cc93ba399e258ac4.ts' for writing
2023-01-21 16:03:29.440 [DEBUG][57] [FFMPEG]: [hls @ 0260d280] Opening 'C:\Users\Public\NPVR-Data\web\temp\CNNHD-7ec2d5890ca64ce09cc93ba399e258ac.m3u8.tmp' for writing
2023-01-21 16:03:29.823 [DEBUG][65] [FFMPEG]: frame= 1588 fps= 79 q=32.0 size=N/A time=00:00:28.16 bitrate=N/A speed=1.39x   
2023-01-21 16:03:30.360 [DEBUG][65] [FFMPEG]: frame= 1619 fps= 78 q=31.0 size=N/A time=00:00:28.67 bitrate=N/A speed=1.38x   
2023-01-21 16:03:30.893 [DEBUG][65] [FFMPEG]: frame= 1652 fps= 78 q=31.0 size=N/A time=00:00:29.22 bitrate=N/A speed=1.37x   
2023-01-21 16:03:31.396 [DEBUG][65] [FFMPEG]: frame= 1684 fps= 77 q=31.0 size=N/A time=00:00:29.76 bitrate=N/A speed=1.37x   
2023-01-21 16:03:31.898 [DEBUG][65] [FFMPEG]: frame= 1713 fps= 77 q=27.0 size=N/A time=00:00:30.24 bitrate=N/A speed=1.36x   
2023-01-21 16:03:32.376 [DEBUG][50] Renewed lease... (16000B)
2023-01-21 16:03:32.376 [DEBUG][50] Renew lease ok (0x16000B)
2023-01-21 16:03:32.445 [DEBUG][65] [FFMPEG]: frame= 1746 fps= 77 q=31.0 size=N/A time=00:00:30.79 bitrate=N/A speed=1.35x   
2023-01-21 16:03:32.516 [DEBUG][65] [FFMPEG]: [h264_qsv @ 02ac05c0] Error during encoding: device failed (-17)
2023-01-21 16:03:32.516 [DEBUG][65] [FFMPEG]: Error submitting video frame to the encoder
2023-01-21 16:03:32.529 [DEBUG][65] [FFMPEG]: [aac @ 01c002c0] Qavg: 506.912
2023-01-21 16:03:32.529 [DEBUG][65] [FFMPEG]: [aac @ 01c002c0] 2 frames left in the queue on closing
2023-01-21 16:03:32.534 [DEBUG][65] [FFMPEG]: Conversion failed!
2023-01-21 16:03:32.563 [DEBUG][50] Client has disconnected

[mvallevand]

You have a few problems first your camera extra is not working well so you have more to fix on it. The main problem seems to be you are using the UI client web app which likely needs more testing. How is playback in the traditional web client? You might also want to try the Android UI client called uidroid to see if it a protocol issue or specific to the web implementation

Martin

[benhase]

You have a few problems first your camera extra is not working well so you have more to fix on it.  The main problem seems to be you are using the UI client web app which likely needs more testing.  How is playback in the traditional web client?  You might also want to try the Android UI client called uidroid to see if it a protocol issue or specific to the web implementation

Martin

From in my original post:  "I don't think this happens on the Desktop App (but maybe I haven't waited long enough yet)."

What is this, and how do I fix it? "first your camera extra is not working well so you have more to fix on it."

Not sure what this is either: "How is playback in the traditional web client?".

I don't think it is a bandwidth issue:
I have WMC recording the NFL game on tuner 1.
The Desktop App playing CNNHD on tuner 2.
The Web App playing CLEO on tuner 0 with no freeze.

If I change the Web App (on tuner 0) to FNCHD it will eventually freeze.
Just for fun, I tried the Web App also on CNNHD. It seemed to share tuner 2 with the Desktop App but the Web App eventually froze (the Desktop App was still working).

I have not tried the Android UI client.

[mvallevand]

Sorry I was looking at the wrong logs you didn't use the normal web download and I picked the wrong file on the tablet. Hw transcoding is failing try turning on software decoding for now

Martin

[benhase]

Okay, I changed: Transcoder - Video Encoder - from INTEL to CPU and it doesn't appear to freeze anymore.
My low end Intel G1850, dual core/thread, 2900 MHz CPU runs at around 66% now (around 85% with the Desktop App running in parallel).

I tried this days ago (before the NShared.dll patch) and it didn't seem to help.
Maybe the two issues are related (or it is just the phase of the moon -lol).
I guess I can back out the NShared.dll patch at some point and run another a test.

Will a fix to NextPVR be made at some point (I thought INTEL used to work)?
Thanks for your help.

[mvallevand]

I don't think it was because of NShared.dll QSV should work but you might not be able to run with NextPVR as a service. Enable QSV or D3D and stop the recording service and then run NextPVRServer.exe command line and see if transcoding works.

Martin