NPVR2.5.5 Database Playback Position Table Change?

[Lao Pan]

I have come across a couple of videos where it now always asks if you want to resume from the same point.
On checking the database with sqlspy it appears that the file naming has changed with NPVR2.5.5 in the playback position table. Before it contained the full path (//Tower/Adult Content/Video name.mkv)and now only contains the file name (Video name.mkv). I think these files were partly watched before upgrading to 2.5.5.

Would deleting all the entries with full path names in this table be the best way of dealing with this? - i.e. pre NPVR 2.5.5 entries.
Think I might just back up the database first

[sub]

It should still find the position info in the logs assuming the filename part is exactly the same ie 'Video name.mkv'. It looks for a match in the database ending with the filename part.

If you zip and attach your npvr.db3, and actual filename, I can check it out.

[mvallevand]

There is a issue in 2.5.x when the same filename was played from multiple locations in the older database, which I could only resolve by removing the entries with duplicate records.

Martin

[Lao Pan]

I found that the files in question had different playback positions in the old and new entries so it was always using the old resume position. Changing the playback position data to the duration data (as in fully watched) in the database has solved the problem.

I know it is not really a problem but now every file that was played before and since 2.5.5 was installed has 2 entries in the table - any simple way to remove the redundant entries?

I'd rather not share this part of the db given the file path I gave earlier

[Lao Pan]

Finally Got this sorted.
What was happening was the old filename entries with file paths that still had playback positions - i.e. partly watched before upgrading to NPVR 2.5.5 were no longer being updated, a new entry (without file path) is being created instead and the old entry remains with the old resume position.

In the end I used SQLiteSpy to run SQL DELETE on all the entries in the table with \\ or a Drive letter in the filename using the "LIKE %". I figured that after a month since updating, the resume positions are not going to be of much use. (Did it on a copy of the db first)