The “Year” field gets populated with exact dates of release e.g. 2006-03-31 when these exist in the MusicBrainz database.
This unfortunately confuses some applications that expect to find only a year in that field; my mp3 player has been informing me that some of my tracks will be released in 3016… talk about pre-release demo! :lol:
I would like to have an option in preferences to only allow the year to be entered in that field. Possibly even a similar autocorrecter option.
Ok, a very simialr issue has already been added to the todo list
Shameless bump :roll:
(it hasn’t made it into the forthcoming enhancements, features and minor improvements lists yet)
Youre right that this should be addressed, I will look into it in the next few days.
This option has been added in Jaikoz 2.5.0
Thanks Paul, I’ve tried it and it works great.
I’ve got it selected to only show the year, but I’m still getting the full date in a lot of entries.
(I’ve also got the “earliest release” selected but I continue to get the year of whatever compilation or reissue it feels like–maybe my preferences just aren’t sticking for some reason.)
[quote=bink]I’ve got it selected to only show the year, but I’m still getting the full date in a lot of entries.
[/quote]
This option is only used by Action/Local Correct/Correct Year, doesnt effect what is fixed from Musicbrainz. So you just need to run Correct Year
[quote=bink]
(I’ve also got the “earliest release” selected but I continue to get the year of whatever compilation or reissue it feels like–maybe my preferences just aren’t sticking for some reason.)[/quote]
A ‘release’ in Musicbrainz is a particular set of Songs, then there can be a release event for every Country that the release is released in, this is what Preferences/Musicbrainz/AutoFormat/When selecting country and year of release is for.
If an album is released with different/extra tracks then it is a new release but this particular option does not effect what release is selected.
So why aren’t you getting the earliest release, lets consider some of the reasons.
Maybe you don’t have the original release but a reissue with additional tracks. For example if you have 11 tracks, the original album only had 8 and then 3 were added to a reissue your tracks are going to get a better score on matching the reissue because the total no of tracks match.
Maybe your tracks came from a compilation album, and the compilation album is set in your album field, in this case its going to give a better score to the compilation album (everything else being equal. Delete the album field before matching to prevent it favouring a compilation.
Maybe your match is based on a Puid, and then Puid is currently only linked to the reissued track. You can help here by linking to the correct track and using Submit Musicbarinz/Puid Pairs to create a link to the original release.
When I run local correct years I get this back in the console:
Nov 16, 2010 8:38:12 PM: INFO: Started correct recording times on 3,297 song
Nov 16, 2010 8:38:12 PM: INFO: Completed correct recording times on 3,297 songs
What is it actually doing?
Thanks for your hard work on this program!
Fran Mc
Not much, removing any values in the year field that are not dates
I was confused by the term “recording times” and thought it meant length of time of the recording. But it means date of the recording, right?
Consistent words in command and response avoid confusion.
Yes, your right ‘Recording time’ is a hangover from the original ID3 field name, it should be changed.