Soo, I use zap2xml.pl as a stand alone on my Linux entertainment server running by cron and using tv_grab_file to import into tvheadend, NextPVR can just import the xmltv file.
Several months ago I updated the Kodi zap2epg addon to work with NextPVR which works well with Kodi or from the command line. If you want to try it post on the NextPVR forum. It is a little easier then the perl script.
After deleting addons and deleting package cache I am pretty sure there is a Kodi bug that requires you to restart Kodi.
It is failing in CE and Window too on Omega. The SeekTime error makes me suspect it is the issue on seek with ffmpeg 6 https://github.com/xbmc/xbmc/issues/23199 since the faulty UpdateCurrentPTS() is being called.
Adding a rule to play ogg files with the VideoPlayer also works it doesn't try to seek on startup.
Martin
Thanks for your help so far. It will be the same file anyway so figure on 2 or 3 weeks for LE12 and much longer for LE11. You don't have to wait for the addon update, since there is an option in settings to pull the latest update once 6.1.4 is available.
ghtester let me know if you want to try a pre-release update to one file that should address the server-side issue with the EPG character set and also an issue initiating a parameter for the dvb sub-system used in changing channels. I can provde a link with more details.
If not, this update will be included 6.1.4 which will be released hopefully this coming weekend but it takes longer to trickle down to LE so you would probably need a manual update.
Thanks again for the full mux files, they were of great help.
No problem. The reason I was asking was to determine if you saw the same thing sub and I did and that is one mux only scanning was working and the problem for you was changing mux as your earlier logs indicated. The two scans I did yesterday seemed pretty complete to Saturday and beyond https://imgur.com/a/yYmwtYm so sub can continue to look at that and not a data issue.
ghtester the reason I thought there might be an issue is the guide date you have on Nova (your 35) was what I as seeing on NOVA on 490. I have now found the logs that show a tuning issue during the EPG process for 490 and I will post them for sub.
If you delete the the channels from your tuner( clicking the trash can icon) and re-scan using a conf restricted to the 490 mux are you able to get EPG data?
You asked for ghtester to open an thread to discuss their issues if you want to continue to repeat the same points go back to the other thread and stop interrupting use and move on. He has noted that TVHeadend has issues too.
My unprocessed streams are fine on LE and CE too, I don't have 3% error rate,
My point here was about Windows relate to development priority. If there wasn't a Windows server and Windows drivers to consider, or NextPVR users that want features Kodi doesn't have or don't like, adding support for platform like Roku, LG OS that Kodi doesn't certainly support etc than adding things like adding service and provider information to a Kodi screen would probably be
I don't think any moderator is going to tell users to stop using Emby, Plex or NextPVR with or on LE. Without the closed source firmware distributed with LE there would be no LE, certainly no PVR. In the spirit of open mindedness let the users decide.
ghtester I was just checking why fullmux642 (with Nova) was not working here and I found that it has 2.89% transport errors. with zero in the others (using tsduck). This could explain why you aren't getting guide data for channels like Nova. Also as I noted NextPVR works with raw ts streams and sends them as-is to Kodi. TVHeadend I believe remuxes them and it is possible that this can help but that it not an insignificant error rate.
Sorry to interrupt and hate to burst your bubble but Kodi is THE primary client here. If you want adoption on LE you’ll need to take that onboard. You really should invite the author to join this discussion as I suggested before.
Pleases stop trolling me. I am quite onboard with the Kodi client I told you I am the primary maintainer of pvr.nextpvr and ksooo has been helping me out by adding some features that make the pvr.nextpvr integration better. The author is aware of this thread and he (like I am) are interested in helping all our users and all priorities. There are a lot of users running Kodi on Windows with Windows backends too.
The channel numbers in NextPVR can be whatever you want assuming you ignore Kodi's odd default to use Kodi numbering.
it looks you have two NOVA and nova. nova on 35 is the one on 498 showing as NOVA here. I am having trouble getting nova on 642 to scan, sub can scan it, his tuners are going to be better than mine.
Regarding your last comments features in NextPVR need to work in Windows and Linux. Tuning is faster in TVHeadend for digital tuner, I would expect 1 or 2 second tuning in NextPVR for digital tuners. The prime focus in NextPVR is on portability and typically recording not, on Live TV, has been the main user focus. Now with 100's of channels people tend not to zap between channels anyway.
However my experience is Kodi users do use Live TV a lot. I would expect pvr.hts to be integrated better since the maintainer is also the main developer for Kodi core..
Note too that the primary client for NextPVR is not Kodi.
I add your 490 fullmux and I don't have any problems with NOVA. https://imgur.com/a/nTEOQXd Do you know any channels that don't provide data that should?
I think sub got it to work, Kodi channel 6 is xmltv but OTA looks better now https://imgur.com/a/99TrRBZ Thanks for providing the full mux streams.
The data screen is not supported in either pvr.nextpvr or the API to the backend. never saw the point to implementing providers as it is mainly cosmetic. The signal strength info can be of value but only for digital tuners and is not multi-platform and is sometimes incorrect. I know when my signal is bad by watching but no doubt technical users who are used to it will miss it.
Watching TV and doing an EPG update is not supported and will cause issues. If you must do it issue a pkill DeviceHostLinux in PostUpdateEPG.sh
NextPVR logs would tell us why only on frequency is being scanned.
The EPG issue is known for sure, as I said sub is looking looking into it, and making progress
Thanks, my system is totally fake streaming from your fullmux in a loop as dvb-t but this test is on an lesser machine than an RPi4 (CE20 S905X4 with the Sony tuner on Astrometa) but I can't get tuning to fail https://imgur.com/a/IdE7s2d (you need to enable sound on imgur) Does tuning work on the same mux for you? If not I might need to try the same test on an RPi4, since your messages appear to be kernel related.
Note in the video I did import one channel using XMLTV to get proper text. Sub is looking into your problem and if you want to use XMLTV I can help you out there in the meantime.
Thanks ghtester you certainly went above and beyond. I will make sure that sub can access them too. Can you also provide /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf it might help with some utilities I have.
Regarding that test, did you have have any issues running the different zaps? If not then maybe the NextPVR initialization can be improved. I do see a warning output buffer overrun after 36.11 seconds which
7. Most wireless RF remotes are USB HID compatible and many have a keyboard if you need that too. No need for a FLIRC unless you want IR, since RF is better anyway and doesn't depend on line of sight.
My favourite with the keyboard is the AuviPal G9S backlite, programmable keys for the TV and rechargeable batteries. Another choice would be the G20BTS since it is IR, RF and Bluetooth but it eats batteries.
Martin
Sorry, I didn't know that libdvbv5 was included with LE, being in /usr/bin I think means it is in the baseline. In any case I am happy to see that you found 1.24.1 since you can try other tests. Plus it includes a PR I submitted that was causing scans to fail here in North America.
The syntax for the full mux capture is below You will need to find a host for the 200MB ts files that get created.
dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-frontend1-DVB-T-channels.conf Prima\ Max -P -t 60 -o fullmux.tsYou can use any channel name in the mux. It might be good to try CT 2 HD T2 as well. If it is easier any channel on those frequencies will do and you don't need to worry about the space. I don't think my demodulator supports DVB-T2 so I am not sure I can try the channel change issue but sub might be able to check that when he looks into the EPG issue.
You would need restart the NextPVR service if it has opened the tuner.
The other test you can do is backup /storage/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32/libdvbv5.so.0 and copy in the new version from 1.24.1 that you found. It won't help with the EPG but it might help the tuning issue.
The Kodi log does not have debug logging before the dvb_fe_set_parms failed stopped playback so I can't see the skip information.