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.
With v4, I had the Ch+ & Ch- buttons on my remote mapped to 'Page Up' & 'Page Down'. This did page up & down on the EPG screen, and also changed channels while watching live TV.
Ch+ (Page Up) incremented the channel number (ie from 2 to 3), and Ch- 'Page down' did the opposite (3 to2).
With v5, this seems to be reversed. In live TV, Ch+ is moving up the channel list, (ie 2 to 1) and Ch- is moving down the channel list (2 to 3)
This is causing confusion and frustration in my household. Is there any way I can get this to behave like v4?
(I know I can map Ch+ and Ch- to '+' & '-' to change channels, but these don't do anything on the EPG screen.)
If not, can I request a change or option to change this behavious in a future release please?
I think I could do with a bit of help if somebody could oblige.
PVR is having trouble updating the EPG overnight.
Between ~3-7 days after a full update gaps start appearing. A manual update only scans one frequency, updates a number between single digits up to a few thousand of listings and is likely to wipe some previously included, correct listings of channels not even broadcast over the frequency it has updated from. These sometimes showing gaps or alternatively showing “no listings”.
The overnight updates do seem to be doing something as they can also delete previously correct listings and surprisingly reinstate recordings of programmes in a series that I have already told it I do not want it to record.
Update: Since I wrote this the EPG update has failed after 1 day with massive gaps appearing where there were no gaps yesterday.
I added some channels to NextPVR and since I don't have an epg source I went ahead and inserted into the database using DB Browser. I can see the channels and correct epg info in the NextPVR web app as well as Emby. The channels show up in Kodi but there is no guide info.
Would anyone have any ideas of where to look to help troubleshoot this?
