View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001663 | MMW v4 | Synchronization | public | 2004-12-14 01:29 | 2010-11-22 18:22 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Summary | 0001663: Problems with MM Created DB for H120/H140 devices | ||||
| Description | According to one user, MM-created DB doesn't work correctly for some tracks (it's impossible to play those tracks) on H120/H140 devices. I hope that we'll receive more feedback on this issue, but one possibility is to change the default encoding for the db contents on those devices. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?t=2913 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 820 | ||||
|
|
Fixed in build 820. - iRiver plug-in has a new option - ASCII or Unicode DB format. |
|
|
I can't test this, but I just wanted to ask: Does it default to unicode for H320 and ASCII for H120/H140? |
|
|
No, the default is always Unicode for now. The reason it that I don't have H140 and can't test neither USB device IDs, nor how different firmware versions handle ASCII/Unicode. We might change it in the future depending on feedback or additional testing with devices. |
|
|
Re-opening to discuss further: based on user feedback to-date, the latest firmware for H1xxx doesn't work with Unicode as default. This means that users of those devices _will_ have problems with mm with the default setting. Doesn't this merit changing the default setting for those particular devices? |
|
|
I don't think there necessary must be problems with H140, according to one user report there can be problems with files >52 chars and Unicode. If we choose ASCII, there can be other problems with character sets. Also, I can't test it with H140 (not sure about its USB ID, how is it with its firmwares etc.). So I don't think we should do anything about it until we have some testing device (and maybe not even then). |
|
|
Closing, due the user confirmation of firmware bug |
