# Fiio Snowsky Echo Mini

**URL:** https://community.mp3tag.de/t/fiio-snowsky-echo-mini/71000
**Category:** General Discussion
**Tags:** player
**Created:** [April 5, 2026, 7:16am UTC](https://community.mp3tag.de/t/fiio-snowsky-echo-mini/71000 "2026-04-05T07:16:09Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 5, 2026, 8:21am UTC](https://community.mp3tag.de/t/fiio-snowsky-echo-mini/71000/4 "2026-04-05T08:21:02Z")

</div>

We (as in, the community) recently identified an issue where special unsupported ID3v2 frames made supported frames not being displayed as expected.

Here is the respective topic with a workaround

> [@Snowsky Echo Mini no longer recognizes tags touched by MP3Tag](https://community.mp3tag.de/t/snowsky-echo-mini-no-longer-recognizes-tags-touched-by-mp3tag/70918/9):
>
> 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]](#footnote-240392-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](https://community.mp3tag.de/t/customization-of-tag-panel-and-file-list/56067#p-168275-customizing-the-file-list-2) using %\_id3v2\_unknown\_frames% as Value. A filter w…

---

_[View the full topic](https://community.mp3tag.de/t/fiio-snowsky-echo-mini/71000)._
