[quote="rusty"]Teapot,

Thanks--fixed in build 1279: http://www.ventismedia.com/mantis/view.php?id=6089

-Rusty[/quote]

I'll download the latest build and give it a workout. :D

Terry

Teapot,

Thanks--fixed in build 1279: http://www.ventismedia.com/mantis/view.php?id=6089

-Rusty

[quote="Ludek"]Studing the log I guess that the problem is that MM auto-analyzes the song while you want to deleted it. You should try to disable Tools->Options->Volume leveling->'[x] Auto-analyze volume of unanalyzed Tracks' on the background feature in order to see if it helps. We should probably enter new issue so that MM would properly terminate auto-analyzation thread when an user tried to delete the folder where it lies.[/quote]

As per your request, I unchecked the General Volume Leveling options, then I deleted the 12 tracks from my previous test from the Library and computer. I copied the same 13 files, 12 .mpg and 1 .jpg, to the temporary staging area on C: and used Windows Explorer to drag & drop them onto the Library node. I got a message that the .jpg file already existed (forgot had been added previously). Until I answered, nothing happened. As soon as I answered, MM added and Auto-organized the 12 .mp3 files with no error messages.

As a second test, I left the all General Volume Leveling options unchecked and deleted the 12 tracks from the previous test from the Library and computer. This time, I copied only the 12 .mpg files to the temporary staging area on C: and used Windows Explorer to drag & drop them onto the Library node. I got 12 messages that the folder on C: couldn't be deleted. After answering the 12th message, MM added the 12 tracks and Auto-organized them to the G: drive per the Mask.

As a third test, I left the all General Volume Leveling options unchecked, unchecked the Delete emptied folders option and deleted the 12 tracks from the previous tests from the Library and computer. I copied only the 12 .mpg files to the temporary staging area on C: and used Windows Explorer to drag & drop them onto the Library node. MM almost instantly added and Auto-organized the tracks without any messages.

As a fourth test, I checked the Volume Auto-analyze and Leveling options, left the Delete emptied folders option unchecked and deleted the 12 tracks from the previous tests from the Library and computer. I copied only the 12 .mpg files to the temporary staging area on C: and used Windows Explorer to drag & drop them onto the Library node. MM almost instantly added, Auto-organized and began Auto-analyzing the track volumes without any messages.

From these tests, it appears that the Delete Empty Folders option is where the issue lies. I would think that MM should only delete empty folders when it empties them through it's own processes, not when I use an outside process like drag & drop to empty a folder outside the Library (as defined by the Mask).

Let me know how else I can help.

Studing the log I guess that the problem is that MM auto-analyzes the song while you want to deleted it. You should try to disable Tools->Options->Volume leveling->'[x] Auto-analyze volume of unanalyzed Tracks' on the background feature in order to see if it helps. We should probably enter new issue so that MM would properly terminate auto-analyzation thread when an user tried to delete the folder where it lies.

[quote="rusty"]teapot, re. the problem with the error messages re. deleting a folder, we still can't replicate using build 1277. Can you generate a debug log as described at:
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=341

That'll give us the information needed to figure out why this is happening.

Thanks.

-Rusty[/quote]

Just finished putting it together and sent to the Helpdesk.

teapot, re. the problem with the error messages re. deleting a folder, we still can't replicate using build 1277. Can you generate a debug log as described at:
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=341

That'll give us the information needed to figure out why this is happening.

Thanks.

-Rusty

I have the Gold version which has always allowed me to use Windows Explorer to add tracks to my MM Library. I have a process for adding new music where the files are accumulated in a New Music folder, then when I'm ready to add them, I use Windows Explorer to highlight, drag & drop some or all of them on to the Library node. I have auto-organize set to automatic and a mask defined in Options. The tracks are being added to the Library and auto-organize is moving them to the drive and location as defined in the mask just fine. The issue is that I'm getting a message that MM can't delete my New Music folder for EACH track that I'm adding to the Library in this manner. If I add 100 .mp3 files, I get 100 messages. In releases prior to 3.1, I didn't get ANY messages during this process.

The progress bar only seems to do this when new tracks are added to the MM Library with drag & drop from Windows Explorer. I don't use File Monitor and seldom use Add/Rescan as I want more granular control when adding new music. I'll do some more testing to see if I can provide more details or a movie.

Teapot,

Thanks for the feedback.
[quote]
I get a "Cannot delete directory" message for each track when I use Windows Explorer to drag & drop new files into the Library. I have the folder where I store my new music files before putting them into MM set to read-only to prevent this from happening, but 3.0 didn't give me this message.[/quote]
I can't replicate this--but I'm not sure I understand what you're doing;
- If I drag files from Windows Explorer into MM's library node it just adds them to the library, same for folders
- If I drag them with auto-organize enabled, then they get organized correctly (even if read-only flag is enabled)
- If I try to drag tracks from Windows Explorer to a particular Locations > C:/ >... node in MediaMonkey, I'm not able to (but I don't think that MediaMonkey ever supported a 'move' operation from a Windows Explorer folder to a MediaMonkey tree > Locations folder.
Please explain a bit more.

[quote]The progress bar is now going to 100% before the process is completed for the number of tracks being processed, then jumping back to less than 100% and completing normally on the last few tracks. For instance, after dropping 22 .mp3 tracks on the Library, MM was analyzing the sound for the 17th of 22 when it reached 100%, then jumped back to about 80% and finished normally reaching 100% at the end of the 22nd track.[/quote]
When I scan a folder, MM scans the folder correctly (the progress bar doesn't move back and forth). Can you make a video of this?

[quote]The track browser columns are not automatically updating when changes are made to tracks. For instance, renaming a misspelled Artist name on the only tracks with that error is not removing the name from the Artist column until opening another Library node or using refresh.[/quote]
This was never the case in previous builds, but I'll add it to our todo list.

Thanks again.

-Rusty

For the first time since 3.1 was released, I can use Windows Explorer to drag and drop new tracks into the Library again ! Thank you, thank you, thank you.

These may be the normal behaviors, but I didn't start noticing them until 3.1 was released.

Good:
The quickness is back. Instead of over a minute delay before MM starts to process new tracks, it's back to being seconds.

Bad:
I get a "Cannot delete directory" message for each track when I use Windows Explorer to drag & drop new files into the Library. I have the folder where I store my new music files before putting them into MM set to read-only to prevent this from happening, but 3.0 didn't give me this message.

The progress bar is now going to 100% before the process is completed for the number of tracks being processed, then jumping back to less than 100% and completing normally on the last few tracks. For instance, after dropping 22 .mp3 tracks on the Library, MM was analyzing the sound for the 17th of 22 when it reached 100%, then jumped back to about 80% and finished normally reaching 100% at the end of the 22nd track.

The track browser columns are not automatically updating when changes are made to tracks. For instance, renaming a misspelled Artist name on the only tracks with that error is not removing the name from the Artist column until opening another Library node or using refresh.

Thank you for all the hard work you all put in to make MM the BEST music manager out there !!!