![]() The first level is called source, in practice it is a folder given to Kodi to represent a portion of your music library. To allow all this magic to happen (and also to have most of the Kodi addons to work properly) the filesystem structure containing your music shall be structured as follows: nfo files (simply text files with some data inside) and optionally to download additional information like lyrics and fan art to be shown on the graphical user interface of Kodi. Kodi allows you to store information about your albums and songs in so called. Actually the official Kodi forum advises to use Musicbrainz to tag everything correctly.Ī quick digression on Kodi way of doing things. ![]() MusicBrainz Picard comes at help to accomplish this task in a matter of minutes (or hours, depending on the dimension of your music bank). If you converted all your CDs of the past into a more manageable and portable electronic format, no information is included yet into the mp3 (or any other equivalent format). The more information your file have the more precisely they will be shown in your library. ![]() So, all those files need to be equipped with the necessary information to be fetched correctly. Files need to have a proper name so you can navigate in the filesystem easily in a typically manual fashion.īut Kodi does not use filenames to populate your library, but the metadata embedded in the files instead. When it comes to music files, songs, albums, playlist and the like it all reverts into the so called tagging quest. I will also use some odd examples to enter into the details of Picard processes to explain you how to prevent some common mistakes that get unseen and wrongly accepted in bulk renames of big music archives. Then you need a proper schema to tag everything effectively without spending ages to check your work manually. Mainly I care about displaying albums in the correct chronological order of their original release.Are you planning to organize your music bank in a definitive way and make it ready to be digested by Kodi scraper? I really don't care about the specific release dates since my library contains very few alternate releases of the same album, with the exception of a few Beatles albums for which I have both the mono and stereo versions, and a few others where I have originals and remasters. I really can't seem to figure it out, however, so I was hoping for a little more assistance. I have tried to figure out how to map a custom field or virtual field to the "originaldate" value that is in all my music files so I can use that, instead of "date," for sorting and displaying purposes. For post-1990ish music, that's not often a problem, but it just drives me nuts to see, for instance, 10cc's 1966 album Sheet Music listed with a date of 1990. The date of the earliest release of a particular album is instead given in a tag that is, in internal MusicBrainz usage, called "originaldate." But it appears that MusicBee uses not this field, but just the basic date field, when displaying and sorting in the various browsing windows. This is because MusicBrainz distinguishes between individual releases of a given album. In the basic "Date" field, MusicBrainz Picard tagger puts the date of the specific medium that is the source of your set of mp3 or flac or whatever files. I still have one big nagging issue, however, caused I suspect by the fact that I use MusicBrainz to tag my files. I've been using MusicBrainz for a couple weeks now and am basically pretty happy with it and have (I think!) mastered most of the learning curve.
0 Comments
Leave a Reply. |