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.
2025-05-06 12605, 2025
kepstinbrainz
hmm, maybe not 2 disc
2025-05-06 12611, 2025
kepstinbrainz
either way, australian :/
2025-05-06 12657, 2025
kepstinbrainz
oh, i'm just confused, apparently they used that number in multiple countries possibly with different formatting
2025-05-06 12606, 2025
kepstinbrainz
actually, that might be a legit hong kong release?
2025-05-06 12646, 2025
Jigen joined the channel
2025-05-06 12621, 2025
LupinIII has quit
2025-05-06 12644, 2025
sennoide joined the channel
2025-05-06 12645, 2025
scrumplex has quit
2025-05-06 12626, 2025
scrumplex joined the channel
2025-05-06 12643, 2025
sennoide has quit
2025-05-06 12619, 2025
LupinIII joined the channel
2025-05-06 12658, 2025
Jigen has quit
2025-05-06 12615, 2025
ApeKattQuest joined the channel
2025-05-06 12616, 2025
ApeKattQuest has quit
2025-05-06 12616, 2025
ApeKattQuest joined the channel
2025-05-06 12651, 2025
fwa joined the channel
2025-05-06 12637, 2025
fwa
hey everyone
2025-05-06 12606, 2025
fwa
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)
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.
2025-05-06 12647, 2025
fwa
oh yes, works like a charm, and i have a better understanding on how the software works now
i'll have a very good time tagging and contributing anyway =)
2025-05-06 12622, 2025
fwa
tyvm crism
2025-05-06 12656, 2025
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.
2025-05-06 12616, 2025
dascandy[m]
yes, iirc not listed. Will doublecheck looking for China and HK. Iirc hk rejoined China in '99?
2025-05-06 12610, 2025
dascandy[m]
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.
2025-05-06 12637, 2025
dascandy[m]
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
2025-05-06 12634, 2025
m1gr has quit
2025-05-06 12625, 2025
Island_ has quit
2025-05-06 12630, 2025
tagomago joined the channel
2025-05-06 12608, 2025
m1gr joined the channel
2025-05-06 12604, 2025
hamsung[m] joined the channel
2025-05-06 12604, 2025
hamsung[m]
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-4dd… 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
2025-05-06 12604, 2025
hamsung[m]
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
2025-05-06 12604, 2025
hamsung[m]
sorted in cases like that. Thanks!
2025-05-06 12659, 2025
rinsuki[m]
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
2025-05-06 12657, 2025
rinsuki[m]
* 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
2025-05-06 12609, 2025
petitminion joined the channel
2025-05-06 12630, 2025
applecuckoo[m_c] joined the channel
2025-05-06 12630, 2025
applecuckoo[m_c]
<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
2025-05-06 12621, 2025
sennoide joined the channel
2025-05-06 12648, 2025
applecuckoo[m_c]
applecuckoo[m_c]: so yeah, that's probably a mainland China release and not a Hong Kong release
2025-05-06 12624, 2025
petitminion has quit
2025-05-06 12643, 2025
crazyroostereye joined the channel
2025-05-06 12624, 2025
dascandy[m]
thanks, will file it in Discogs as a Chinese release. I'm in Europe so not in any position to confirm
2025-05-06 12650, 2025
dascandy[m]
I thought it could have been an early HK release since it does look to match most of what that release says
2025-05-06 12614, 2025
sennoide has quit
2025-05-06 12604, 2025
crazyroostereye has quit
2025-05-06 12624, 2025
crazyroostereye joined the channel
2025-05-06 12650, 2025
Aerozol[m]1 has quit
2025-05-06 12603, 2025
Jormangeud joined the channel
2025-05-06 12615, 2025
crazyroostereye has quit
2025-05-06 12602, 2025
crazyroostereye joined the channel
2025-05-06 12656, 2025
crazyroostereye has quit
2025-05-06 12644, 2025
otisolsen70 joined the channel
2025-05-06 12621, 2025
Maxr1998_ joined the channel
2025-05-06 12643, 2025
Maxr1998 has quit
2025-05-06 12636, 2025
cloverfield joined the channel
2025-05-06 12607, 2025
sennoide joined the channel
2025-05-06 12649, 2025
thuna` joined the channel
2025-05-06 12601, 2025
BobSwift[m]
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.
2025-05-06 12613, 2025
thuna` has quit
2025-05-06 12603, 2025
crism has quit
2025-05-06 12610, 2025
sennoide has quit
2025-05-06 12622, 2025
julian45[m] has quit
2025-05-06 12656, 2025
otisolsen70 has quit
2025-05-06 12655, 2025
AJ_Z0 has quit
2025-05-06 12644, 2025
zoedivision[m]
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
2025-05-06 12624, 2025
zoedivision[m]
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 🤷
2025-05-06 12631, 2025
sennoide joined the channel
2025-05-06 12628, 2025
zoedivision[m]
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
2025-05-06 12601, 2025
AJ_Z0 joined the channel
2025-05-06 12640, 2025
crazyroostereye joined the channel
2025-05-06 12609, 2025
AJ_Z0 has quit
2025-05-06 12618, 2025
sennoide has quit
2025-05-06 12639, 2025
AJ_Z0 joined the channel
2025-05-06 12610, 2025
AJC_Z0 joined the channel
2025-05-06 12619, 2025
AJ_Z0 has quit
2025-05-06 12619, 2025
AJC_Z0 is now known as AJ_Z0
2025-05-06 12643, 2025
Island_ joined the channel
2025-05-06 12633, 2025
AJ_Z0 has quit
2025-05-06 12629, 2025
AJ_Z0 joined the channel
2025-05-06 12602, 2025
ridge[m] has quit
2025-05-06 12643, 2025
sanojjonas[m] has quit
2025-05-06 12640, 2025
krei-se- has quit
2025-05-06 12633, 2025
krei-se joined the channel
2025-05-06 12627, 2025
sennoide joined the channel
2025-05-06 12657, 2025
UltraFuzzy joined the channel
2025-05-06 12653, 2025
sennoide has quit
2025-05-06 12645, 2025
UltraFuzzy
Hey folks.
2025-05-06 12633, 2025
scrumplex has quit
2025-05-06 12617, 2025
BlastboomStrice[
ayo
2025-05-06 12641, 2025
chrisw83 joined the channel
2025-05-06 12659, 2025
sennoide joined the channel
2025-05-06 12633, 2025
UltraFuzzy
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?
2025-05-06 12651, 2025
chrisw83 has quit
2025-05-06 12635, 2025
sennoide has quit
2025-05-06 12623, 2025
BobSwift[m]
Should be the same information in both.
2025-05-06 12626, 2025
BobSwift[m]
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.
2025-05-06 12654, 2025
UltraFuzzy
I haven't done anything to commit myself yet.
2025-05-06 12605, 2025
rinsuki[m]
I think with CD lookup Picard will reads MCN but ripper log doesn't
2025-05-06 12606, 2025
rinsuki[m]
^ well actually Picard reads MCN but it seems not using MCN for lookup (sry)
2025-05-06 12639, 2025
crazyroostereye has quit
2025-05-06 12636, 2025
UltraFuzzy
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.
2025-05-06 12659, 2025
rinsuki[m]
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
2025-05-06 12652, 2025
UltraFuzzy
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'll check that out. If I want to use Python, what's the brief high-level outline of the approach? Who calls into who?
2025-05-06 12650, 2025
UltraFuzzy
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?
2025-05-06 12648, 2025
rinsuki[m]
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.
2025-05-06 12659, 2025
UltraFuzzy
This was lots of very useful info. Thanks!
2025-05-06 12605, 2025
rinsuki[m]
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)
2025-05-06 12607, 2025
UltraFuzzy
wait, I can't figure out what "D&D" means in that context and now I can't let it go, please help
2025-05-06 12608, 2025
rinsuki[m]
just drag and drop, from Finder to Picard's GUI window
2025-05-06 12619, 2025
UltraFuzzy
oh X-P
2025-05-06 12617, 2025
UltraFuzzy
Well if I end up getting everything glued together nicely myself then maybe I'll come back and we can compare notes. 😉
