I'm experiencing live tv issues since upgrading. I'm on version 6.1.4.230625 running on a Pi4 with multiple pi4 Kodi clients connecting. Live TV plays for a few seconds, buffers and then plays - which has been the same behavior in previous versions. However, I am now getting further buffering - seems to be centered around when a recording starts or stops, or when another Kodi client connects and is streaming live TV.
In addition to this, I am now getting audio / video sync issues once the buffering clears. I did a "stress" test of the system and had multiple clients connected, while recording a few different channels. This is not the normal use case, but maybe a recording here or there with 2 Kodi clients watching live TV is the norm. It resulted in everything playing and recording fine for a while, but then a long freeze, followed by a recovery, but all clients streaming showed the audio / video sync issues. Video seemed ahead of the audio.
I have the nextpvr server live TV directory set to the SD on the pi4. I have the recording directory set to a usb mounted drive. In the past versions I didn't have these issues.
The nextpvr logs are attached. I'm hoping I have a simple setup issue.
How do I get REW and FF to show up while viewing IPTV on the Android client? I have pause and stop at the bottom of my screen when I press my remote but nothing else.
I've had problems recording Jeopardy! recently. It happened a few times since I installed NextPVR several months ago, but only infrequently and with no consistency. Most of the time Jeopardy! records normally and with no issues. Now the same problem has happened two days in a row. In every single instance the recording has started OK but then when I try to watch the recorded show later it simply will not play. When I examine the files on my hard drive I find the truncated recordings always have exactly the same file size of 5,569KB ( they should be more like 1.5 ish GB).
In searching through the logs, the only error I find is this...
2023-09-26 19:29:27.439 [DEBUG][39] Request had range request
2023-09-26 19:29:27.439 [DEBUG][39] Requested Range: 0- (0 bytes)
2023-09-26 19:29:27.441 [ERROR][39] IsComplete(): Object reference not set to an instance of an object.
I don't know what "range request" might be or why it would be there.
I am currently using channels dvr but dislike its non-support for roku and windows pc. My main question was: how much resources nextpvr uses roughly to just display iptv from channels (tve+chrome capture). Its unfortunate I have to run more than one. Also, could nextpvr take advantage of something similar? https://github.com/fancybits/chrome-capt...r-channels
Posted by: djenson - 2023-09-28, 10:37 AM - Forum: Wishlist
- No Replies
I think this would be quite useful for some that have multiple series recordings setup. An ability to lock certain recordings to prevent them being overwritten would be a nice sub feature too.
Hi, I'm at my wits' end with this feeling like I've tried everything so I'm hoping someone may be able to help please.
I've recently bought a mini PC with an Intel N100 which I'm hoping to use for NextPVR and Jellyfin with a Hauppauge WinTV DualHD. Initially I started off using Debian but have swapped to Ubuntu 22.04 LTS trying to see if it might help with my issue (below).
Where I've got to is that the official NextPVR docker container is fine with the default kernel (5.15) of Ubuntu 22.04. The quality is decent and everything in NextPVR seems to work but I've obviously got no QuickSync for either NextPVR or Jellyfin to use. My problem seems to come about when I upgrade my kernel to one which will play nice with the N100 for Quicksync. As soon as I start watching DVB-T2 channels through NextPVR they're unwatchable due to corruption (see attached image).
I've tried a few different kernels (5.17, 5.19, 6.5 to name a few) and this happens straight away with them because they have support for the N100. 5.15 is the only one I've had fine initially until I add the Intel drivers into the mix. I've tried the docker container from Ranbato which uses ffmpeg 5 as well as bulding my own with ffmpeg 6 and the Intel drivers (which is the only way I ccould get vainfo in the NextPVR container to work) but no luck for this issue, which I should add is only an issue for DVB-T2.
Most strangely recordings seem to come out ok and watching another channel while that recording is going on seems to be better but not perfect still.
None of this seems to change whether I'm using CPU or VAAPI transcoding though the VAAPI output is a lot lower quality with horrible interlacing (seemingly at least on live tv, I think recordings are ok or aren't as bad).
I can see these errors in the logs which seem to be showing the corruption but I'm completely at a loss as to how to solve this.
Quote:[28] [FFMPEG]: [h264 @ 0x55de9dfd0140] concealing 3074 DC, 3074 AC, 3074 MV errors in B frame
[36] [FFMPEG]: [h264 @ 0x55de9e086e40] cabac decode of qscale diff failed at 92 37
[36] [FFMPEG]: [h264 @ 0x55de9e086e40] error while decoding MB 92 36, bytestream 1185
[36] [FFMPEG]: [h264 @ 0x55de9e086e40] concealing 3797 DC, 3797 AC, 3797 MV errors in B frame
I've attached logs with a brand new container where I've used just one of the tuners to scan for channels and started watching BBC 1 HD which then presents the issue.
Posted by: sweh - 2023-09-26, 12:54 AM - Forum: Linux
- Replies (22)
So I'm a n00b at this software. Indeed a n00b at OTA recording in general. A Linux geek, but a n00b here :-)
I have a Hauppauge "WinTV DualHD" USB device, and I'm running on Debian 12. It appears all the necessary drivers are present OOB because the controller shows up.
In NextPVR I can pick "adapter0/frontend0 (LG Electronics LGDT3306A VSB/QAM Frontend)" and tell it to scan, and it finds 86 channels; close enough to what my TV found with the antenna plugged into that. Since it's a dual tuner I duplicated that to adapter1/...
And that's good; I can tune to channels and it works. I can watch TV; yay!
So now the EPG problem.
I configured each channel via AutoMap "ATSC" "DVB/ATSC EPG" "Numbers and Identifiers".
Based on comments I saw on this forum I also adjusted the timeout to be 120 seconds, but I'm not sure that's important.
I then do an Update EPG. And I can see it scanning.
The device adapter log shows activity
eg
Code:
2023-09-25 20:42:33:416 [DEBUG] ProcessRequest@1
2023-09-25 20:42:33:416 [DEBUG] ProcessRequest@2
2023-09-25 20:42:33:416 [DEBUG] ProcessRequest@done
2023-09-25 20:42:33:423 [DEBUG] Got table_id=c7
2023-09-25 20:42:33:423 [DEBUG] Got MGT
2023-09-25 20:42:33:423 [INFO] Removing all PIDs
2023-09-25 20:42:33:424 [DEBUG] Reading VCT
2023-09-25 20:42:33:681 [DEBUG] - WCBS-HD (source_id=0x1)
2023-09-25 20:42:33:681 [DEBUG] - STARTTV (source_id=0x2)
2023-09-25 20:42:33:681 [DEBUG] - DABL (source_id=0x3)
2023-09-25 20:42:33:681 [DEBUG] - FAVE-TV (source_id=0x4)
2023-09-25 20:42:33:681 [DEBUG] - CIRCLE (source_id=0x5)
2023-09-25 20:42:33:682 [DEBUG] EIT-0: 0x1388
2023-09-25 20:42:33:682 [DEBUG] EIT-1: 0x1389
...
2023-09-25 20:42:33:705 [DEBUG] ETT-22: 0x141e
2023-09-25 20:42:33:705 [DEBUG] ETT-23: 0x141f
2023-09-25 20:42:38:423 [DEBUG] Received 133668 bytes from device so far
2023-09-25 20:42:43:480 [DEBUG] Received 150212 bytes from device so far
2023-09-25 20:42:48:538 [DEBUG] Received 252296 bytes from device so far
2023-09-25 20:42:48:716 [DEBUG] EPG collection thread exiting
2023-09-25 20:42:48:716 [DEBUG] @exit
2023-09-25 20:42:53:545 [DEBUG] Received 268840 bytes from device so far
2023-09-25 20:42:58:603 [DEBUG] Received 314900 bytes from device so far
...
2023-09-25 20:44:24:278 [DEBUG] Received 1057500 bytes from device so far
2023-09-25 20:44:29:336 [DEBUG] Received 1158456 bytes from device so far
2023-09-25 20:44:32:290 [INFO] received request
2023-09-25 20:44:32:290 [DEBUG] about to process request...
2023-09-25 20:44:32:290 [DEBUG] got 75 bytes
2023-09-25 20:44:32:290 [DEBUG] got request:
Hi NextPVR devs - I have noticed that after 5 - 7 days, my hauppage adapter will fail to play antenna (ATSC) channels. Restarting NextPVR always fixes the issue. Please help me diagnose this .
Attaching logs, let me know if you need anything else!
FWIW this seems to be the relative part of the logs from what I can tell -
Thought I had better make a new thread.
This is a follow on to the Windows 10 vs 11 thread.
I believe I have discovered a way to resolve the micro-stutter issue mentioned in the other thread.
As mentioned, I am having problems playing back STB recordings in Kodi.
The thought occurred to me that if Kodi has issues playing back the TS files, what would happen if I converted to a different format.
I tried the following using the FFmpeg in NextPVR/Other folder.
It created a new mp4 file in around 10 seconds on my rig.
When I tested the above file in Kodi, to my surprise it plays perfectly, and does not exhibit the micro-stutters that the original TS recording has.
I am wondering if I can use postprocessing.bat to issue the above ffmpeg conversion automatically?, OR could I use the transcoding feature of NextPVR.
I am thinking postprocessing would be best, as I believe it is not recoding the original video.
.