View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010527 | MMW v4 | Synchronization | public | 2013-02-14 17:04 | 2013-07-05 21:54 |
Reporter | lowlander | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 4.1 | ||||
Fixed in Version | 4.1 | ||||
Summary | 0010527: Log shows delphi expections on connection of Sansa Clip+ | ||||
Description | Log shows delphi expections on connection of Sansa Clip+. Note no errors are evident in MediaMonkey, it's just shown in DBGView. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 1625 | ||||
|
You are true, in the log there are some exceptions while Querying device capabilities, but looking into the code and and the log they doesn't seem to be important as they are catched and capabilities are found: WMDM: Supports M3U playlists WMDM: Supports PLA playlists WMDM: Supported formats: MP3, WMA, WAV, FLAC, OGG, AA, M3U etc. So unless you find an usability problem, I think they are fine. What exact model of Snasa Clip+ it is? I am thinking about getting one own for testing purposes and to debug some others issues reported with Sansa Clip+ |
|
There seems to be no negative impact, but I haven't done anything but connect/disconnect the 4GB Sansa Clip+ (ie. no syncing was done) |
|
Could you please generate another log using attached d_WMDM.dll ? |
|
With the new dll the device rebuilds its db after first connect/disconnect (no sync), but not after second connect. The Delphi errors seem gone [debug2.zip] Note: even after restart of MM I can't reproduce device rebuilding, so it may have been a new dll first run issue (log may show why). |
|
OK, according to the log it seems to be resolved and MM now extracts properly Sansa Clip+ capabilities. Fixed in build 1625. |
|
Verified 1646 for regressions with all my devices Closing as no additional reports are received. |