MediaMonkey forum

I tried to rescan after adding a couple of albums tot he library. MM wants to add add all of my 12k songs I am using 1297 Gold.

I do not remember this happening during last spring. Come on, please do not introduce basic bugs like this.

LikeMM wrote:I tried to rescan after adding a couple of albums tot he library. MM wants to add add all of my 12k songs I am using 1297 Gold.

I do not remember this happening during last spring. Come on, please do not introduce basic bugs like this.

That's the expected behavior. If you rescan a folder all the files within will be rescanned.

Did you verify that " only for files with changed timestamps or size" is checked in tools/options/library?

Yes. Also, the "date added" field does not change, which is good. But it is going to take many hours to scan all files... How long should it take to compare previous time stamp and current time stamp and ignore it if it is exactly one hour different? I have a quad core CPU. It should not be that slow to read time stamps for all files from hard disk. Or is MM reading time stamp and finding it different, opens each file and reads the tags to compare with the database?

Do you have the library node opened while you are scanning your tracks?
Try switching to a node that is empty.
See if it makes it go faster.
Are there any other background process (for example volume analyzing) ?

If you only added a few album, with a library of your size. It should take approximatively 30seconds.

LikeMM wrote:I am using 1297 Gold.

Latest release is 3.2.2.1300.
Might be worth upgrading.

It ran out of memory.

There was a problem querying database
Error executing SQL statement "UPDATE Songs SET
SongPATH=?,Artist=?,... WHERE ID=?
": out of memory (7,7)

I restarted and got "MediaMonkey has encountered an error. Needs to close"

I restarted again, did 'maintain library" and scanned again. It finished in about 2 minutes as it had done re-scanning 90% of the files during the first run. No, the focus was not on library node when I scanned first time. It was on one of the Magic Nodes - "genre", which has most of my songs. No background process was on.

Similar report here: http://mediamonkey.com/forum/viewtopic. ... &hilit=dst

It seems that this does happen. Just did a scan of a directory and it seemed to scan each file again instead of just the new files.

Lowlander wrote:It seems that this does happen. Just did a scan of a directory and it seemed to scan each file again instead of just the new files.

Maybe that also causes the problem with device sync. Did the timestamp update for each file that was rescanned?

No, it did not update the time stamps as seen in the main tracks window. Time stamps range from 2008 to current. That part is OK.

@Nohitter151, what type of timestamp change should be observed? Should be a hour difference or should it be the date of the scan?

Lowlander wrote:@Nohitter151, what type of timestamp change should be observed? Should be a hour difference or should it be the date of the scan?

It would be date and time of the scan, I imagine.

I've also experienced the same issue with MM re-scanning all tracks when only a few are added and using Tools/Add/Rescan Tracks to the Library.... My last scan was before the local time change and took less than a minute. Now scan has been runing for well over 30 minutes and has added less than 5500 songs, averaging about 3 songs per second. The songs are all MP3s stored on an external drive attached via eSATA and formatted NTFS on Windows 7 64-bit. I routinely use RoboCopy to backup the songs to a remote share and have just ran it again to verify the time stamps of the MP3 files have not changed as only the new albums were copied. I've used MM for years and have never had this issue across a time change. I'm running the latest version 3.2.2.1300. As well, when I right click on the "adding" status bar and choose Terminate from the popup menu it does not terminate. I'm not sure if this is typical but when I first looked MM was using just over 400MB in Private Bytes and now at just under 6000 tracks scanned it is using 650MB in Private Bytes. It looks like there is some sort of bug with MM.

MinersC wrote:I've also experienced the same issue with MM re-scanning all tracks when only a few are added and using Tools/Add/Rescan Tracks to the Library.... My last scan was before the local time change and took less than a minute. Now scan has been runing for well over 30 minutes and has added less than 5500 songs, averaging about 3 songs per second. The songs are all MP3s stored on an external drive attached via eSATA and formatted NTFS on Windows 7 64-bit. I routinely use RoboCopy to backup the songs to a remote share and have just ran it again to verify the time stamps of the MP3 files have not changed as only the new albums were copied. I've used MM for years and have never had this issue across a time change. I'm running the latest version 3.2.2.1300. As well, when I right click on the "adding" status bar and choose Terminate from the popup menu it does not terminate. I'm not sure if this is typical but when I first looked MM was using just over 400MB in Private Bytes and now at just under 6000 tracks scanned it is using 650MB in Private Bytes. It looks like there is some sort of bug with MM.

When I asked about timestamp, I meant the reported timestamp in MediaMonkey, not the one you find in Windows Explorer.

I can't say if the timestamps changed in MediaMonkey, but they didn't change to the scan date.