Is anyone using the EASY PLAYER SWITCH plugin?  It lets you switch to a different playercorefactory.xml upon demand; or completely switch to VLC as your Kodi player. 

Does anyone have an edited XML with MX PLAYER PRO as the default player?

So recorded a nice long movie of two hours. Went to play it and the player in Kodi just would not play the TS file. Switched to try MX PLAYER PRO and worked fine to play the same TS file.

 Likely indexing or slight glitches in the stream when recording. Have had problems recording long streams forever. Always seems to be a glitch somewhere, but you would think that NEXTPVR would recover from the stream pausing.

I have a external drive that Records all my tv shows. With 2020 it creates a season folder and inside is a recording thats episode and number. Ie 2020.S48E4.ts and comskip will not even run on it. My other videos are labeled as ie DatelineNBC202550056.ts

I do have "Use episode number when possible" but 2020 is the only show using season and episode numbers.

I would appreciate any help!!

Thank you!!

I am new to NextPVR and got the channels to show but the listing doesn't show any details whatsoever. What am I missing? I am using Schedules Direct and logged in.

Thanks!

Hi all, 

I run NextPVR inside a Proxmox Linux (Debian) container, installed through the nextpvr-helper.deb package. I passed-through the USB TV tuner device (Hauppauge TV WinTV-dualHD model 01590) to the container and it works like a charm.

I have however found an anomaly that more than one time compromised the DVB recordings I have scheduled: the recording of DVB streams is interrupted by scheduled EPG updates, if that operation takes place during the time of the recording and is performed via the DVB tuner (Settings > Guide > EPG Sources = 'DVB/ATSC EPG' for at least one channel) and not via XML resources ('XMLTV').

The possible workarounds are:

• schedule EPG updates only once per day, at a time when you are unlikely to record anything from the DVB tuner, for example 5:00 AM
  
• unset EPG from 'DVB/ATSC EPG' from ALL the channels and use exclusively 'XMLTV' instead: EPG update from the web does not interfere with DBV tuner recordings
  

• Settings > Channels > at least one channel is set with EPG Source = DVB/ATSC EPG
  
• Settings > Guide > Automatic EPG Update = 06:55:00,21:55:00 (now changed to 05:00)
  

• Schedule the recording of any event on any channel via DVB tuner whose duration overlaps with the scheduled Automatic EPG Update via the same tuner, say from 21:00 to 23:00
  
• Result: the DVB recording is interrupted at the time of the EPG update, in this case 21:55, with no error shown in GUI
  

Hi, I've been using NPVR on the same Windows hardware for years but yesterday, for no apparent reason although it did follow a Windows update, NextPVR was failing to stream any channels and reporting Streaming failed (transcoder exited). After numerous checks and finally re-installing NPVR I now have the problem that I can't re-scan/populate any channels to see if it's now working.

Buried in the logs are numerous lines "status":"Scanning: 177500KHz (7MHz b/w) (0 channels found)" and later followed by {"stat":"Failed","code":11,"msg":"Scanner not active"}

My USB DVB-T is connected and active as, noting an earlier post about using TS Capture, I installed this and can scan and record any stream successfully.

The logs attached are from the re-install onwards.

Could you help please

Attached Files

  logs-20251016-1214.zip (Size: 23.39 KB / Downloads: 2)

Everything was fine yesterday. Today, the devices have disappeared.  Re-scanned devices multiple times.  Update to the latest software.  Still no devices. Log file attached.

Attached Files

  logs-20251015-0903.zip (Size: 109.74 KB / Downloads: 3)

Two Windows updates this week  KB5066835 and KB5065789 break NextPVR's ability to communicate with digital tuners on Windows.   A good starting reference on the issue is here https://learn.microsoft.com/en-us/answer...-10-cumula with

Here is a solution that worked for me taken from that thread https://forums.nextpvr.com/showthread.ph...#pid604153

If you haven't installed them yet I would pause your Windows updates until more information is available. I will try updates when they come out, fortunately I only use Windows for testing so it doesn't hurt my production servers.

The original forum post here https://forums.nextpvr.com/showthread.php?tid=66616 has more information.


Martin

NextPVR stopped doing scheduled recording and was also unable to do a live viewing of programs selected via the program guide.

It tried to view a couple scheduled recordings but they all ended up in the Failed Recordings folder and refuse to play.

I found this in the logs (note, these logs were captured before several of the scheduled recordings failed but the reason seems pretty clear)...

"No connection could be made because the target machine actively refused it"

Anyone else have this problem after today's Win 11 update?

Logs attached.

Thanks!

Attached Files

  logs-20251015-1355.zip (Size: 127.86 KB / Downloads: 2)

I have traced the behavior of the NextPVR Kodi addon when initiating a series recording from the Kodi EPG.
In Kodi, this is done from the EPG screen with an episode highlighted, and pressing the "t" key on the keyboard or initiating ActionID "ShowTimerRule".
In Kodi Omega, this is the dialog that appears with the listed settings pre-selected.

   

At these default settings, the pvr.nextpvr addon creates a recurring_type=3 entry which corresponds to "Record Series (Daily, this timeslot)" in NextPVR.

Changing the "Prevent duplicate episodes" option from All to New when Type=Recording: Repeating (guide) as shown does not affect the recording type that gets created in NextPVR.
Changing the Channel from the specified one to "All" changes the recording type to "Advanced by Keyword"

However, after playing around with the various options circled, I did observe the following resulting behavior.

1. Changing the Type to "Recording: Repeating (all episodes)" has an effect. Alone, it changes the passed recording_type=2 and causes "Record Series (All Episodes)" in NextPVR. 
(Too bad this isn't the default option in the dialog).
2. With the Type set to  "Recording: Repeating (all episodes)", now the "Prevent duplicate episodes" option works as expected. Changing it as well from all to "New Only" changes the passed recording_type=1 and causes "Record Series (NEW Episodes)" in NextPVR.
3.  With the Type set to  "Recording: Repeating (all episodes)", if the Channel is also changed to "ALL", no recording is possible and a Kodi error is thrown.

I also noticed in the Kodi logs, that when the ShowTimerRule is initiated it appears that the system is trying to load defaults from somewhere, but I don't know where that is.

See: