(2021-08-20, 17:02)shedrock Wrote: It is a brand new installation of Matrix on LE.
I still have doubts @
shedrock, because in the first post you asked
Quote:Is there some way I can convert my MyMusic72.db to MyMusic82.db I dropped mine in there and renamed it, but it keeps prompting me to re-scan the tags.
It sounds much more like you are updating the version installed on a device. Do you really have a brand new installation of Matrix, with default settings, default skin, no sources added, empty music and video libraries etc.?
But let's say that you do, that for some reason you didn't just update the Leia version (which is the easiest thing to do), or maybe it is on another device or you are using a new SD card. I have to admit I am curious what the situation is. Anyway you are looking at this brand new installation of Matrix with an empty music library and no music sources added.
The simple way forwards, assuming that you have nfo files, is to recreate the music library from scratch - add sources, scan tags and scrape from nfo files which you say you have correctly located.
But you don't want to do that because you have had previous (mysterious to me) problems with nfo files being applied. So I offer you this slightly more complicated alternative:
You could add the music sources exactly as you did before but NOT scan to music library, or copy the sources.xml file from the Leia installation. The path to the music sources for this device needs to be exactly as same as when Leia was installed otherwise you can not do the following databse file manipulation.
Then, with Kodi off, delete MyMusic82.db and copy MyMusic72.db from the Leia installation. On restarting Kodi it will migrate this database to the Matrix version. When you enter the music library navigation screen it will keep prompting you to re-scan the tags. When it is convenient for you (it happens in the background so you can continue to use Kodi to play media etc., but you want to be able to leave the device on until scanning completes) allow this scan to happen. It will NOT rescrape additional album or artist data for any album or artist that has been previously scraped, that data is safely stored in the database already, so your manual edits will not be lost. There will be no need to import anything from previous exports.
Any now to what you did, and the problems you report.
(2021-08-20, 17:02)shedrock Wrote: I re-scraped and scanned all the music back into the library using local NFO in the scraper settings for music but it does nto pickup all the info for quite a lot of artist, even though the NFO files are perfect. They contain all the requirements that Musicbrainz calls for. However, if I go to Files > "Music_Library" and go to the particular artists that has no info being displayed, all I do there is Scan to Library with a full tag search and it populates the artist/album info.
Sorry, this makes no sense.
For starters NFO files get applied to the artist or album as dictated by their location, and not by the xml tags inside the NFO file.
There are no Musicbrainz requirements. You previously had issues where you had multiple artist entries for the same artist (caused mostly by variations of punctuation in artist names), trying to save the same artist Musicbrainz ID from the NFO files (or scraping remotely) to both artist entries raised a db error. This is possibly the source of your confusion.
If within file view doing "Scan to Library" from the context menu and saying yes to full tag scan when on a
particular artist subfolder (that is what you said works) picks up the nfo data, then doing that on the music source will do the same thing for ALL your music .
I don't know what process you followed when you "I re-scraped and scanned all the music back into the library using local NFO in the scraper settings for music".