-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
READ BEFORE OPENING ISSUES #363
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Welcome to the OneTagger project! Here are few things you should keep in check before you open an issue:
Notice:
At this moment I am a little busy with personal life, so bug fixes, features, and replies will be delayed.
What to do before posting:
onetagger.log
file. You can find it by going to Settings -> Advanced -> Open data folder.Known problems:
Spotify, Traxsource, Shazam giving too high rate limits: we can't do much about it, since it is limited by the servers. In the latest builds, those platforms are intentionally slowed down to prevent such high rate limits.
OneTagger gets stuck at X%: this can be related to rate limits, or some problematic tracks / uncaught issues. We highly recommend making backups before tagging, and running it on smaller folders.
OneTagger writes wrong tags / How to manually confirm changes: in that case AutoTagger is not the thing for you. AutoTagger is for fully automatic tagging, and tries to match tracks on best-effort basis. If you prefer more manual control, check Manual Tag (you can access it by right clicking on a track in Tag Edit).
Known feature requests:
Album based tagging: planned in (rather far) future, because it requires major changes to how 1T works.
Add platform X: if the platform is popular enough, we might add it, however are also working on new Python-based plugin system & repository to add more platforms more easily.
The text was updated successfully, but these errors were encountered: