Auto-tagger stuck at 20%

Marekkon5 / onetagger

Music tagger for Windows, MacOS and Linux with Beatport, Discogs, Musicbrainz, Spotify, Traxsource and many other platforms support.

https://onetagger.github.io/

GNU General Public License v3.0

633 stars 35 forks source link

Auto-tagger stuck at 20% #301

Open Timonstip opened 1 year ago

Timonstip commented 1 year ago

I used this program a while ago on a different system and it worked great. However on this new pc, whenever I use the auto-tagger it seems to get stuck around the 20% mark. I have tried it starting with beatport, and starting with traxsource as well. Happened both times. My taskmanager indicates the app is still using a lot of memory and cpu, however even after 3 hours no progress is made. Am I impatient or is the app freezing in a weird way?

bascurtiz commented 1 year ago

Can you share your onetagger.log so we can further inspect? You can get it here:

Open One Tagger
Click Settings icon
Click Preferences/General
Click Open Data Folder

Drag and drop it into your reply here.

Timonstip commented 1 year ago

Wow, this is a quick reply, on a sunday. Didn't expect that, thanks! onetagger.log

bascurtiz commented 1 year ago

I dont see any particular ERROR that might interupt the progress in the log though. The one at the bottom simply shows you are running 2 instances of One Tagger (prolly u opened it again in order to follow the instructions above).

What I can recommend though:

Delete the onetagger.log (since it's now bloated with info)
Grab the latest build from the actions tab ( https://github.com/Marekkon5/onetagger/actions )
Click the latest build on top (which is named More UI changes as of writing)
Scroll all the way to the bottom, click the artifact/binary for your OS and install it

We have fixed a few things in between the official release, u seem to use, and now, so it might help. Let us know! Thanks.

Timonstip commented 1 year ago

I've followed your steps and started a new run through. Now it seems to freeze at 17%, but since I have to go I'll leave it running to see if anything changes. 17% I gave it a good 5 hours on 17%, then the internet went down so after that I guess testing on was pretty pointless. still 17 % onetagger.log

bascurtiz commented 1 year ago

Kinda hard to pinpoint with 6200+ songs to tag... Perhaps, since some are in their own folder, u could try to pinpoint it down by trying out where it left off?

I see you didnt add the OneTagger tag in Tags, which actually comes in handy here. If you enable it, 1T knows which ones it tried already next time, so it will skip those. This way we can filter it down to where it might stall on a certain file or foldername.

So my suggestion: Do it again - with One Tagger tag enabled in Tags. If it stalls again. Close 1T. Run it again. Now it will skip previously tagged tracks. Then we might find the culprit. Good luck!