Wait…does “should give very similar results” mean that it’s a waste of time to run the process I’m running now? Should I wait until the bug is fixed?
Or did you mean it should give similar results to the process I ran in Preview mode?
Memory issue cancelled fixing songs (java heap space)
The second, yes continue running
1 Like
The process has slowed down considerably. 90 minutes in now and just 4100 songs. But it’s chugging along.
I dont know why it is slow, but if possible just be patient and let it continue, the process does not require user interaction so can just be left to run.
1 Like
I’m trying to be patient, honestly! I was really just worried about it running for a few days then stalling again.
The good news is that not even 24 hours since the process started, it’s completed fixing some 46000+ songs. With a little luck, it should complete sometime tomorrow afternoon. Fingers crossed!!
Okay, excellant.
One thing to note the progress bar shows it has actually already matched 87,237 songs to MusicBrainz release (and the previous Preview run only matched about 89,263) so the matching is close to completion, however it has only saved the changes fo 35,256 songs and completed 46,077 songs (it only has to save if there are changes)
So it does seem for what ever reason the bottleneck is actually saving the changes to your files which concurs with the issue you had with Rename Files task, but hopefully should complete regardless.
1 Like
Almost made it:
Now I can’t use SongKong because it says there’s something wrong with my license! It all looks good to me…
Hmm, what does it say, maybe support files wil explain issue.
I got some weird error message about my license. I checked the codes and they both seemed correct. Restarting the app seemed to fix it.
As for Fix Songs - the process seemed to complete, or it got VERY close to completing, at least. I’m looking through the files now, and sending support files.
Hi, thanks for support files. Yes it essentially worked, just 500 songs not processed. If you have a large grouping of files such as a boxset the processing is more and sometimes it takes too long, if not completed after certain time we cancel it, occasionally this cancellation is not handled correctly and that is why you get the 118,179 songs checked against MusicBrainz and Discogs before task cancelled by SongKong because of unreported error message.
This is what happened here
Cancelled class com.jthink.songkong.analyse.analyser.task.MusicBrainzSongGroupMatcher1:G62159:Foldername:Mozart Serenades & Divertimenti (Vegh-Camerata Salzburg):isPartOfMultiDisc:false: because taken too long
led to
java.nio.channels.ClosedByInterruptException
All the files that have been processed okay have been saved with the changes made.
There was a temporary issue accessing the license server, maybe an issue with your network
Thanks Paul. I guess there’s no way of determining which 500 songs weren’t processed?
Not sure of exact folder name because of the errors these folders were not written to the report but from the Errors and Warnings tab the groups not processed were:
- Telemann Tafelmusik-Wassermusik-Konzerte
- Vivaldi 55 Concertos (Pinnock; English Concert-DG)
- Bach Orchestral Music (Pinnock; English Concert-DG)
- Mozart Serenades & Divertimenti (Vegh-Camerata Salzburg)
You could find these, alternatively probably easier to rerun Fix Songs but set For Songs already fully matched to Ignore. This will skip over the 70% already matched, now it will try to match all folders not already matched again rather than just trying to match those four but there is an advantage to this because sometimes the limited information added first time round can help get additional matches second time round.
1 Like