WACUP

Preview Build Discussion => Preview Build Discussion => Topic started by: VulgarAscetic on May 09, 2026, 03:33:23 PM

Title: [Bug] Edited metadata regresses to previous values, "update file tags" fails
Post by: VulgarAscetic on May 09, 2026, 03:33:23 PM

When updating some mp3's metadata, it appears successful, but any subsequent edits to the same file metadata will regress previous edits. Additionally, some files will regress by themselves over time, effectively going back to previous metadata. It's unclear what causes this "timed" regression.

Selecting "Update file tags" checkbox in the metadata editor will give a "Metadata updating error" box, but it is unclear what causes this to fail, when other mp3 files will update their metadata correctly.

Worth noting that these same files can be successfully edited in other software such as mp3tag.

Screenshot show the metadata successfully changed in Wacup but not in the file metadata seen in explorer.

Repro steps:

• Right click a file in library
• Go to "edit metadata for selection"
• Ensure "update file tags" is UNCHECKED
• Edit the track name to something else
• Click update
• Track name appears to change
• Repeat steps but change the album title this time
• Album title updates, but track title will regress to before the above edit
• Open metadata editor again
• Ensure "update file tags" is CHECKED
• Change any metadata and click update
• Update fails

Title: Re: [Bug] Edited metadata regresses to previous values, "update file tags" fails
Post by: dro on May 09, 2026, 03:56:53 PM

Saving metadata to mp3 files with the x86 build relies on the old in_mp3 plug-in from 5.666 & I am not at all surprised that it's not working correctly. The saving process will send to the local library (if present) & also to the input plug-in that claims to handle things for saving support. That's why if the save to the actual file didn't occur but it was able to make it into the local library (e.g helpful for vgm / virtual file formats), if you then edit things externally there's even more of a disconnect between the local library cached values & what the actual file might now have.

If using the x64 build (doesn't look it from the partial images) then there's no handling in place for mp3 files to even attempt to save them out & it just relies on the local library since none of that has yet been coded.

tl;dr: metadata editing is known to be a mess especially for mp3 & is another reason for why wacup is still deemed as a preview which needs to be sorted out later this year.