View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013169 | MMA | UPnP / Casting | public | 2016-03-04 21:00 | 2016-03-28 21:03 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.1.3 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0013169: UPnP rendering fails for tracks containing '&' in the filename to certain devices | ||||
| Description | As reported at http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=82817 , when MMA plays tracks containing '&' or other foreign characters, they'll work with most devices, but not with some such as a Denon or Airplay player. Strangely, according to one user, MMW does render correctly in such cases. Is MMA doing something differently than other renderer apps in terms of substituting certain characters or using a certain character set? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 585 | ||||
|
|
I can't replicate it on any renderer, but I tested it deeply and I changed encoding local path to uri by Uri.encode(path, "/"); Description of this method: // * Encodes characters in the given string as '%'-escaped octets // * using the UTF-8 scheme. Leaves letters ("A-Z", "a-z"), numbers // * ("0-9"), and unreserved characters ("_-!.~'()*") intact. It's working well now on all my Upnp Renderers and Chromecast too. Fixed in build 1.2.0.0585 |
|
|
Verified 585 |
