Jump to content

Music: YYYY-MM-DD in year tag? confused MB3


Recommended Posts

ginjaninja
Posted (edited)

Hi Luke

Version 3.0.5112.40848

 

 

For a while now i had been using Musicbrainz/Picard's value for Year which is in format YYYY-MM-DD in my music files/tags, which seemed ok.

 

I just noticed

 

for album with tags

album:Junip

artist:Junip

albumartist:Junip

year:2013-04-23

(File format FLAC)

 

was detected by MB3 as another album by the band Junip- Rope and Summit EP

2014-01-04 11:02:58.5066, Info, App, HttpClientManager GET: http://ws.audioscrobbler.com/2.0/?method=album.getInfo&mbid=ea3c0dec-fba5-38ec-bf58-8cee1119a88c&api_key=7b76553c3eb1d341d642755aecc40a33&format=json

junip.jpg

rather than (the correct)

MB3 release date:23/04/2013

MB3 year:2013

MB3 MBZID:e263e701-da41-4ea3-a73c-4636fafc1a1d

 

i deleted all the tags/mbzids using mb3 tag editor and changed the source files to year:2013 (on a suspicion that this was a problem)

A refresh in Mb3 resulted in the correct detection above.

 

ffprobe output from the original file (note the YYYY-MM-DD format)

Input #0, flac, from '01. Line of Fire.flac':
  Metadata:
    GENRE           : Indie
    ALBUM           : Junip
    TRACKTOTAL      : 10
    ALBUMARTISTSORT : Junip
    MUSICBRAINZ_ARTISTID: fb2df245-81b0-4a2b-9d01-e0955ba68be7
    ORIGINALDATE    : 2013-04-22
    SCRIPT          : Latn
    ARTIST          : Junip
    MEDIA           : Digital Media
    TOTALTRACKS     : 10
    ARTISTSORT      : Junip
    RELEASETYPE     : album
    RELEASECOUNTRY  : US
    MUSICBRAINZ_ALBUMID: e263e701-da41-4ea3-a73c-4636fafc1a1d
    RELEASESTATUS   : official
    TITLE           : Line of Fire
    album_artist    : Junip
    MUSICBRAINZ_ALBUMARTISTID: fb2df245-81b0-4a2b-9d01-e0955ba68be7
    DATE            : 2013-04-23
    track           : 1
    MUSICBRAINZ_TRACKID: 68a17820-f51e-48ca-9176-277c58037441
    MUSICBRAINZ_RELEASEGROUPID: ca788588-76a2-4a79-be4b-68f2550db4a2
  Duration: 00:05:39.29, bitrate: 969 kb/s
    Stream #0:0: Audio: flac, 44100 Hz, stereo, s16

.maybe it was the year format? maybe the self titled album maybe something else that upset MB3.

Maybe the log will lend weight

https://dl.dropboxusercontent.com/u/84611964/server-63524390400.log

Edited by ginjaninja
ginjaninja
Posted (edited)

thinking about it a bit more, given that mb3 now takes year from tags, it must be that the year format confused MB3 and is not currently supported? so Year was taken from the online providor for the wrong album?

I wonder why MB3/Musicbrainz api missed the entire match for the album in the first place.

 

For some reason the request (from log)

2014-01-04 11:02:57.5156, Info, App, HttpClientManager GET: http://www.musicbrainz.org/ws/2/release/?query="(2013)+Junip" and arid:fb2df245-81b0-4a2b-9d01-e0955ba68be7

prefers the completely incorrect match.

Edited by ginjaninja
ginjaninja
Posted (edited)

FWIW

http://www.musicbrainz.org/ws/2/release/?query=release:(2013)%20Junip%20AND%20arid:fb2df245-81b0-4a2b-9d01-e0955ba68be7

 

finds the correct album,

as does

http://www.musicbrainz.org/ws/2/release/?query=release:(2013)%20Junip%20AND%20arid:fb2df245-81b0-4a2b-9d01-e0955ba68be7%20%AND%20date:2013-04-23

even more specifically.

 

maybe when searching with multiple criteria, MBZ prefers all values to be prefixed (release and arid)

Edited by ginjaninja
ginjaninja
Posted (edited)

further troubleshooting suggests it isnt the year format that caused the problem; this was a red herring.

having recreated the original problem/symptom; After removing incorrect mbz ids and release dates from MB3 (but not changing the year tag value), saving and hitting refresh , the correct album was detected by mb3 with log entry

 

2014-01-04 15:59:10.0417, Info, App, HttpClientManager GET: http://www.musicbrainz.org/ws/2/release/?query="Junip" and arid:fb2df245-81b0-4a2b-9d01-e0955ba68be7

 

On initial album ingestion, (log in first post),  MB3 referenced what seemed like the filesystem parent folder in the mbz api search terms "(2013) Junip", but on this subsequent refresh MB3 referenced only tag? value "Junip"..which worked...is the inconsistency highlighting a potential improvement?

 

https://dl.dropboxusercontent.com/u/84611964/server-63524437749.log

Edited by ginjaninja

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...