Posts by emveepee

You say you have the backend setup so I assume the web setup is finished and configured too. The fact that you are seeing your Windows instance to me means that the problem is that your client pvr.nextpvr settings are set to the IP of the Windows server. Change that in the addon setting. For LE on the same box you can use 127.0.0.1

Note if the client you are using is the Windows client NextPVR.exe it will only connect to the local Windows backend.

Further questions should be on the NextPVR forum.

Any h/w issues would be in the kernel logs. If it is an issue with NextPVR server it would be in the NextPVR server logs.

Also is it all frequencies, just DVB-S frequencies (patch #2) or certain frequencies? It could even be the dtv-scanning-tables.

Martin

Did they tell you if kernel support needed to be added for that firmware? I saw this patch mentioned recently https://github.com/b-rad-NDi/Ubun…ment-3335838122 so I expect more is needed. I am not even sure if this https://launchpad.net/~b-rad/+archiv…g-archive-extra is in the LE kernel.

I see this as a continuation of this thread [x86-64] WinTV-Nova-S2 USB DVB-S2 Tuner since you are answering chewitt

Martin

What about skins which can call python. Does Estuary work?

Hauppauge has reasonable kernel support (not the latest Nova 2) but Kodi doesn't support USB PVR tuners you also need a backend. LE has services for TVHeadend, NextPVR and VDR backends. You wrote antenna not aerial so maybe you are in US and Canada that would be ATSC.

There are also DVB-T and ATSC network tuners from Silicondust that will work without a backend.

Martin

For the Eagles VC1 sample does it pixelate around 40 seconds in? On my N100 it does in LE and in Ubuntu/VAAPI

There is no CE support for this yet. It really isn't CE support though. It is the work of Team LE that gets much of the non custom work going, there would be CE without LE.

As for the Nova on any Linux it will depend on your version RE: [x86-64] WinTV-Nova-S2 USB DVB-S2 Tuner don't expect that in the HK kernel.

It isn't even ready for Kodi so have patience and it will likely make it to LE13.

Quote from chewitt

"You can please some of the people all of the time, and you can please all of the people some of the time, but you can't please all of the people all of the time” ..

I don't understand why allowing weak password fit that. User who want strong password would still have the choice. The decision makes no sense to me, just to placate a few users who complain. More weak password users just need to make their opinion felt.

Quote from nvdias

I use an Ubuntu VM machine with 2 processors and 4 GB RAM.

Maybe the x64 build is different?

I needed a lot of RAM to do build LE Monitoring with htop it was hitting over 24GB even with one CPU. so if you don't have enough memory make sure you have lots of swap. I ended up increasing my RAM to 64GB.

Martin

This is the LE forum, why would we test flathub? Your short sample plays on LE 13 nightly for me from the file system but with the SW decoder.

I am using an N100 with LE 12.0.2 (with NextPVR as my PVR service) and I tested HEVC 4k via PVR and don't see any issue playing for maybe 30 minutes (streamed via http).

I do see this logged when it starts streaming before playback but not afterwards, it takes time for my capture device

2025-03-31 10:11:23.014 T:1211    error <general>: ffmpeg[0x39aa1de0]: [hevc] Failed to end picture decode issue: 23 (internal decoding error).
2025-03-31 10:11:23.014 T:1211    error <general>: ffmpeg[0x39aa1de0]: [hevc] hardware accelerator failed to decode picture

Since the OP didn't bother to send LE logs, we are only assuming an x64 VAAPI problem, and it might not even be Intel or if it is which flavour is causing the problem. It also would be nice to know if software decoding works etc.

You don't have to be a developer to do minimum reporting before complaining about Kodi or LE who need thanks not this crap.

In the related post on the issue on this forum from maple, I thought this RE: Irrelevant Kodi Omega (on Ubuntu) post linked to the problem. Given that http streaming might work wouldn't the problem be TVHeadend or pvr.hts and not Kodi (ffmpeg building aside)

Did they tell you what they meant by released? There was a test patch released for their Ubuntu 6.8 mediatree released in January which they might be talking about.

Quote from ifoehn

This is everywhere the same root cause. The hardware isn't identified because of a new identifier.

It is a new identifier but it is also new internal h/w if you follow this parallel thread [x86-64] WinTV-Nova-S2 USB DVB-S2 Tuner I guess the good news is there is a potential for a kernel patch https://launchpad.net/~b-rad/+archiv…g-archive-extra eventually.

Quote from jcjefferies

The exact name on the device is "WinTV-Nova-S2" and is not listed on the LinuxTV Hauppauge Wiki. It was bought back in December so is "New".

Windows automatically downloaded the Hauppauge driver describing it also as a PCTV 461e. The NextPVR server recognises it as a "PCTV 292 e/461e BDA 28179 TV Tuner S"

I dont want to abandon my LibreElec server for a a Windows server just to be able to use this USB DVB-S2 tuner. I will contact Hauppauge Support to see what they say.

If you read the b-rad issues on GitHub (best place for Hauppauge Linux support) you will see that Hauppauge marke the Pinnacle 461 (as shown on your Windows BDA driver) branded as a Nova S2 type 3 which isn't supported in Linux.