If you are seeing 'adding' then you are more than likely attempting to load your entire collection into the UI. Your Mac will run out of memory long before Yate loads 130k tracks. When draining the Mac that much many applications will come unstable and it is virtually impossible to test for for the condition.
The Invalid Tag Size is possible if one of the files has a corrupted tag. I'd be surprised if in a 130k tracks you didn't find a few of these.
This is not the way to go. As you have found out the UI cannot handle the load. However, Yate has a Batch Processor which can run over your entire collection and only load a folder at a time.
What you want to do can be done with actions but there is no way to do this directly in the UI.
You can write an action which will run through the Batch processor and produce the fingerprint, extract metadata from AcoustID, attempt to match and extract metadata from MusicBrainz. I can guarantee you that because of the nature of acoustic fingerprinting and matching, some results will be totally incorrect. Have many will be inaccurate depends on the contents of folders (single album, multiple albums or singles). Further with 130k tracks many will not be matched at all. It might pay to do the operation without committing the results, saving them to temporary locations in the tracks and/or producing a track database where you could look at the results. Looking at the results does not sound attractive with 130k tracks. Audio fingerprinting, unlike human fingerprinting is not exact. Quite often many tracks have the same fingerprint and this can lead to false matches.
Fingerprinting if it works will get you MusicBrainz IDs which will enable you to extract artwork from a few sources, if it can be found. Unfortunately, quite often Google is the best source for artwork.
Assuming that some sort of success could be attained, Yate could find the duplicates in a produced Track database (doing this is a one line action).
I don't know the quality of the metadata you currently have in the files. It is quite easy to produce a track database which will describe the metadata in each track in your collection. You could also display the number of artwork items in each file. To do this you would create an Export set describing the fields that you are interested in. You do this in Preferences-Export Sets. You more than likely want to include at a minimum the following fields:
Album, Artist, Album Artist, Genre, Title, Artwork Count and File Path. You must have File Path.
You can then create a one line action with a 'Create Track Database' statement, using the Export set that you created.
You would then run the action through the Batch Processor. When done, you will have a database file which you can open in Yate or any other application capable of reading a CSV file. If your metadata is decent, you could always attempt the duplicate detection without any other processing.
You can of course go any way you like. Personally I would not attempt to 'blindly' update the metadata of 130k tracks.
It is tough for me to even give sound advice at this point. There are a lot of unknowns. (again, folder contents and structure). There are applications out there which claim to 'fix' a collection with a single button press. I guess it works for some people but I've also heard horror stories. It's not the quantity of songs which worries me ... it is inaccurate results.
|