Snowsky Echo Mini no longer recognizes tags touched by MP3Tag

OS version: Mac OS Ventura 13.7.4

MP3Tag version: 1.11.0 (134)

Filetypes: .mp3 (id3v2.3 tags)

When I load an album into MP3Tag, all tags appear correctly.

If I highlight one track and simply “save” without changing any tag values, then copy the entire album over to a microSD card and insert that card in a DAP (Snowsky Echo Mini), the track that I “saved” appears with “unknown” for album, artist, and genre.

The rest of the tracks from the album appear correctly.

This behavior only started with this version of MP3Tag. Is there a way to download a previous version?

What kind of files are this? MP3? Flac? etc?

.mp3 files. (I’ll update the original post)

Please show us a screenshot of the extended tags dialogue of a file that still works and one that got modified.

Thank you for those screenshots
I had the suspicion that perhaps the tag version might have changed. But it looks like still being the same.
So I don't really know what MP3tag could do any more.
Do you have other programs that could display the tag data?
Or a program to check the file integrity?

I agree. It’s pretty odd. I used Kid3 to examine the tags and the results are the same: no visible difference in the tag formatting.

This behavior didn’t happen with previous versions. Is there a way to get an older version of MP3Tag for Mac OS?

This issue is popping up on subreddits for other users where we have been recommending MP3Tag. (both on the Windows and Mac versions)

I don't know anything about your player.
That is why I wonder if other players also have problems or only this particular one.
E.g. it could be that the player does not like UTF-16 encoding but needs ISO-8859-1.

Yet, it is very strange that only some tags fields are effected.

I've requested example files and they contain various unsupported GEOB and PRIV ID3v2 frames. It's likely that the DAP chokes on those, as they can appear in a different order on rewrites.

Removing the tag of those files via Edit → Remove Tag[1] and undoing the change via Edit → Undo removes those unsupported frames, so that the file might appear to be "repaired".

You can display those unsupported frames by adding a new column to the File List using %_id3v2_unknown_frames% as Value. A filter with NOT %_id3v2_unknown_frames% IS "" lists all files with unsupported frames.


  1. Removing ID3v2 at Settings → Tag Types → Remove needs to be enabled for this workaround to be effective. ↩︎