Thanks, I'll give it a try. I do have the 32 bit installed. Will mp3tag save my settings? If not, Any suggestion on how i can save my settings/layout/filters and apply to the different version?
See here for the notes on a new version:
(the link is right next to the download link ...)
Thanks! Now starting the process all over again. Hopefully it won't be as long a day as yesterday was!
Well, i'm beginning to think MP3Tag just can't handle large collections. Upgraded to 64 bit, same or nearly same issues. After 2.5 hours loading mp3tag is stuck, for additional 45 minutes, here....
After over 9 hours yesterday and about 4 today, i'm back at square one. It seems it's just not going to work. I think i'd like to go back to my original 2.88a version. A quick search doesn't bring up this older version. Anyone know where i might find a copy?
Thanks
If MP3tag cannot read certain files, then if would be a good idea to check them for consistency.
Honestly, going back to 2.88 will not solve that problem of problematic files.
Understood. I am pretty meticulous about my files. They are "consistent", i believe. If i split the files in half they read fine, so i don't think not being able to read them is an issue. The older version read the same files for years without any issues. The issue seems to be the size, if i do a workaround by reducing the size it works. The new version has other issues/features that i am finding out about that i like better in the prior version, i.e. the new version does not remember the location and size of the window after closing, the older version did (not sure if this is a setting?).
I now know that i have to add the workaround to my work flow. Which i can live with. Loading the files twice, and making the edits twice is a bit inconvenient (with a nearly two hour wait/load prior/between) but it is doable.
PS - I have found the older version on the web at sites like "FileHippo", not sure i want to take that chance. Would love to find it here instead.
I don't have to convince you.
@poster 's idea with the 64-bit version is one way to overcome your problem. The 64-bit version expands the possible address space to a lot more than the meagre 3 GB of a 32-bit version.
So your collection should be readable.
If reading the files stops then it could be due to problems with files - or perhaps other circumstances that may be wothwhile to be investigated further.
The version i have installed now is the 64 bit version, yet the problem persists. Not sure how there is a problem with the files considering that, as mentioned, doing them in two separate processes works. Seems clear that the only non-constant, is not the files, but the size of the process that MP3Tag handles. In other words, if the files are somehow bad, reducing the size of the process wouldn't necessarily fix bad files. Does that make sense?
In a way it may make sense.
But as always: I cannot look over your shoulder and have to rely on that what you tell me.
Here is a link to programs that check different properties of audio files:
As I said: you don't have to do anything of what I suggest
I have frequently loaded more than 200,000 files without problems.
Thanks for your help! I appreciate it. Through all this I've learned how to use the filter feature, which is very helpful. It seems that 200.000 files is fine (on my end as well), but 300.000 may be a bit much. In any event, i'll split them in groups of 200.000 or less going forward and all should be good, i'm fine working around the MP3Tag's limitations.
Thanks for the links,
Tom
Another quick question comes to mind. When using the filter (%genre% HAS Pop AND %genre% HAS Psych) i am getting results that include (Psychedelic). How can i limit the results to only what i asked/typed to be filtered?
You can try to use the words in quotes like
%genre% HAS Pop AND %genre% HAS "Psych"
But as the word "Psych" is also included in Psychedelic you may have to combine them with some AND NOT combinations as in this example topic:
Try
genre IS Psych
(without the % around the fieldname)
Because I was not at home in the last weeks I didn't have the opportunity to test the reading of a really large amount of mp3-files. Now I did.
I loaded about 346000 mp3s with activated and already existing library and an exception for windows defender. My system needed 5 minutes and 20 seconds to load all files.
My system is rather outdated:
13 years old mainboard, CPU AMD Phenom II X4 955, 16 GB DDR-3 RAM, Windows 10
but:
(not very fast) internal SSDs for system, mp3tag-library and mp3-files.
Since the release of the 64bit-version of Mp3Tag I never had any problems with reading great amount of files, before I was not able to handle so many files without splitting.
Anyway I do this only on special cases when the task needs to have all files loaded because filtering so many loaded files is so slow that it's not really fun. I suspect that it will be more acceptable with a current PC system.
My conclusion:
There can only be reasons in your environment for the extremely slow loading, for example external instead of internal data storage, network data storage, USB data storage, not enough RAM, no SSDs etc.
BTW: If I don't define an exception for Mp3Tag for windows defender reading the files takes about 90 minutes instead of the mentioned 5 minutes and 20 seconds