I am having a DB conflict by a Release and I am unsure how to solve it or where the error is. Maybe s.o. with more experience want to help or guide?
2020-07-04 18641, 2020
rdswift
Camini, please provide more information. Link to the release, what you're trying to do, and what isn't working.
2020-07-04 18625, 2020
Camini
Hey rdswift :) . Its about release group: https://musicbrainz.org/release-group/acdc6a25-03…. I own the disc with barcode: 8715197003025 but it was not in the DB. And the NL and US Version do have the same Barcode 067003031424 . So I imported it as another release on this group. Finaly i wanted to add the disc ID. And from
2020-07-04 18625, 2020
Camini
picard it pointed to 067003031424 (missmatching the code on my CD Case)
2020-07-04 18606, 2020
rdswift
To confirm, you have tagged your files and then created a new release, and now want to attach your disc ids to the new release?
2020-07-04 18619, 2020
Camini
i tagged it in picard and found that there was a NL Release but having not the barcode on my disc. then i searched for it and read through the existing NL DB entry (where i saw that the barcode was duplicated (NL and US). Then I found on discogs a release with the same barcode I have on my CD. So I thought there are 2 versions from NL. Imported it
2020-07-04 18619, 2020
Camini
and in the end though i add the Disc ID to it which then lead me to the conflict that its not matching between the physical Disk and the one on the jewel case
2020-07-04 18618, 2020
rdswift
So you think you attached your disc id to the wrong release?
2020-07-04 18627, 2020
upperechelon has quit
2020-07-04 18612, 2020
Camini
I thought maybe the discID is connected to the wrong barcode in the DB. But when i read my disc in Picard it points to barcode 067003031424 while i do have a barcode on my case with 8715197003025 .
On the line showing the incorrect release, click on the "Move" link. Then search for and select the release you entered, and it should then be applied to that release.
2020-07-04 18643, 2020
Camini
ok then one question. when i use picard and say read disc (for the id). The Barcode line is from the physical disk or is it looking it up in the MB database?
2020-07-04 18642, 2020
rdswift
When you do a disc lookup, it finds items in the database that have the matching id attached. If your release isn't in the list, you can lookup in your browser and attach your id to the correct release (with the option of entering a new release if necessary).
ok now I understand. "a list of matching releases will be displayed." so its not from the disc and points to a DB error (what I first thought by the duplicated Barcodes). So I will attach both IDs to the entry I made (but stil have the feeling that the existing NL Version just has errors)
2020-07-04 18657, 2020
killmePI has quit
2020-07-04 18633, 2020
Camini
and thanks again for your help. Its funny - its again you to help me (after the questions regarding your script)
2020-07-04 18630, 2020
rdswift
Glad to help where I can. Actually, this conversation is prompting me to add a section to the documentation about how to attach disc ids to a release (step-by-step with pictures). That might help others in the future. Thanks.
2020-07-04 18620, 2020
upperechelon has quit
2020-07-04 18622, 2020
Camini
cool, glad to help too. and I am just at the very beginning in learning at mb, database and the connection to picard, but its so much better for tagging and bringing all files to one good structure (and that massivly by big support of your script)
2020-07-04 18650, 2020
upperechelon joined the channel
2020-07-04 18621, 2020
Camini
so thanks again and stay healthy in such a challenging time atm.
hmm. here's an interesting one: in radio we apparently *often* get partial digital promotional copies (sometimes of things that have not been released, but aren't released as a "single"). For example, for https://musicbrainz.org/release/c134b782-7c81-431… I only have tracks 9 and 10. Does this qualify as a release?
2020-07-04 18654, 2020
echarlie
(and of course, it may have a different effective release date, but I'm not tracking that down for a lot of these; I'm not the MD)
probably 2/3rds of the releases I've added this month have been promotional, unless it was a straight import from bandcamp or whatever.
2020-07-04 18647, 2020
rdswift
👍
2020-07-04 18610, 2020
echarlie
it's very time-consuming. Labels are also really bad about setting metadata in their own digital releases (I'm lucky if they set ISRC; usually they set a shortened title, correctly set album and artist, and don't set label), which is why I'm going through this at all.
2020-07-04 18642, 2020
echarlie
'cos they don't give me enough info in their own metadata to play it on-air.
2020-07-04 18626, 2020
chaban
Just spotted an editor who learned the hard way that a photo they've uploaded contained EXIF location data and due to MBS-4753 they can't easily undo this mistake.
