(2016-12-24, 17:50)melons2 Wrote: Yes ........there was an error....I updated and it runs now.
I have a music library that is 3.65 TB in size and when I go to update it by using "ADVANCED > MODIFY ADDON DATABASE > UPDATE DATABASE"
it is a day or more painfully slow process.
Is there anything I can do to improve this?
Should I be updating it every time I run it?
Thanks
If you want to increase the scanning speed for the music library there are some things you can check:
1. Don't use Universal Album/Artist Scraper, use TheAudioDB Album/Artist Scraper, as it's a lot faster than the Universal one. However if you have your library tagged via MusicBrainz Picard you may lose a lot of the added detail MusicBrainz adds to your tags. I think MBID's are supported in the AudioDB listings, but likely not much else. I've never personally compared the two feature for feature. What I do know is the AudioDB scraper is notably faster.
2. Turn off the Option "Fetch Additional Information During Updates" for the music library. I think you loose artist / album biographies and such, but these can be enabled by turning on this setting after the initial scrape and doing a library refresh. YMMV.
3. Check the status / tags of any artist / album that continually appears to be being re-processed on each launch scan (i.e: a significant amount of time where the scraper is focusing on that artist/album during the scan), as this may indicate problems with the tags of that artist/album that may need correcting. One such example could be incorrect MusicBrainz IDs for artist/album/track.
4. Disable the option: "include artists that only appear on compilations" (Kodi versions up to 16.1) and "Show song and album artists" (Kodi 17 Upwards) as the scraper won't search for detailed info about featured artists and/or artists who only appear on compilations (or are contributor artists on an album) to the database.
5. file size / format type may also be a factor. This is supposition on my part, but I've noticed that scanning of albums/tracks seems to take longer for me on single-track albums (i.e: the album is one super-long track or a track of high bitrate) than on lower quality / smaller files.
6. Use a local database instead of a shared MySQL (or MariaDB) database. While I do use a network shared DB, and like the benefits it brings, sharing a library between multiple systems, it's SLOW when doing library scanning. because all data transactions to the database are going backwards & forwards across your weakest link - your local network. It's been my experience that quite often, with all the above enabled, a complete library scan (34,000 tracks) has taken over 12 hours for me. Also, other devices on the network communicating will reduce the amount of bandwidth available to Kodi. So with this in mind, attempt to schedule your library updates at a time when the network isn't going to be over-saturated if your using the MySQL / MariaDB option.
Also, if your MySQL server is a device like a NAS, unless it has a powerful CPU (an Intel Core Series CPU at least), your scraping speed will be limited by the speed of the CPU in the NAS and it's ability to process and add that data to the shared database, alongside managing it's resources with the other usage demands being placed upon it.
Hope this helps.
