Marekkon5
commented
2 years ago Hello, thank you for your feedback. We've actually planned adding a file renamer/library organizer, but didn't really get to it yet, and until now there weren't any requests for it. So we are going to add it. However which features do you wish to see there? How do you imagine it to work?
We appreciate your feedback, thanks.
Hi there. First of all thank you for your efforts in developing this excellent cross platform tagging tool. I have tried it tonight. It seems to work very well and is full of interesting features for DJs.
Being a very early adopter of MP3 mixing (since 1998) and DJ for 35 years now, I have been looking for a proper automatic tagger / renamer for nearly a quarter of a century. Yes this long... I have folded back to using MP3tag, but this forces me to run a Windows VM which I despise more and more, operating fully on Linux.
All tools I've used in the past have always failed to fulfill my requirements in one way or another especially the ones running on Linux such as Picard, witch has a dubious UI and a very poor track database for DJs
Your approach seems quite intelligent as nowadays we can benefit from valid online metadata repositories allowing us to grab structured tracks information. Also it is a great feature to be able to enrich tags that can then be properly exploited by modern DJ applications, one area of much controversy for sure. I myself tend to rely on my musical memory and structured file system to access my music, more than any tagging. But I agree that in order to match keys in the best possible way, it is quite interesting to have properly filled tags.
Currently managing a collection of 300 000 files, all properly named and tagged, I could not do this manually, this is where a tool like yours can be of great help.
But after having read all issues in this GitHub page, I am quite surprised to see that almost no one seems to pay attention to one major feature absent from your implementation, which is automatic file renaming.
From my dinosaur experience with such tools, there are two major data streams that need to be addressed : -One is tagging information : tag structure management, tag versioning and of course proper source definition and external API integration. Your approach seems great for this. -Second one is the ability to properly structure the file system : file naming convention, directories, based on dynamic rules, mostly based on properly tagged information (going back to point one). MP3tag works fine for my use case, allowing me to batch process incoming files (having whatever file naming convention) and export them to a "OK" directory, all tagged and renamed. But with such a tool, I still have to edit my incoming files on a per disk basis, mainly because MP3tag has very little intelligence in grabbing and processing data from external APIs. Mainly using Discogs with this software, it works fine 90% of the time for albums, but not at all for latest EPs, which take ages to commit to Discogs database. So it is a very lengthy process that I'd rather spend doing something else. I mean this has been a major choir for decades for me!
As I cannot control the sloppiness of naming convention on the files I get, I'd like to be able to batch process a full directory with hundreds of records with a set of half a dozen of rules (depending of the type of record : EP, LP, Mix...).
So my question is simple: do you intend to implement an automatic renaming engine to your dev roadmap, as I strongly believe this is quite mandatory to properly address DJ needs, or is this feature out of your current scope ? I would feel very sad to be able to tag hundreds of files at once with your tool, to then having to rely on another tool to rename them.