I've been a long-time user of Mp3tag, and it's an exceptional tool. Your work in creating such a powerful and flexible metadata editor is truly appreciated.
I believe that further strengthening Mp3tag's core purpose—metadata editing—will continue to solidify its place as the best application in its category.
While I understand that some users find features like playlist support valuable, I suggest that focusing development on core metadata features would benefit a wider range of users. If playlist features are to be maintained, perhaps they could be offered as optional plug-ins to keep the main application's interface focused on its primary function.
I also wanted to suggest enhancing support for chapter metadata across various formats, including ID3v2 CHAP frames, Apple QuickTime chapter atoms, and Nero-style MP4 chaptering. With the growing popularity of podcasts and audiobooks, robust chapter support has become an increasingly critical feature for many users. Improving this functionality would be a significant value-add for a large and expanding user base.
Finally, I have a specific usability suggestion regarding the "Filetype" column. While I understand the shuffle behavior is related to playlist functionality, it's confusing and inconsistent with how column headers typically function both within Mp3tag and in other applications. I would suggest that this behavior be changed to the expected sort, which would better serve the application's core metadata editing purpose. The shuffle functionality could then be moved to an alternative control or grouped with other playlists features.
Thank you for your continued dedication to Mp3tag and for considering this feedback.
I see that this is the second time that you have weighed in here against the Randomizing feature, despite the negative response to your first mention of this in 2024. I find Randomizing very useful, and am mystified by your persistent dislike of the current implementation. It works, and it's easy. OK, you don't use it, but others do. I see no need to change it.
As to your suggestion that "...focusing development on core metadata features would benefit a wider range of users", that is a very broad judgment indeed. What is your basis for that? Might not the opposite be true? Mp3tag appeals to a wide variety of users at all levels. I see that very much as its strength, not its weakness.
Looks to me as though you never used View>Sort by ... in which you can select the column by which you want to sort - even if it is not in the current view. You only have to include the preferred data somewhere as a column.
The point that other users who used the randomizing function would have to learn a new behaviour is still valid.
If I look at the repeated support pleas which ask where the user-defined genres have gone and a special HowTo had to be created to reduce the number of repeated explanations, I rate the modification of an established function as a really bad idea.
I want to sincerely thank those who took the time to respond to my post—your insights and perspectives are genuinely appreciated.
Doug, I respect that you find the randomizing feature useful in your workflow. While I personally don’t view randomization as a core metadata function, I understand that features people rely on can feel essential, and it’s natural for users to speak up when changes are proposed. That kind of engagement is valuable, not a roadblock—it helps shape thoughtful development.
The heart of my post was to encourage Florian to continue refining and strengthening Mp3tag’s core metadata capabilities. With such a widely used and respected tool, there’s always enthusiasm for new features—bells, whistles, and clever add-ons. But sometimes these can drift away from the foundational purpose of the app. That’s why I mentioned playlists, which to me seem more aligned with music playback than metadata editing.
Thanks again for the thoughtful discussion. I’m grateful for the community’s passion and for Florian’s continued dedication to making Mp3tag the best it can be.