Kodi not playing channel on first attempt

[Tunes0710]

Just about to stop NextPVR and try the Index.
Will post another log once I've restarted it carried out another curl

[mvallevand]

For curl we just need the time of the request and the http ok response.

Martin

[sub]

This is the log file from doing a curl on BBC 1 (Terrestrial) with the reversepriority set to false

Did this one take a long time too? ie, there is a 20 second delay in there I wouldn't expect to see:

2020-05-10 18:02:06.009 [DEBUG][4] HDHomeRunRecorder.StartStream()
2020-05-10 18:02:26.602 [DEBUG][4] source@1

Here is an updated NShared.dll, which gives us more logging between those two points:

[Tunes0710]

After running the index command and restarting NextPVR, the reply on the curl was instantaneous.. not even a second had passed before it started returning data.
Logs and curl output attached

EDIT: Curl didn't attach first time.. have readded.

[sub]

You'd normally expect a few milliseconds between those two messages. I've added some more log messages, so we get more info on where the delay is:

2020-05-11 05:21:19.472 [DEBUG][17] HDHomeRunRecorder.StartStream()
2020-05-11 05:21:19.473 [DEBUG][17] ipaddress is 192.168.1.82
2020-05-11 05:21:19.474 [DEBUG][17] building graph
2020-05-11 05:21:19.475 [DEBUG][17] About to load channel from tuning
2020-05-11 05:21:19.476 [DEBUG][17] source@1

[sub]

After running the index command and restarting NextPVR, the reply on the curl was instantaneous.. not even a second had passed before it started returning data.
Logs and curl output attached

EDIT: Curl didn't attach first time.. have readded.

Yep, that looked more normal:

2020-05-10 18:20:10.334 [DEBUG][4] HDHomeRunRecorder.StartStream()
2020-05-10 18:20:10.361 [DEBUG][4] source@1

[Tunes0710]

For some reason the Curl archive doesn't appear to be adding.
Would you still like me to run it again using your updated dll?

[sub]

For some reason the Curl archive doesn't appear to be adding.

Probably need to post the logs again.

Would you still like me to run it again using your updated dll?

I suspect the index has fixed this 20 second delay we saw, but maybe install it anyway, because it'll still be useful if we're looking at any delays.

[Tunes0710]

This is the latest one, after running the index command

Code:

18:21:11.140000 == Info:   Trying <ip>...
18:21:11.140000 == Info: TCP_NODELAY set
18:21:11.171000 == Info: Connected to <ip> (<ip>) port <port> (#0)
18:21:11.171000 => Send header, 103 bytes (0x67)
0000: 47 45 54 20 2f 6c 69 76 65 3f 63 68 61 6e 6e 65 GET /live?channe
0010: 6c 5f 69 64 3d 37 35 35 32 20 48 54 54 50 2f 31 l_id=7552 HTTP/1
0020: 2e 31 0d 0a 48 6f 73 74 3a 20 31 39 32 2e 31 36 .1..Host: <ip>
0030: 38 2e 31 30 2e 35 35 3a 32 32 30 38 39 0d 0a 55 :<port>..U
0040: 73 65 72 2d 41 67 65 6e 74 3a 20 63 75 72 6c 2f ser-Agent: curl/
0050: 37 2e 35 35 2e 31 0d 0a 41 63 63 65 70 74 3a 20 7.55.1..Accept:
0060: 2a 2f 2a 0d 0a 0d 0a                            */*....
18:21:11.781000 <= Recv header, 17 bytes (0x11)
0000: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d HTTP/1.1 200 OK.
0010: 0a                                              .
18:21:11.781000 <= 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 31 37 3a 32 31 3a 31 31 20 y 2020 17:21:11
0020: 47 4d 54 0d 0a                                  GMT..

The other half is just watching something, but as soon as she is done, I'll swap over the DLL and run it again and attach the logs to this thread

Thank you for your suggestion Martin, that index command seems to have done it!

[sub]

I'll either add the index for the next build, or remove the need for it. This type of lookup only happens with HDHR devices, but It'd never seen it take more than a few milliseconds.