I thought it might similar to this issue https://github.com/xbmc/inputstream.ffmpegdirect/pull/320 with confusion between which version of CURL::Encode() and CURL::Decode() are being called.
Martin
I thought it might similar to this issue https://github.com/xbmc/inputstream.ffmpegdirect/pull/320 with confusion between which version of CURL::Encode() and CURL::Decode() are being called.
Martin
I would think it should calls Parse with the constructor and Parse shouldn't even be called ie.
CURL url(m_streamUrl);
Edit: that patch does get pvr.nextpvr's call working.
For pvr.nextpvr on x86_64 here is the crash file https://paste.libreelec.tv/natural-dragon.log I can't tell if it it the Kodi CURL:: Reset() or the one in inputstream.ffmpegdirect()
Martin
As a test I did a test with pvr.nextpvr which has an input stream.ffmpeg option and it fails too at the same point. https://paste.libreelec.tv/heelthy-beetle.log. For the log replace hee with hea apparantely because of of banned forum word
It also crashes on CE nightlies at exactly this same spot.
However it is working in Windows with 22.1.3
2025-10-05 12:54:39.089 T:6361 info <inputstream.ffmpegdirect>: OpenWithFFmpeg - IO handled by FFmpeg's AVFormat
The kernel logs didn't identify that it found anything on this device
I would expect to see kernel: usb 1-2: New USB device found, idVendor=2013, idProduct=-4062, bcdDevice=##
Do you see anything with find /dev/dvb
If yes the do the journalctl | paste again.
Note the NextPVR server does the /dev/dvb scan on startup and if it is slow to be detected you would need to rescan to find the device. There are also scripts on the NextPVR forum showing how to have the server startup delayed.
Since the device is new to the kernel I don't know how Hauppauge can say LE should have the drivers.
Martin
Do you see the device if you run lsusb
Martin
I think his point might be that the /dev/dvb device isn't being created so the server doesn't recognize it.
Martin
You don't need to install the client pvr.nextpvr on LE if you don't want to. If for example you are using the NextPVR web client to connect to the server you would need to use the LE IP and not the IP of your server or localhost.
This is not an LE issue (or Linux for that matter) so you should post on the NextPVR forum.
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
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.
"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.
I use an Ubuntu VM machine with 2 processors and 4 GB RAM.
Maybe the x64 build is different?