NextPVR had been working well but I have upgraded a few things and I no longer have the ability to change the channel without rebooting the server. It seems strange because I can still connect via my phone to the local server on port 8866 and watch live TV from it.
A brief description of my setup
I am running NextPVR version 5.2.4.220103 on Ubuntu server version 20.04.3 LTS and and accessing it from LibreELEC 10.0.1 running on a Raspberry PI4.
On the Ubuntu server I have a Hauppauge WinTV-quadHD card which takes in the local TV signal.
I seem to have errors when checking if the service is running. I have also attached log files. I hope someone can help
Jan 10 17:55:51 mediaserver systemd[1]: Started NextPVRServer.
Jan 10 17:57:29 mediaserver server.sh[1471]: /var/opt/nextpvr/adapter3-DVB-T-channels.conf: No such file or directory
Jan 10 17:57:29 mediaserver server.sh[1473]: /var/opt/nextpvr/adapter2-DVB-T-channels.conf: No such file or directory
Jan 10 17:57:29 mediaserver server.sh[1475]: /var/opt/nextpvr/adapter1-DVB-T-channels.conf: No such file or directory
Jan 10 17:58:13 mediaserver server.sh[1471]: /var/opt/nextpvr/adapter3-DVB-T-channels.conf: No such file or directory
Jan 10 17:58:13 mediaserver server.sh[1473]: /var/opt/nextpvr/adapter2-DVB-T-channels.conf: No such file or directory
Jan 10 17:58:13 mediaserver server.sh[1475]: /var/opt/nextpvr/adapter1-DVB-T-channels.conf: No such file or directory
Jan 10 18:02:07 mediaserver server.sh[1471]: /var/opt/nextpvr/adapter3-DVB-T-channels.conf: No such file or directory
Jan 10 18:02:07 mediaserver server.sh[1473]: /var/opt/nextpvr/adapter2-DVB-T-channels.conf: No such file or directory
Jan 10 18:02:07 mediaserver server.sh[1475]: /var/opt/nextpvr/adapter1-DVB-T-channels.conf: No such file or directory
Using nextpvr.exe 5.2.4 (220103), in fullscreen, if I hit F1 for the EPG, it uses a massive font and hardly appears on screen This is a full screen screenshot.
I presume for the channel info, if it is using the same font/image sizing, it may actually be appearing but way off the bottom of the screen.
Posted by: a1blues - 2022-01-10, 11:39 AM - Forum: Wishlist
- No Replies
Would be great if nextpvr add a feature similar to media center where you could browse movies under different genres or all movies in order of date and view them with big thumbnails or posters.
I remember this being really useful to view upcoming movies and to pick ones worth watching.
If this could be implemented into the desktop app or even the web app, this would be fantastic.
If it isn't already known, I have been given clearance by the GitHub project developer to share the availabllity of his own personally modified version of Kodi for Windows. It contains built-in native support for OTA broadcast ATSC 3.0 channels now rolling out across the country, and its new AC-4 audio along with HEVC video.
I have bought a Silicon Dust HDHomeRun Flex-4K network tuner box to specifically get me going in the new "NextGen" ATSC 3.0 world. This new standard will support video of not only 720p and 1080i supported by MPEG-2, but also 1080p and potentially 2160p supported by HEVC. And audio is improved as well over the AC-3 5.1 supported by ATSC 1.0, with AC-4 audio potentially also supporting 7.1 and even 7.1.4 Dolby Atmos.
While HEVC is freely available from the MS Store for Win10/11, the LAV Filters work for HEVC in Win7.
However support for AC-4 is essentially totally absent in widely available software today. Dolby has licensed the AC-4 codec to TV manufacturers for use in their built-in tuners supporting both ATSC 1.0 and ATSC 3.0, typically for TV models 2021 and newer. Certainly Sony, LG, etc., have taken this path. So if you buy a new TV you can automatically get support of OTA ATSC 3.0 channels (assuming you use a roof antenna or rabbit ears, of course, to receive them).
As of right now no AVRs have yet been produced by any manufacturer that support decoding AC-4, so bitstreaming (pass-through) the AC-4 audio to an external sound system is not an option. Also no currently available streaming devices provide support for decoding AC-4, so their pass-through audio option is similarly worthless for client apps like NextPVR running on them.
Even for apps written to run on new TV's (like the official HDHR client app for LG OLED) can only go as far as making use of the built-in AC-4 support (e.g. LG has had built-in support for AC-4 on all OLED TV models since 2017), which is designed to produce decoding support needed only for the two speakers in the TV. So its output (say via ARC/eARC bitstreamed to an external audio system via HDMI) is only 2-channel L/R 2.0 even if the original audio was AC-4 5.1.
In other words... at the moment we are still at the bleeding edge of ATSC 3.0. Appropriate hardware to actually make use of the new AC-4 audio is unavailable. Plus, there are really very few ATSC 3.0 channels available yet in the 36 cities where initial rollout has started. So far, only FOX has really been the major leader in the early charge to upgrade their local affiliates with ATSC 3.0 channels along with the existing ATSC 1.0 versions of the same channel. All the other channels will follow over the next year or two or three, but for now it's essentially only FOX which has taken the lead on ATSC 3.0.
So whereas FOX stations nationwide have all used 720p as their video protocol for ATSC 1.0, the new ATSC 3.0 versions of FOX channels are broadcasting in native 1080p. Looks beautiful upscaled to 2160p for display on a 4K LG OLED TV! Also, other early rollout channels that were interlaced 1080i on ATSC 1.0 are now also delivering native 1080p for the same program on ATSC 3.0.
We're probably years away from this really being the widespread norm, and people replacing their old equipment only capable of handling AC-3 and ATSC 1.0 broadcast TV with new equipment properly supporting ATSC 3.0 for both HEVC video and AC-4 audio.
Which brings me to the point of this post: there is available today a GitHub project which is "Kodi AC-4" for Windows 7, 10 and 11. And it delivers decoded AC-4 audio... natively, using a beta version of FFMPEG that adds support for AC-4.
So because it is actually Kodi it utilizes the NextPVR backend for its live TV and recording services, which in turn supports my Flex-4K tuners. And it uses the beta FFMPEG to support AC-4 natively, so ATSC 3.0 channels containing AC-4 audio are perfectly supported and deliver 5.1. You will get 5.1 audio out, either on your PC or pass-through bitrstreamed to an external audio system. And if you connect your Windows Kodi-enabled desktop PC graphics card or laptop HDMI output to an external audio system, you can get true 5.1 audio while enjoying the native 1080p video upscaled to 2160p, on your home entertainment system. NATIVE AC-4 SUPPORT IN KODI!
Here is the GitHub project page, with all the details. It also shows my recent conversation with the author. So everything I've learned about and questioned over the past few days is documented there in the comments below. All his answers are in the comments below. You will know everything I know, because it's all written down there.
I have now installed Kodi AC-4 on both my Win7 and Win10 systems. Note that it uses PVR.NEXPVR as its add-on, which is the one from Graeme Blackley. Turns out we had some problems getting the add-on installed initially, because the Kodi distribution had been changed since November when this project was posted on GitHub. The solution/workaround is to download the add-on manually in ZIP form, and then place the un-zipped folder in Kodi's \addons folder. Then the add-on can be configured and enabled as normal (being sure to un-check the "automatically apply updates" option).
And it works perfectly, albeit it only for Windows. But if you're looking for the perfect solution to how to properly support the new Flex-4K product from SD, and the new ATSC 3.0 channels with built-in native support for the imbedded AC-4 audio, THIS IS THE CLIENT FOR YOU as your Windows client!
Unless I haven't found how to do it, the default recordings filename does not contain date/time (which is REALLY IMPORTANT).
Nor does it include either station call letters (i.e. network ID) and/or channel number, either or both of which would again be supremely useful.
Are these options that I've missed setting? I would think at least date/time in the file name should absolutely be ON by default (assuming it is a setting). I can make the same case for network ID and/or channel number. Maybe channel number is less valuable, but at least network ID call letters please.
Let the user turn both values off if wanted, but by program install default I feel absolutely date/time should be ON as well as station ID, again assuming you even want to make them optional settings and not just always have them in the file names.
Strange symptom. When I choose a channel to watch, there is a brief bit of activity where it looks like something is starting to be presented on the screen, starting from the bottom of the screen and moving up.
And then just about right away, it stops. And there is no live TV picture appearing.
In contrast, if I play a recording, it seems to get started properly. The recordings are shown, and I can select them to begin playback. But when I actually do push ENTER on the recording to start playing, it immediately starts and stops, identically to what happens trying toplay live TV as well.
I had thought it was a problem on with Live TV which would need a tuner (from Flex-4K) needed to be accessed in order to satisfy the live TV request, but that something prevented that tuner from being allocated and assigned for use by the NextPVR app running on the ATV4K. Potentially it could be a BitDefender Firewall problem, and that perhaps some exception rule is needed for some special port number? Just speculating.
However the fact that it fails the same way when actually starting playback of a recording, which doesn't need a tuner, shoots down that theory. So it's got to be something else.
Note that there is no problem getting both Live TV and Recordings when running NextPVR client on the NVidia Shield Tube, as well as NextPVR client on Win10, as well as Kodi on Win10. So this would suggest it's something specific to the ATV4K client app and not related to BitDefender Firewall. Also this is the Win10 NextPVR Server that is booted at the moment, not Win7. I probably should try booting to Win7 to see if the problem persists, or if it is more compatible with the ATV4K client such that things now work. I will try that in a bit.
Anyway, neither starting live TV nor starting playback of a recording works, using Win10 server, and ATV4K client. Zip of Logs folder attached. Note that I first STOP'ed and then START'ed NextPVR Service so as to ensure a clean log starting point for the tests. Then I tried several Live TV channel attempts (both ATSC 1.0 to keep things simple) followed by several recording playback attempts.
I have just built a new PC and installed NPVR ,(it is many years since I have had a problem with the software on my old machine )
When I execute the client I get a red cross and the following error :- I may have seen this in the distant past but can not remember the solution may be graphics or dot net
I am currently using the graphics built into my new AMD Radion 5600G CPU and Gigabyte Aous Elite motherboard
Any assistance would be appreciated.
Maurice
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at SkiaSharp.Views.Desktop.SKGLControl.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
I am trying out ATSC 3.0 with the HDHR 4K and I thought I would get AC4 audio support via passthrough on my NVidia Shield to my Denon AVR. But I get no sound - it doesn't even recognize an audio track in Kodi. Is there a setting somewhere that I am missing or is this not supposed to work yet? I do get audio with the HDHR app.
VB-T -device:adapter3/frontend0 -instance:1 -parent:1013 -primed
![[Image: bad_epg.png]](https://www.howitts.co.uk/bad_epg.png)
This is a full screen screenshot.
