<![CDATA[NextPVR Forums - NextPVR Support]]> https://forums.nextpvr.com/ Fri, 16 Oct 2026 19:28:51 +0000 MyBB <![CDATA[Kodi 21 / pvr.nextpvr 21.3.2.1 – Live TV stops after 30–60 minutes, HTTP range error]]> https://forums.nextpvr.com/showthread.php?tid=67200 Thu, 08 Oct 2026 13:02:23 +0000 Rad]]> https://forums.nextpvr.com/showthread.php?tid=67200 I am experiencing recurring Live TV playback interruptions when using the NextPVR PVR client in Kodi.

My setup:
  • NextPVR Server: 7.1.1.260616
  • NextPVR running in Docker on a Synology NAS
  • Kodi 21 with pvr.nextpvr 21.3.2.1
  • IPTV channels configured in NextPVR
  • Kodi and NextPVR are connected over the local network

The problem:
Live TV playback works normally for approximately 30–60 minutes, then suddenly stops and Kodi returns to the channel guide.
The issue occurs with different IPTV sources, not just one channel. Playback through the NextPVR web player appears stable.

Tests already performed:
I tested different NextPVR Live TV buffer settings:

Buffer size       Approximate playback duration

20 minutes      28–30 minutes
60 minutes      40 minutes
120 minutes    55–60 minutes

I also tested the Kodi NextPVR client's Real Time and Timeshift playback methods.
For the latest test:
  • Live TV method: Timeshift
  • Direct Streams: Disabled
  • NextPVR Live TV buffer: 120 minutes
  • Kodi
    Code:
    advancedsettings.xml
    :
    Code:
    curllowspeedtime=60
Unfortunately, the problem still occurs.

Relevant log messages:
Kodi reports:
Code:
CVideoPlayerAudio::Process - stream stalled
followed by:
Code:
Reconnect, (re)try 1
and:
Code:
Failed: Requested range was not delivered by the server (33)
The NextPVR logs show messages including:
Code:
stream@2 got zero bytes client disconnected Live stream expired without 15 second renewal.
After the stream disconnects, Kodi attempts to reconnect using an HTTP byte-range request, but playback cannot recover.

My questions:
  1. Is this a known issue with the Kodi NextPVR client or NextPVR's Live TV streaming?
  2. Could the HTTP range/reconnect behavior be responsible for the playback stopping?
  3. Is there a recommended fix or workaround?

I have attached sanitized Kodi and NextPVR logs from the latest playback failure. Sensitive URLs, credentials, network addresses and identifiers have been redacted.
Any help would be greatly appreciated.
Thank you!

.zip   nextpvr_forum_logs_sanitized.zip (Size: 101.21 KB / Downloads: 1) ]]> I am experiencing recurring Live TV playback interruptions when using the NextPVR PVR client in Kodi.

My setup:
  • NextPVR Server: 7.1.1.260616
  • NextPVR running in Docker on a Synology NAS
  • Kodi 21 with pvr.nextpvr 21.3.2.1
  • IPTV channels configured in NextPVR
  • Kodi and NextPVR are connected over the local network

The problem:
Live TV playback works normally for approximately 30–60 minutes, then suddenly stops and Kodi returns to the channel guide.
The issue occurs with different IPTV sources, not just one channel. Playback through the NextPVR web player appears stable.

Tests already performed:
I tested different NextPVR Live TV buffer settings:

Buffer size       Approximate playback duration

20 minutes      28–30 minutes
60 minutes      40 minutes
120 minutes    55–60 minutes

I also tested the Kodi NextPVR client's Real Time and Timeshift playback methods.
For the latest test:
  • Live TV method: Timeshift
  • Direct Streams: Disabled
  • NextPVR Live TV buffer: 120 minutes
  • Kodi
    Code:
    advancedsettings.xml
    :
    Code:
    curllowspeedtime=60
Unfortunately, the problem still occurs.

Relevant log messages:
Kodi reports:
Code:
CVideoPlayerAudio::Process - stream stalled
followed by:
Code:
Reconnect, (re)try 1
and:
Code:
Failed: Requested range was not delivered by the server (33)
The NextPVR logs show messages including:
Code:
stream@2 got zero bytes client disconnected Live stream expired without 15 second renewal.
After the stream disconnects, Kodi attempts to reconnect using an HTTP byte-range request, but playback cannot recover.

My questions:
  1. Is this a known issue with the Kodi NextPVR client or NextPVR's Live TV streaming?
  2. Could the HTTP range/reconnect behavior be responsible for the playback stopping?
  3. Is there a recommended fix or workaround?

I have attached sanitized Kodi and NextPVR logs from the latest playback failure. Sensitive URLs, credentials, network addresses and identifiers have been redacted.
Any help would be greatly appreciated.
Thank you!

.zip   nextpvr_forum_logs_sanitized.zip (Size: 101.21 KB / Downloads: 1) ]]> <![CDATA[Playback stops after changing recording directory]]> https://forums.nextpvr.com/showthread.php?tid=67184 Mon, 28 Sep 2026 04:32:53 +0000 robmorren2]]> https://forums.nextpvr.com/showthread.php?tid=67184
I'm on Version: 7.1.1.260616  on a Windows 10 PC with clients that are all RasPi, Onn, Fire. 

I had a secondary recording location that was pointed at my NAS on my network. It was called "DS418play". The path was "\\DS418play\TV Shows\NextPVR Recordings\". That setup worked fine for years. I recently got a new NAS. I named it "DS1618". The folder structure is the same, so I updated the recording location to "\\DS1618\TV Shows\NextPVR Recordings\"

For some reason, that causes a problem. I can get TV to play on a client for maybe 30 secs, sometimes longer, and then an error will pop up that says timeshifting is disabled, and the stream stops shortly after. To test, I renamed my NAS "DS418play" (the same name as my old NAS and old file path, even though this is a DS1618 NAS now). That made the errors stop and playback was fine again. I changed the names to DS1618, error started again.

Has anyone else experienced this? Is there a fix? I did export the logs zip file, but I'm unsure what specifically would be needed from it. Thanks in advance!

Rob]]>
I'm on Version: 7.1.1.260616  on a Windows 10 PC with clients that are all RasPi, Onn, Fire. 

I had a secondary recording location that was pointed at my NAS on my network. It was called "DS418play". The path was "\\DS418play\TV Shows\NextPVR Recordings\". That setup worked fine for years. I recently got a new NAS. I named it "DS1618". The folder structure is the same, so I updated the recording location to "\\DS1618\TV Shows\NextPVR Recordings\"

For some reason, that causes a problem. I can get TV to play on a client for maybe 30 secs, sometimes longer, and then an error will pop up that says timeshifting is disabled, and the stream stops shortly after. To test, I renamed my NAS "DS418play" (the same name as my old NAS and old file path, even though this is a DS1618 NAS now). That made the errors stop and playback was fine again. I changed the names to DS1618, error started again.

Has anyone else experienced this? Is there a fix? I did export the logs zip file, but I'm unsure what specifically would be needed from it. Thanks in advance!

Rob]]> <![CDATA[VAAPI fails with Intel Arrow Lake-S]]> https://forums.nextpvr.com/showthread.php?tid=67182 Sun, 27 Sep 2026 18:41:49 +0000 krasty633]]> https://forums.nextpvr.com/showthread.php?tid=67182 I'm running NextPVR in the official Docker container nextpvr/nextpvr_amd64 on Unraid.
I noticed playback issues while testing my recordings.

The host also has an Intel Arc A310, but that GPU is bound to vfio-pci and is not used by NextPVR.
The Arrow Lake iGPU is exposed to the NextPVR container as: /dev/dri/renderD128

The mapping on the host is:
pci-0000:00:02.0-card  -> ../card1
pci-0000:00:02.0-render -> ../renderD128

Inside the NextPVR container:
crwxrwxrwx 1 root 18 226, 128 /dev/dri/renderD128

NextPVR runs as root, so this does not appear to be a permissions issue.
1. VAAPI / web playback
With VAAPI enabled in NextPVR, playing a recording in the web interface fails with: Failed to start requested stream

Testing VAAPI directly inside the NextPVR container reproduces the problem:
ffmpeg \
  -hide_banner \
  -vaapi_device /dev/dri/renderD128 \
  -f lavfi -i color=size=1280x720:rate=25 \
  -vf 'format=nv12,hwupload' \
  -c:v h264_vaapi \
  -frames:v 25 \
  -f null -

[AVHWDeviceContext @ ...] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[AVHWDeviceContext @ ...] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
[AVHWDeviceContext @ ...] Failed to initialise VAAPI connection: -1 (unknown libva error).
Device creation failed: -5.
Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error
Error parsing global options: Input/output error

The versions installed in the NextPVR container are:
ffmpeg 5.1.9-0+deb12u1
intel-media-va-driver-non-free 23.1.1+ds1-1
libva2 2.17.0-1
libva-drm2 2.17.0-1

I also tested what upgrading the VAAPI stack from Debian Trixie would require. It would provide:
intel-media-va-driver-non-free 25.2.3
libva 2.22.0
libdrm 2.4.124

but it would also upgrade libc and several other core packages from Debian 12 to Debian 13, so I did not perform that upgrade.
As soon as I disable VAAPI in NextPVR, web playback works correctly.
Therefore this seems to be specifically related to the Intel VAAPI/media-driver version in the current NextPVR container and Arrow Lake-S.
Interestingly, Plex is running on the same Unraid server with the same /dev/dri device exposed and ships its own iHD_drv_video.so and works fine.

My questions is:
Is the Intel media-driver included in the current NextPVR Docker image known to be too old for Arrow Lake-S, and is there a plan to update it?

.zip   logs-20260927-2012.zip (Size: 1.21 MB / Downloads: 0) ]]> I'm running NextPVR in the official Docker container nextpvr/nextpvr_amd64 on Unraid.
I noticed playback issues while testing my recordings.

The host also has an Intel Arc A310, but that GPU is bound to vfio-pci and is not used by NextPVR.
The Arrow Lake iGPU is exposed to the NextPVR container as: /dev/dri/renderD128

The mapping on the host is:
pci-0000:00:02.0-card  -> ../card1
pci-0000:00:02.0-render -> ../renderD128

Inside the NextPVR container:
crwxrwxrwx 1 root 18 226, 128 /dev/dri/renderD128

NextPVR runs as root, so this does not appear to be a permissions issue.
1. VAAPI / web playback
With VAAPI enabled in NextPVR, playing a recording in the web interface fails with: Failed to start requested stream

Testing VAAPI directly inside the NextPVR container reproduces the problem:
ffmpeg \
  -hide_banner \
  -vaapi_device /dev/dri/renderD128 \
  -f lavfi -i color=size=1280x720:rate=25 \
  -vf 'format=nv12,hwupload' \
  -c:v h264_vaapi \
  -frames:v 25 \
  -f null -

[AVHWDeviceContext @ ...] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[AVHWDeviceContext @ ...] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
[AVHWDeviceContext @ ...] Failed to initialise VAAPI connection: -1 (unknown libva error).
Device creation failed: -5.
Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error
Error parsing global options: Input/output error

The versions installed in the NextPVR container are:
ffmpeg 5.1.9-0+deb12u1
intel-media-va-driver-non-free 23.1.1+ds1-1
libva2 2.17.0-1
libva-drm2 2.17.0-1

I also tested what upgrading the VAAPI stack from Debian Trixie would require. It would provide:
intel-media-va-driver-non-free 25.2.3
libva 2.22.0
libdrm 2.4.124

but it would also upgrade libc and several other core packages from Debian 12 to Debian 13, so I did not perform that upgrade.
As soon as I disable VAAPI in NextPVR, web playback works correctly.
Therefore this seems to be specifically related to the Intel VAAPI/media-driver version in the current NextPVR container and Arrow Lake-S.
Interestingly, Plex is running on the same Unraid server with the same /dev/dri device exposed and ships its own iHD_drv_video.so and works fine.

My questions is:
Is the Intel media-driver included in the current NextPVR Docker image known to be too old for Arrow Lake-S, and is there a plan to update it?

.zip   logs-20260927-2012.zip (Size: 1.21 MB / Downloads: 0) ]]> <![CDATA[Can't upgrade from 6.1.1.221106]]> https://forums.nextpvr.com/showthread.php?tid=67134 Mon, 31 Aug 2026 10:31:28 +0000 blobbyguts]]> https://forums.nextpvr.com/showthread.php?tid=67134
I have been trying, unsuccessfully, to upgrade from 6.1.1.221106 on Windows 11 Pro.
I use https://nextpvr.com/NPVRSetup.exe and the installer runs but when it is complete the version is still 6.1.1.221106.
I have successfully run the installer on a different machine with NO version of NextPVR installed and this successfully installs 7.1.1.260616.
The WebUI for the currently installed version (6.1.1.221106) normally indicates when a new version is available but this is not the case now.
I have held off uninstalling and re-installing but this is an option if necessary, I can export all my recording data prior to uninstall.

Any help gratefully received.]]>
I have been trying, unsuccessfully, to upgrade from 6.1.1.221106 on Windows 11 Pro.
I use https://nextpvr.com/NPVRSetup.exe and the installer runs but when it is complete the version is still 6.1.1.221106.
I have successfully run the installer on a different machine with NO version of NextPVR installed and this successfully installs 7.1.1.260616.
The WebUI for the currently installed version (6.1.1.221106) normally indicates when a new version is available but this is not the case now.
I have held off uninstalling and re-installing but this is an option if necessary, I can export all my recording data prior to uninstall.

Any help gratefully received.]]> <![CDATA[Channel 9 (Brisbane, Australia) issue]]> https://forums.nextpvr.com/showthread.php?tid=67119 Mon, 17 Aug 2026 21:05:01 +0000 SpinyNorman]]> https://forums.nextpvr.com/showthread.php?tid=67119
All is working well except for channel 9 and 9GEM. They give me "Streaming Failed (transcoder exited)" when viewed on a Windows 11 PC and similar on an Apple TV 4k.

I tried nextpvr on the Windows pc, the streams load but then hang. I have a good internet connection (500\50).

I'm using Matt Huisman's raw m3u8 files.

I've tried the different transcoders in nextpvr.

Any advice gratefully received.]]>
All is working well except for channel 9 and 9GEM. They give me "Streaming Failed (transcoder exited)" when viewed on a Windows 11 PC and similar on an Apple TV 4k.

I tried nextpvr on the Windows pc, the streams load but then hang. I have a good internet connection (500\50).

I'm using Matt Huisman's raw m3u8 files.

I've tried the different transcoders in nextpvr.

Any advice gratefully received.]]> <![CDATA[persistent loss of Donation Status]]> https://forums.nextpvr.com/showthread.php?tid=67118 Thu, 13 Aug 2026 15:18:47 +0000 sorahl]]> https://forums.nextpvr.com/showthread.php?tid=67118 My donation status disappears, and thus the channels available to watch (and more importantly record) go away. This disrupts the recording schedule, even after restoration of the donation status. 
Recently, it has become problematic to register that I have donated, as seen in the attached screenshot.

.jpg   nextpvr.jpg (Size: 79.34 KB / Downloads: 32) ]]> My donation status disappears, and thus the channels available to watch (and more importantly record) go away. This disrupts the recording schedule, even after restoration of the donation status. 
Recently, it has become problematic to register that I have donated, as seen in the attached screenshot.

.jpg   nextpvr.jpg (Size: 79.34 KB / Downloads: 32) ]]> <![CDATA[RealTimeIsUniversal.]]> https://forums.nextpvr.com/showthread.php?tid=67105 Wed, 05 Aug 2026 22:26:27 +0000 bufulo]]> https://forums.nextpvr.com/showthread.php?tid=67105 <![CDATA[Using JellyFin as client to NextPVR]]> https://forums.nextpvr.com/showthread.php?tid=67104 Wed, 05 Aug 2026 17:07:49 +0000 ceejayemm]]> https://forums.nextpvr.com/showthread.php?tid=67104
Questions:
1. Is this the correct NextPVR plugin version to use ?  Is there likely to be a revision of the plugin for the new JellyFin 12.x release when this comes about ?

2. Although, as noted above, I can see Live TV and recordings without any visible problems on screen, the Jellyfin log files repeat the following error/warning multiple (lots and lots of) times (http://cmdock-av1:8866 is my Docker NextPVR installation):

Quote:[2026-08-05 01:37:55.319 +01:00] [WRN] [61] Emby.Server.Implementations.Library.LibraryManager: Cannot fetch image from "http://cmdock-av1:8866/service?method=channel.icon&channel_id=7267"
System.InvalidOperationException: Unable to convert any images to local
  at Emby.Server.Implementations.Library.LibraryManager.ConvertImageToLocal(BaseItem item, ItemImageInfo image, Int32 imageIndex, Boolean removeOnFailure)
  at Emby.Server.Implementations.Library.LibraryManager.UpdateImagesAsync(BaseItem item, Boolean forceUpdate)

Is it something I need to worry about ? Am I missing something in the setup of NextPVR or Jellyfin or plugin?  I am not sure if this is a NextPVR or a Jellyfin issue but I thought I would start here as I have some history with NextPVR.  I am happy to move it to the JellyFin forums if this deemed necessary


I have attached a recent set of logs below for both NextPVR and JellyFin.

Thanks for any pointers / help.

Chris

.zip   logs-20260805-1632.zip (Size: 1,017.44 KB / Downloads: 5)

.zip   jellyfin_log_20260805.zip (Size: 36.05 KB / Downloads: 2) ]]>
Questions:
1. Is this the correct NextPVR plugin version to use ?  Is there likely to be a revision of the plugin for the new JellyFin 12.x release when this comes about ?

2. Although, as noted above, I can see Live TV and recordings without any visible problems on screen, the Jellyfin log files repeat the following error/warning multiple (lots and lots of) times (http://cmdock-av1:8866 is my Docker NextPVR installation):

Quote:[2026-08-05 01:37:55.319 +01:00] [WRN] [61] Emby.Server.Implementations.Library.LibraryManager: Cannot fetch image from "http://cmdock-av1:8866/service?method=channel.icon&channel_id=7267"
System.InvalidOperationException: Unable to convert any images to local
  at Emby.Server.Implementations.Library.LibraryManager.ConvertImageToLocal(BaseItem item, ItemImageInfo image, Int32 imageIndex, Boolean removeOnFailure)
  at Emby.Server.Implementations.Library.LibraryManager.UpdateImagesAsync(BaseItem item, Boolean forceUpdate)

Is it something I need to worry about ? Am I missing something in the setup of NextPVR or Jellyfin or plugin?  I am not sure if this is a NextPVR or a Jellyfin issue but I thought I would start here as I have some history with NextPVR.  I am happy to move it to the JellyFin forums if this deemed necessary


I have attached a recent set of logs below for both NextPVR and JellyFin.

Thanks for any pointers / help.

Chris

.zip   logs-20260805-1632.zip (Size: 1,017.44 KB / Downloads: 5)

.zip   jellyfin_log_20260805.zip (Size: 36.05 KB / Downloads: 2) ]]> <![CDATA[Sudden failure of recordings]]> https://forums.nextpvr.com/showthread.php?tid=67066 Thu, 09 Jul 2026 19:39:18 +0000 bruce_rainwater]]> https://forums.nextpvr.com/showthread.php?tid=67066
I checked the disks, they seem to be ok, I recorded and played back using WinTV, everything OK, I tried running Setup again, don't think it did anything.  If I try to playback recordings from NextPvr on another windows viewer they have the same problems.

.zip   logs-20260709-1438.zip (Size: 480.24 KB / Downloads: 2) ]]>
I checked the disks, they seem to be ok, I recorded and played back using WinTV, everything OK, I tried running Setup again, don't think it did anything.  If I try to playback recordings from NextPvr on another windows viewer they have the same problems.

.zip   logs-20260709-1438.zip (Size: 480.24 KB / Downloads: 2) ]]> <![CDATA[Question on Modifying Series Settings]]> https://forums.nextpvr.com/showthread.php?tid=67054 Sat, 27 Jun 2026 14:31:38 +0000 JohnySmith1010]]> https://forums.nextpvr.com/showthread.php?tid=67054
I am recording OTA all the FIFA Football matches on Fox.  As of tomorrow, they will potentially have extra time and PK's if needed?  I think.  What is the best approach to add 1.5 hours to my series settings, forward looking from 06/28/2026?  Should I just wait until the morning, delete the series and readd or can I just modify the existing one?  If I modify existing, will that change todays also?]]>
I am recording OTA all the FIFA Football matches on Fox.  As of tomorrow, they will potentially have extra time and PK's if needed?  I think.  What is the best approach to add 1.5 hours to my series settings, forward looking from 06/28/2026?  Should I just wait until the morning, delete the series and readd or can I just modify the existing one?  If I modify existing, will that change todays also?]]> <![CDATA[JellyFin loosing channels]]> https://forums.nextpvr.com/showthread.php?tid=67053 Fri, 26 Jun 2026 21:21:22 +0000 asaxton]]> https://forums.nextpvr.com/showthread.php?tid=67053
Tony

.zip   logs-20260626-1420.zip (Size: 1.15 MB / Downloads: 0) ]]>
Tony

.zip   logs-20260626-1420.zip (Size: 1.15 MB / Downloads: 0) ]]> <![CDATA[Does NextPVR regularly "ping" schedules direct?]]> https://forums.nextpvr.com/showthread.php?tid=67033 Tue, 16 Jun 2026 14:48:22 +0000 kevin-pvr]]> https://forums.nextpvr.com/showthread.php?tid=67033
The error is...

Schedules Direct [Exceeded maximum number of unique IP addresses in 24 hours. Please contact Schedules Direct support: service@schedulesdirect.org for more information or create a support ticket: https://www.schedulesdirect.org/lineupsupport (not active)]

I can see that my VPN is changing server IP addresses (I am looking into this).  

I have the NextPVR set to request updated schedules once a day.

Does NextPVR regularly "ping" schedules direct even if it is not requesting an update?

Just wondering why SD saw too many IP address changes.

Thanks,
Kevin]]>
The error is...

Schedules Direct [Exceeded maximum number of unique IP addresses in 24 hours. Please contact Schedules Direct support: service@schedulesdirect.org for more information or create a support ticket: https://www.schedulesdirect.org/lineupsupport (not active)]

I can see that my VPN is changing server IP addresses (I am looking into this).  

I have the NextPVR set to request updated schedules once a day.

Does NextPVR regularly "ping" schedules direct even if it is not requesting an update?

Just wondering why SD saw too many IP address changes.

Thanks,
Kevin]]> <![CDATA[Skip frequencies ? Channels missing]]> https://forums.nextpvr.com/showthread.php?tid=67026 Sat, 13 Jun 2026 11:10:27 +0000 FloFlow]]> https://forums.nextpvr.com/showthread.php?tid=67026
Since few days / weeks, lot of issues with NextPVR, so I unsintalled and reinstalled, and now a channel scan on my DVB-T tuner only finds 15 channels.
Still works perfectly with same hardware on Linux.

**Setup:**
- NextPVR 7.1.0.260607 (Windows)
- Tuner: AF9015 BDA Filter (DVB-T)
- Region: France (TNT)

**What the logs show (according to Claude):**
- The tuner locks fine — e.g. at 474000: `locked=1, present=1, strength=20, quality=20`
- But the scan only probes a small set of frequencies: 474, 490, 498, 522, 562, 586 MHz, which is far fewer than the full French UHF lineup.
- Result: `"channelCount": 15` for the DVB-T device (normally around 40)

It really looks like the scan isn't covering all the multiplexes it used to.
I attach the logs.

Thanks!

.zip   logs-20260613-1100.zip (Size: 374.17 KB / Downloads: 1) ]]>
Since few days / weeks, lot of issues with NextPVR, so I unsintalled and reinstalled, and now a channel scan on my DVB-T tuner only finds 15 channels.
Still works perfectly with same hardware on Linux.

**Setup:**
- NextPVR 7.1.0.260607 (Windows)
- Tuner: AF9015 BDA Filter (DVB-T)
- Region: France (TNT)

**What the logs show (according to Claude):**
- The tuner locks fine — e.g. at 474000: `locked=1, present=1, strength=20, quality=20`
- But the scan only probes a small set of frequencies: 474, 490, 498, 522, 562, 586 MHz, which is far fewer than the full French UHF lineup.
- Result: `"channelCount": 15` for the DVB-T device (normally around 40)

It really looks like the scan isn't covering all the multiplexes it used to.
I attach the logs.

Thanks!

.zip   logs-20260613-1100.zip (Size: 374.17 KB / Downloads: 1) ]]> <![CDATA[TVNZ IPTV stopped working.]]> https://forums.nextpvr.com/showthread.php?tid=67005 Wed, 03 Jun 2026 23:40:31 +0000 Jaggy]]> https://forums.nextpvr.com/showthread.php?tid=67005 (TV Three is still working)

These are the channel links I have been using for years

https://i.mjh.nz/.r/tvnz-1.m3u8
https://i.mjh.nz/.r/tvnz-2.m3u8

sub what are you using & are they still working?]]> (TV Three is still working)

These are the channel links I have been using for years

https://i.mjh.nz/.r/tvnz-1.m3u8
https://i.mjh.nz/.r/tvnz-2.m3u8

sub what are you using & are they still working?]]> <![CDATA[Automatic Recording Cleanup]]> https://forums.nextpvr.com/showthread.php?tid=66998 Mon, 25 May 2026 18:02:50 +0000 weavol]]> https://forums.nextpvr.com/showthread.php?tid=66998
 -- Delete Videos that have already been viewed
 -- Delete Videos that have aged like anything more than three weeks old.]]>
 -- Delete Videos that have already been viewed
 -- Delete Videos that have aged like anything more than three weeks old.]]>