Apollo TV IPTV service. Works fine on my NVIDIA Shield using TiviMate, so I don't think this is a problem with Apollo TV.
I have been using Apollo TV and NextPVR for MANY months. However, I just changed computers and now I cannot get the EPG to load in NextPVR. Apollo offers three possible URL's to access their EPG data, and I have all 3 plugged into the m3u Guide data for my IPTV device in NextPVR. However, when I try to load the EPG data, I immediately get this - EPG Update Complete - 0 updated, 0 inserted, 0 skipped.
Attached is the log file. The EPG update attempts are at the very end.
I had to laugh when I found out someone had put our televised 1pm covid updates (from our prime minister and director of health) on to IMDB, with seasons for each time we've had an outbreak (and the 1pm updates have returned to our screens).
From within the UI client I tried to update a reoccurring recording type but it would not change. I tried the using left/right arrow keys and the mouse clicking on the arrow buttons but I could not get it to change. The Roku client also has this issue. Haven't tried Knewc.
The web client works ok, it's just the UI clients.
Is it possible to add sling channels to my Windows based NextPVR recording computer? If so, Are there directions anywhere on how to add the Sling Channels? My IPTV service just recently crapped the bed and am looking for replacement.
Setup: Win10/NextPVR 5.1.4.210802 host, Nvidia Shield 2019 w/Kodi Matrix and Next PVR client 8.2.6, fibre internet
After many months of trouble-free recording and viewing, TVNZ's "1 News at 6" recordings started getting randomly truncated about a month ago. I typically view start viewing these about half an hour after they start recording - but the truncation doesn't correspond to that moment, nor is its location consistent when it happens.
Example truncation (will be captured in the attached logs): last night's News was truncated about 42 minutes in - the .ts file is about 530MB compared to the previous night's full 800ish.
Fwiw, I can't be 100% certain but the problem seems to have begun about the time Windows 10 updated itself to v21H1.
I tried a few patches like updated nshared.dll (from other threads) in the right places, then a full upgrade or two, getting to the latest version a couple or three days ago. But the intermittent problem recurred last night.
If I watch a TV show live in Kodi then click on the record button at the bottom of the screen then everything freezes and I have to restart the NextPVR service to unfreeze.
The log shows that NextPVR could not write to c:\Users\Public\Videos.
I have the NextPVRF service running using the login for my accoount so that it can see and write to a Samba share \\server_ip_address\Videos. That is working fine.
What do I have to do to avoid this problem?
The permissions for the Videos directory does not show my user name so just now I have added my user name and checked Modify, Read and Execute, List Folder Contents, Read,
Write.
Think that will fix the problem?
I am so recording shows most of the day so there is only a short period of time each day when I can risk crashing NextPVR by testing this.
Can Channel Name be added to the search criteria in V5? This was by far the most useful item in V4 NEWA, generating a list of everything showing on a particular channel for the next 2 weeks. Thanks.
Not sure if this is a Kodi/NextPVR/HDHomerun/Router problem but since it's happening while using kodi I'll post here first.
Getting a message on some channels, not all, when trying to watch live tv.
Says "Playback failed, One or more items failed to play. Check the log for more information about this message."
Getting this message sometimes on seemingly random channels. Sometimes the channels play fine other times they will take a long time to start, ~20 seconds, and sometimes that message appears with no playback.
Kodi also seems slow to exit channels and exit the application when this live playback fails or the channels take awhile to start.
Kodi logs should show a couple successfully live playback channels but then got that error message on DiscoveryHD 620.