... or select all the wanted subfolders in the explorer and invoke Mp3tag via context menu.
This seems to be true in practice.
A few days ago I did some tests using Mp3tag v2.62 on a 2GHz 2GB WinXP machine with a big amount of files.
Results are:
1.
One folder with 175769 dummy test mp3 files (each of 5 Byte filesize) has been the limit for the Windows Explorer resp. the disk subsystem.
Mp3tag was able to load all files, but it took rather long time.
Mp3tag was able to embedd a JPG picture of 59 KB filesize into 81567 files, then stopped by memory failure.
Having 10000 subfolders with each having 20 dummy test mp3 files (each of 5 Byte filesize), given 200000 files, Mp3tag was able to load all files, much faster than from one big folder.
While loading a JPG picture of 59 KB filesize there were several Mp3tag breakdowns because of memory failures.
Especially when setting the Filter, e. g. ...
"%_covers%" IS ""
NOT "%_covers%" IS ""
%_covers% PRESENT
NOT %_covers% PRESENT
... Mp3tag instantly got a memory failure.
After several attempts with smaller groups of files, all files got the picture embedded ...
(50000 + 50000 ... machine cold start ... + 100000).
Mp3tag load time was about 35 minutes for all 200000 files with embedded 59 KB picture, overall about 11.5 GB.
Because of the limits given by the machine, it was not possible to work with this big amount of files in a satisfying manner.
There are several error logs I have to send to the developer.
DD.20140819.1127.CEST