AFAI can tell it does not make sense to map RELEASEDATE to RELEASEDATE (the same applies to most other fields with the same source and target).
Could you remove (at least) this mapping and see which fieldname you really get?
See e.g. this thread about Mapping
The field list is no reliable indicator that a field is a standard field as it fills up with all the field names that have been used before. You would have to reset the field list for a more reliable picture.
Okay, I think I understand. You want me to remove everything related to the RELEASEDATE field I created in Mp3tag, go back to DJAY PRO, enter a value in its Publicado field, and then return to Mp3tag, to the extended tags, to see which field DJAY PRO is actually filling, right? I really appreciate the help — you’re very quick! I just hope my translator and comprehension are as good. Thanks!
Okay, I did the test: I downloaded new FLAC tracks, not for any special reason, just to avoid working with copies. I deleted all the tag configurations in Mp3tag.
The new tracks came without RELEASEDATE but with YEAR in DD/MM/YYYY format (see the image). Then I imported these tracks into DJAY PRO, and it read the information without the “Publicado” field — for you, that would be RELEASEDATE.
Next, from DJAY, I added a date in D/M/YY format and reloaded the files in Mp3tag. Now, RELEASEDATE appears in Mp3tag in YYYY-MM-DD format.
Then I edited the RELEASEDATE metadata in Mp3tag to see if DJAY PRO would update it, but it didn’t. From what I’ve been able to find, there are already complaints about this — DJAY PRO doesn’t handle tags properly, or we don’t know which editors/tools to use to edit metadata, since some people say it’s better to use Apple Music (DJAY PRO is largely Apple-based).
With all that, I continued testing: I created the RELEASEDATE tag in Mp3tag so it appears as a column. Whenever I save (Command+S) in Mp3tag the modified data, then close and reopen DJAY PRO, it reads the tag correctly. The same happens with the MONTH field — TRACK for you and Mp3tag.
What I did notice is that YEAR, which in the original track is shown in DD/MM/YYYY format, is used by DJAY PRO only as YYYY in its field.
After all this, I now know what I need:
YEAR must have the original full date.
This should be copied in D/MM/YY format to RELEASEDATE.
Then the MONTH of YEAR (which should be the same as in RELEASEDATE) must be copied to TRACK.
There are already suggestions in this thread to get the individual parts of the date and how to shuffle them around.
Yes, I know, and I've tried them, but it deletes the YEAR field, the month field -TRACk- puts it as YYYY and the RELEASEATE field fills it in... or not?? I'm not sure about this right now, I've already done a lot of tests, then I'll confirm, but the YEAR and TRACK metadata draft.
Then I check it again
I referred to this.
The format strings can be used in Convert>Tag-Tag or an action of the type "Format value"
Use the "only" expressions before you shuffle the data around in YEAR
I’ve spent a lot of time looking into it (even downloaded djay Pro) and came up with the following:
Please delete RELEASEDATE → RELEASEDATE in Mapping/Tipos de etiqueta, matching a tag to itself seems to cause it to remove itself.
Admittedly, I’m on Windows and don’t have access to djay Pro’s metadata editor to edit RELEASEDATE. Why it leaves a RELEASEDATE tag that can’t be consistently read or edited?… clueless. That’s on Algoriddim.
From your findings, djay Pro is also funny about how it reads and shows metadata: YEAR must be YYYY yet shows RELEASEDATE as DD/MM/YYYY when it must be stored as YYYY-MM-DD.
The only consistent way to get a value into Released/Publicado is by entering it into djay Pro’s own metadata editor into its own database or it accesses the file from another database such as Beatport or iTunes (with .m4a, doesn’t support .flac).
I also tried every combination of other potential date-related tags including RELEASEDATE as YYYY-MM-DD and constantly deleting/relinking a file with no luck. Users made lists of metadata that can be read: What parameters need to be specified to display Metadata tags in djay? - Questions - Algoriddim Community Forums
In relation to djay Pro not showing metadata, the only real solution I can offer is keep an extra copy of DD/MM/YYYY in DESCRIPTION which does show up in djay Pro as Comment/Comentarios.
In relation to the original issue, we’ve left enough for you to customise your setup. Make more than one Action if you find the full date isn’t always in YEAR.
Thanks a lot, everyone.
Yes, your diagnosis matches what I mentioned earlier — it’s clearly an issue with how djay internally manages metadata. It’s quite curious how, through its own editor, djay writes the information correctly, but then isn’t able to read back that same data when it’s been edited or created by another piece of software.
Equally strange is the date format — I’m not sure if it’s due to localization or how the software handles different languages, but I’ve already reported all of that, along with other users, to Algoriddim.
Still, thanks to this thread, I now have tools to create actions and modify metadata from Mp3tag. However, until Algoriddim improves or changes how their system works, I’m afraid I’ll stick to editing everything except Artist–Title–Genre directly inside djay Pro. For now, it’s manageable — and I don’t really have another choice.
I’ll also delete the RELEASEDATE mapping as you suggested, because regardless of the djay/Algoriddim issue, something in Mp3tag itself seems to cause that field to be wiped when running an action.
Again, thank you all very much for your help. I hope this discussion proves useful for other users of these applications as well.
