[attachment=undefined][attachment=undefined]Hello! I have a problem with nextpvr on my Raspberry Pi 4, 2 MB RA, OS: Raspian. Installed with nextpvr-helper. Should be the newest version. Tuner USB-Stick: Hauppauge WinTV SoloHD EPG Source: DVB/ATSC EPG Installation is generally running fine: recording, playing, connection to web client, connections to Kodi … Sufficient resources: RAM, CPU, OS/Programs on SD-Card, Recording Directory and Recording Buffer at external NAS (Windows Server) But if I start Update EPG it stops after 6 frequencies. After that recording is no longer possible. Restart of nextpvr-service or unplugging the tuner stick does not help. After restart of the Raspberry, recording and/or start of EPG update again is possible (but stops again after 6 frequencies). If I delete some channels and start Update EPG at other frequencies it also stops after 6 frequencies. Empty EPG database does not help. Database npvr.db3 has ca. 12000 EPG entries (3,5 MB). The database could be opened with SQLite, looks o.K. Same version on my windows server is running fine. EPG database should have ca. 45 MB. I have added log files (device-adapter0: middle part deleted to match 2 MB). Hope someone has an idea.
I realise the easiest way to find out is to try it, but would anyone happen to know if I move a TBS pci-e card to a different slot on the mobo, what will I have to do - reboot and carry on watching TV, rescan for channels, chuck every NextPVR setting out and start again ?
My wife says she's seen this happen since we switched from Windows/v4.25 to Linux/v5, first time for me.
I was watching a recording from some time ago, about 32 minutes into a 60 minute recording and the video playback disappeared leaving me with the folder view (under Videos), but the audio playback continued. There's a lot of "stops" in the log file around 20:47 which would have been about right and you can see where I actually pressed the "stop" button on the remote which stopped the audio playback. I was able to restart the video, but not given the resume/restart option.
I think the event spanned the current and previous log files.
I would love to develop a new systems plugin for the windows client for v5, but I am not even sure this is possible. If anyone has the knowledge of where/how to add GUI elements to run a few commands, like shutdown -r, shutdown -s, and hard drive space, etc.
I just installed the latest version and Parallelprocessing.bat was running. It is not being invoked now. This was all to see why comskip wasn't running.
Any tips. It could be a permission issue, but I am not certain.
I am having a blast with NextPVR, awesome application!
I have an IPTV provider that prefixes all the channels with the group name. It is great when wanting to find something, but clutters the Guide, sometimes so I cannot see the whole channel name.
When I change the channel name in the settings -> channel, it looks great!
Unfortunately, when I update the IPTV device to add an additional channel, (settings -> devices -> iptv(<device>) -> Update m3u) those channels that I changed the name of disappear from my lineup.
Is there a way to have the channel name displayed in the guide (and other areas, like settings -> channels) divorced from the name the IPTV provider uses and still keep the link to the providers name during an m3u update?
I am using an Intel processor with integrated 4600 graphics, Win10/64. This has always worked fine with NextPVR for live and recorded TV and anything I use it for. (Intel Core i7-4710MQ @ 2.5GHz, not overclocked; 4th generation). I was using Intel driver win64_154037.4835.exe of 6 November 2017 ("4835"). When I updated to 5107 (10 Jan 2020), NextPVR did not display correctly. I think I didn't try 5144 of 18 August 2020, but just tried 5166 of 23 October 2020; it fails in the same way.
The problem: when displaying live TV or playing back a recording the screen is black most of the time with very brief flashes of picture every second or so.
If anyone has any light to throw on this, I'd be grateful; in the meantime 4835 works fine, no problem (except the Intel updater nagging me to update). If not, at least anyone else with the same problem can know they're not alone.
Best wishes, pol098
(I have since found a discussion of this issue, and have added to it, but I've started this new thread as the old one might not be followed.)
