#musicbrainz

tbh, i'd suspect a bootleg. note that the number printed on the sticker - 9362473862 - is the catalog number/barcode of the 2 disk austrialian release.

hmm, maybe not 2 disc

either way, australian :/

oh, i'm just confused, apparently they used that number in multiple countries possibly with different formatting

actually, that might be a legit hong kong release?

hey everyone

i'm a noob to the tagging world, musicbrainz picard is such a nice tool. I had a soundtrack to the musicbrainz website database, but scanning my albums still not getting the right infos yet (sorry for my english)

here is my release https://musicbrainz.org/release/84a66cfb-3b68-4...

how do I make the software match my directory scan with that release, if you got any clue ?

dascandy[m]: Have you looked on Discogs for the release?

fwa: What, exactly, are you doing? What, exactly, is happening, and how, exactly, does it differ from what you expect?

crism: i want to tag my local directory containing a rip of a cd of 19 titles with the corresponding release I just publish on musicbrainz website

crism: but when i scan my directory using musicbrainz picard, the track fetched aren't matching

What, exactly, are you doing in Picard? What, exactly, does Picard do when you do that?

crism: https://ibb.co/8L2VqBHJ

i just select them all and click on "analyze"

the result i was expecting is getting all of them, not some of them, and all from my release https://musicbrainz.org/release/84a66cfb-3b68-4...

Ah, en français… Try « Rechercher dans le navigateur » instead. Select the release you want in your browser, and then the « tagger » link there. It should open the release on the right-hand half of Picard, and then you can drag your files to the release.

oh yes, works like a charm, and i have a better understanding on how the software works now

thanks

can you enlight me about the "duplicate lines" ? https://ibb.co/PZHVchdp

i'll have a very good time tagging and contributing anyway =)

tyvm crism

Pas de problème. I’m not sure about those duplicates… I haven’t seen that before. Looks like either files that matched the same track, maybe? But if it comes out OK, then ça suffit.

yes, iirc not listed. Will doublecheck looking for China and HK. Iirc hk rejoined China in '99?

checked, there are no listed releases in China, but there is a HK one - labeled as "Printed in Hong Kong. Manufactured and Distributed by Warner Music Hong Kong. " - except mine says "Manufactured in Germany", so it's definitely not that one.

can somebody who's familiar with Chinese and/or Kantonese tell me whether the label above is likely HK or China? I'd guess China, but Californication has so many releases that it could well be a second HK release from the same year

GREETINGS!!! I am insanely new to this and was just looking to improve documentation around a few albums I saw were missing data. I'm curious as to the best way to find and cite track lengths on releases. I'm looking at https://musicbrainz.org/release/3e8e83ee-76c2-4... right now. I have the HEDO-006 release and the track lengths are 0:46.307, 3:28.253, 4:00.280, 2:23.293, 4:45.093, and 3:14.720. Since this is the

actual quoted release, I'm assuming these rounded down to the nearest second are what should be input but how would this be cited? I was also curious because Spotify agrees with these numbers but Qobuz thinks tracks 5 and 6 are 1 second shorter than the release I have. With this being a web release, I imagine this is entirely irrelevant to the release I'm looking at, but I was also curious how discrepancies in track length are

sorted in cases like that. Thanks!

AFAIK, If you have a original CD, most good (and easy) way is add the Disc ID (using MusicBrainz Picard or something) to release and click "Set track lengths" link and submit edit (if link isn't appear after add disc id, length data is already (automatically) applied). I don't know about how can we submit digital release's millisecond length, but at least someone on here know it

* AFAIK, If you have a original CD, most good (and easy) way is add the Disc ID (using MusicBrainz Picard or something) to release and click "Set track lengths" link and submit edit (if link isn't appear after add disc id, length data is already (automatically) applied). I don't know about how we can submit digital release's millisecond length, but at least someone on here know it

<dascandy[m]> "can somebody who's familiar with..." <- that looks to me like simplified Chinese which is only used on the mainland, Hong Kong, Macau and Taiwan all use traditional which is not what's on the label

applecuckoo[m_c]: so yeah, that's probably a mainland China release and not a Hong Kong release

thanks, will file it in Discogs as a Chinese release. I'm in Europe so not in any position to confirm

I thought it could have been an early HK release since it does look to match most of what that release says

fwa (IRC): You might also consider checking out the Picard User Guide https://picard-docs.musicbrainz.org which has a section on workflows that may help.

anyone ever come across ISRC mis-matches that make no sense at all? for this release group:

the streaming ISRCs all start with USL4Q (makes sense, US band & US label), BUT the (official) CD-R I just got has all the ISRCs starting with QMAAK

It looks like QM is valid as well, but it seems quite odd to me to see different ones for what I *believe* is a concurrent release...... I haven't given the release a listen yet to compare whether or not the recordings are the same, but I don't have any reason yet to believe they're different 🤷

so I did just try out one of the QMAAK ISRCs on isrcsearch.ifpi.org and it doesn't return a hit, while the US4LQ code does

Hey folks.

ayo

I'm figuring out my workflow for ripping a bunch of CDs with XLD + MusicBrainz. In Picard, is lookup by CD vs ripper log functionally identical? Or does the CD have some sort of additional data?

Should be the same information in both.

If you still have the CD in the drive, you can use the CD lookup, but if you've moved on you can use the rip log.

I haven't done anything to commit myself yet.

I think with CD lookup Picard will reads MCN but ripper log doesn't

^ well actually Picard reads MCN but it seems not using MCN for lookup (sry)

Awesome. Thanks for checking. What I'm thinking is that it makes the most sense to just rip one CD after another without bothering awkwardly struggling to get XLD to do a first draft of the naming and tagging - just dump all the data that's there to work with to uniquely named directories, each full of 'Track 01', Track 02', etc., and then do the naming and tagging once with the full power of Picard and when I can look at the disc if need be.

btw: I'll recommend you to set XLD to include MCN and ISRC to your ripped file name, since XLD will not write these info to tags and/or ripper log (maybe does to cue sheet, but I didn't tried it). which may helps you later

Ok, I'll check. But those don't end up in the tags and I have to stash them in the filenames or elsewhere, what's the trick for feeding that back into Picard?

I'm using private python scripts to do that, but I think you can do it by something like https://picard-docs.musicbrainz.org/en/usage/ta... (not tried though)

I'll check that out. If I want to use Python, what's the brief high-level outline of the approach? Who calls into who?

e.g. feed into Picard via command line, somehow call into Picard as a library, somewhere Picard will let me call out to external programs?

in my case, I'm running python scripts manually, after that day's ripping jobs are all done. my python scripts reads every ripping logs and modify their tags by https://pypi.org/project/mutagen/ (which is also used by Picard so I can trust them), then I manually feed audio files (by D&D :P) to Picard.

This was lots of very useful info. Thanks!

off-topic: I think i should polish and publish my python scripts... (since its very optimized to my workflow, its not suitable for anyone other than me by as-is, but it should be able to use as a reference)

wait, I can't figure out what "D&D" means in that context and now I can't let it go, please help

just drag and drop, from Finder to Picard's GUI window

oh X-P

Well if I end up getting everything glued together nicely myself then maybe I'll come back and we can compare notes. 😉