I need some advice please with regards to dealing with MPD files.
I currently have two NextPVR servers.
One in the UK, the other in Johannesburg.
On the server in the UK, I have the BBC channels which are all now in MPD format. They do open in NextPVR, so it's most likely there's no encryption.
I then import the channels via the M3U playlist from the UK, to Johannesburg server, it's always worked till the BBC pulled the plug on the legacy HLS streams.
On the UK server with the MPD streams on NextPVR, I get severe buffering, and then with the playlist imported to JHB, the UK channels don't load at all, they just time out....
Just about the only thing I cannot do with my mouse in NextPVR Client for Windows is to scroll left or right to different times in the EPG listing. I can jump ahead 24 hours and back 24 hours, but I have to use the arrow keys on the keyboard to scroll in smaller increments. If there were arrows at the bottom to skip <-2Hrs and +2Hrs>, in addition to the existing |<-24Hrs and +24Hrs>|, that would solve the problem.
Hi,
this is my first post. I'll start by saying I love NextPVR: great piece of software guys!
Now to the issue in the subject line
SBS TV in Australia (at least in Sydney) shows (no lisitings) for all EPG entries on its multiplex (including radio).
The SBS entries on the 'Channels' page are blank.
I found the following on the SBS web site:
SBS EPG Enhancements In order to add Consumer advice to all SBS channels and Country of Origin for SBS World Movies in the Electronic Program Guide (EPG), on 2nd December 2019 SBS has made the following changes for Free-To-Air (FTA) Terrestrial and VAST satellite platforms (NOT for FOXTEL or FETCH TV):
TThe program synopsis has been moved from ‘Short Event Descriptor’ to ‘Extended Event Descriptor’ in the Event information Table (EIT) that’s used by the Digital TVs and receivers to display the EPG.
The ‘Short Event Descriptor’ now contains Consumer Advice and Country of Origin information for relevant programs.
Some old TV sets may not be compatible and therefore, won’t able to display the program synopsis which is now under ‘Extended Event Descriptor’.
This incompatibility can only be addressed by the manufacturer. SBS recommends viewers with affected receivers to contact the manufacturer, report the issue and ask if a firmware update will be available to fix it.
I have a sneaking suspicion that this change may be the reason for the EPG not updating in NextPVR.
Anyway, just letting the NextPVR team know (if the they don't already) and hopefully they can look at adding a fix further down the development schedule
I also note that I am running version 6.1.4.230625 under Windows 10.
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.
