[HeresJohnny]

I'm no expert but there might be a problem if you connect clients based on mixed OS to a centralized database. Windows is case insensitve AFAIK whereas linux based OS willl be case senstive. If you have not taken care of this on database level appropriately and start deleting paths based on case you might or might not create a mess for yourself.

The problem already starts with what I regard a design flaw in Kodi where Windows created databases called "MyVideosxxx" and linux based creates databases called "myvideosxxx". Depending on the right (or wrong) circumstances you might already have created two databases...

[rafi1]

I don't think it is  the way Kodi design meant to work with centralized DB .. see -  https://kodi.wiki/view/MySQL.

[andrzejls]

I don't think it is  the way Kodi design meant to work with centralized DB .. see -  https://kodi.wiki/view/MySQL.

@rafi1
What this link states is that all Kodi seats that access centralized database needs to be on same Kodi version, for instance v21.1. It does not matter if you are in Android, Windows or Linux. I run Kodi database in MarisDB, for a several years, which run in Openmediavault NAS based in Debian Linux. and is accessed by 3 Nvidia Shiels Pro and 2 Firestick 4K MAX. If you, for instance, have a mix of Kodi v21.1 and v21.0 is when running Kodi "Backup" in restore mode you will just get a message that you are restoring Kodi to a different release ( backup made with v21.1 and you are restoring to v21.0). With centralized Database you cannot have a Kodi v20 and Kodi v21 installs. Kodi v20 is using MyVideos121 database while v21 is using MyVideos131. In case you have a diffrent releases of Kodi then you will have to have database local to that Kodi install seat.

[andrzejls]

I'm no expert but there might be a problem if you connect clients based on mixed OS to a centralized database. Windows is case insensitve AFAIK whereas linux based OS willl be case senstive. If you have not taken care of this on database level appropriately and start deleting paths based on case you might or might not create a mess for yourself.

The problem already starts with what I regard a design flaw in Kodi where Windows created databases called "MyVideosxxx" and linux based creates databases called "myvideosxxx". Depending on the right (or wrong) circumstances you might already have created two databases...

@HeresJohnny
Bellow is my post from this thread "https://forum.kodi.tv/showthread.php?tid=370915" post #13.

"Interesting add-on, "Kodi Selective Cleaner". So I got v1.0.7 (latest) and did some testing. It does clean some extraneous data in database, but.... 

My setup:
- Kodi 21.1 database MyVideos131 is in MariaDB running in Debian based Openmediavault NAS and used by 5 (five) kodi seats (3 on Nvidia Shield Pro 2019 and 2 on Firestick 4K MAX).

The scenario:
- Removing from Kodi TV Show or Movie using "Long press Enter or OK Button" --> MANAGE --> REMOVE FROM LIBRARY. I will use as an example "All.Creatures.Great.and.Small.1978" TV Show.
- SETTINGS --> MEDIA --> CLEAN LIBRARY. At this point that TV Show is cleaned in the database table "tvshow"
- Deleting this show from a drive designated and assigned to TV Shows in NAS so MariaDB does not see it when "Update Library is run in Kodi.
- Bring back this show to the drive that this show was originally on.
- When "Clean Library" was run from Kodi the Database table "path" is not cleaned (the tv show path is not removed), so when I run Update Library in Kodi that show is not recognized and is not scanned into the Database.

The workaround:
At this point I have to go into MariaDB using "dbeaver-ce" on one of me Linux boxes and remove this show entries in "path" table, so then it can be scanned back into Kodi database.
My hope was that this add-on will take of this issue but unfortunately it does not. I still think that it is a good attempt, "Kodi Selective Cleaner", but it falls short of being great, IMHO.

BTW, why Kodi SETTINGS --> MEDIA --> CLEAN LIBRARY is not cleaning library including table "path". Could this function be incorporated into future versions?"

I have been using above "workaround" for a long time and I did not notice any corruptions. I would love to see "Kodi Selective Cleaner" clean/remove entries in "path" table of movies and tvshows no longer listed in respective tables.

Regarding database name, Database that was created in MariaDB always was "MyVideoxxx"

[jbinkley60]

What this link states is that all Kodi seats that access centralized database needs to be on same Kodi version, for instance v21.1. It does not matter if you are in Android, Windows or Linux. I run Kodi database in MarisDB, for a several years, which run in Openmediavault NAS based in Debian Linux. and is accessed by 3 Nvidia Shiels Pro and 2 Firestick 4K MAX. If you, for instance, have a mix of Kodi v21.1 and v21.0 is when running Kodi "Backup" in restore mode you will just get a message that you are restoring Kodi to a different release ( backup made with v21.1 and you are restoring to v21.0). With centralized Database you cannot have a Kodi v20 and Kodi v21 installs. Kodi v20 is using MyVideos121 database while v21 is using MyVideos131. In case you have a diffrent releases of Kodi then you will have to have database local to that Kodi install seat.

Correct, when you are using MySQL and similar as a centralized database without a translation layer.   Only Kodi clients on the same copy of the database (i.e. database number) can share data.  Other sharing solutions, like I use Mezzmo and the Mezzmo Kodi addon, do not have this limitation because the addon provides a translation layer to the versions of Kodi.  I do this with Mezzmo by syncing the local Kodi client databases with the Mezzmo central database which allows each client to run what they want.  The clients also run faster since they are running off of their local databases and I don't have the issue of a user messing with a Kodi client and breaking the metadata for everyone.  This is just my approach to Kodi sharing.  Ironically much of the KSCleaner code comes from the Mezzmo Kodi addon.


Thanks,

Jeff

[jbinkley60]

- When "Clean Library" was run from Kodi the Database table "path" is not cleaned (the tv show path is not removed), so when I run Update Library in Kodi that show is not recognized and is not scanned into the Database.

The workaround:
At this point I have to go into MariaDB using "dbeaver-ce" on one of me Linux boxes and remove this show entries in "path" table, so then it can be scanned back into Kodi database.
My hope was that this add-on will take of this issue but unfortunately it does not. I still think that it is a good attempt, "Kodi Selective Cleaner", but it falls short of being great, IMHO.

BTW, why Kodi SETTINGS --> MEDIA --> CLEAN LIBRARY is not cleaning library including table "path". Could this function be incorporated into future versions?"

I have been using above "workaround" for a long time and I did not notice any corruptions. I would love to see "Kodi Selective Cleaner" clean/remove entries in "path" table of movies and tvshows no longer listed in respective tables.

 

Regarding database name, Database that was created in MariaDB always was "MyVideoxxx"

I took some time and went back through the KSCleaner code and did some testing. Path table cleaning is included.  I had forgotten I added that awhile back.  I tested it by manually adding a path table entry with no other references to it (i.e. nothing in the files or tvshowlinkpath tables) and KSCleaner analyzed and cleaner the orphaned entry properly.  If you are seeing instances where you think the path table entry is orphaned and should be removed then we need to look closer at what is going on with your database.  I have found a number of Kodi users have things in their database which they are not aware of, including path tables with over 1200 entries.  
 

Regarding database name, Database that was created in MariaDB always was "MyVideoxxx"

Yeah, this issue was addressed in v1.0.6 of KSCleaner.  I updated the default MySQL database names to match the Kodi documentation.  This was an original error on my part.


Thanks,

Jeff

[andrzejls]

@jbinkley60
cc @latts9923
Thank you for your reply. I did some more testing and here is what I found out:
After removal TV Show from MyVideo131 using Kodi "MANAGE" --> "REMOVE FROM LIBRARY" the show was removed from tables "tvshow" and "files" Table "path" was still showing path to the show and seasons. Running "Kodi Selective Cleaner" --> VIDEO DB DATA ANALYZER --> CLEAN TABLES (this option is not set in the initial add-on settings, so it is not available until is activated. I think it should be selected as default option in settings) table "path" is cleaned (TV Show seasons are removed) but TV Show name directory path is still listed. At this point Kodi will not scan this show back to the database. Then I did run  "Kodi Selective Cleaner" --> VIDEO DB DATA ANALYZER --> CLEAN TABLES for a second time and then TV Show directory path name was removed and I was able to scan back this show into the database.
I do not know as to why I had to run it twice (maybe because I use NFS and not Samba/cifs), but it did the job. For now, just in case, I keep full backup of the database.
Thanks for a great work and bringing this add-on to Kodi.

[jbinkley60]

I do not know as to why I had to run it twice (maybe because I use NFS and not Samba/cifs), but it did the job. For now, just in case, I keep full backup of the database.
Thanks for a great work and bringing this add-on to Kodi.

You had to run it twice because of the nature in how it operates.  When you analyze or clean tables KSCleaner looks at the current state of the tables and does not due a multi-pass or recursive analysis or cleaning.  This is for safety reasons.   So the first time you ran it KSCLeaner saw the TVShow table orphaned entries (due to how Kodi left them) and cleaned them.  That cleaning then caused, on the second run, the path table orphaned entries because there were no longer any TVShow entries pointing at them.  For some tables Kodi leverages triggers to handle clearing orphaned entries but here it doesn't. 

I could look to add multi-pass or recursive capabilities into KSCleaner but i believe that would overly complicate things and given how fast it runs, I don't see the current operating mode as a major drawback.  I can't think of a scenario where it would need to be run three times.


Thanks,

Jeff

[andrzejls]

I do not know as to why I had to run it twice (maybe because I use NFS and not Samba/cifs), but it did the job. For now, just in case, I keep full backup of the database.
Thanks for a great work and bringing this add-on to Kodi.

You had to run it twice because of the nature in how it operates.  When you analyze or clean tables KSCleaner looks at the current state of the tables and does not due a multi-pass or recursive analysis or cleaning.  This is for safety reasons.   So the first time you ran it KSCLeaner saw the TVShow table orphaned entries (due to how Kodi left them) and cleaned them.  That cleaning then caused, on the second run, the path table orphaned entries because there were no longer any TVShow entries pointing at them.  For some tables Kodi leverages triggers to handle clearing orphaned entries but here it doesn't. 

I could look to add multi-pass or recursive capabilities into KSCleaner but i believe that would overly complicate things and given how fast it runs, I don't see the current operating mode as a major drawback.  I can't think of a scenario where it would need to be run three times.


Thanks,

Jeff

@jbinkley60
Thank you for the explanation of the "logic" process of this add-on. Now it makes sense. Current operating mode is not a drawback at all. The issue is that,unless you "play" with it and try different scenarios, like running it twice, you would not know. I think that enabling "CLEAN TABLES' as default in settings would help as well as, maybe, including note/instruction regarding ruining it twice or something to that effect. Overall I think, once I know how it works, that this is a great addition to Kodi as it eliminate the need to do a dangerous manual database manipulation.

[andrzejls]

What this link states is that all Kodi seats that access centralized database needs to be on same Kodi version, for instance v21.1. It does not matter if you are in Android, Windows or Linux. I run Kodi database in MarisDB, for a several years, which run in Openmediavault NAS based in Debian Linux. and is accessed by 3 Nvidia Shiels Pro and 2 Firestick 4K MAX. If you, for instance, have a mix of Kodi v21.1 and v21.0 is when running Kodi "Backup" in restore mode you will just get a message that you are restoring Kodi to a different release ( backup made with v21.1 and you are restoring to v21.0). With centralized Database you cannot have a Kodi v20 and Kodi v21 installs. Kodi v20 is using MyVideos121 database while v21 is using MyVideos131. In case you have a diffrent releases of Kodi then you will have to have database local to that Kodi install seat.

 I use Mezzmo and the Mezzmo Kodi addon,

Thanks,

Jeff

@jbinkley60
I tried to install "Mezzmo" but Kodi (21.1) is missing python 2.25.0 dependency. Can you advise where I can get that so I could test this add-on?.

[jbinkley60]

@jbinkley60
I tried to install "Mezzmo" but Kodi (21.1) is missing python 2.25.0 dependency. Can you advise where I can get that so I could test this add-on?.

That error would indicate you attempted to install the Kodi 18 version of the addon.  There are 2 versions, Kodi 18 and below and Kodi 19 and above.  This is due to the Kodi Python version change which occurred between Kodi 18 and 19 (Python 2.x to 3.x).  You can see all of the releases here to download.   I am not sure what you are attempting but the Mezzmo Kodi addon is designed to run with a Mezzmo DLNA server or other UPnP servers.  Please read How it Works and Getting Started for more information.


Thanks,

Jef

[Karellen]

@jbinkley60

I ran this yesterday. I was wondering if it is possible to use a different colour text. That electric blue is very difficult to read off the tv screen.

[jbinkley60]

I ran this yesterday. I was wondering if it is possible to use a different colour text. That electric blue is very difficult to read off the tv screen.

What if I add an addon settings option so you can choose from 3-4 colors like maybe Blue, Red, Green and Yellow ?


Thanks,

Jeff

[Karellen]

What if I add an addon settings option so you can choose from 3-4 colors like maybe Blue, Red, Green and Yellow ?

I don't mind. As long as the text is legible in those colours.
Where are the colours set in the addon? I'll have a fiddle with the colour.

[andrzejls]

@jbinkley60
I tried to install "Mezzmo" but Kodi (21.1) is missing python 2.25.0 dependency. Can you advise where I can get that so I could test this add-on?.

That error would indicate you attempted to install the Kodi 18 version of the addon.  There are 2 versions, Kodi 18 and below and Kodi 19 and above.  This is due to the Kodi Python version change which occurred between Kodi 18 and 19 (Python 2.x to 3.x).  You can see all of the releases here to download.   I am not sure what you are attempting but the Mezzmo Kodi addon is designed to run with a Mezzmo DLNA server or other UPnP servers.  Please read How it Works and Getting Started for more information.


Thanks,

Jef

So basically, there is no "Mezzmo" version for Kodi 21, it is not really Kodi add-on (in my understanding) and is not free. So....why I would even consider it?. I run Openmediavault (free) with MariaDB (free) to serve Kodi (free) database to multiple clients. At first Mezzmo sounded interesting but.....

Thanks