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>

    Are you using the chapter arrows in PVR? They don't seek by time, their seeks are EPG based. I made this video a couple of years ago on an RPi4 with seeking on the timeline not on the arrows, excuse the sound I messed up OBS.

    The add-on doesn't really control what the GUI does, it just passes requests to the server.

    For clarity the other thread was about the nextpvr service addon and this so far is about pvr.nextpvr addon.

    Martin

    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.


    Edited 2 times, last by ghtester: Merged a post created by ghtester into this post. (June 8, 2023 at 1:48 AM).

    Quote from ghtester

    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.

    Your second image shows you using the chapter prev button, you need to move focus to the timeline on the light grey sliding scrollback buffer to skip properly. I thought I posted the link from the RPi4 earlier, in ite you can see the I bar cursor moving on the timeline

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
    with the remote.

    Out of curiosity are the channels you are having problem with h265 (as shown in that error)? Also sre you switching to and from DVB-T and DVB-T2 on the same tuner?

    Here is the error in the dvbv5 front end subsystem. https://git.linuxtv.org/v4l-utils.git/…5/dvb-fe.c#n522 it isn't coming from NextPVR

    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.

    Edited once, last by ghtester (June 8, 2023 at 2:20 AM).

    Ok thanks so without Kodi debug logs I can't help further, I am asking too many questions they would answer.


    I will however try and see how h265 timeshifts here on an RPi4 our digital channels are still mpeg2video but I can try and use an HDMI streamer.

    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

    Edited once, last by ghtester (June 8, 2023 at 3:47 AM).

    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.

    Code
    dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-frontend1-DVB-T-channels.conf  Prima\ Max -P -t 60 -o fullmux.ts

    You 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.

    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

    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

    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

    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.

    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.

    Edited 5 times, last by ghtester: Merged a post created by ghtester into this post. (June 12, 2023 at 10:17 PM).

    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

    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. :)

    Edited once, last by ghtester: Merged a post created by ghtester into this post. (June 13, 2023 at 12:21 AM).