Thought I would try getting Debian 12 loaded on my intel celeron NUC and see how well NextPVR worked. Got everything working and VAAPI for transcoding.
From a Chrome browser I started a live TV stream and it played fine. Then after playing a couple different channels I got the red stream error message and the stream failed to start. Restarting the stream didn't work. Tried ctl F5 a few times then it would play the live TV stream again.
I captured logs of this happening. My other Linux server using Deb 11 doesn't have the same issue.
I thought that this discussion about the potential of OTA encryption being added to the new standards would be of interest here.
It seems like it would break all existing hardware tuners once rolled out.
Updated to Version: 6.1.4.230625 from the previous version, now can't watch any live channels on either the desktop or web app, get the above errors. Recording and play back work fine, all was OK before the update. Any idea's ? any help would be appreciated, sogs attached
I subscribe to DISH Network in a DMA that doesn't have a PBS OTA station. DISH provides our DMA with the PBS National feed in standard definition. The nearest PBS OTA transmitter is on the fringe and is unreliable. I do support PBS with an annual subscription and I have access to PBS Passport, which gives me access to the PBS library. I prefer to record PBS shows in full HD with captioning. I've done that successfully for quite some time via NPVR and the PBS National IPTV URL. I record to a .ts file on the Windows desktop, extract closed captioning with CC Extractor, copy the .ts file to .mp4 with ffmpeg, and stream the recorded program to an Android TV box. All has worked well until a few months ago when PBS apparently changed their format from closed captions to an as yet undetermined (by me) sub-title format. The URL will no longer display captions/sub-titles in NPVR, whether watching or recording. The same URL will display sub-titles in VLC but will not record the sub-titles in VLC. I've reached the limits of my technical abilities and I'm wondering if anyone has a work-around to get sub-titles working again in NPVR with this PBS IPTV URL. Perhaps something in NPVR configuration that needs to be tweaked? I'm attempting to attach the URL in txt and m3u files for reference.
When I try to enter a punctuation character in the Name field for a Manual Recording, other characters are displayed. I don't think logs are needed since it doesn't get to the server. I was trying to use a single quote, but most other punctuation characters are incorrect, as well. If I wanted to use double quotes in the name, I could use the Page Down key since it produces a double quote. I tried other keys, but none of them produce a single quote.
I ran an update a few days ago, and am seeing something weird - the bitrate for my DVB-C recordings are "off" - I am typically getting 3-4 Mbit (measured with ffmpeg) on SD and around 15 Mbit on HD (ARD, ZDF, etc). I've noticed in the last two days that recordings are coming thru with typically "low" bitrates for the various channels - so around 3-4 Mbit lower than usual.
This can, of course, but Vodafone Germany playing with my head - and there are of course different episodes/shows shot and processed with different rates - but just wanted to ask if you had made any changes to the code responsible for pulling data off of the DVB-C transport stream and dropping it to disk? I know it's far-fetched, as the TS capture on NextPVR has been bomb-proof for years, but unless Vodafone is dropping bitrates across the board, updating NPVR is the only change I've made.
Is there any easy way to go back to a previous version of NextPVR to check?
I used to have an E: drive where I recorded TV and updated the xmltv.xml file. So, the recording drive was at E:\ and the update EPG went to [e:\EPG\xmltv.xml]. I subsequently lost that drive, so I changed the recording drive to C:\users\...\videos, and located the epg updater to C: drive. However, see picture, I can't get npvr to update the epg at the right location. If I put it on a thumb drive (that happens to become E) it works fine. But at the C path, it doesn't work. I delete the E location and remove the thumb drive and restart the service, and the E location channel lineup just keeps coming back like a bad penny. If I delete E and run with only the C lineup, it can't update. It seems to be forcing me to have the lineup on E for some reason, I can't figure out. what am I doing wrong?
Hello, been fighting recently with NextPVR live TV and Recordings with Hauppauge Colossus 2 card.
Thanks to Martin and Sub, have resolved one issue I was having with severe flicker and strobing.
However, I still have this really annoying issue, where randomly the playing video or Live TV stream in Kodi will zoom up, to the extent it looks like viewing image thru a microscope.
Very hard to replicate, but it does it at random, but only from the STB channels. (MySkyHDi)
It seems to do it whether I am using 720p or 1080i output from the STB.
It is the most bizarre thing I have ever seen Kodi do.
I am guessing it is somehow losing the aspect of both live TV and the recording, as if something in the video is triggering it.
I think it is some kind of video corruption occuring in the stream, as I notice that Kodi has issues resuming the recordings, and sometimes can not even start playing them.
Then, if I try again, it does play them once more.
Any ideas?. I know this is a really vague issue, but for me it only started doing this behavior when I replaced my original Hauppauge Colossus card with Colossus 2.
I was watching a recorded show NextPVR recorded rom Sky STB. 3 or 4 times the weird zoom issue happened.
I played back the same recording using Martin's NextUI client (UIDroid), and it does not appear to exhibit the strange zooming issue that occurs when viewing in Kodi.
If I say selected 'Recordings Auto Transcode' in NextPVR server preferences, could this help correct any video stream errors.?
I am running NextPVR server on the following laptop:
Processor Intel® Core™ i7-10750H CPU @ 2.60GHz 2.59 GHz
Installed RAM 16.0 GB (15.8 GB usable)
Device ID 298EFCB8-C150-48C8-8DDE-35722FC55241
Product ID 00329-00000-00003-AA781
System type 64-bit operating system, x64-based processor
Windows 10 Enterprise 22H2
wired network
npvr version: 6.1.4.230625
I played back my 2-hour recording on an Android TV Kodi NextPvr client but encountered the following issue:
Fast forward and skip worked until at around 57 mins mark, beyond that point, any fast forward or skip would return back to this 57 mins mark after playback was resumed. For example, when I forwarded to 1 hour mark, after play resumed, it resumed from 57 mins mark instead.
I tired web browser on the laptop as well. It quickly got confused and the time scale got messed up.
I also tried to play the recording .ts file directly on VLC on the laptop. Here are the strange things:
1. The start time was displayed as 00:00, but the end time was displayed as -7:22:47.
2. Using the mouse to click on the time line, all worked until 57 mins mark. After that 57 mins mark, the playback still worked (i.e., it didn't go back to 57 mins mark), but the current play time instant was always displayed as 00:00.
Seems like the recording has some timing related issue? Hope someone can help.
