Because of changes in Kodi v19 (Python 3) and NextPVR v5 (no more NEWA) x-newa 2.5.4 is the final release for v4 NextPVR and Kodi v16-v18. The good news is I have successfully ported x-newa to Python3 and it working pretty well on Kodi v18 (python 2 and 3) using the compatibility tools that Kodi thankfully provides.

The bad news is I am not going to test this version for release alone especially now that I use the Kodi addon more with v5 testing it is hard to catch some of the less frequent errors. The initial port involved removing 1000's of lines of code, removing several obsolete libraries, dead code and changing significant number of lines of code. The original codebase https://forums.nextpvr.com/showthread.ph...R-FrontEnd was from GBPVR and EWA days with XBMC and lots has changed since I updated that in 2012. Going for the python utf-8 model to unicode has been an issue in some places so that is the biggest trouble spot I foresee.

If anyone is interested in seriously testing the next generation plugin, knew4v5 - called "New for v5" aka "canoe" or "new client" post here. (I wanted to get rid of the x- for years now) My preference is that testers start using it full time to trap error.s If there is enough interest I will update the repo so people can get automatic updates. I am hoping to find testers for v17 and maybe v16 too (SPMC users maybe)

Martin

Using the same url I am able to get EPG in other iptv software, but my EPG stopped working in both of my NextPVR instances for some reason.

I don't know where to look for answers to the problem.

Hi,

I've seen a lot of recordings of films which have hard coded subtitles. It would be much more convenient if these sections of the films were dubbed.

Could this be added as a feature in NextPVR V5.x?

Cheers

My area (San Diego, CA) recently in the past few weeks had some of the local TV digital broadcast channels change physical frequencies/channels so a rescan on all receiving digital TV tuner devices was required.

Both of my HDTVs tuners after rescan correctly detected all of the channels that changed and they all work fine on my HDTVs.
With my Hauppage WinTV card in my PC (model HVR-1250) however the rescan for channels using NextPVR was unable to find a couple of the channels that changed frequencies, specifically KNSD(NBC) now using physical channel 17 and KSWB(Fox) now using physical channel 26. Each of those channels have four sub-channels.
I could see those physical channels tried in the scan process, but the channels were not detected there. All other local TV channels were properly detected and work in NextPVR however.

I have already installed the latest WinTV drivers and no change.
Same problem with the latest versions of WinTV7 or WinTV8 apps.

I noticed a new version of Hauppauge's WinTV8.5 app (which requires a code to install I don't have) came out a few days ago and in the release notes this is listed:
Fixed an issue when channels move frequency on ATSC Repack, but rescanning still shows "No Signal"

Which sounds like the issue I'm experiencing!
However the latest device drivers included with that latest version of WinTV8.5 did not help (it allows installation of the drivers without a code, only the WinTV app itself requires a code to install after).
But if the WinTV app's channel scanning process changed to fix this issue, wouldn't NextPVR need to make a similar change in its channel scanning process to fix the issue too?

Anyone else experiencing a similar problem with WinTV cards after local TV channel frequency changes recently?

Hi,

I have figured out that the following api command works for streaming recordings:

http://<ip>:8866/live?recording=<id>&client=myclient

But if I open the stream in vlc the length of the stream is undefined and thus seeking is not possible.

Is there anything I can do to fix this? Maybe another api method?


Thank you!

Hi,

Its not going to sleep since the recent update of NPVR.

I've seen this before with previous versions and its been fixed. It just seemed to reappear again. I've rebooted etc and set the sleep timeout to 1 min to check.

powercfg is showing:

DISPLAY:
None.

SYSTEM:
[DRIVER] Legacy Kernel Caller

AWAYMODE:
None.

Even when no recording are going. Legacy kernel caller is keeping it awake. Since the computer had nothing but NPVR on it its most likely it.

Zip file included.

Rob

Hadn't used NextPVR on one of my computers in quite a while. When I did today I got a message that the Microsoft Video Decoder was disabled. So, I decided to use the LAV filters like on my other computer. Installed both video.ax and audio.ax. Went to the decoders settings page in NextPVR and the LAV Video Decoder and LAV Audio Decoder do not show up in the drop down lists. Has the process changed or am I forgetting some other step to complete this task?

Hi,

Was wondering how the Season Folder option actually works; and specficialy why it would not work in this instance?.
I recorded . am recording GoT S1 to S7

I expected seven (7#) Folders, namely Game of Thrones Season 1 ....Game of Thrones Season 7 with each season i.e. Game of Thrones S01E01.... S01E10 => S07E01...S07E10 within the respective folder.

What occured was simply 7 x 10 sets of recorded each with its own folder.

What is supposed to happen here i.e. do I need to change a setting other than what I changed in the settings (see attached)?

I will try to re-import those somehow, maube wiht IGL (hope that will work) or just a drag and drop and reimport.

k.

I didn't give it much thought when I first saw it, but I'm getting this type of file with each new recording.

Please, what is a ...ts.map file and can I hide it somewhere?

Thanks.

I have been finding holes in the EPG, with the guide showing no program information available. I've tried running a manual EPG update both with and without the NPVR service running but in both cases the update seems to cause NPVR to crash out to the Win 10 desktop at a point that does not appear to be consistent. Some of the holes in the EPG are filled by the update but others that previously held info are then "no information". Could this be another problem with the UK over-the-air EPG data, as with the recent unicode changes? NB: I've been experiencing a lot of issues using Kodi on a client PC, as documented in other threads.