<![CDATA[NextPVR Forums - Docker amd64]]>

<![CDATA[NextPVR Forums - Docker amd64]]> https://forums.nextpvr.com/ Wed, 13 May 2026 12:06:07 +0000 MyBB <![CDATA[SATIP Channel scan returns no channels on 7.0.5]]> https://forums.nextpvr.com/showthread.php?tid=66919 Fri, 20 Mar 2026 17:44:25 +0000 something_fishy]]> https://forums.nextpvr.com/showthread.php?tid=66919 docker pull nextpvr/nextpvr_amd64:prerelease, all other container parameters unchanged) also finds channels as expected.

Logs are attached from immediately after the channel scan.

As an aside would it be possible to have the previous version kept on Docker Hub for reversion purposes.

.zip

logs-20260320-1739.zip (Size: 1.21 MB / Downloads: 1) ]]> docker pull nextpvr/nextpvr_amd64:prerelease, all other container parameters unchanged) also finds channels as expected.

Logs are attached from immediately after the channel scan.

As an aside would it be possible to have the previous version kept on Docker Hub for reversion purposes.

.zip

logs-20260320-1739.zip (Size: 1.21 MB / Downloads: 1) ]]> <![CDATA[Tinyurl xml giving error]]> https://forums.nextpvr.com/showthread.php?tid=66905 Thu, 12 Mar 2026 00:09:27 +0000 Basche]]> https://forums.nextpvr.com/showthread.php?tid=66905

Code:
[32] Unexpected error processing xmltv file (http...): System.IO.InvalidDataException: The archive entry was compressed using an unsupported compression method.

   at System.IO.Compression.Inflater.Inflate(FlushCode flushCode)

   at System.IO.Compression.Inflater.ReadInflateOutput(Byte* bufPtr, Int32 length, FlushCode flushCode, Int32& bytesRead)

   at System.IO.Compression.Inflater.ReadOutput(Byte* bufPtr, Int32 length, Int32& bytesRead)

   at System.IO.Compression.Inflater.InflateVerified(Byte* bufPtr, Int32 length)

   at System.IO.Compression.DeflateStream.ReadCore(Span`1 buffer)

   at System.IO.Stream.ReadAtLeastCore(Span`1 buffer, Int32 minimumBytes, Boolean throwOnEndOfStream)

   at System.IO.Stream.ReadAtLeast(Span`1 buffer, Int32 minimumBytes, Boolean throwOnEndOfStream)

   at System.Xml.XmlTextReaderImpl.InitStreamInput(Uri baseUri, String baseUriStr, Stream stream, Byte[] bytes, Int32 byteCount, Encoding encoding)

   at System.Xml.XmlTextReaderImpl..ctor(String url, Stream input, XmlNameTable nt)

   at System.Xml.XmlTextReader..ctor(Stream input)

   at NShared.XmltvEPGSource.LoadXmlTv(String fileLocation)

   at NShared.XmltvEPGSource.UpdateEPG(List`1 channels, IEPGUpdateCallback callback, String specificSource)

[32] https://tinyurl.com/.../xxxxxxxx?....  [fe+CLt2kBCsXj5KcDMnvGdEhbvz6S/201b1roh+e05YTBqMp/czx87Y29prpodafMfnTYV1Ci0CNm6zt1DeaO0icVzQS870RQNmDXC1pwcb++0h8O8yniQ7+CegCQiuZageD9nEoqK+Rsp5GcldfE3vpWAz+ArIgdajMu4FlkfHwMSHMAIhFnIv2t5Z5z9DAp51MQf5/8FkryJFGOAOQXYgICqhCIsDU/NLGw6o8wPUZ3KkwxlikzJ7Vi7u2cl/Geqc1fLh16gM9FzJdFVg+oj8xawQGZDJh1pBTFXVh29AhcKd15B65M+maAmgYr156Wq30prwpbOioY0tWUjOZre8Kn6PVj0BHx01Xk3RLfAagGYpWTdRaJJy27ttw5HRbfBUSyh1+7WdiuR8fuMxyyw==]

EDIT: Looks like there was an error with the m3u URL as well.

Code:
[16] System.Collections.Generic.KeyNotFoundException: The given key 'https://tinyurl.com/XXXXXXX' was not present in the dictionary.

   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

   at NShared.IPTVRecorder.StoreNewChannels(List`1 channels)

   at NShared.Extend.SettingsRequestHandler.ScanSave(Dictionary`2 parameters)

]]>

Code:
[32] Unexpected error processing xmltv file (http...): System.IO.InvalidDataException: The archive entry was compressed using an unsupported compression method.

   at System.IO.Compression.Inflater.Inflate(FlushCode flushCode)

   at System.IO.Compression.Inflater.ReadInflateOutput(Byte* bufPtr, Int32 length, FlushCode flushCode, Int32& bytesRead)

   at System.IO.Compression.Inflater.ReadOutput(Byte* bufPtr, Int32 length, Int32& bytesRead)

   at System.IO.Compression.Inflater.InflateVerified(Byte* bufPtr, Int32 length)

   at System.IO.Compression.DeflateStream.ReadCore(Span`1 buffer)

   at System.IO.Stream.ReadAtLeastCore(Span`1 buffer, Int32 minimumBytes, Boolean throwOnEndOfStream)

   at System.IO.Stream.ReadAtLeast(Span`1 buffer, Int32 minimumBytes, Boolean throwOnEndOfStream)

   at System.Xml.XmlTextReaderImpl.InitStreamInput(Uri baseUri, String baseUriStr, Stream stream, Byte[] bytes, Int32 byteCount, Encoding encoding)

   at System.Xml.XmlTextReaderImpl..ctor(String url, Stream input, XmlNameTable nt)

   at System.Xml.XmlTextReader..ctor(Stream input)

   at NShared.XmltvEPGSource.LoadXmlTv(String fileLocation)

   at NShared.XmltvEPGSource.UpdateEPG(List`1 channels, IEPGUpdateCallback callback, String specificSource)

[32] https://tinyurl.com/.../xxxxxxxx?....  [fe+CLt2kBCsXj5KcDMnvGdEhbvz6S/201b1roh+e05YTBqMp/czx87Y29prpodafMfnTYV1Ci0CNm6zt1DeaO0icVzQS870RQNmDXC1pwcb++0h8O8yniQ7+CegCQiuZageD9nEoqK+Rsp5GcldfE3vpWAz+ArIgdajMu4FlkfHwMSHMAIhFnIv2t5Z5z9DAp51MQf5/8FkryJFGOAOQXYgICqhCIsDU/NLGw6o8wPUZ3KkwxlikzJ7Vi7u2cl/Geqc1fLh16gM9FzJdFVg+oj8xawQGZDJh1pBTFXVh29AhcKd15B65M+maAmgYr156Wq30prwpbOioY0tWUjOZre8Kn6PVj0BHx01Xk3RLfAagGYpWTdRaJJy27ttw5HRbfBUSyh1+7WdiuR8fuMxyyw==]

EDIT: Looks like there was an error with the m3u URL as well.

Code:
[16] System.Collections.Generic.KeyNotFoundException: The given key 'https://tinyurl.com/XXXXXXX' was not present in the dictionary.

   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

   at NShared.IPTVRecorder.StoreNewChannels(List`1 channels)

   at NShared.Extend.SettingsRequestHandler.ScanSave(Dictionary`2 parameters)

]]> <![CDATA[overlapping streams]]> https://forums.nextpvr.com/showthread.php?tid=66776 Wed, 21 Jan 2026 16:46:11 +0000 krasty633]]> https://forums.nextpvr.com/showthread.php?tid=66776 My base operating system is Debian 13. I have also tested this with different operating systems such as Unraid and others, and the behavior is always the same.

If I only watch a single stream or make one recording, it works perfectly. As soon as I start a second stream or recording, the overlapping issue happens.

Is there a setting I can check or adjust for this?

Thank you in advance for your help.]]> My base operating system is Debian 13. I have also tested this with different operating systems such as Unraid and others, and the behavior is always the same.

If I only watch a single stream or make one recording, it works perfectly. As soon as I start a second stream or recording, the overlapping issue happens.

Is there a setting I can check or adjust for this?

Thank you in advance for your help.]]> <![CDATA[No nvenc option]]> https://forums.nextpvr.com/showthread.php?tid=66770 Sat, 17 Jan 2026 17:19:26 +0000 javaqueen]]> https://forums.nextpvr.com/showthread.php?tid=66770
image: Nextpvr/nextpvr_amd64 Confused

table

There appears to be no option in the settings menu to choose nvenc ? only "vaapi" and "cpu" is present and this causes issues with some of my streams.
i probed ffmpeg inside the container and this is the output ....

docker exec -it tv-frontend bash
root@ee238cb68e37:/app# ffmpeg -encoders | grep nvenc
ffmpeg version 5.1.6-0+deb12u1 Copyright © 2000-2024 the FFmpeg developers
built with gcc 12 (Debian 12.2.0-14)
configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
libavutil 57. 28.100 / 57. 28.100
libavcodec 59. 37.100 / 59. 37.100
libavformat 59. 27.100 / 59. 27.100
libavdevice 59. 7.100 / 59. 7.100
libavfilter 8. 44.100 / 8. 44.100
libswscale 6. 7.100 / 6. 7.100
libswresample 4. 7.100 / 4. 7.100
libpostproc 56. 6.100 / 56. 6.100
V....D h264_nvenc NVIDIA NVENC H.264 encoder (codec h264)
V....D hevc_nvenc NVIDIA NVENC hevc encoder (codec hevc)
root@ee238cb68e37:/app# exit

I also tried to delete the container adding "--gpus all" nvidia to runtime and -e variables NVIDIA_VISIBLE_DEVICES=all
NVIDIA_DRIVER_CAPABILITIES=compute,video,utility.

Im kind of at a loss and I Dont know what else to do .]]>
image: Nextpvr/nextpvr_amd64 Confused

2026-01-09 15_33_06-Settings — Firefox Developer Edition.png (Size: 4.95 KB / Downloads: 68) ]]>
.png

2026-01-09 15_33_06-Settings — Firefox Developer Edition.png (Size: 4.95 KB / Downloads: 68) ]]> <![CDATA[Issue with scanning DVB-T channels]]> https://forums.nextpvr.com/showthread.php?tid=66690 Mon, 17 Nov 2025 20:39:55 +0000 zbuzanic]]> https://forums.nextpvr.com/showthread.php?tid=66690
>>> Scanning 546000000

but nothing is detected, same machine, same card in Windows nextpvr works fine. I tried to copy npvr.db3 from windows data and then I got channels there but it does not work so I'm attaching logs, maybe you can help me with this.

I tried to scan inside docker:

./DeviceHostLinux -device:adapter0 -type: DVB-T -scan:/usr/share/dvb/dvb-t/hr-All
Partial output (not sure if this meas it found something or not):

Code:
025-11-17 21:33:41:966 [DEBUG] >>> Scanning 690000000

       (0x00) Signal= -91.99dBm

          Layer A: Signal= 0.00%

               (0x00) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

logs-20251117-2125.zip (Size: 72.06 KB / Downloads: 2) ]]>
>>> Scanning 546000000

but nothing is detected, same machine, same card in Windows nextpvr works fine. I tried to copy npvr.db3 from windows data and then I got channels there but it does not work so I'm attaching logs, maybe you can help me with this.

I tried to scan inside docker:

./DeviceHostLinux -device:adapter0 -type: DVB-T -scan:/usr/share/dvb/dvb-t/hr-All
Partial output (not sure if this meas it found something or not):

Code:
025-11-17 21:33:41:966 [DEBUG] >>> Scanning 690000000

       (0x00) Signal= -91.99dBm

          Layer A: Signal= 0.00%

               (0x00) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

          Layer A: Signal= 36.82%

        RF     (0x01) Signal= -71.87dBm

logs-20251117-2125.zip (Size: 72.06 KB / Downloads: 2) ]]> <![CDATA[new build old docker]]> https://forums.nextpvr.com/showthread.php?tid=66670 Sun, 09 Nov 2025 04:48:01 +0000 techpro2004]]> https://forums.nextpvr.com/showthread.php?tid=66670 <![CDATA[Channel tuning issue - ABC Australia in Melbourne]]> https://forums.nextpvr.com/showthread.php?tid=66633 Tue, 21 Oct 2025 03:11:12 +0000 bossanova808]]> https://forums.nextpvr.com/showthread.php?tid=66633
As of this morning, I am using the `docker image: nextpvr/nextpvr_amd64 Confused

table` - prior to this I have had NextPVR working well for years with Windows 10.

(This is Docker in an LXC on Proxmox, hardware is a Hauppage WinTV 2200 PCI card).

It's mostly working well, I can stream TV etc...but I just cannot get it to tune ABC here in Melbourne (I'm located reasonably centrally). Previously I've had no issues tuning ABC under Windows (although I do recall, very long ago, I perhaps had to modify some config somewhere but not sure if that was ABC related or something else...)

It appears you're now using: https://git.linuxtv.org/dtv-scan-tables....-Melbourne - is that right? And the files I found in the docker tuning folder are not used?

In any case, I have tried all the available options vaguely related to Melbourne (and my state, Victoria) options in the list - none result in ABC becoming available. The main Melbourne available options are all for towers quite some distance from central Melbourne, and there is a more local option:

https://ozdigitaltv.com/transmitters/VIC/720-Melbourne, which lists:

ABC
ABC43
634.500 Mhz

vs what seems to be in the current Melbourne related entries:

ABC
ABC12
226.500 Mhz

(I am fairly confident I was using 226.500 in the past though, as it happens). Perhaps something is going on with signal strength - it is possible to extend the searching time and/or lower the threshold to see what happens? I've ne ver had any actual playback issues once things were tuned.

Is there some way to explicitly try particular frequencies, rather than use these lists (that are seemingly rather incomplete)? Basically - what can I do to get this solved?

(I see recommendations for tscapture etc for daignosis - is there a Linux equivalent?)]]>
As of this morning, I am using the `docker image: nextpvr/nextpvr_amd64 Confused

table` - prior to this I have had NextPVR working well for years with Windows 10.

(This is Docker in an LXC on Proxmox, hardware is a Hauppage WinTV 2200 PCI card).

It's mostly working well, I can stream TV etc...but I just cannot get it to tune ABC here in Melbourne (I'm located reasonably centrally). Previously I've had no issues tuning ABC under Windows (although I do recall, very long ago, I perhaps had to modify some config somewhere but not sure if that was ABC related or something else...)

It appears you're now using: https://git.linuxtv.org/dtv-scan-tables....-Melbourne - is that right? And the files I found in the docker tuning folder are not used?

In any case, I have tried all the available options vaguely related to Melbourne (and my state, Victoria) options in the list - none result in ABC becoming available. The main Melbourne available options are all for towers quite some distance from central Melbourne, and there is a more local option:

https://ozdigitaltv.com/transmitters/VIC/720-Melbourne, which lists:

ABC
ABC43
634.500 Mhz

vs what seems to be in the current Melbourne related entries:

ABC
ABC12
226.500 Mhz

(I am fairly confident I was using 226.500 in the past though, as it happens). Perhaps something is going on with signal strength - it is possible to extend the searching time and/or lower the threshold to see what happens? I've ne ver had any actual playback issues once things were tuned.

Is there some way to explicitly try particular frequencies, rather than use these lists (that are seemingly rather incomplete)? Basically - what can I do to get this solved?

(I see recommendations for tscapture etc for daignosis - is there a Linux equivalent?)]]> <![CDATA[Is it possible to redirect the web\temp folder]]> https://forums.nextpvr.com/showthread.php?tid=66544 Fri, 12 Sep 2025 01:55:17 +0000 TheFonz]]> https://forums.nextpvr.com/showthread.php?tid=66544 is it possible to redirect that with the docker run command:

Code:
docker run -d

--name nextpvr

--user root:10000

--volume /root/config:/config

--volume /mnt/livetv:/recordings

--volume /mnt/livetv:/buffer

--volume /mnt/livetv:/web/temp 

--restart unless-stopped

--publish 16891:16891/udp

--publish 8866:8866

nextpvr/nextpvr_amd64:stable

(adding the line: --volume /mnt/livetv:/web/temp )
would that do it??

TIA!
_Fonz]]> is it possible to redirect that with the docker run command:

Code:
docker run -d

--name nextpvr

--user root:10000

--volume /root/config:/config

--volume /mnt/livetv:/recordings

--volume /mnt/livetv:/buffer

--volume /mnt/livetv:/web/temp 

--restart unless-stopped

--publish 16891:16891/udp

--publish 8866:8866

nextpvr/nextpvr_amd64:stable

(adding the line: --volume /mnt/livetv:/web/temp )
would that do it??

TIA!
_Fonz]]> <![CDATA[Docker image for arm64?]]> https://forums.nextpvr.com/showthread.php?tid=66541 Wed, 10 Sep 2025 21:47:40 +0000 Jack_Burton505]]> https://forums.nextpvr.com/showthread.php?tid=66541
So to get closer to my question: I just realized there isn't a NextPVR Docker image for arm64. What I've been able to find (after asking my friend Google multiple questions) says the arm32v7 image won't work with M4 machines and the amd64 image is for Intel machines. But, I also saw that Docker has some sort of built-in emulation process, and using the amd64 image might work in Docker (or maybe Orbstack instead) on Mac OS on an M4 machine. Can anyone offer any advice on this?

Failing being able to run in a Docker container on the Mac, at this point I think my only other options are to add a Raspberry Pi 3 to the network and run the server on it in linux or Docker (but I'd rather not add another device I have to manage and pay attention to) or run it in a Docker container on the NAS, which has an Intel chip.

The NextPVR forum has been very helpful to me, and I thank you in advance for any help you can provide.]]>
So to get closer to my question: I just realized there isn't a NextPVR Docker image for arm64. What I've been able to find (after asking my friend Google multiple questions) says the arm32v7 image won't work with M4 machines and the amd64 image is for Intel machines. But, I also saw that Docker has some sort of built-in emulation process, and using the amd64 image might work in Docker (or maybe Orbstack instead) on Mac OS on an M4 machine. Can anyone offer any advice on this?

Failing being able to run in a Docker container on the Mac, at this point I think my only other options are to add a Raspberry Pi 3 to the network and run the server on it in linux or Docker (but I'd rather not add another device I have to manage and pay attention to) or run it in a Docker container on the NAS, which has an Intel chip.

The NextPVR forum has been very helpful to me, and I thank you in advance for any help you can provide.]]> <![CDATA[Distorted Audio]]> https://forums.nextpvr.com/showthread.php?tid=66533 Fri, 05 Sep 2025 13:21:50 +0000 magnetar]]> https://forums.nextpvr.com/showthread.php?tid=66533
I'm running NextPVR in docker on an Unraid server. I've tried transcoding via CPU and VAAPI but it has the same results. I also tried linking NextPVR to my Emby server and running it through that but it has the same results.

Any ideas what is going on? Thanks.]]>
I'm running NextPVR in docker on an Unraid server. I've tried transcoding via CPU and VAAPI but it has the same results. I also tried linking NextPVR to my Emby server and running it through that but it has the same results.

Any ideas what is going on? Thanks.]]> <![CDATA[Using RAM for /buffer causes crash]]> https://forums.nextpvr.com/showthread.php?tid=66455 Sun, 27 Jul 2025 16:50:42 +0000 LiLao]]> https://forums.nextpvr.com/showthread.php?tid=66455
How, here's my docker compose:

services:
nextpvr:
image: nextpvr/nextpvr_amd64:latest
container_name: nextpvr
restart: unless-stopped
privileged: true # Necessario per accedere ai dispositivi DVB
ports:
- 8866:8866 # Porta per l'interfaccia web
- 16891:16891 # Porta per l'accesso ai dispositivi remoti
devices:
- /dev/dvb:/dev/dvb # Passa i dispositivi DVB al container
volumes:
- /mnt/Applicazioni/NextPVRConfig:/config # Configurazione persistente
- /mnt/VAULT/registrazioni:/recordings # Directory per le registrazioni
tmpfs:
- /buffer Confused

ize=536870912 # 512MB in RAM per il buffer (in byte)
environment:
- PUID=568
- PGID=568
- TZ=Europe/Rome
networks: {}

As you can see i've used tmpfs for storing the /buffer directory and i've experimented both with 256MB and 512MB buffer sizes, and what i noticed is that after a while (this time gets longer as the buffer size is increased) the stream eventually locks up, as this didn't happen before this is cleary the buffer filling up with stuff and NextPVR not being able to "Garbage Collect" the buffer.

Is this a bug? Does NextPVR normaly empty out the buffer during playback or it justs fills up until the stream is interrupted ?]]>
How, here's my docker compose:

services:
nextpvr:
image: nextpvr/nextpvr_amd64:latest
container_name: nextpvr
restart: unless-stopped
privileged: true # Necessario per accedere ai dispositivi DVB
ports:
- 8866:8866 # Porta per l'interfaccia web
- 16891:16891 # Porta per l'accesso ai dispositivi remoti
devices:
- /dev/dvb:/dev/dvb # Passa i dispositivi DVB al container
volumes:
- /mnt/Applicazioni/NextPVRConfig:/config # Configurazione persistente
- /mnt/VAULT/registrazioni:/recordings # Directory per le registrazioni
tmpfs:
- /buffer Confused

ize=536870912 # 512MB in RAM per il buffer (in byte)
environment:
- PUID=568
- PGID=568
- TZ=Europe/Rome
networks: {}

As you can see i've used tmpfs for storing the /buffer directory and i've experimented both with 256MB and 512MB buffer sizes, and what i noticed is that after a while (this time gets longer as the buffer size is increased) the stream eventually locks up, as this didn't happen before this is cleary the buffer filling up with stuff and NextPVR not being able to "Garbage Collect" the buffer.

Is this a bug? Does NextPVR normaly empty out the buffer during playback or it justs fills up until the stream is interrupted ?]]> <![CDATA[NZ IPTV url - streaming failed]]> https://forums.nextpvr.com/showthread.php?tid=66449 Tue, 22 Jul 2025 08:08:40 +0000 Jamo]]> https://forums.nextpvr.com/showthread.php?tid=66449
Hoping you can help me - im trying to stream nz IPTV from this url - https://i.mjh.nz/nz/raw-tv.m3u8

I'm running a Synology DS918+ and have NextPVR setup as a container.

It loads fine in NextPVR and discovers all channels but when going to stream through chrome, android app, apple app or emby it fails everytime for any channel, starts off 'starting device, then after 20 seconds or so comes back red 'streaming failed, transcoder exited'

If using this same url through my tivimate app or IPTV app (Android) for example it works absolutely flawlessly.

Appreciate any input to help me get this working please.

Have uploaded log if that helps.

I also have 2 other services i use through NextPVR and they work perfect, it just seems to be this NZ url that doesn't stream.

I'm racking my brains to figure this out if you can help.

Thanks.

.png

NextPVR Streaming Failed.png (Size: 35.47 KB / Downloads: 32)

.zip

logs-20250722-0801.zip (Size: 1.77 MB / Downloads: 1) ]]>
Hoping you can help me - im trying to stream nz IPTV from this url - https://i.mjh.nz/nz/raw-tv.m3u8

I'm running a Synology DS918+ and have NextPVR setup as a container.

It loads fine in NextPVR and discovers all channels but when going to stream through chrome, android app, apple app or emby it fails everytime for any channel, starts off 'starting device, then after 20 seconds or so comes back red 'streaming failed, transcoder exited'

If using this same url through my tivimate app or IPTV app (Android) for example it works absolutely flawlessly.

Appreciate any input to help me get this working please.

Have uploaded log if that helps.

I also have 2 other services i use through NextPVR and they work perfect, it just seems to be this NZ url that doesn't stream.

I'm racking my brains to figure this out if you can help.

Thanks.

.png

NextPVR Streaming Failed.png (Size: 35.47 KB / Downloads: 32)

.zip

logs-20250722-0801.zip (Size: 1.77 MB / Downloads: 1) ]]> <![CDATA[Docker options]]> https://forums.nextpvr.com/showthread.php?tid=66435 Sat, 12 Jul 2025 08:42:35 +0000 tom_tav]]> https://forums.nextpvr.com/showthread.php?tid=66435
First steps into nextpvr it raised some questions:

1. When starting the container in host mode .... it seems the container doesnt get a valid ip via DHCP. And to set it manually for testing is a little bit difficult with the missing ipaddr tool. Do i miss something? (Docker is running on OS X)

2. The "--env SATIP_DEVICES=xxx" option. I found some hints here but it is not in the docs. In the forum there is one usage of "--env SATIP_DEVICES=http://192.168.178.20/octoserve/octonet.xml" ... but what exactly is it expecting? Is it just a link to the receivers channel list? The m3u style request string? ... The ffmpeg -i option params?

3. The extras-*.xml file: The documentation is refering to put the file into the "data" dir, which is a little bit misleading because all the docker related docs is not mentioning data. In fact it is loaded from /config. Also a hint to properly format XML ( "&" -> "&") would be good, many receiver strings do have these characters inside the request strings

These are just some points i stumbled over, the main problem and one bug i did encounter i will open another thread to nut clutter this one

Cant wait to get nextpvr working and to see what it can Smile

]]>
First steps into nextpvr it raised some questions:

1. When starting the container in host mode .... it seems the container doesnt get a valid ip via DHCP. And to set it manually for testing is a little bit difficult with the missing ipaddr tool. Do i miss something? (Docker is running on OS X)

2. The "--env SATIP_DEVICES=xxx" option. I found some hints here but it is not in the docs. In the forum there is one usage of "--env SATIP_DEVICES=http://192.168.178.20/octoserve/octonet.xml" ... but what exactly is it expecting? Is it just a link to the receivers channel list? The m3u style request string? ... The ffmpeg -i option params?

3. The extras-*.xml file: The documentation is refering to put the file into the "data" dir, which is a little bit misleading because all the docker related docs is not mentioning data. In fact it is loaded from /config. Also a hint to properly format XML ( "&" -> "&") would be good, many receiver strings do have these characters inside the request strings

These are just some points i stumbled over, the main problem and one bug i did encounter i will open another thread to nut clutter this one

Cant wait to get nextpvr working and to see what it can Smile

]]> <![CDATA[Migrating from Windows to Docker?]]> https://forums.nextpvr.com/showthread.php?tid=66379 Mon, 09 Jun 2025 19:38:55 +0000 boringgit]]> https://forums.nextpvr.com/showthread.php?tid=66379 )

It also runs docker with a few images, including Cloudflare tunnel which I use for remote access to NPVR - config, not streaming.

I wondered about migrating to Linux as I can then use host networking for HomeAssistant which is pretty much required in order to use discovery.

2 questions:

Currently all my NPVR recordings are saved to my NAS, I just run the NPVR service as a user in Windows who can access the NAS and it works fine with the UNC path. Is there a similarly easy method in Docker? I saw lots of doom and gloom over UNC paths on these forums, but a lot of that was historic.

How easy is it to migrate the config? I'm aware I could just add my recordings again, but that's extra effort and I'm already wondering if I can be bothered Smile

I'm on my third or fourth Windows NPVR install and migrating in Win is easy as it gets Smile

Thanks in advance!]]> )

It also runs docker with a few images, including Cloudflare tunnel which I use for remote access to NPVR - config, not streaming.

I wondered about migrating to Linux as I can then use host networking for HomeAssistant which is pretty much required in order to use discovery.

2 questions:

Currently all my NPVR recordings are saved to my NAS, I just run the NPVR service as a user in Windows who can access the NAS and it works fine with the UNC path. Is there a similarly easy method in Docker? I saw lots of doom and gloom over UNC paths on these forums, but a lot of that was historic.

How easy is it to migrate the config? I'm aware I could just add my recordings again, but that's extra effort and I'm already wondering if I can be bothered Smile

I'm on my third or fourth Windows NPVR install and migrating in Win is easy as it gets Smile

Thanks in advance!]]>