View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007522 | MMW v4 | Synchronization | public | 2011-03-15 00:51 | 2011-05-13 21:56 |
Reporter | peke | Assigned To | |||
Priority | urgent | Severity | tweak | Reproducibility | always |
Status | feedback | Resolution | reopened | ||
Summary | 0007522: Sync Path Is Ignored by wmdm plugin | ||||
Description | In MM3, a workaround was introduced for the WMDM plugin (manual setting COMApartmentThreading=1 ) which solves the failed synchronization for a number of devices. See more info at: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=16 This mode of operation should be introduced into MM4 sync profiles so that users can automatically sync to this growing list of devices which otherwise require the user to manually edit config files. | ||||
Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=12&t=56743 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Reminder sent to: jiri, rusty Triage Needed. |
|
Not a bad idea, but I'd rather not do so because: 1. It would be a new UI option, which isn't needed for most users. 2. It changes whole d_WMDM behavior, it can't be done to make a difference for one device only. |
|
What do you say that I make small Script that will add Additional Sheet in options regarding this setting. Compromise solution to cover both reasons you stated? |
|
You certainly can try it, but I don't think that it would be too useful, because if user finds that script/addon, he could find the KB article about it as well. Also note that a restart of MM would be needed. |
|
Updated descriptions. Re 2: I wonder if COMApartmentThreading=1 can be default one apron MM install I do not see any regressions when used with devices which work without it. |
|
It really seems that we have to leave it as is, this is my comment as taken from MM sources: It seems that this thread _has_ to be again COINIT_MULTITHREADED otherwise some users have reported problems with some devices (termination of synchronization). |
|
Cleared Bug info and left as resolved, won't fix in case of future needs to reopen. |
|
Note: the list of devices with this problem is getting bigger and bigger. See: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=16 Other recent reports indicate that the problem is occuring: - on some android devices: http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=11825 - on latest generation archos devices: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=56279 |
|
Reopening for me to review handling of MSC devices, where the problem shouldn't occur (since MM knows that the device has a drive letter and can be accessed as any other drive). |