-
I'm using Jaikoz to pre-fill my album tag data before importing and cleaning in MC. One of the tags being written is the Discogs URL into a WXXX tag. Tag editors show the data as, eg
undefined url link: DISCOGS_RELEASE 'https://www.discogs.com/release/1666691'
Any way I can import this data into MC? Haven't found a solution yet...
-
If you know the name of the tag, you can add it to MC. Case must match. See the wiki.
Please post it here if you find it.
-
Thanks, Jim. I did try that but doesn't work - or as far as I can see. The tag is above 'DISCOGS_URL'. I added that to my library and updated tags from file, but no joy...
-
In MC select a track that has that tag/metadata in it and in the Modern Tag Window scroll down to the Tag Dump section and look in that section to see if you can spot the metadata you think should be there. If it is there the line it appears on will have the name that tag is using - that's the name you have to assign to the tag/field you add to MC.
-
WXXX: <unknown data type>
-
Is that what is showing in the Tag Dump? Because if it is the field has been set to the wrong data type in whatever software you used to add it.
-
You can try creating a field called WXXX.
However, this seems to be a structured field with 2 strings separated by a NUL (0x00) character - It's likely MC cannot handle it without some explicit support for it (at least for editing/changing it, maybe it's able to read it):
https://id3.org/id3v2.3.0#User_defined_URL_link_frame
User defined URL link frame
This frame is intended for URL links concerning the audiofile in a similar way to the other "W"-frames. The frame body consists of a description of the string, represented as a terminated string, followed by the actual URL. The URL is always encoded with ISO-8859-1. There may be more than one "WXXX" frame in each tag, but only one with the same description.
In this case, the description part would be "DISCOGS_RELEASE" and the URL part is the link.
-
Is that what is showing in the Tag Dump? Because if it is the field has been set to the wrong data type in whatever software you used to add it.
That is what is appearing in Tag Dump, yes. Exploring the id3 tags with other software, eg windows native viewer and the tag is correct, so I suspect this may be an issue with MC...
-
You can try creating a field called WXXX.
Thanks, tried, but that didn't work either. Just an empty field called WXXX.
-
WXXX: <unknown data type>
Yeah, probably requires explicit MC support.
-
Thanks all for the input.
-
Thanks, Jim. I did try that but doesn't work - or as far as I can see. The tag is above 'DISCOGS_URL'. I added that to my library and updated tags from file, but no joy...
Without the single quotes? DISCOGS_URL
-
Yep, as in tried that - no joy.
-
To import some outside fields you can use foobar2000. I do the same thing when comes to add some fields from other software. It adds some extra work, but it will help you having those fields in MC.
-
Thanks. I'm trying to avoid any extra steps by directly importing tags. If the direct import doesn't work, as seems to be the case with WXXX currently, then I'll manually add the data within MC, which is what I'm doing right now - that manual work becomes the "extra step".
-
WXXX tags were not being read properly, I've fixed the reading, but of course any custom fields are not mapped automatically, so the above suggestions still hold once the build is out. So let us know if it works then!
-
Awesome, will do! Thanks, Hendrik ;D
-
With the .21 update the various WXXX fields are now in the tag dump correctly showing, eg:
WXXX (DISCOGS_RELEASE): https://www...
But the data isn't finding its way to the user field of the same name. I've added
Discogs Release
DISCOGS_RELEASE
But both remain empty.
-
Parentheses?
-
That's just the way MC displays the tags in the Tag Dump, same for the other tags which do import as expected, eg
TALB (Album): Colin Scot
ends up in Album field.
-
I can see why its happening, it only expects to map TXXX fields to custom fields, and would also write any custom field as TXXX. So while I could make it read it, if it were to write it back to the file it would convert it to TXXX, which seems undesirable. But we also don't keep any metadata which field would be what type..
I'll think about it for a bit.
-
What about... if the field contains a valid URL, save to WXXX ?
Valid URL would be a string starting with http/https/www.
-
Just looking at a podcast here it has
TXXX (Episode URL): https://...
That field should really be a WXXX then?
id3
4.3.2 WXXX [#WXXX User defined URL link frame]
It seems that WXXX should be treated functionally in the same way as TXXX, except that it's focus is on URLs and any user defined URLs should be written into WXXX. Apologies for adding work!