Page 1 of 3
Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 2:53 am
by Donus
MediaMonkey is scanning some music folders with about 200.000 files on an external drive, USB 3, it takes very much time here, about 10 hours now for 100.000 files. Is that like it should be? How could one accelerate it?
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 8:08 am
by Donus
Is this the usual time needed to scan that amount of files?
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 9:57 am
by Lowlander
Depends on your settings. If you enable duplicate analysis, have the whole Library shown in the File Listing or do a lot of database operations while scanning it will be slower.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 10:36 am
by Donus
I left the default settings. So no duplicate analysis and such.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 11:11 am
by Lowlander
Then access to the USB drive may be slow. Is the database file also located on it?
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 11:21 am
by Donus
Then access to the USB drive may be slow.
Well, I would say it is a common connection, like usual.
Is the database file also located on it?
No, it is on an SSD.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 11:34 am
by Lowlander
Do any subsequent scans still take long?
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 11:42 am
by Donus
I do not know, the first scan ever is still running...respectively not running anymore, do not know what this means:
I activated the last option, at the bottom, pressed OK and now I do not have any access to MM anymore.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 11:47 am
by Lowlander
That's not something you want to do when your scan is still running. MediaMonkey may still be running both tasks, but remain unresponsive as the database is hung on those operations. If you close MediaMonkey you may end up with a corrupted database.
Optimization will fix database errors which can result in improved performance. However you'll want to leave that running when MediaMonkey is not doing anything else.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 11:56 am
by Donus
So the best is to wait until MM is responsive again? Or close it with the Task Manager or so?
But above all, why is that option available at all in such a situation (while scanning) when it causes problems using / activating it then? It seems to be totally senseless.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 1:04 pm
by Lowlander
I'd wait.
However if you just started you're not standing to loose anything from the database if it would become corrupted, just the long scan again.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 1:20 pm
by Donus
OK, I will keep trying waiting, there are some more drives to scan and 14 hours for just 200.000 files seems to be very slow. foobar does it much more faster.
If I should interrupt it, do I have to remove the (corrupted) data base manually, create a new one or does it MM do automatically?
Seems to be poor programming.
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 2:16 pm
by Lowlander
If the database is corrupted you can remove it manually:
http://www.mediamonkey.com/support/inde ... -ini-files
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 2:24 pm
by Donus
Many thanks for the link.
Sorry, I am not quite sure, I just can remove MM.DB, just delete the file, nothing else, that's it? After MM automatically creates a new one?
Here (I have portable mode):
Portable Mode:
In the 'Portable' subdirectory of the location to which MediaMonkey was installed. e.g.
<MediaMonkey Portable Install Folder>\Portable\MM.DB
Re: Scanning music folder lasts extremely long?
Posted: Wed Mar 28, 2018 3:06 pm
by Lowlander
Yes, just remove the file and a new one will be created. However your database may not have any corruption in the first place. There is just a risk of it if you close MediaMonkey while working on the database.