Author Topic: Is it possible to revert changes done by a custom/virtual tag?  (Read 450 times)

ChuChu

  • Newbie
  • *
  • Posts: 6
I was trying to figure out if it was possible for MusicBee to automatically convert dates to a specific format. For example, if I were to enter 26 Jul 2023 in the Year field, it would automatically convert it to Jul 26, 2023. I tried creating a custom/virtual tag and it bulk-converted all of my dates to numbers (7/26/2023). Is there any way I can bulk-revert this?

Mayibongwe

  • Sr. Member
  • ****
  • Posts: 1733
  • Heal The World
Custom Tags and Virtual Tags are two completely different tags that serve unique purposes.
What you describe sounds like the workings of a virtual tag making use of a $Date() function and the <year> field.

However, using phrases like "bulk conversion" and the need to "revert changes" implies that your actual <year> field has been altered.
Of which if true, would mean that there is more you've done other than just play around with custom or virtual tags.

Therefore, can you post screenshots of all the tools/features/dialogue boxes you've been accessing and messing around with concerning the above.
From there on, I for one will have a bit of an idea of what is being referred to (it's not clear right now).
Strength and Honour (2025)

ChuChu

  • Newbie
  • *
  • Posts: 6
This is what I did:

I went to MusicBee > Edit > Edit Preferences > Tags (1) and clicked on "Define New Tags". I put this in the dialogue box:


I clicked on "Save", and then set the "save to music file as tag" field to "CustomDate" and clicked on "Apply":


 MusicBee then scanned my entire library and converted all of the dates in the "Track Information" section and edit dialogue box to number format:

tjinc

  • Sr. Member
  • ****
  • Posts: 830
I don't think this has been caused by any virtual or custom tag but simply by the act of rescanning all files (admittedly as a result of creating a custom tag saved to file, but would have happened at some time anyway).
The date format for MP3 is a limitation of the metadata standard practices for that file format and your Windows short date setting (at least for ID3v2.3 - I think ID3v2.4 gets around this).

This 'change' cannot be undone but I wouldn't advise that anyway as it won't stick. Simply force the format of the displayed date by using the following code in the customise panel settings for the Track Information panel:

Code
$Date(<Year>,MMM dd, yyyy)
Or use this code in a virtual tag and display this virtual tag in place of the <Year> field.
(Which I think is what you were trying to do in the first place).