Posts by ghtester

Thank you for info & offer, in the meantime I have switched back to Tvheadend which works a bit better for my usecase, so I'll wait and give it a try again when the NextPVR updated version is available in LE add-ons.

It's the same like in earlier RPi4 LE versions - you need to install Tvheadend add-ons (Services-Tvheadend Server 4.2 or 4.3(Alpha) and PVR_clients-Tvheadend HTSP Client)

Is there any positive change in LE 12 Nightly?

Well, I don't want deleting the channels and limit to 490 mux only. Hopefully you should be able to find the issue anyway.

Instead, I tried to clear the EPG data in both NPVR and Kodi, restarted both and expected EPG should be clear. But some channels still kept the EPG data in Kodi. Tried to Update EPG in NPVR, only 2 muxes were scanned (514 and 490), NOVA channel (and most others) still empty.

Quote from emveepee

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 is not the correct mux. I have been mentioned NOVA channel (the name with all capitals) which is on fullmux490.

Yes the error rate is a serious issue (for Kodi live play which is unstable then) but this is not the case as this mux has 0% error. So far I was not able to get the EPG from NPVR for channels you can see on recent screenshots.

Quote from petediscrete

I cannot speak for other users setup but my TVH streams are passed raw and unprocessed directly to LE client without any issues.

The same here.

Quote from petediscrete

In the spirit of the LE project open source solutions will always be preferred over closed source commercial solutions every time. If you’re in any doubt about that just contact the devs/mods for clarification.

Personally I don't care much about closed sources [as it is sometimes the case (at least partially) even in Linux world] if it's working as expected, does not contain any bloats and even available free.

OK, thanks for the info, emveepee. I understand the devs priorities. It's good when there're concurrent add-ons and everybody has a choice to select the proper one for his specific use case.

Quote from emveepee

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.

FYI in Tvheadend this works fine; if such items are in Kodi, it would be fine to be supported by add-ons as well - it's useful at least for debugging because from Kodi you can't see this info elseewhere (AFAIK) and sometimes you need it.

Quote from emveepee

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.

Well, this looks to be a common Kodi's issue. I have reported that in LE forum a couple years ago but nobody from devs cared about it. So I had to make a custom scripts for my tuners that show that info correctly in right top corner when I activate it by button like you see on screnshot in post #14.

Quote from emveepee

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

I understand but it "repaired" the tuning (I suppose temporarily and after reboot or NPVR service restart it won't work again).

Thanks for the additional info regarding to PostUpdateEPG.sh.

I don't know how this works in Tvheadend but it's much better for sure (except the occassional EPG database corruption/screwing).

Perhaps you should consider looking for (conditional, configurable) EPG update after switching channels (switching channels in NPVR is very slow anyway, if it ever works, compared with Tvheadend).

Quote

NextPVR logs would tell us why only on frequency is being scanned.

The log posted earlier, hopefully it should be there.

Quote from emveepee

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?

Please look at the screenshots where you can see the channels with empty EPG (not all of them are provided but at least several of them should)

BTW. I have different channel numbers, AFAIK first 11 I have changed manually (edited channel nuumbers to have the prefferred channels at first 11 positions in Kodi) through NPVR web GUI (but I think it should not be important regarding to empty EPG)

Quote from emveepee

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.

Thanks for the update, this is correct now.

No, even the channel change to another on the same mux fails. So it's probably some configuration different from defaults (on NextPVR service/client) which make troubles. I need to restart the service.nextpvr to be able to open any channel again.

BTW. there must be more things wrong as I don't see any info about the Service / Provider in Kodi (when the LiveTV channel is playing properly).

The EPG texts on your video are also improper (the same bad diacritics like I see here). It's somehow readable though so it's not the major issue.

Edit - Huh, the tuning now works. What I did? Tried to force updating EPG as the NOVA channel did not still have any EPG info. So I tuned to NOVA channel in Kodi, in NextPVR web GUI invoked EPG update which interrupted playing the NOVA channel but now I am able to tune... EPG Update is still running and scanning all frequencies (don't know why it now scans all frequencies and sometimes only 1 frequency). It's interesting no EPG update happened as some channels (including NOVA) have it empty still.

The config file is here: http://sharegadget.com/754891094

No issues with zaps.

I have encountered the NextPVR client has been updated to version 21.0.1.1 after the LE12 upgrade to nightly-20230610-c7acfc7 but without any positive change (regarding to tuning & timeshift issues). I wonder what configuration change broke the tuning as at first it was working.

Check the fresh logs with debug enabled, the tuning issue should be visible there for sure:

http://mysharegadget.com/345723612

http://ix.io/4y5H

Jun 12 21:47:48 LE kernel: rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

Jun 12 21:47:48 LE kernel: rpivid feb10000.codec: rpivid_h265_stop

Jun 12 21:48:29 LE service.nextpvr[27348]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:48:29 LE service.nextpvr[27348]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:49:44 LE service.nextpvr[27348]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:49:44 LE service.nextpvr[27348]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:49:47 LE service.nextpvr[27348]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:49:47 LE service.nextpvr[27348]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:50:03 LE systemd[1]: Stopping service.nextpvr.service...

Jun 12 21:50:03 LE systemd[1]: service.nextpvr.service: Deactivated successfully.

Jun 12 21:50:03 LE systemd[1]: Stopped service.nextpvr.service.

Jun 12 21:50:03 LE systemd[1]: service.nextpvr.service: Consumed 1min 3.824s CPU time.

Jun 12 21:50:03 LE systemd[1]: Started service.nextpvr.service.

Jun 12 21:50:06 LE kernel: si2168 22-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'

Jun 12 21:50:08 LE kernel: si2168 22-0064: firmware version: D 6.0.13

Jun 12 21:50:11 LE connmand[697]: ntp: adjust (slew): -0.005944 sec

Jun 12 21:50:22 LE kernel: si2168 22-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'

Jun 12 21:50:23 LE kernel: si2168 22-0064: firmware version: D 6.0.13

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: rpivid_h265_start: (1920x1088)

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: SPS changed

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: PPS changed

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

Jun 12 21:56:24 LE service.nextpvr[52168]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:56:24 LE service.nextpvr[52168]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:56:24 LE kernel: rpivid feb10000.codec: rpivid_h265_stop

Jun 12 21:57:19 LE service.nextpvr[52168]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:57:19 LE service.nextpvr[52168]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:57:24 LE service.nextpvr[52168]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:57:24 LE service.nextpvr[52168]: ERROR FE_SET_PROPERTY: Bad file descriptor

Find the full muxes here: https://www.uschovna.cz/en/zasilka/LH9B8LBFU47RFTU4-UF3/

The commands used for grabbing are below, note the buffer overrun on some muxes.

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf Nova -P -t 60 -o fullmux642.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8001

service has pid type 06: 278

service has pid type 05: 281

tuning to 642000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -59.00dBm C/N= 27.00dB UCB= 13463 postBER= 0

Lock (0x1f) Signal= -59.00dBm C/N= 27.00dB UCB= 13463 postBER= 0

Record to file 'fullmux642.ts' started

received 245682160 bytes (3998 Kbytes/sec)

Lock (0x1f) Signal= -59.00dBm C/N= 27.00dB UCB= 26449 postBER= 990x10^-9

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf NOVA -P -t 60 -o fullmux490.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8000

service has pid type 06: 3318

service has pid type 05: 3317

tuning to 490000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -42.00dBm C/N= 31.00dB UCB= 26449 postBER= 0

Lock (0x1f) Signal= -42.00dBm C/N= 31.00dB UCB= 26449 postBER= 0

Record to file 'fullmux490.ts' started

buffer overrun after 36.18 seconds

received 246022252 bytes (4004 Kbytes/sec)

Lock (0x1f) Signal= -42.00dBm C/N= 31.50dB UCB= 26449 postBER= 0

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf CT\ 2\ HD\ T2 -P -t 60 -o fullmux514.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 06: 2250 2130

service has pid type 05: 2260

tuning to 514000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -46.00dBm C/N= 36.25dB UCB= 26449 postBER= 0

Lock (0x1f) Signal= -46.00dBm C/N= 36.25dB UCB= 26449 postBER= 0

Record to file 'fullmux514.ts' started

received 249851812 bytes (4066 Kbytes/sec)

Lock (0x1f) Signal= -47.00dBm C/N= 38.25dB UCB= 26449 postBER= 0

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf Ocko -P -t 60 -o fullmux626.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8000

service has pid type 05: 4211

tuning to 626000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -43.00dBm C/N= 34.25dB UCB= 26449 postBER= 0

Lock (0x1f) Signal= -43.00dBm C/N= 34.25dB UCB= 26449 postBER= 0

Record to file 'fullmux626.ts' started

buffer overrun after 35.87 seconds

received 246622160 bytes (4014 Kbytes/sec)

Lock (0x1f) Signal= -43.00dBm C/N= 36.25dB UCB= 26449 postBER= 0

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf Ocko\ Black -P -t 60 -o fullmux682.

ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8000

service has pid type 05: 1283

tuning to 682000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -60.00dBm C/N= 24.75dB UCB= 26449 postBER= 160x10^-6

Lock (0x1f) Signal= -60.00dBm C/N= 24.75dB UCB= 26449 postBER= 160x10^-6

Record to file 'fullmux682.ts' started

buffer overrun after 36.11 seconds

received 200292380 bytes (3259 Kbytes/sec)

Lock (0x1f) Signal= -60.00dBm C/N= 25.25dB UCB= 26449 postBER= 340x10^-6

Quote

I can't confirm on LE12 but on LE11, I just download the Debian package for libdvbv5 https://packages.debian.org/bullseye/libdvbv5-0 armhf version and extract dvbv5-zap to ~/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32 from there confirm

LD_LIBRARY_PATH=./ ./dvbv5-zap --version

I did not find the requested utility in the linked package, found it here:http://ftp.us.debian.org/debian/pool/ma…-5+b2_armhf.deb

Unpacked and copied to destination folder.

LE:~/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32 # LD_LIBRARY_PATH=./ dvbv5-zap --version

dvbv5-zap version 1.24.1

edit - btw. this utility was already part of LE (dvb-tools add-on?)

/usr/bin/dvbv5-zap

Here you are, debug level turned on recently but the latest tuning issue should be there.

http://ix.io/4xJ4

http://mysharegadget.com/230987988

At about 4:07 I have encountered a popup from Kodi GUI saying tuner is no longer available & timeshift stopped

http://mysharegadget.com/280447611

The reason was EPG update scheduled at 04:05:00

The "second image menu" I usually don't use for timeshift navigation. It was just last chance I have found, 'pushing' the highlighted button (didn't know it's chapter prev) to get back to timeshift starting position (very left) like it's visible on third image.

Usually (when it works like should) I am just using Left (arrow) and Right (arrow) on my remote control which opens the timeshift bar on display top like it's visible on first image. And moving inside the timeshift window back and forward with these two keys.

Yes only HEVC (h265) currently, don't use old DVB-T channels in mentioned issue examples.

Quote

I noted there is a PR submitted to have the DVB-T channels removed for the TVH repo.

Not the ideal choice as I have mentioned - there are still some local minor DVB-T providers which won't be found automatically then.

Quote

You would need to post a wishlist post of the forum for the author to optionally allow a size based buffer. I tend not to support that since it could be confusing for users to not really know how much buffer is available. I'd also have to rework pvr.nextpvr.

Well, currently I don't have a spare time to take a part in next two forums (TVH and NPVR). I would like to use better product under LE and it's up to developers if they are interested to improve their add-ons or not. The development of TVH is very slow and I don't see any progress here for years. So you have a chance to take over. `

Not supporting the requested feature is a bad choice because with variable data rates you can't predict at all how large buffer you need. So I believe my request has a reason. I don't know how the add-on communicate with Kodi regarding to timeshift "window", perhaps it's too complex to program it properly but I believe it should be possible.

Quote

For timeshifting I did see an seek back on Seznam.cz that had odd range headers for http that is why I would need the Kodi debug logs.

In my case it was not Seznam but CT1 (HD stream). Usually there are more issues with HD streams.

Quote

I can't confirm on LE12 but on LE11, I just download the Debian package for libdvbv5 https://packages.debian.org/bullseye/libdvbv5-0 armhf version and extract dvbv5-zap to ~/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32 from there confirm

LD_LIBRARY_PATH=./ ./dvbv5-zap --version

works and then we can continue, if not I will install LE12.

Thanks, I'll give it a try and let you know when ready (it may take some time)

Quote from emveepee

Are you using the chapter arrows in PVR?

Probably not as I don't know what it is and how to use.

Simply using Left and Right buttons on my IR Remote control.

Currently I am not able to switch the channel (without restarting the NPVR service), as mentioned earlier in previous thread.

in Kodi's log I see this after the (unsuccessful) channel change:

Jun 08 02:41:22 LE service.nextpvr[224764]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 08 02:41:22 LE service.nextpvr[224764]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 08 02:41:22 LE kernel: rpivid feb10000.codec: rpivid_h265_stop

The first attempt does not return any error in Kodi GUI, just like STOP pushed. Another attempt to start any channel returns Playback failed - One or more items failed to play. Check the log for more information about this message.

And the two lines appears in log again:

Jun 08 02:44:36 LE service.nextpvr[224764]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 08 02:44:36 LE service.nextpvr[224764]: ERROR FE_SET_PROPERTY: Bad file descriptor

After the NPVR service restart I can start playing any channel again.

OK, let's continue here with NextPVR add-on only: NextPVR add-on issues

Fork from this thread: RE: NextPVR vs TVHeadend

The issue with timeshift rewind (using left key button) encountered again.

I have found I can jump to start but only with another menu invoked by OK button, then I can't use the Left or Right butons for rewind otherwise it jumps to middle position and can't rewind to start again.

The status of .ts files at that moment:

LE:~/.kodi/temp # ls -l -h /tmp/ramdisk/

total 480M

-rw-r--r-- 1 root root 102.9M Jun 8 01:11 live-CT 2 HD T2-0-1.ts

-rw-r--r-- 1 root root 376.7M Jun 8 01:09 live-CT 2 HD T2-0.ts

-rw-r--r-- 1 root root 4.0K Jun 8 01:00 live-CT 2 HD T2-0.ts.map

LE:~/.kodi/temp # cat /tmp/ramdisk/live-CT\ 2\ HD\ T2-0.ts.map

<map>

<stream_length>430068612</stream_length>

<stream_duration>532882</stream_duration>

<complete>false</complete>

<live>true</live>

<files>

<file>

<filename>/tmp/ramdisk/live-CT 2 HD T2-0-1.ts</filename>

<offset>394997212</offset>

<start_ms>501008</start_ms>

<end_ms>532882</end_ms>

</file>

<file>

<filename>/tmp/ramdisk/live-CT 2 HD T2-0.ts</filename>

<offset>0</offset>

<start_ms>0</start_ms>

<end_ms>501008</end_ms>

</file>

</files>

</map>

Thanks for your quick reply as well.

Quote from emveepee

However from what I can tell both those frequencies should be in the tables that the service downloads https://github.com/tvheadend/dtv-…nd/dvb-t/cz-All

This table looks OK but the DVB-T2 items are at the end while DVB-T is obsolete so this should be reflected. I am not sure how tuning works but I believe best option should be to put DVB-T2 and DVB-T sections together with the same frequency, like outlined above ( so the tuning could be perhaps quicker ).

Quote from emveepee

- You have timeshifting set to 25 minutes of buffering so it should be able to rewind to the beginning of the buffer not the show. The actual file might be a little longer but the API restricts it to 25 minutes. I would treat this as an add-on issue though and would need Kodi debug logs.

In this case I believe it was Kodi's bug. I think .ts files were recorded correctly but in Kodi I could (at specific time, when the .ts was about 15 minutes long) rewind about 5 mins back. With TVH sometimes I can get the timeshift point outside of timeshift window. It works quite bad. TVH timeshift also does not work if the option to limit saved timeshift data size is set. This is completely ignored. I would like to see this (working) option in NPVR because the limitation by time is not very good. There are different channels with different stream data rates so you have to limit timeshift for the maximum data rate channels. Thus you can't use the remaining capacity for timeshift when watching channels with low data rate and this is pity. I would just like to configure the ramdisk volume with some capacity and wish NPVR to use it for timeshift data completely (until it's capacity is exhausted) regardless the data rate ( or till the configurable data size limit instead of time limit ). Hopefully this shouldn't be so complex task to add that feature.

I'll keep testing and provide you with Kodi logs when I encounter an issue recorded there.

Quote from emveepee

saw some trouble tuning at the driver level "dvb_fe_set_parms failed" Since I am pretty sure that NextPVR always tunes the same way, I feel that is a driver issue.

Yeah when I sent the comments, rebooted LE and then switching channels did not work again (without detail from Kodi)... Then tried the web client to get the error message which was that there's no available tuner (but the tuner device was visible in settings and it's MyGica which was always very reliable, at least in earlier LE versions & Windows). So I believe there could be some issue. I can also try another tuner (Astrometa).

Quote from emveepee

To tackle the EPG problem sub (the author) would need a full mux capture, from the RPi or any other PC you have. I can help you with this if you would like to continue. I could also use the full mux to feed into a modulator here to see if I can duplicate the tuning issue.

OK, this shouldn't be a problem if the full muxes (5 muxes used in my case) can be recorded from LE 12 / 11. I am looking forward for your instructions. Thanks for your effort!