2017-07-08, 21:43
@Milhouse got a question for you
1st really nice work on the mklocal.py and texturecache.py scripts.
It does exactly what I wanted.
But now... here's my question
Running the scripts it looks like it uses the "Texture" database of Kodi.....
But does it also modify the "art" table in the "MyVideos##" Main Kodi database ?
Because I believe that the Texture database is created based on the information in the "art" table.....
Here's an example:
In my case I have a Synology, it contains all my movies and also the Kodi main database MyVideos##
If I was to install Kodi on a computer and configure it to use my existing Kodi database, it would recreate a Textures database locally on the machine based on the info found in the MyVideos## database, no ? thus re-using all the HTTP link, and not the actual local images (located in the Synology with the movies)
1st really nice work on the mklocal.py and texturecache.py scripts.
It does exactly what I wanted.
But now... here's my question
Running the scripts it looks like it uses the "Texture" database of Kodi.....
But does it also modify the "art" table in the "MyVideos##" Main Kodi database ?
Because I believe that the Texture database is created based on the information in the "art" table.....
Here's an example:
In my case I have a Synology, it contains all my movies and also the Kodi main database MyVideos##
If I was to install Kodi on a computer and configure it to use my existing Kodi database, it would recreate a Textures database locally on the machine based on the info found in the MyVideos## database, no ? thus re-using all the HTTP link, and not the actual local images (located in the Synology with the movies)
