Autosynchronize always synchronizes some directories

Beta Testing for Windows Products and plugins

Moderator: Gurus

MrMoo
Posts: 21
Joined: Sat Feb 25, 2006 4:49 pm

Autosynchronize always synchronizes some directories

Post by MrMoo »

MM 2.5.2.943 beta 2, synchronizing with a Creative Labs Vision:M (MTP device, latest Vision:M firmware).

It seems that, when using "Synchronize only the following" for auto-synchronization settings, the contents of some directories are always synchronized, regardless of whether or not the files have actually changed.

After a lot of trial-and-error, including wiping all music off my Vision:M :cry: , it seems that this problem is triggered by setting a non-default destination for a directory (i.e., under "Synchronize only the following", enable advanced settings, and change the device destination from "Default" to something else). In my case, I've set the destination to "\Music\<path:5>".

Unfortunately, every directory, with a non-default destination path, gets re-transferred every time I do an auto-sync. I verified this by making two identical copies of a directory containing MP3 files. I set one directory to auto-sync with the default destination. The other directory was configured to use a non-default destination. Autosynching would then always transfer the directory with the non-default destination.

I can give a lot more information, including the (freely redistributable) MP3 files that I used to narrow down this problem. I've tried using the debug version, but DebugView doesn't seem to give any useful information, aside from "Uploading track ...", "Uploading to ...", etc.
MrMoo
Posts: 21
Joined: Sat Feb 25, 2006 4:49 pm

Post by MrMoo »

Just FYI, this issue still exists in 2.5.2.947 RC-1.

Also, I don't know if this can be addressed for the final 2.5.2, but I'd just like to mention that this significantly affects podcast users, among others. I'd like to synchronize podcast files into certain directories on my MP3 player, and this issue causes all of the podcast files to be re-transferred, even though almost nothing may have changed. In my case, we're talking hundreds of megabytes (if I actually used this feature, which I can't, because of this bug).
jiri
Posts: 5431
Joined: Tue Aug 14, 2001 7:00 pm
Location: Czech Republic
Contact:

Post by jiri »

Thanks, this will be fixed in the next release.

Jiri
MrMoo
Posts: 21
Joined: Sat Feb 25, 2006 4:49 pm

Post by MrMoo »

Great news, thanks!
MrMoo
Posts: 21
Joined: Sat Feb 25, 2006 4:49 pm

Post by MrMoo »

It appears to be fixed in 2.5.2.948 RC-2. Yay!
Post Reply