Field Separator LOST when editing Genre (0x3B replaced with 0x00)

[toyzrme2]

The ";" was removed from the Genre field of genres I edited, and replaced with the null character (or CR/LF)

Just installed MMW5 (latest), taking the upgrade from MM4 (latest).
Took defaults for most things. Did not change the separator (still shows as ";" in Tools > Options > Library > Fields)
Used the list of Genres on the left to fix some Genres - renaming them, changing case, etc.
For example:
MM4: "Dance; video: motion"
MM5: edited to capitalize "V" and "M" (in a different case, I added a genre "; TEST", but similar results)

The genres appear correct in MM5, displaying with ";" to separate them..

HOWEVER, the additional genres used to appear correctly in Window's (10) File Manager "Properties", but after this change, they do NOT.

Looking in a hex comparator between pre-edit and post-edit versions, I can see the that the ";" (0x3B) was replaced with 0x00.

Is this the expected behavior? Is this a standard that MM is adopting, or just an internal change MM decided to make?

[Lowlander]

Is this for MP3? In MMW5 ID3v2.4 is used as default instead of ID3v2.3 and this causes the change in separator (as it follows the tagging standard). You can switch back to ID3v2.3.

[toyzrme2]

Ahhh, thank you!
Yes, for MP3. Stopped following the tag format wars 10 years ago once I got my MMW3 library all set up

I'm assuming MM5 handles both formats just fine - is there any reason to convert all existing tags to ID3v2.4?

Or, if I change the setting back to v2.3, will it auto-convert all of the v2.4's back to ID3v2.3?

[Peke]

Hi,
You need to sync tags eg. select files -> CTRL+S

[toyzrme2]

Thank you kind sir, genres back to where they were!

Question: in verifying the fields vs. a recent backup, I noticed in the files that had been altered, one tag (RGAD) was consistently different:
RGAD New: 3F 7F FD F8 2C 1E 4E 0B ...vs... Old: 3F 7F FE 00 2C 1E 4E 0B

It seems the 3rd & 4th bytes are different, but the rest are the same - and the old value always had a 00 in byte 4.
Is this expected?

[Peke]

Hi,
You would need to send me sample file over support ticket and let me know when file that byte is changed. Some tags update on each change so it is normal.