Following the evolution of Teletext, the next standard that seems to have emerged and adopted by free to air TV is HbbTV.
Given that for a PVR server most likely the requirement to support this standard would be somehow simple as described in the below
TVheadend thread: https://tvheadend.org/issues/1711
"The HBB TV data is simply data PIDs linked to the channel in question. It's a table called AIT, and the data is a format called DSM-CC. I don't think TVHeadend would have to do anything other than not filter out the AIT data PIDs (it does currently, even in a raw stream of a channel without "/play" in the URL). Then the data would be available for processing by some kind of plug-in on the client side (Kodi via HTSP, etc.) I guess this is how teletext works currently? For an example, I've attached a full mux TS dump of 11494H from Astra 1 19.2°E. This carries German ARD channels, and they all have PIDs carrying the HBBTV data. For example, Das Erste HD has HBBTV data on PID 1170, and then some more on PID 2171 (not sure what this latter one is for). Looking at the data in PID 1170, it's carrying the URLs for the HBBTV service, for the HBBTV plugin on the receiver to receive the content from. PID2171 may be some of the data for offline viewing (I don't know). I found a plugin for Firefox called FireHbbTV - with this installed, if you visit one of the URLs shown in the PID 1170 stream - http://itv.ard.de/ardstart/ You see the data that gets fetched, as if it were on a TV or receiver that supports HBBTV. On the face of it, all I think TVHeadend needs to do is pass through any data PIDs marked as carrying HBBTV data!"
Is there something that NextPR can do and possibly go one step further and even expose somehow these PIDs also in the web client so that if somebody for instance uses an HbbTV emulator addon like for instance this one for Chrome (and Chromium Edge): https://chrome.google.com/webstore/detai...ated?hl=en can use it?
I miss the option to use an UNC path to the recordings location.
That's important to host the recordings on a different system and
is possible with the old Version 4.
logs-20200423-0755.zip (Size: 1.11 MB / Downloads: 2)
Hi, While server is running it constantly says {236} Unexpected error in HTTP input sourceystem.net.webeception:The remote server returned an error (403) forbidden. I am a newbie and im guessing it is password issue but i recently unsed epg buddy 0.5.0.8 and removed it and used schedules direct assigning each channel individually which has been working out good I have included my logs. Also getting one other error {9} writer.close() did not complete in a timely fashion.
Hi
I used nPVR 4 for a couple of years and most times it was a pleasure. I now have a fresh install of v5 on a new Windows10, but my DVB-S double tuner TBS6982 Dual DVBS/S2 BDA Tuners is not recognized at all. The list of devices is always empty. But the device is correctly listed in my windows hardware manager.
Any idea?
Thanks+regards dontspeak
I seem to have lost the ability to view live TV from NPVR via Kodi. I am not sure whether this is an NPVR problem or a Kodi / plugin problem so I thought I would start here before heading over to the Kodi/LE forums.
I am running LibreElec 9.2.1 (Kodi 18.6) on a RPI3b+ using the latest LE repo version of the NPVR plugin for that version, I have made no changes to this setup, other than auto-updated plugins, since the release of LE9.2.1. I can see LE/Kodi loading the TV channels/guide/recording etc at the top right of my TV when the plugin starts. I can view the NPVR provided TV guide information and can watch recordings without any problem. Switching to Live TV however gives the error:
'One or more items failed to play. Check the log for more information about this message'
I can see some information about the error in the Log Viewer plugin but I am not sure where Kodi keeps its logs otherwise. As far as I can see the error reported in the log file is:
ERROR:<general>:XFILE:CFileCache::Open failed open source <http://192.168.86.225:8866/live?channeloid:8060&client=XBMC<long sting of numbers /letters to many to copy)
ERROR:<general>:CCurlFile::Open failed with code 404 for http://192.168.86.225:8866/live?channelo...=XBMC<long sting of numbers /letters to many to copy)
If you know where to find the Kodi logs, and can tell me, I will provide them for you. I have also tried using the latest Daily 'Matrix' Kodi version on my Windows 10 PC and get the same problem and errors.
I am running NPVR 5.0.3.200415 on an RPI 4 (4GB) for recordings only (no viewing) which in turn is getting its TV information from a HDHomeRun Quattro. I have been running this setup since early Junuary with no problems. The IP number reported in the LE/Kodi error above is the IP number of my NPVR RPI.
I can view live TV directly from the Quattro using the HDHomeRun app on my Windows 10 PC, so there seems to be no problems there. All the above components are on the same wired network. I have attached the latest NPVR logs for you to see, I was trying various live channels between 09:30 and 10:00 BST on Thursday Apr 23. Please let me know if you need any further information from me.
I was looking at getting this working on my machine and the wiki is sparse when it comes to Linux examples, and searching the forums left me with breadcrumbs that got me to success, but I thought I'd chronicle my experience here for anyone else who'd love this wonderful addon to npvr.
I'm running on bare metal Ubuntu 18.04.
Building Comskip is really quick and easy on Ubuntu, so probably the same for any Debian based distro:
Note: I might be missing some dependencies. Sorry. I compiled several days before writing this post, and my system has been doing media stuff for years, it's very likely I already had necessary dependencies installed.
Next you need a comskip.ini . It doesn't really matter where you put this file as you specifically call out its location when you use it later. It just needs to be accessible by the user running the nextpvr service. Mine is /etc/comskip.ini:
Note: the "verbose=10" line will result in a lot going to your log file, if you use a log file. If you redirect to /dev/null, the verbosity setting doesn't matter.
Next you need ParallelProcessing.sh. This file needs to live in /var/opt/nextpvr/scripts. A very basic one is this:
Remember that this script is called by the user who is running the nextpvr service, and you probably don't know for sure what the PATH variable is. Make it easy on yourself and provide the full paths to the executables. You can find them by running "which nice" and "which comskip".
This file needs to be executable by the nextpvr user. Being executable by all is fine afaic:
And there you go. Restarting the nextpvr service is not necessary to bring these changes into service.
A note on usage: sub/mvallevand can correct me if I'm wrong here, but I believe ParallelProcessing.sh is only called when you specifically record a show. That means that if you tune in to a live TV channel it does not start processing the stream for commercials until you hit the 'record' button.
Posted by: VCR58 - 2020-04-23, 03:28 AM - Forum: Linux
- Replies (2)
I noticed some odd behavior when rewinding the recorded TV show with the web browser (Google Chrome) on my MX-Linux PC. Advancing in time was ok but going backwards in time caused the red Streaming Failed (transcoder exited) error to show but it still seemed to recover and go backwards in time. After a couple more backups the video started going bonkers then eventually gave up and closed the stream.
i just set up nextPVR on a Windows 10 machine for IPTV only, using Kodi as a front end with client version 3.3.19.1 back end 5.0.3.200415 (i am running CoreELEC on cheap android AMLogic s905x box's for Kodi front end)
i am loving how nextPVR loads tv show and movie artwork, and set up was a breeze, but I am having some issue related to the windows install itself.
prior to using next PVR i was using Kodi simple IPTV client and it worked great, but no pause functionality, so i tried out TVHeadend, installing both back-end server and kodi client on my s905x box running CoreELEC. This worked very well on the low powered box, but i didn't like the way TVHeadend sorted channels (not matching m3u) and also the fact that TVHeadend needs a channel to be 'up' when scanning for it to be created, so all my live event channels don't get created when TVHeadend scans, hence trying nextPVR.
I am having choppy playback with nextPVR on any 1080p channel. On investigation it appears to be related to ffmpeg.exe on my win 10 pc (it is a fairly old PC with 6 core 2.5ghz CPU) ffmepeg is using around 600mb memory at any given time when a stream is running and keeps spiking my CPU, and this coincides with playback being choppy (does not happen with SD channels) and is impossible for me to have two concurrent TV streams to different nextpvr clients on my network. for normal streaming of 1080p mkv files i have on my pc, i am able to stream three different films concurrently to different TV's in my house (maybe even more, just have not tried!) without issue, albeit with no trans coding going on...
although my PC is old, it is much more powerful than the s905x box i had both back-end and front end TVHeadend installed on that worked OK, so i am surprised at the CPU/Memory hit on my PC
is there anything i can do to optimize ffmpeg on my PC?
I was browsing the Schedules Direct forum and ran across a post from the developer of an application called Typecast at 12noon dot com.
It looks like a very flexible search engine against your SD downloads.
I haven't done anything more than glance at it but I thought I'd pass my find along in case others might be interested.
ystem.net.webeception:The remote server returned an error (403) forbidden. I am a newbie and im guessing it is password issue but i recently unsed epg buddy 0.5.0.8 and removed it and used schedules direct assigning each channel individually which has been working out good I have included my logs. Also getting one other error {9} writer.close() did not complete in a timely fashion.
