First off, I love your software.
However, the list of matching albums using Tag Sources like MusicBrainz, is often quite long to choose from. I know all my CDs are US versions, and I usually have all the songs on a give CD.
I assume that when i'm searching Tag Sources by Artist and Album, that Mp3tag is generating the score.
Is there any way you can add a feature to tweak that score a little? Like increase a score if a listing has matching fields, like Country Code, number of tracks (based upon number selected), or format (e.g. CD).
Currently, I sort by Country Code then Tracks and then go to the section that has those matching criteria. But given the criteria that I know i'm looking for, there really should only be 1 or 2 albums that get 100% score.
I don't think that Mp3tag is generating this score.
If you refer to this score
then it will be returned from the search server of the source itself: MusicBrainz.
This score will be builded with the given information.
What you can try is to use one of the "MusicBrainz expanded" scripts where you can search more specifically for ASIN, Barcode, Catalog Number or even directly by MB Album ID
It is not.
The Score column is populated with values returned by MusicBrainz API. You can find more info about this field in this MusicBrainz documentation page.
Currently we can only use max. 3 search fields for Web Sources Scripts in Mp3tag.
If you use the "MusicBrainz expanded" version with "Search by Artist + Album" I could try to add 1 more search criterion.
What would be the value that reduces the number of search results the most?
Is that the number of tracks of your local album (based upon number selected)?
Or is that the media format, like "CD"?
Or is that the (release-) country, like "US"?
@rboss Yes, the MusicBrainz SOLR-Search Server returns the values visible in the list of search results, including the value in the second column Score.
According to some developer answers at MusicBrainz, this score is calculated by the underlaying Apache Lucene code and some pretty complicated formulas like Similarity and Score Boosting and some Algorithms weighting, filtering and sorting the result for the given search parameters.
my apologies. I didn't see the score column when doing a search directly on the MB side, so i made a poor assumption.
Blockquote
What would be the value that reduces the number of search results the most?
I think any would be fine. Whatever you think would be the most helpful to the most users? For me, # of tracks would be the most helpful since it gets rid of all the EPs or completely wrong items. However I can see some users wanting other ones, so i'm certainly not set on it.
I have created a variant of the existing "Search by Artist + Album" WSS with a 3rd search field. The number of selected files will be provided (and can be overwritten manually).
The MusicBrainz search now looks for releases with the given ARTIST, ALBUM and number of tracks and only returns results that match this number.
This should also work for releases with more than 1 disc. For example, if you are looking for a release with 14 tracks on the first disc and 10 tracks on the second disc, this search should return matching releases with 24 tracks.
MusicBrainz expanded#Search by Artist + Album + Tracks.src (2,8 KB)
-> Hint: You also need at least the files MusicBrainz expanded.inc and MusicBrainz expanded#Settings.settings from my collection of "MusicBrainz expanded" Web Sources scripts.
Please test it and let me know if it works for you as expected.
I will add this variant later (after your feedback) to my collection.
Works great! thank you so much.
It's a lovely addition if you want to find/match exactly the release that you have.
However I sometimes find out that there is a better release with bonus tracks available while scrolling through the musicbrainz results while tagging, which I then hunt down and upgrade what I had. These "fortunate surprises" are lost by matching exactly. It's good to have it as an option tho.