Watching in-progress recording goes past end of recording

[cncb]

When watching an in-progress recording, the Kodi timeline reflects the growing recording length properly, however, it does not recognize when the recording stops.  For example, I start watching an hour-long program after it has been recording for 45 minutes.  The recording length as reported by the Kodi timeline keeps growing past 1:00:00 and doesn't stop until I stop and restart playback.  Is there any way around this?  Thanks.

[mvallevand]

It's not clear to me what you are saying. Do you mean the recording stays looping and retryinh at the end with the timeline growing instead of exiting? If so I would need to see the logs it does seem like a possible bug.

Martin

[cncb]

No, playback stops at the real end of the recording, but the recording is not marked as watched due to the length "confusion". Is there a way to indicate to Kodi that the recording is done?

[mvallevand]

That is clearer and I do need the Kodi debug log.

Martin

[cncb]

I will have to turn on Kodi logging and see if I can capture it next time. Thanks.

[mvallevand]

Thanks I use comskip so I don't play many in progress recordings to completion so this is an annoying test. The timebar increasing make sense because during playback there is no mechanism to say when the recording truly ends if for example it is extended outside of Kodi in a browser or by NextEnd.

I am not sure I can actually resolve it but I wanted to see what the addon is sending NextPVR.

Martin

[cncb]

Here is the log from when I started watching a 30-minute recording from the beginning after it had been recording for ~23 minutes.  I let it play until it stopped on its own when it reached the end of the recording.

[mvallevand]

Thanks it is telling me what I think is correct

method=recording.watched.set&recording_id=1439&position=1922

That would be 1800 seconds plus one minute for each padding.

What is odd about this is this might not be the addon. I see this

2020-11-15 11:56:15.948 T:28798 DEBUG: Mysql execute: insert into bookmark (idBookmark, idFile, timeInSeconds, totalTimeInSeconds, thumbNailImage, player, playerState, type) values(NULL,306,1922.213798,3428.000000,'','VideoPlayer','', 1)

and it is not clear why Kodi is telling mysql that the file is that long. If it was just the time past the recording it wouldn't be 3428 seconds.

I also note that you might be getting information from mysql

<importwatchedstate>true</importwatchedstate>
<importresumepoint>true</importresumepoint>

I wonder if that is perhaps overriding the NextPVR backend data. Does it work as expected with mysql turned off?

Martin

[cncb]

and it is not clear why Kodi is telling mysql that the file is that long.  If it was just the time past the recording it wouldn't be 3428 seconds.

This makes sense since the reported length keeps growing on the timeline.  I started watching about 25 minutes in plus the 32-minute recording is about 57 minutes length on the timeline when it stopped.  It could be that MySQL might be keeping it from being marked as watched due to an incorrect length, but sorry, I don't really want to mess with the MySQL connection to test.

[mvallevand]

I'll change my debug world from locast and try some tests here and see what my logs and the database say. You shouldn't be putting pvr in mysql though it makes no sense competing with the backend but maybe these can't be separated.

Martin