View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003241 | MMW v4 | Conversion/Leveling | public | 2007-07-09 15:24 | 2013-02-04 13:13 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0003241: Conversion fails (DRM error) when track filename contains Japanese characters | ||||
| Description | User-reported bug. This may be the cause of similar unexplained/occasional conversion problems: Hello I report on the bug that occurs on a specific condition. The following errors occur when the file including a Japanese character string is Convert Audio Format. ---Error message--- File D:\Music\[Japanese character string].mp3 cannot be decoded. It is possibly due to DRM restrictions. | Cancel | | Retry | | Ignore | ---Error message--- If rename [Japanese character string].mp3 to [ASCII character string].mp3, Convert Audio Format complete. This bug occurs by both MM3.0.0.1045 and MM2.5.5. My environment: Windows XP SP2 Japanese Locate Pentium M 1GHz , Memory 512MB 1 DVD/CD-RW Drive, 1HDD (C:/, D:/) MM3.0.0.1045 All default plugin install and enabled. | ||||
| Additional Information | Log and original japanese file are posted to the ftp server | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
It seems that I'm not able to extract the file with Unicode characters. Can you? Using which application? Otherwise, we could ask the user to pack it into a RAR archive, it should work well there. |
|
|
I extracted it using Izarc. I re-uploaded the file and an unzipped version of it. |
|
|
No matter what I try, I see just ordinary characters with accents (i.e. 8-bit ASCII), no Japanese. Do you really see Japanese characters? In such a case, could you repack the file as RAR? It should be easily possible to extract then. |
|
|
what about the log--does that help at all? |
|
|
Not much, the original Japanese file would be the best for testing/resolving the issue. |
|
|
There have been no reports of such an issue in years. Closing. |
