Thanks. It's planned and specced for 4.1:
http://www.ventismedia.com/mantis/view.php?id=9368

BUT, you should see further performance improvements in 4.0.5 build 1493.

-Rusty

[quote="rusty"][quote]But it seem logical to me that the sync destination list would be the same as the scan destination list.[/quote]

I think that the only real solution will be to give users the flexibility to configure MM to scan other additional destinations.

-Rusty[/quote]

+1 from me as well.
In my opinion MediaMonkey should honor the synchronize directories as well as the ignore directories, regardless of the type of device.
I'm not too happy about the fact that MediaMonkey tries to open and read all images, video files, DVD files, etcetera on devices, even though the folders are set to ignore. It takes forever on external drives that have lots of photos on it. The ignore folder is there to [b]ignore[/b].
MediaMonkey is not the tool to specify what kind of files reside on the device: I use it to manage my (music) libary, and nothing else.

[quote="rusty"]I think that the only real solution will be to give users the flexibility to configure MM to scan other additional destinations.[/quote]

I agree. (for what it is worth)

[quote]But it seem logical to me that the sync destination list would be the same as the scan destination list.[/quote]

That seemed logical to us as well, and we'd implemented something like that during the course of MM 4.0.0 beta testing. But we found that some users have tracks on their phones that are in directories that they don't want to sync, so we had to undo the change.

I think that the only real solution will be to give users the flexibility to configure MM to scan other additional destinations.

-Rusty

[quote="ACraigL"]I thought it did. From my SDCard, I have every destination box set as /Andy/[path to my media]. My expectation is that it only looks in the folders specified here. Maybe I'm wrong.[/quote]

As I understand it, that is just where it looks to sync. But it seem logical to me that the sync destination list would be the same as the scan destination list.

EDIT: from the bug-tracker comments, it looks like that is what Ludek is recommending. "So I would suggest to limit the scanning to sync targets only at least for all android devices connected in MTP mode"

I thought it did. From my SDCard, I have every destination box set as /Andy/[path to my media]. My expectation is that it only looks in the folders specified here. Maybe I'm wrong.

sounds good. Thanks.
It would be very useful if the user could define which folders are scanned. Perhaps an entry in device configuration boxes? Just an idea.

Yes, based on another log I can confirm that folders like Wallpapers includes many files that slows the scanning, therefore I have already added them to ignored folders for build 1491:
http://www.ventismedia.com/mantis/view.php?id=9284#c31143

Yes, I have USB Debugging disabled.

I ran DebugView, and from what I can tell, it is not hanging at all. It is just taking forever to scan the contents of my phone. You can look at the log, but it definitely takes a long time to scan the cache of a wallpaper app, called Wallbase, and a OneNote app, called MobileNoter, that I use. Apparently, the cache for those two apps are quite large. So maybe this is normal? But I don't think my setup is all that abnormal. That is, there are bound to be many MM users that use apps with a large cache on their phone.

Anyways, I let the DebugView run for a few minutes and then saved the log to a file. I also generated a log of my GNex's internal structure and I am going to PM you and Lowlander both of the files.

Please keep me posted. Thanks

I have Galaxy Nexus and the scanning process takes just several seconds with 1490 for me.

Could you generate debug log while the "Scanning..." is in process?

Item 4B) here http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=341

Based on the log I can tell you what happens.

BTW. Do you have disabled USB debbuging in your Nexus? It is disabled by default, but for sure.

Thank you.

Yes, definitely.

Is your Galaxy Nexus really running in MTP mode?

Unfortunately scanning still grinds to a halt for me on my Galaxy Nexus. But I actually suspect that it is an issue with the Galaxy Nexus more than with MediaMonkey. It might be this Google bug? http://code.google.com/p/android/issues/detail?id=23090

Is anyone else having success with the Galaxy Nexus?

Great thanks!

Note that this should be improved (and also tested with) build 1490.