Saving of pause position

[Druhl]

This feels like a dumb question because I am sure I saw this option previously but now can't find it for the life of me, and no mention of it here or anywhere.

I am sure I saw an option in Kodi along the lines of "save pause position in Kodi or in NextPVR or both" or something like that.

I (often but not always) suffer from a bit of random returns to beginning when skipping in a recording and am hoping varying this setting might help.

Anyone know where this is?


Thanks

[mvallevand]

Yes Kodi has two options. One lets you store the resume position in NextPVR and one lets you store it with Kodi. That second option is for multiple users who watch the same shows but at different times and don't want to share. This requires two boxes or two accounts on one Kodi instance.

Regardless of which you choose, the most common reason for a file not saving the resume point would be a bad timeline in an mpeg ts file causing a seek to fail so the choice won't matter. If it happens a lot you may need to consider remuxing or using the NextPVR options to convert to mp4.

There is also a logic issue if you play using the web player it can lose you resume position, I have a work around until sub releases an official update.

Martin

[Druhl]

Could you please do me a huge favour and direct me to where this option is in Kodi? I literally can't find it again. haha

To confirm, I am using the NextPVR plugin within an Android Kodi install on my TV, not the web player.

As for the seek errors: if I'm 5:00 into a file, and skip :30, 3/5 times it works. The other 2 times there's a brief wait, then it restarts from 0:00.

But on this same file, if I then direct-enter a go-to time of say 5:30, though this may also take a couple attempts, it will work after 2 or 3 tries.

This remains true throughout the file, and across many different files. So I don't think there's a timeline error on the files, maybe a communication lag or something between host and client...:?

[mvallevand]

It's an expert setting so you need to switch to expert mode but it won't fix the problem.

Definitely sounds like a bad file to me but I guess it could be wifi, it is unlikely to be NextPVR or pvr.nextpvr.

I don't look at Kodi problems without the Kodi debug logs

Martin

[Druhl]

I have expert mode enabled everywhere.

Could you please point me to the path to or page containing this setting? I literally have lost the ability to re-find it.

If the problem persists i can see about the Kodi logs.

Thanks!

[mvallevand]

Here

[Druhl]

Thank you very much.

I must have whizzed past it a dozen times!

[Druhl]

As you suggested, the "Kodi only" resume location did not fix problem - but it did seem to have an effect: it was worse.

Setting it back to NextPVR the problem remained as discussed above - hit or miss.

I have attached a Kodi debug log of me playing back a troublesome file, which should show some skipping successes and some skipping failures. With varying success, I was able to skip to various points along the entire length of this file, and at all points, its audio and video are synced.

The file in question reported to MediaInfo 1:03 length for audio, video, and any text streams.

But out of curiosity I used MKVtoolnix to write this TS file to an MKV and though it didn't report errors during the writing, the length of the new file changed from 1:03 to 1:58, and when played, the video appeared to still follow the original 1:02 timeline but the audio was messed up - falling behind.

Please let me know if you would like any more or different logs.

Thanks!

[mvallevand]

Logs needs to be zipped and under 2MB.

Recording clock time is reported to Kodi so it shouldn't change when remuxed. If the clock time was 1:03 (is that 63 seconds?) not sure why remuxing it would make it grow unless the remux was bad too.

Martin

[Druhl]

They were under 2mb, but were a RAR. Must have been rejected I guess.

Here is a ZIP.