View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002493 | MMW v4 | Synchronization | public | 2006-05-12 16:24 | 2007-09-11 20:38 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0002493: Device Synchronization: 'Copy .m3u playlist' setting is ignored | ||||
| Description | When synching a USM device using the wmdm driver, a playlist is copied to the device even when configured not to. Per discussion, this was implemented for the same reason as playlists are always synched for iPods--because MTP devices usually support the playlists. However, this doesn't take into account the fact that: a) There are MTP devices that may not support the playlists b) There are USM devices that may not support the playlists c) for both a) and b), it is possible that copying the playlist and associated directory will cause problems for the device. Thus, the recommended approach would be: -If the MTP device indicates that playlists are supported, then the driver can automatically create playlists in the device DB (however, the users configuration should still match what happens on the device). -If the MTP device doesn't indicate that playlists are supported, then the users configuration should tell MM what to do. -If a USM device is using the MTP driver, then the users configuration should tell MM what to do. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
In order to make it fully consistent how about: - Change 'Copy M3U playlists' to 'Copy playlists' - By default this option would be used for all items (artists, albums, etc.), but the logic could be overriden in the Advanced mode of synchronization tree for individual items. - Disable 'Destination directory' for devices where it doesn't make sense (currently only iPod). |
|
|
Per discussion over IM: For a USM device: [x] Copy playlists would be enabled and directory would be configurable. Iff enabled, All playlists are copied. For an MTP device that indicates that playlists ARE supported: [O] Copy playlists would be 'forced' to enabled, and directory configuration enabled. If enabled, only actual playlists would be copied (as per current implementation). For an MTP device that doesn't indicate playlist support or a USM device using the MTP driver: [ ] Copy playlists would be manually configurable, and directory configuration configurable or greyed out depending on the state of the checkbox. If enabled, only actual playlists would be copied (though it would probably be preferable that ALL Playlists be copied for this scenario). For an iPod device: It would be forced enabled with directory configuration greyed out. If enabled, no playlists would be copied (only db updated). For another custom driver for a database driven device (e.g. H320): It would be forced enabled with directory configuration enabled. |
|
|
Fixed in build 863. |
|
|
Verified build 962--all categories of device synchronize correctly. iPod: Nice UI touch, just greying out the checkbox. MTP ifp880: If Copy Playlists enabled, then ALL playlists copied. creative sleek: If Copy Playlists enabled, then only playlists copied. H10: If Copy Playlists enabled, then only playlists copied. Creative Vision: If Copy Playlists enabled, then only playlists copied USB Generic Driver If Copy Playlists enabled, then ALL playlists copied. |
|
|
A user with the Dell DJ indicated that MM doesn't create Playlists on the device for Albums that have been explicitly added to the Synch List. He also indicated that this problem started with MM 2.5.2 and 2.5.3, but that MM 2.5.1 works. This is consistent with Jiri's statement that in 2.5.2 a fix was added "For devices that report over WMDM that they support some format (mp3, wma, m3u) these playlists aren't created because it's quite likely the device has also some kind of DB." I'm quite sure there are other devices with this problem (i.e. where our assumption is incorrect). Effectively, we need another way of determining whether a device has a DB. |
|
|
This one was already fixed, because user can now configure which entities need Playlists on the device. |
