It would certainly be possible in this particular case, but the whole memory management of tracks data is a more complicated issue which we will hopefully improve soon.

Jiri

Why doesn't the queue read the current metadata at the point in time the file is modified instead of when they were queued?

It wasn't really fixed in MM3 (at least not yet), but it can be prevented by using the automatic volume leveling analyzation in MM3, because it doesn't require that long lists of tracks to be created for analyzation, it's handled internally by MM.

Jiri

Anyone know if the issue is resolved in MM v3?

That is certainly one of the most annoying traits of MediaMonkey.

Yea that is annoying.

What is happening is thus:

- you queue up a bunch of files to get analyze volume
- you change any metadata BEFORE the file gets analyzed
- AFTER you changed the metadata, THEN the file gets analyzed, MM REVERTS to the previous metadata that was there when the file was queued

I'm using MediaMonkey Gold v2.5.4.978 on Windows XP SP2

I have a music library of about 7000+ tracks, none of which had any volume-leveling performed on them yet, so I selected all of them by pressing Ctrl+A from the "Artist" view node, and went to Tools > Analyze Volume. From the progress meter at the bottom, I saw that this process was going to take a while to perform on 7000+ tracks, so while that was in progress I decided to go through and rate my tracks, by right-clicking on each track and selecting a rating from "My Rating" in the popup menu.

I soon noticed that as each track became volume-leveled (that is, a volume-level value would appear in the "Leveling" column), the rating which I had set on the track would become erased.