Closed AndreaCan closed 2 years ago
Hello, I don't see anything wrong in the log, maybe 1T can't read the tag. Could you please send one of the songs as example so we can test? Thanks
I don't see anything wrong in the log
In fact, the LOG shows only that OneTagger is unable to read the tags from the files.
Could you please send one of the songs as example
Ok I send it as an attachment below. DJ Kuba & Neitan & Skytech - Dancing (Wh0 Festival Remix).zip
Hello, the track works fine on the development (master) version. There has been some changes since 1.3.0 release, so your issue probably got resolved as well. You can get the test version from the Actions tab on Github.
Also the track gets no match - that's because on Beatport the name is Dancing Wh0 Extended Festival Remix
and yours is Dancing (Wh0 Extended Festival Remix)
. The word Extended
makes so big difference the accuracy is below the default strictness (0.8). So either change the strictness or rename your song to match it succesfully on Beatport.
If you have any more issues feel free to comment / reopen. Thanks
the track works fine on the development (master) version.
Well then I await the new version.
You can get the test version from the Actions tab on Github.
I have tried to figure out how to do this, but could not find the installation file. If I have to compile the source for windows I am not equipped to do it.
Also the track gets no match - that's because on Beatport the name [...]
This wouldn't be a problem, it can happen. The important thing is that the track is not skipped without motivation.
ok thanks, then I'm waiting for you to publish the new version.
You don't have to compile it from source. You just have to be logged into Github, then click the Actions tab on top:
Then click on the latest commit:
There scroll to bottom and you can see the Artifacts
section:
If you use Windows - click onetagger-win-setup
and it will download the Windows Setup version.
You don't have to compile it from source.
Thanks to your help I was able to find the file to download.
I installed the new version (which in any case is always indicated as 1.3.0 in the home of the program) and I analyzed the previous folder: none are skipped and all are "Matched" except the one you said, because there is that difference in the title. However now it works fine, as before. Who knows what the old version had that didn't make the program work.
I thank you again for your work you have done with this very useful program.
I use version 1.3.0 on Windows 10. When I use Auto Tag on some MP3 files I always get that my tracks are skipped. This occurs with any platform (Beatport, Discogs, etc):
These files have been verified with MP3tag and they have the Title and Artist tags perfectly compiled and readable:
I also checked the OneTagger LOG and it seems that there is no track metadata (I am attaching the onetagger.log file)
But if the tracks opened with MP3Tag display the Artist and title tags, then why can't One Tagger be able to read them?
Thanks Andrea
onetagger.log