Kodi not playing channel on first attempt

[Tunes0710]

So it seems to be something to do with the number of channels I have...
The only channels I have issues with are the terrestrial channels coming via the HDHomeRun.
Any IPTV channel opens up pretty much instantly.

However.
If I delete all of the IPTV channels from NextPVR, then the terrestrial channels work fine.

As an example. From the Log I took of BBC1, it took 80 seconds from
13:43:15.546000 => Send header, 103 bytes (0x67)
to
13:44:35.656000 <= Recv header, 17 bytes (0x11)

However
if I delete the IPTV (around 5000 channels)
trying to load the same channel
13:48:16.000000 => Send header, 103 bytes (0x67)
to
13:48:32.171000 <= Recv header, 17 bytes (0x11)

Just 16 seconds.

I can upload both logs if needed? But essentially it seems like with lots of channels, NextPVR takes a while to reply when a terrestrial channel is selected

[mvallevand]

I would have preferred the actual zip, but it seems to be what I suspected from the beginning however even 16 seconds is typically too long for Kodi. If you change this setting to false in config.xml

<ReversePriorityForLiveTV>false</ReversePriorityForLiveTV>

Do things improve?

I suggest re-adding your normally channel, and upload the zipped curl log for and the corresponding NextPVR log to show where a bottleneck might be would help, perhaps an index on the table is necessary.

Also checking why you really need 5000 channels (other than being to lazy to reduce the list) might be something to consider.

Martin

[Tunes0710]

5000 *is* reduced, lol.
If I just imported the full M3U including the VOD, it's over 72000 "channels" as each ep of each series is classed as it's own channel.
If I do the curl with all channels imported, it takes over 20 minutes to respond.

Once my current items have finished recording, I'll make the change you suggested and then try the curl command again with Terrestrial only/reduced iptv/full iptv and I'll zip up each log and post here for you. Will including 30 seconds of data after I see it start receiving a response (and data downloading).

Many thanks for taking the time to help.

[mvallevand]

If you have access to a sqlite tool I would see if creating an index like this help backing up your npvr.db3 file first.

CREATE INDEX index_tuning ON CHANNEL_MAPPING (tuning);

Martin

[sub]

5000 *is* reduced, lol.
If I just imported the full M3U including the VOD, it's over 72000 "channels" as each ep of each series is classed as it's own channel.
If I do the curl with all channels imported, it takes over 20 minutes to respond.

Once my current items have finished recording, I'll make the change you suggested and then try the curl command again with Terrestrial only/reduced iptv/full iptv and I'll zip up each log and post here for you. Will including 30 seconds of data after I see it start receiving a response (and data downloading).

Many thanks for taking the time to help.

With all the channels imported, and no web browser point at the NextPVR web app, restart NextPVR (so the logs are reset), then do the curl command. Wait until the data starts arriving, before starting the web app and zipping the logs.

[sub]

I have a suspicion it's actually related to getting the channel list and and more specifically checking if the icons are available for the channel.

[Tunes0710]

I would have preferred the actual zip, but it seems to be what I suspected from the beginning however even 16 seconds is typically too long for Kodi.    If you change this setting to false in config.xml

<ReversePriorityForLiveTV>false</ReversePriorityForLiveTV> 

Do things improve?

I suggest re-adding your normally channel, and upload the zipped curl log for  and the corresponding NextPVR log to show where a bottleneck might be would help, perhaps an index on the table is necessary.

Also checking why you really need 5000 channels (other than being to lazy to reduce the list) might be something to consider.

Martin

After adding the above command, when I do a curl, it now doesn't wait for me to CTRL-C, it exits immediately

Code:

10:20:18.609000 == Info:  Trying <ip>...
10:20:18.625000 == Info: TCP_NODELAY set
10:20:18.640000 == Info: Connected to <ip> (<ip>) port <port> (#0)
10:20:18.640000 => Send header, 110 bytes (0x6e)
0000: 47 45 54 20 2f 70 6c 61 79 65 72 2e 68 74 6d 6c GET /player.html
0010: 3f 63 68 61 6e 6e 65 6c 5f 69 64 3d 37 35 35 32 ?channel_id=7552
0020: 20 48 54 54 50 2f 31 2e 31 0d 0a 48 6f 73 74 3a  HTTP/1.1..Host:
0030: 20 31 39 32 2e 31 36 38 2e 31 30 2e 35 35 3a 32  <ip>:<port>
0040: 32 30 38 39 0d 0a 55 73 65 72 2d 41 67 65 6e 74 ..User-Agent
0050: 3a 20 63 75 72 6c 2f 37 2e 35 35 2e 31 0d 0a 41 : curl/7.55.1..A
0060: 63 63 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a      ccept: */*....
10:20:18.640000 <= Recv header, 20 bytes (0x14)
0000: 48 54 54 50 2f 31 2e 31 20 33 30 32 20 46 6f 75 HTTP/1.1 302 Fou
0010: 6e 64 0d 0a                                    nd..
10:20:18.640000 <= Recv header, 37 bytes (0x25)
0000: 44 61 74 65 3a 20 53 75 6e 2c 20 31 30 20 4d 61 Date: Sun, 10 Ma
0010: 79 20 32 30 32 30 20 30 39 3a 32 30 3a 31 37 20 y 2020 09:20:17
0020: 47 4d 54 0d 0a                                  GMT..
10:20:18.640000 <= Recv header, 17 bytes (0x11)
0000: 53 65 72 76 65 72 3a 20 4b 65 73 74 72 65 6c 0d Server: Kestrel.
0010: 0a                                              .
10:20:18.640000 <= Recv header, 19 bytes (0x13)
0000: 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 Content-Length:
0010: 30 0d 0a                                        0..
10:20:18.640000 <= Recv header, 25 bytes (0x19)
0000: 43 61 63 68 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e Cache-Control: n
0010: 6f 2d 63 61 63 68 65 0d 0a                      o-cache..
10:20:18.640000 <= Recv header, 18 bytes (0x12)
0000: 50 72 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 68 65 Pragma: no-cache
0010: 0d 0a                                          ..
10:20:18.640000 <= Recv header, 13 bytes (0xd)
0000: 45 78 70 69 72 65 73 3a 20 2d 31 0d 0a          Expires: -1..
10:20:18.640000 <= Recv header, 64 bytes (0x40)
0000: 4c 6f 63 61 74 69 6f 6e 3a 20 6c 6f 67 69 6e 2e Location: login.
0010: 68 74 6d 6c 3f 73 61 6c 74 3d 34 65 33 61 36 64 html?salt=4e3a6d
0020: 38 32 2d 34 37 33 32 2d 34 61 61 35 2d 62 38 66 82-4732-4aa5-b8f
0030: 65 2d 63 34 66 36 31 33 32 30 63 32 32 62 0d 0a e-c4f61320c22b..
10:20:18.640000 <= Recv header, 250 bytes (0xfa)
0000: 53 65 74 2d 43 6f 6f 6b 69 65 3a 20 2e 41 73 70 Set-Cookie: .Asp
0010: 4e 65 74 43 6f 72 65 2e 53 65 73 73 69 6f 6e 3d NetCore.Session=
0020: 43 66 44 4a 38 4e 62 77 65 33 59 59 33 6a 42 42 CfDJ8Nbwe3YY3jBB
0030: 67 46 50 7a 4f 49 50 79 53 67 6d 39 55 4a 47 50 gFPzOIPySgm9UJGP
0040: 61 59 4c 5a 6f 51 73 50 58 78 78 75 6b 7a 69 33 aYLZoQsPXxxukzi3
0050: 6e 71 6c 65 66 4c 51 6d 25 32 42 63 55 6f 6d 68 nqlefLQm%2BcUomh
0060: 70 73 30 75 62 31 70 69 56 66 46 5a 45 4e 71 4a ps0ub1piVfFZENqJ
0070: 67 31 6e 46 55 4c 68 57 54 58 56 6c 45 64 31 68 g1nFULhWTXVlEd1h
0080: 76 44 6f 4c 58 41 32 68 57 75 64 67 62 37 7a 39 vDoLXA2hWudgb7z9
0090: 74 4e 49 42 46 59 34 6f 49 54 70 45 56 31 30 78 tNIBFY4oITpEV10x
00a0: 39 57 37 49 37 37 43 4f 6d 78 31 7a 43 39 36 25 9W7I77COmx1zC96%
00b0: 32 42 37 4e 6e 25 32 42 35 4a 58 76 68 6a 45 4c 2B7Nn%2B5JXvhjEL
00c0: 43 25 32 46 36 6d 34 43 32 49 61 33 74 42 6f 6b C%2F6m4C2Ia3tBok
00d0: 65 47 30 66 44 77 35 38 3b 20 70 61 74 68 3d 2f eG0fDw58; path=/
00e0: 3b 20 73 61 6d 65 73 69 74 65 3d 6c 61 78 3b 20 ; samesite=lax;
00f0: 68 74 74 70 6f 6e 6c 79 0d 0a                  httponly..
10:20:18.640000 <= Recv header, 2 bytes (0x2)
0000: 0d 0a                                          ..
10:20:18.656000 == Info: Connection #0 to host <ip> left intact

I've used xTeve and whittled down to around 1200 channels, but it still seems to take about 16 seconds when trying to view the channel in Kodi or on the web browser saying "Starting Device, Please wait..." before it starts saying "receiving data".

I'll also try your index command and see if it makes any difference and report back.



EDIT: Oh wait... no.. sorry..it's me being an idiot.. I'm using the wrong link!
GAH!
Let me start this all over again and try...

[Tunes0710]

5000 *is* reduced, lol.
If I just imported the full M3U including the VOD, it's over 72000 "channels" as each ep of each series is classed as it's own channel.
If I do the curl with all channels imported, it takes over 20 minutes to respond.

Once my current items have finished recording, I'll make the change you suggested and then try the curl command again with Terrestrial only/reduced iptv/full iptv and I'll zip up each log and post here for you. Will including 30 seconds of data after I see it start receiving a response (and data downloading).

Many thanks for taking the time to help.

With all the channels imported, and no web browser point at the NextPVR web app, restart NextPVR (so the logs are reset), then do the curl command. Wait until the data starts arriving, before starting the web app and zipping the logs.

As it doesn't wait anymore, I'll change the reversepriority setting and give this a go

[mvallevand]

You aren't using the correct syntax. I asked for playback of the direct channel number URL http://ip:8866/live?channel=## but you went off script to use the web player URL http://ip:8866/player.html?channel_id=7552 If you want to use that channel id it is fine

curl -v --trace - --trace-time http://ip:8866/live?channel_id=7552 -o NUL >filename.txt

Martin

[Tunes0710]

You aren't using the correct syntax.  I asked for playback of the direct channel number URL http://ip:8866/live?channel=## but you went off script to use the web player URL http://ip:8866/player.html?channel_id=7552  If you want to use that channel id it is fine

curl -v --trace - --trace-time http://ip:8866/live?channel_id=7552 -o NUL >filename.txt

Martin

Yup, sorry.. I just realised this and edited my post before I had seen this reply...
I'm just running the correct command for Sub with *all* channels (with reversepriority set to true).

I'll then do it again with your suggestion and the *correct* syntax this time..