It takes almost 10 seconds before the video loads. I have 2 HdHomerun devices...Connect 4 tuner model, and the original 2 tuner model. This issue occurs using Kodi 18.9 and Kodi 19.1...AND the desktop version of NPVR. I saw that there is a new Nshared.dll....I installed it and restarted the Win10 computer....issue still exists. Is there any way to speed this up? Below is what I found in the logs...I am on version 5.1.4.210802 on NextPvr.5.1.4.2108025.1.4.2108025.1.4.210802
Failed to start stream: System.NullReferenceException: Object reference not set to an instance of an object.
at NShared.Shim.InputSourceHTTP.StartStream(String target)
at NShared.Shim.GenericCapture.StartStream(String target, String& reason)
2021-08-13 15:51:27.649 [ERROR][7] Unable to StartStream(): No connection could be made because the target machine actively refused it. No connection could be made because the target machine actively refused it.
This happens several times and then finally loads.
I got a new Roku TV that I've been using as a new client for my NextPVR server here in NC. My postprocessing script generates an .mp4 for it to play. The source is an HDHR with a cablecard and Spectrum cable. (The cable does seem to be a bit glitchy at times even with their settop boxes. But I don't think that this problem is signal related.)
Frequently, I'll be watching a program and all of a sudden the audio will continue, but the video will freeze. And if I hit OK to bring up the OSD, it shows that the current position is something wonky like 13+ hours into a 1:03 recording. And, if I hit the <- button to stop playback, I get the prompt saying the show has been played to completion and asking if I want to delete. Of course, the resume point is also lost/messed up.
I have found that if I restart playing the program and use the "remote menu" to enter a jump time to somewhere around where I was, it will begin playing fine (and the timeline appears correct). Sometimes this happens once in a show. Other times it's many times in the same show. It is (almost?) always during an actual show, so shouldn't be a problem with the .ts timeline getting changed by commercial insertion or something like that.
This morning, the problem happened several times while I was playing an episode of Big Brother. So you should see several examples of the problem, my recovery, continued playback, repeat, etc. in these logs.
Is the current (timeline) position coming from the Roku or the NextPVR backend server? I've also got an RPi 4 with LE and knewc which I'm using heavily here. I have not experienced this problem with it's playback. But it would be using the .ts file and I believe that it is reading the file directly via SMB not streaming via the NextPVR server.
I'm hoping that Martin will see something obvious in the logs.
I went in to toggle a VOD series from 'no' to 'yes' in 'pluto-vod-series-filter.lst' and it returned an error. Pluto live tv is working ok, so is updating the Pluto guide.
I previously had several series showing up ok.
Output is below.
System Windows 10, version 19043.1110, Windows Feature Experience Pack 120.2212.3530.0.
Python 3.9.5
This is the first time I adjusted anything in the lst files.
I reverted the edit to 'pluto-vod-series-filter.lst' and the error still persists.
Code:
C:\Users\Public\NPVR-data\scripts\plutotv>python pluto.py reset-vod
Page 1 of 2
Found 100 categories Total categories 100 Total Series 1625
Page 2 of 2
Found 26 categories Total categories 126 Total Series 1848
C:\Users\Public\NPVR-data\scripts\plutotv>python pluto.py vod
Generating Extra VOD file in C:\Users\Public\NPVR-data\
Read page file C:\Users\Public\NPVR-data\scripts\plutotv/vod-cache-1.json
Traceback (most recent call last):
File "C:\Users\Public\NPVR-data\scripts\plutotv\pluto.py", line 326, in <module>
vod.GenerateVOD()
File "C:\Users\Public\NPVR-data\scripts\plutotv\vod.py", line 127, in GenerateVOD
VODChannel(extras, station)
File "C:\Users\Public\NPVR-data\scripts\plutotv\vod.py", line 249, in VODChannel
ET.SubElement(channel, 'landscape').text = station['featuredImage']['path']
KeyError: 'path'
C:\Users\Public\NPVR-data\scripts\plutotv>
So my default recording drive shows 0 bytes left, while there is still over 1tb left on my secondary recording drive. I thought v4 had a feature that looked for the drive with the most space, and recorded to that drive. Here is a link to the setting i'm talking about under v4. So far, I can't seem to find this setting under v5. Is it hidden, not yet implemented, or do i need to edit the config.xml file. Again I'm completely out of space, and I don't understand why nextpvr didn't use my second hdd with over a terabyte left of space. Here is my log, and here is the recording part of my config.xml file. Please let me know if there is a way to fix this behavior.
Thanks
I just got the roku app and I'm looking forward to trying it. However, it closes as soon as I get into the settings. If I try to enter an address manually, it closes immediately. If I let it detect the server, it does, and closes as soon as I select it. I originally thought this might be related to the 7 day expiration, so I donated and reported the donation. Now I'm seeing that it's unlikely related. But I'm hoping to figure out what kind of debugging I can help do.
Thanks,
Hardware: Element TV (unsure of model) with built in roku.
I’ve been using DVB-S and DVB-T card with PCs for many years under WMC. I’ve now come back to this as I discovered NextPVR.
I’m using Windows 10 with an Intel CPU and have a Nova 500 dual tuner and a Hauppauge HD S2.
Terrestrial - The Nova 500 will work under W10 but with old drivers. If you use the latest drivers or Windows update drivers it fails. However, when its working, its flawless.
Satellite - The DVB-S S2 card has been difficult to setup. Hauppauge were no help at all. There are latest windows 10 drivers that you must purchase, didn’t work. The windows update drivers do work.
It scans and finds circa 800 channels on Astra 28.8. Issues start when you start tweaking the audio streams and the EPG etc including blue screens. I still think its driver- driven.
I will keep on trying as I love the idea of everything in one backend box which is managed by Librelec client.
I’m not sure if scanning is best through browser or fat client or if LAV filters need to be set differently for DVB-S
Sub,
I updated to 5.1.4.210802 when it came out and everything seemed good until the last few days when I started having strange incidents where live tv would freeze up using Kodi. After about 30 seconds or so it would dump me back to the channels list. I’m running NextPVR in a Ubuntu 20.04 VM with a 60Gb system drive and recordings go to a NFS share. livetv stays on the VM. This setup has worked very well since V5 came out.
Long story short, I found this error in the logs “Unexpected error writing to OutputSink: System.IO.IOException: No space left on device” I tracked down the problem to the livetv directory being full of orphaned .ts files. It was so full it was also causing problems with the logs too. The first set I tried to grab was completely blank and the second set as you can see shows the error.
Deleting the orphans solved the problem for now. I wanted you to be aware and ask if you might be willing to incorporate a small routine to delete any orphans occasionally? I know it’s supposed to do this anyway but obviously something is going sideways occasionally.
