![]() ![]() Release Artist credits are helpful and necessary resource when identifying releases. The Release Artist list is not the right place for a detailed list of everybody. The challenge for you is to persuade others that the Release Artist list should do a better job of helping you find and identify releases, and what words to add to the CSG/Release/Artists guideline to make that happen. It looks like I didn’t persuade enough people. The challenge for me was to persuade others that my reasons justified adding words to CSG/Release/Artist about length of the Release Artist string. The whole purpose of this thread has been to review different choices for what CSG/Release/Artist could say, in order to guide all of us to enter data that others will find useful. Someone else: "assign releases to specific artists" Me: “ReleaseArtist string triggers bugs in my taggers”, "useful ReleaseArtist string for music files directory name" Each has their own opinion on which arguments are “good”. ![]() So many people use MusicBrainz, each for their own reasons. ![]() Since when it has been a problem of having too much data? ![]() It could have taken tens of minutes to add all opera performers (often adding new artists to MB) from the cover and then suddenly some editor decides to remove them because “there’s too many artists” (as I once saw on edit note removing data added by me). I personally hate to see people removing data added by other editors. Sometimes credited names are only composers and sometimes only performers. Credits from spine are quite useless when many releases don’t even include performers on spines. I feel there’s exactly same situation like with front cover: there’s no logic which names label has decided to include. I don’t support adding new fields or new relationships for storing credits from spine or back cover. Both at least for me are lesser problems than making it harder to find and identify releases. What I have now understood is that we got “it’s a problem for my tagging” or “it doesn’t look nice” as a reason to consider it. As for composers/artists, SongKong is on the right track "normalizing" the names.I could understand limiting the amount of artist listed on artist credits if there would be good arguments for it. and even the orchestra: Wiener Philharmoniker-> Vienna Philharmonic, Harmonie českých filharmoniků ->Czech Philharmonic Orchestra. as well as the key: C-mol, -> C Minor, G-dur -> G, etc. It would operate on the music "form" Sonate->Sonata, Violinkonzert->Violin Concerto, etc. ) Similarly would really help having a search and replace capability. Manual overrides much needed and could use some extra support in the "spreadsheet-style" editing (such as replicating the current column (currently only supports replicating the first row. Reason: easier to delete the album from the intermediate folder and re-start the process. I'm spending a lot of time doing these "manual tweaks" and find it's easier to update my new iTunes library on an album by album basis from my existing iTunes library, going through an intermediate folder, before doing the move the the new iTunes "automatically add to iTunes" folder. With the classical albums, the "work and movement" support really helps - I often have to do "manual tweaks", but SongKong does do a lot of the "information gathering and presentation" from the on-line databases. really helps when navigating my music library in iTunes. Providing consistency in the filename, conductor, composer, artist, etc. If the tracks are a decent quality and the release is in the Musicbrainz or Discogs database, Jaikoz will correctly tag the tracks with an over 99% accuracy.Ī very useful tool in organizing my 1000+ albums (mostly Classical). Overall the accuracy is very good though. (I'm running Jaikoz on a server with 2 CPU, 8 core each, 64GB of memory Windows Server 2019 standard, 4 OCZ Vertex 4 250Gb SSD and 500Mbit internet connection). Also memory use frequently exceeds 12GB when a larger collection is loaded. Any larger than this and the GUI gets sluggish and so once in a while just stops responding all together for a few seconds. Though Jaikoz looks fairly professional, some file handling and database optimization really needs to be done for collections of over 100k tracks locally on SSD, or about 50k when this collection resides on external storage like a NAS. MP3tag is a lot faster with Musicbrainz, though not with Discogs. Also the update from Musicbrainz is terribly slow most of the time, though I strongly suspect this is the Musicbrainz API most of the time and not necessarily Jaikoz. You have to go through every release one by one and check these by release if you want metadata updated or added. What disturbs me a little is that the automatic correction does not update metadata when there is already some basic data there. The overall ease of use and layout is petty good. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |