Forum NextPVR Forums

Yes, I'm back... TV show set to record at 6:30. Turn on TV, click on in-process recording and nothing. Stop recording. Go to Guide, click on channel and watch Live. Still using exact same signal, watching show via NextPVR. What is it that prevents the recording that allows the live viewing of a perfectly clear broadcast with no glitches? Yes, I know the answer is that NextPVR is pulling data from the HD HomeRun, but it starts the session, and would run the 30 minutes and then display that it couldn't lock signal or similar. Yet, it could, because I watched it live via NextPVR... Can I alter the strength cutoff somehow? Will add logs shortly.

https://xocdia88.mobile/ là một nền tảng giải trí trực tuyến được giới thiệu dành cho người dùng tại Việt Nam. Website cung cấp thông tin về cổng game, các nội dung giới thiệu, chính sách, điều khoản và kênh liên hệ. Giao diện được thiết kế theo hướng đơn giản, giúp người dùng dễ dàng tìm kiếm những thông tin cần thiết và truy cập các khu vực như đăng ký, đăng nhập hoặc tải ứng dụng. Theo thông tin được công bố trên trang web, Xocdia88 hướng dẫn xây dựng một giải pháp trực tuyến thuận tiện trên nhiều thiết bị. Người dùng nên đọc kỹ năng sử dụng, chính sách riêng tư và các quy định liên quan trước khi tham gia. Đồng thời, hãy chủ động kiểm tra thông tin về chương trình, điều kiện sử dụng và mức độ cho phép để đưa ra lựa chọn phù hợp. Việc sử dụng dịch vụ phải được thực hiện có trách nhiệm, kiểm soát thời gian và ngân sách cá nhân.

Hello, I do not know where this question belongs so please move if you feel so. I have an awesome setup here where I am with my HDhomeruns for now however long ATSC 1.0 will work. I do have a remote place, with an antenna up there also whence I frequent. Straight into TV. I have some decent old hardware laying around with a Hauupage USB Dual OTA tuner, PLUS I have a TAP VPN Server here locally that I use. So I was wondering... will something like this work? https://www.eltima.com/products/usb-over-ethernet/ Thought process would be install proper drivers on the computer and make sure it works, then have the computer connect to TAP VPN Server here with a static IP. Would my local NextPVR solution pick it up? I cannot easily test this, as remote location is 1000 miles away. Wanted the brain trusts' input. Thank you.

Hi, 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

Hi, 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

Martin, In this case, I accidentally exited playback during a game, then hit play to resume and wound up on a blank (blue) screen. I've had this issue happen before, but wasn't at a good spot to capture a log. Usually I'm recording several games and jumping around between them. So a bit of a stress test. I think this is around the point of interest in the log 2026-09-27 11:09:09.184 [DEBUG][8] Got request [10.8.19.77]: /control This is from a client machine. After restarting or removing the sid from the json file the recording has lost the resume position. Art logs-20260927-1109.zip (Size: 1.2 MB / Downloads: 1)

Martin, In this case, I accidentally exited playback during a game, then hit play to resume and wound up on a blank (blue) screen. I've had this issue happen before, but wasn't at a good spot to capture a log. Usually I'm recording several games and jumping around between them. So a bit of a stress test. I think this is around the point of interest in the log 2026-09-27 11:09:09.184 [DEBUG][8] Got request [10.8.19.77]: /control This is from a client machine. After restarting or removing the sid from the json file the recording has lost the resume position. Art logs-20260927-1109.zip (Size: 1.2 MB / Downloads: 1)

Hi, 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 -&t ../card1 pci-0000:00:02.0-render -&t ../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-medi

Hi, 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-

Linux Mint 22.3 - Cinnamon 64-bit Kernel 7.0.0-34-generic I have dotnet 10.0.112 manual updates work fine. I tried searching for similar issues...found a few, but no real help Thank you Sterling logs-20260925-1303.zip (Size: 375.31 KB / Downloads: 2)

Linux Mint 22.3 - Cinnamon 64-bit Kernel 7.0.0-34-generic I have dotnet 10.0.112 manual updates work fine. I tried searching for similar issues...found a few, but no real help Thank you Sterling logs-20260925-1303.zip (Size: 375.31 KB / Downloads: 2)

When you're all caught up with life and have nothing better to do, think about this. Would it be possible to somehow distinguish the different device channels in the web TV guide? For example the 6 channels in device 1 would be displayed in red, the 6 channels in device 2 would be displayed in green, etc. Sometimes I have duplicate channels in 2 or more devices and this would make it easier to select which one I want to record from. I realize you've got a lot on your plate, just something to tuck away in your mind as a future enhancement. Thanx for all your hard work.