Welcome Guest

Pages: 1 2
Crash
tlcPostFebruary 11, 2015, 23:23
Newbie
Posts: 20
Registered:
February 4, 2015, 21:34
Hot topicRe: Crash

deleted -- i'll look into it

2MR2PostFebruary 11, 2015, 23:27
Administrator
Posts: 1642
Registered:
August 23, 2012, 19:27
Hot topicRe: Crash

It's doing that because you already have a release id. It's a quick way of getting back at the associated release once found. Hit 'New Search' when the wizard starts ... or you can delete the MusicBrainz Release Id manually.

tlcPostFebruary 12, 2015, 00:24
Newbie
Posts: 20
Registered:
February 4, 2015, 21:34
Hot topicRe: Crash

OK. I'm seeing something I can't explain in the MB website.

Looking in the MB website with the IDs from the first track I sent you
comment[5]: MUSICBRAINZ_TRACKID=854f4fde-1e96-4620-8148-c6e3c42f4489
comment[7]: MUSICBRAINZ_ALBUMID=27a34c0d-cb38-4c3a-8a16-92bc9f18d7a4

You're right that the ALBUMID
http://musicbrainz.org/release/27a34c0d-cb38-4c3a-8a16-92bc9f18d7a4

doesn't seem to point to the TRACKID. The corresponding track (#1 of CD 2) points at

http://musicbrainz.org/recording/a5709b3c-f5dd-4ae5-aa1b-7e0228c2e1ae

BUT, my TRACKID

http://musicbrainz.org/recording/854f4fde-1e96-4620-8148-c6e3c42f4489

does point back to the ALBUMID.

In fact, look at my track again

http://musicbrainz.org/recording/854f4fde-1e96-4620-8148-c6e3c42f4489

Select the "Fingerprints" tab and notice that the URL changed to the other TRACKID !
You can even select the "Overview" tab and it stays on the other URL/TRACKID !

2MR2PostFebruary 12, 2015, 08:07
Administrator
Posts: 1642
Registered:
August 23, 2012, 19:27
Hot topicRe: Crash

There seems to be a mixup in some releases between track ids (recoding within release) and recording ids. ie. they may be flipped. I should be able to get around this problem by matching either. I currently attempt to match both but I don't cross check. I'll look into it more today.

tlcPostFebruary 12, 2015, 09:54
Newbie
Posts: 20
Registered:
February 4, 2015, 21:34
Hot topicRe: Crash

Is there any sort of alias relationship for tracks in MB?
I know they have aliases on other entities.

I wonder if this could be because I ripped the CDs at least 14 months ago.
Do track entries get merged over time in the MB db?

Thanks!
I'm buying a license today.

2MR2PostFebruary 12, 2015, 12:05
Administrator
Posts: 1642
Registered:
August 23, 2012, 19:27
Hot topicRe: Crash

Not that I know of. I think its simply a case of the database being so large (good!) and that it sometimes causes inconsistencies.

I'm not sure how your originally populated the metadata but it is possible that the application was looking up tracks as opposed to releases. That method causes madness. When loading the metadata associated with a release, the XML stream contains tracks which contain recoding ids and release track ids. We support both and require at least one to match when batch processing. The release track ids which are not directly searchable on the MB site are essentially a recording id unique to the release. This data is all we have to go on. Now there are many cases where there are multiple recording ids for the same recording. Your Billy Joel tracks have references to recording ids which are not referenced when we get the release stream and they do not contain release track ids. So, they may be valid recording ids but there is no reference from the release to them. I've tried cross searching on the two id types and it doesn't help because they are correct in the stream, they're just not the ones you have.

As far as merging entities.... I would assume that inconsistencies get cleaned up from time to time. Thats one of the reasons we support an 'Import Time' for Discogs and MusicBrainz. It enables you to at least know when the data was imported so that you can write an action to test every month, six months or years to see if the remote data has changed. As long as you're importing both the track id fields you should be ok. If the recording id changes at least the release track id won't. (I've never seen it).

I will be trying again in 3.4 to standardize the descriptive names for the fields. The issue is that MB has descriptive names and internal names and that some users know and use both. We're changing the descriptive name for Track Id to Recording Id and the descriptive name for Track Position Id to Track Id. None of your settings will change as its only a descriptive name. Hopefully this is a better fit. (Not in the patch build).

Welcome to the fold 🙂

Pages: 1 2
Mingle Forum by Cartpauj | Version: 1.1.0beta | Page loaded in: 0.075 seconds.