(2024-04-07, 10:26)Hitcher Wrote: Without debug logs, screenshots, skin used, addons affected, and ways to reproduce there's not a single thing we can do to help.

(2024-04-10, 11:43)atlanticcanadianscot Wrote: *no

(2024-04-10, 11:50)Hitcher Wrote:

(2024-04-10, 11:43)atlanticcanadianscot Wrote: *no

No what? No you won't provide debug logs, etc?

(2024-04-07, 16:30)jjd-uk Wrote:

(2024-04-07, 08:03)atlanticcanadianscot Wrote: *smart move, that's exactly what I'll be doing ~ this release is so primitive & bare bones basic I expect another release in a week to bury the memory of this travesty

I can only presume you were using a skin that hasn't been updated for v21 and was forced back to the default Estuary. It's not our fault that skin dev's haven't updated their skins yet, so your best bet is the ask in the relevent forum section for the skin when or even if it will be updated.

(2024-04-10, 11:50)Hitcher Wrote:

(2024-04-10, 11:43)atlanticcanadianscot Wrote: *no

No what? No you won't provide debug logs, etc?

(2024-04-10, 03:10)CrystalP Wrote: @doktourtv the log is not of debug level and doesn't have as much information.
Does it come from the original attempt or from one of your listed steps? It's weird that it's as if Kodi was upgrading from v19 (Matrix) and not v20.

The log you attached has signs of duplication in the movie table, similar to previous users:
 

Code:

SQL: [MyVideos131.db] SQLite error SQLITE_CONSTRAINT_PRIMARYKEY (UNIQUE constraint failed: videoversion.idFile)
Query: INSERT INTO videoversion SELECT idFile, idMovie, 'movie', '0', '40400' FROM movie (UNIQUE constraint failed: videoversion.idFile)

It blocks the normal database migration from v20.

Exporting db with v20 / importing with v21 has some risk. It's not well-tested or supported and I don't know if there were changes that impact the format.
However exporting with v20 / deleting video db / re-importing with v20 is supposed to work to create a cleaner v20 database. You're then in better shape to upgrade the db to v21.

4) what really matters is that ALL the myvideosxxx.db files are deleted. There must not be any left, or Kodi will attempt to migrate from whichever file you kept instead of starting a new video db from scratch.

6) a debug log of that execution of Kodi would give clues why some are missing. You'd have to give specific examples of missing items because it's no fun looking blind at a huge log file.

8) unusual sort: that would be the scan order in 7) again debug log would give clues why some are still missing.

(2024-04-10, 18:10)CrystalP Wrote: @hslansky your nfo file doesn't include hdr information in the streamdetails/video tags so it's not displayed in the skin.

@Colabacardi you likely have the same duplicate entry problem as the other users, but cannot say without a log of the migration to v21. Same workaround would also  likely work (export db with v20, delete all video databases, reimport with v20, then go to v21)

(2024-04-10, 18:36)hslansky Wrote: I use the same nfo for V20 and V21. Did something change with V21 that the hdr tag is now required. This wasn’t the case with V20.

(2024-04-10, 19:03)hslansky Wrote: I use Ember Media Manager. That really shouldn’t matter. The same nfo in V20 produces different results than V21. V20 shows the hdr flags, V21 does not.

(2024-04-10, 19:26)mikeSiLVO Wrote: Might be related to this PR. Maybe this comment helps?

(2024-04-10, 22:22)scott967 Wrote:

(2024-04-10, 19:26)mikeSiLVO Wrote: Might be related to this PR. Maybe this comment helps?

re:  Reading streamdetails by probing file vs using nfo.

I think there has long been some requirements discussion as far as which takes priority,  when is it refreshed, etc.  Assuming not a skin issue (and mikeSiLVO would know).

I see the wiki https://kodi.wiki/view/Databases/MyVideos#streamdetails says "Settings Will be overwritten on first play".  Not sure that is correct any more?

scott s.
.