I use MP3 and FLAC files in my music collection, hence the 2 apps I mentioned.
AudioTester64 for FLAC (only) failure detection (no way to fix them, but replace them with valid files);
MP3 Diags for MP3 (only) - to fix bad tags and more.
I've used the Convert action Filename - Tag on all folders by now, which all seem to do fine.
If I grab more than 5000+ in 1 batch, I get the same ''not enough memory'' error message.
This means, it's not related to a specfic file, right?
After doing a chkdsk /r /v on my C: drive - where Mp3tag is installed - 512GB SSD, waited 50 minutes & finished.
I did the same for E: drive where my audio collection is (2,20TB - 5900RPM): waited 4 hours and still at 14%.
Pushed the Reset-button.
CrystalDiskInfo shows SMART of both drives: GOOD with temps around 35 celcius.
I also have dBPoweramp which is able to do a Filename - Tag in Batch-mode.
Let's see how that works out.
The same friend suggested to look up the mem-usage of Mp3tag.
According to him due there is no 'large address aware' switch for Mp3tag it only uses 2GB max.
TECHNICAL FILE INFORMATION :
File Type Description : Portable Executable (PE)
Entry Point RVA: 003548C1h
Entry Point RAW: 00353CC1h
FILE CHARACTERISTICS :
Relocation info stripped from file
File is executable (i.e. no unresolved external references)
Machine based on 32-bit-word architecture
FILE HEADER :
Machine: 014Ch (i386 or later, and compatible)
Number of Sections: 0004h
Time Date Stamp: 5ABD46AFh -> 29/03/2018 22:03:59
Symbols Pointer: 00000000h
Number Of Symbols: 00000000h
Size Of Optional Header: 00E0h
So I enabled the /3gb switch according to this tutorial and rebooted:
''If a 32bit executable does not have the LARGEADDRESSAWARE flag set to true, the application can't use more than 2 gigabytes. If you are on a 64bit machine with lots of memory, even if you are stuck with a 32bit process, you should ideally be able to start multiple processes each using 3+ gigabytes.''
Yes, I would say so.
But again: I can load FAR more than just 5000 files into MP3tag.
So the assumption is not too far-fetched that it has to be some kind of local condition that causes it.
If the fault is still there when the collection is treated on a different hardware, we are more or less back to square one: it is most likely that one of the files has a fault.
And all this happens with the library switched on?
Just tried it on the i5 PC, this time with Library set to Ext. drive/Music folder, same result.
I will now make a copy of the whole music collection folder (327GB).
And delete the FLAC files; so MP3 is left over.
And do the same on the copy, but then delete the MP3 files; so FLAC is left over.
So the folder structure stays intact.
Re-import only MP3 based collection and re-import only FLAC based collection.
To be continued.