Using latest NextPVR on Docker, iPhone X with latest app on latest iOS 14.3.
I noticed 100% app crashes when doing the following:
1. go to Guide
2. switch guide data to tomorrow
3. click a random menu item for example Channels or Search
4. repeat from step 1 until it crashes (after a few loops it will crash)
Using latest NextPVR on Docker, iPhone X with latest iOS 14.3.
If you go to TV Guide and select the date dropdown it will show in my case 8 days incl. today to which I can jump to. This works for the first 5 days. But when you select a date further into the future nothing happens.
Apparently there's no EPG data for those dates (I double checked this in TV guide on my Samsung KS8000 TV) But I think it's a better experience to show nothing (because there's no EPG data) than to show the previous data (also because date selected in dropdown IS updated). And even better is to not show any dates in dropdown when there's no data for that date (I checked all channels in the guide).
I have been using NextPVR for a few years and it worked very good thanks!
A few months ago some recordings started to be empty and now most recordings are zero bytes. Sometimes it works but often it does not.
Here is a log of a channel I tried recording manually this afternoon. I know the channel was receiving correctly since I could watch the live feed from within NextPVR just before I tried the recording.
When I tune to 13.1 using NPVR guide, the program for 13.5 plays. Program for 13.5 also plays on 13.5 This does not happen when I use the HDHomerun apps on Android or Windows 10 to directly view channels. VLC also gets correct programs. Haven't noticed problems with any other channels.
Attached logs from C:\Users\Public\NPVR-data\logs plus npvr.db3 file.
I just moved to NextPVR V5 over the Christmas break - I had been on V4. Everything has worked well, but I have run into one behaviour change between V4 and V5.
Background first:
I have an HDHomeRun Connect with 2 tuners. It is model HDHR4-2US(CA) if that makes a difference.
It periodically hangs - this has been a problem for years and HDHomeRun support says it is the network in my house, which it is not, having replaced and rewired everything several times. My son has the same set up but is running an older firmware level and his does not hang. (no more on this here unless it is needed to help with looking at the NextPVR behaviour change).
On V4 when the CTV National News recording failed because 'no data delivered' from the hung HomeRun, it would look for an alternate airing, in my case at 5:30 AM the next morning. Of course since the HDHomeRun was hung, this to would fail.
However, now that I am on V5 the recording at 5:30 AM is not failing, rather it is remaining in Pending state even though it is now 10:30 AM in the morning. It is this pending state for the recording at the alternate time that is the behaviour change.
I attempted to clear the problem by doing the following:
Powered off the HDHomeRun and powered it back on. Following this I was able to use NextPVR to watch live TV through the HDHomeRun. However, the pending recording at 5:30 AM remained - it was not cleared or moved to failed state.
I stopped and started the NextPVR service (using Windows services). This cleared the pending recording and placed the 5:30 AM recording in failed state with the message 'Recording service not running at recording time'. According to Windows services it was running - I am guessing it was just stuck. Restarting the service which effectively reloads and starts the program, cleared the problem as I expected it would.
As I said above this is a behaviour change between V4 and V5. Could someone see if this is working as expected in V5.
Environment:
Windows 10 PRO build 19041.685 On a home built PC.
HDHomeRun Connect model HDHR4-2US(CA) firmware level 20200907
NextPVR 5.1.0.201216
There is single gigabit switch between the PC and the HDHomeRun
Logs collected after I cleared the problem are attached.
I had 3 recordings fail yesterday all with the same error, [Failed:The operation has timed out. ].
I'm trying to learn how to detect and solve problems on my own but not finding the answers. My questions are why did the recording start and end times change from default pre and post padding? It looks like a tuner should have been available but the 3 shows below still failed and I can't figure out why.
"Last Man Standing" 09:30:00 to 10:00:00
"Call Your Mother" 09:30:00 to 10:00:00
"Late Night With Seth Meyers" 12:36:00 to 01:36:00 Note abnormal start and end time.
In looking at the logs and schedule of the failed recordings there was some overlap of recording leading to more than 4 simultaneous recordings at one time and I have a quad tuner. This caused "The Conners" to start late. My default padding is 1 minute pre and post. Previously I had 1 minute pre and 2 post so some recurring recordings have a 2 min post.
Below are abnormal start or end times ** , there are some shows in between with normal times.
**"Nature 07:59:01 to 09:03:20
**"American Housewife" 08:29:01 to 09:05:00
**"Last Man Standin 08:59:01 to 09:40:40
"NOVA" 08:59:02 to 10:02:00
"The Conners" started at 09:03:20 when a tuner became available after "Nature" end 09:42:20
"Last Man Standing" 09:30:00 to 10:00:00
"Call Your Mother" 09:30:00 to 10:00:00
"Seinfeld" 12:02:21 to 12:32:00
"Seinfeld" 12:30:40 to 01:02:00
**"Late Night With Seth Meyers" 12:36:00 to 01:36:00
As best I can tell all the failures had similar errors.
Code:
2021-01-13 21:30:40.086 [ERROR][9] Unexpected error on LocalRecorder.StartStream(): System.Net.WebException: The operation has timed out.
at System.Net.HttpWebRequest.GetResponse()
at System.Net.WebClient.GetWebResponse(WebRequest request)
at System.Net.WebClient.DownloadBits(WebRequest request, Stream writeStream)
at System.Net.WebClient.UploadBits(WebRequest request, Stream readStream, Byte[] buffer, Int32 chunkSize, Byte[] header, Byte[] footer)
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadString(Uri address, String method, String data)
at NShared.LocalRecorder.StartStream(ChannelMapping channelMapping, String target, String& reason)
2021-01-13 21:30:40.086 [DEBUG][9] Failed to start recording on allocated device (17402:/home/craig/RecordedTV/Call Your Mother/Season 01/Call.Your.Mother.S01E01.Pilot.ts): 'The operation has timed out.'
I am running NPVR on a Windows Server 2016 Essentials box with a BlackGold BGT3650 tuner with the latest drivers, and using Emby as the primary player. It all works fine to start with, until the server hibernates (Lights Out 3 power management), or as I found out this morning reboots.
When the server is resumed, for what ever reason, none of the tuners can get a channel lock. The 2 ways I have found which solves the problem is to either start and cancel a channel scan, or restart the NextPVRServer service. What I find most confusing is when I rebooted after a Windows update this morning, I had the same issue until I restarted the service.
As a workaround I have created a scheduled task to restart the service when the server is resumed, but I had 2 failed recordings last night, so I dont think it is working ( I havent checked the Windows logs yet)
It has been working, and Im not sure if this started when I upgraded to the last version of NextPVR. I have attached my logs.
Hi.
Some channels in the UK show movies with a split in the middle for a short news slot. The the three parts - movie. news. movie - all have an entry in the EPG so to record, you have to pick two items with the same name and end up with two files to watch.
Is there any way for NPVR to see these two entries in the guide as one and so just record all the way through? Emby seems to be able to do this somehow or another so wondering if NPVR could too.
To migrate to V5, I uninstalled V4 then installed V5.1.0 (201216). Everything works great - followed instructions on this forum and migration was simple.
I was checking to make sure that everything from V4 was cleaned up by the uninstall. After reviewing the forum I understand that there is one Windows registry entry that is not cleaned up (may be used in the future). I have also found 3 files in c:\Program Files (x86)\NPVR. they are
NUtility.dll
NShared.dll
NTray.exe
Since I can also find these files (with the exception of NTray which seems to have been renamed to NPVRTray) in the c:\Program Files\NextPVR directory which is where V5 is installed, I assume that I can delete the c:\Program Files (x86)\NPVR directory and these 3 files.
