#musicbrainz

/

      • petitminion has quit
      • kepstinbrainz joined the channel
      • kepstinbrainz
        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?
      • Jigen joined the channel
      • LupinIII has quit
      • sennoide joined the channel
      • scrumplex has quit
      • scrumplex joined the channel
      • sennoide has quit
      • LupinIII joined the channel
      • Jigen has quit
      • ApeKattQuest joined the channel
      • ApeKattQuest has quit
      • ApeKattQuest joined the channel
      • fwa joined the channel
      • fwa
        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)
      • how do I make the software match my directory scan with that release, if you got any clue ?
      • crism
        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?
      • fwa
        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
      • crism
        What, exactly, are you doing in Picard? What, exactly, does Picard do when you do that?
      • fwa
      • 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...
      • crism
        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.
      • fwa
        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
      • 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.
      • dascandy[m]
        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
      • m1gr has quit
      • Island_ has quit
      • tagomago joined the channel
      • m1gr joined the channel
      • hamsung[m] joined the channel
      • 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-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!
      • 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
      • * 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
      • petitminion joined the channel
      • applecuckoo[m_c] joined the channel
      • 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
      • sennoide joined the channel
      • applecuckoo[m_c]: so yeah, that's probably a mainland China release and not a Hong Kong release
      • petitminion has quit
      • crazyroostereye joined the channel
      • dascandy[m]
        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
      • sennoide has quit
      • crazyroostereye has quit
      • crazyroostereye joined the channel
      • Aerozol[m]1 has quit
      • Jormangeud joined the channel
      • crazyroostereye has quit
      • crazyroostereye joined the channel
      • crazyroostereye has quit
      • otisolsen70 joined the channel
      • Maxr1998_ joined the channel
      • Maxr1998 has quit
      • cloverfield joined the channel
      • sennoide joined the channel
      • thuna` joined the channel
      • 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.
      • thuna` has quit
      • crism has quit
      • sennoide has quit
      • julian45[m] has quit
      • otisolsen70 has quit
      • AJ_Z0 has quit
      • 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
      • 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 🤷
      • sennoide joined the channel
      • 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
      • AJ_Z0 joined the channel
      • crazyroostereye joined the channel
      • AJ_Z0 has quit
      • sennoide has quit
      • AJ_Z0 joined the channel
      • AJC_Z0 joined the channel
      • AJ_Z0 has quit
      • AJC_Z0 is now known as AJ_Z0
      • Island_ joined the channel
      • AJ_Z0 has quit
      • AJ_Z0 joined the channel
      • ridge[m] has quit
      • sanojjonas[m] has quit
      • krei-se- has quit
      • krei-se joined the channel