View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002094 | MMW v4 | Synchronization | public | 2005-10-24 03:44 | 2005-10-28 05:48 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.5 | ||||
| Summary | 0002094: Playback/browsing problems via Device node when using WMDM driver | ||||
| Description | When a device is mounted and 'connected' to MM via the WMDM driver, there are a couple of problems: 1) If the user tries to browse the tracks of a UMS device, track properties aren't displayed (i.e. information contained within the tags, and other header info does not appear in MM)! The only way to see the info is to browse the device in Windows Explorer. 2) If the user tries to play the tracks on the device (UMS or MTP) via the device node, MM just skips the tracks (they become greyed out)! The only way to play them directly is via Windows Explorer! I've verified this with 2 different iRiver UMS devices (N10 and H10) and the Creative Sleek (MTP). Note: These problems do not occur with the iTunes driver. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 906 | ||||
| related to | 0006275 | closed | Playback fails for (some?) MTP devices |
|
|
Fixed in build 905. - 1&2) were fixed for UMS devices. For devices that don't expose a drive letter this can't be fixed easily, for DRM protected tracks it maybe can't be fixed at all. I plan to make some improvements in this area, but it's a very complicated issue and so it won't be in MM 2.5, possibly in 2.6. |
|
|
Tested in 905 on the N10 device and this still occurs exactly as previously. |
|
|
It works for me and I don't see any reason why it shouldn't. Do you see 'Safely remove' option for this device? Generally speaking playback and editing of properties should work for devices that have this option visible. |
|
|
Tested in 905 and the bug still occurs exactly as previously described (tested with N10 USM device). |
|
|
Fixed in build 906. - As discussed over IM, there wasn't the latest dll included in the installer. |
|
|
Verified 906. |
|
|
Verified 906. |
