AirPlay fail renderer if filename has special chars [#13169]

[Desperos]

I ran into the following MMA issue and found the following work-around:
1. Downloaded an MP3 file from amazon
2. Synched this file from my Windows PC (MM) to my Android device (MMA)
3. In MMA, selected my AirPlay speaker as renderer and tried to play back the file

I was unable to play back the file in this setting. Playback just didn't start. However, playing the file to the "local player" renderer was possible. Also I could play other MP3 files to my AirPlay speaker, just not this particular one (along with some others).

I noticed that those files which I could not play back had special characters (German umlauts: ä,ü, ö) in their filenames. I tried assigning a filename without special characters and it worked. After the renaming I was able to play back these files on my AirPlay speaker like all others.

I submit this report in case someone else runs into this problem. As a work-around, I suggest to configure the synchronization settings for the Android device in such a way that synched files receive <Auto Numbers> as filenames. This can be specified in MM under Tools -> Options -> Portable Device Sync -> (your Android device) -> Configure... -> Options -> "Sync files to" settings.

Hope this helps someone. Thanks to the MM team & community for the great product.

[rusty]

Hi,

Thanks for the report.

Can you confirm whether the issue is specific to MMA (i.e. if you play the same file with another UPnP player, does the Airplay renderer work correctly)?

Thanks.

-Rusty

[Elk]

Hi,

i noticed the same behavior, when rendering mp3 via dlna.
All files with special chars (e.g. ampersand <&>) in their filename can't be played on my Denon AV-Receiver.

Other android players like Airwire does it very well. Also rendering from Mediamonkey on Windows works very well.
I tested it on two android-versions, always the same. It's surly because of the special chars

Please fix it, MM it the best player

MM-Version: 1.1.3.0554

[rusty]

I just tested MMA build 554 rendering a track containing '&' in both the Title and the filename to MMW, to Kodi, to an LG DVD player, and to Bubble UPnP, and in all cases it played correctly. Is it possible that the issue is something other than the '&' symbol (perhaps a combination of the symbol and file format)? Could you send me e.g. via dropbox a file that exhibits the problems?

Thanks.

-Rusty

[Elk]

Hallo Rusty .. Tanks a lot.

Because of your feedback I did a small research.
Properbly it depends on the combination of the reproducing device and file-location, wich proviveds the player.

I rendered from several players to Windows-Mediaplayer
Here are my examples, with the filelocations shown in Windows-Mediaplayer.

From MMA to Windows-Mediaplayer; works well
"http://192.168.2.102:42369/mnt/sdcard/e ... gAJwBzAA=="

From Airwire (Android-App) to Windows Mediapalyer; works well
"http://192.168.2.102:7588/proxy/3188.mp ... gAJwBzAA=="

From Windows Mediaplayer to WindowsMediaplayer; works well
"http://[eh80::7321:9284:g8f2:6255%08]:10246/MDEServer/40233D42-4058-4551-830A-508ECE81B79F/1000.adts?formatID=00000020-A9AF-4584-84E2-55BFEF0A7D7E&WMContentFeatures=DLNA.ORG_PN=AAC_ADTS_320;DLNA.ORG_OP=10;DLNA.ORG_CI=1;DLNA.ORG_FLAGS=01700000000000000000000000000000&WMHME=1&WMDuration=2240000000&WMHMETitle=RQBsAGwAZQAgAEsAaQBuAGcAIAAtACAARQB4ACcAcwAgACYAIABPAGgAJwBzACAAKABPAGYAZgBpAGMA"

So i think, the Denon-AVR dont' get along with the real path and/or file-location. Do you think a workaround is reasonable?

By the way: Renaming the file from e.g. Elle King - Ex's & Oh's.mp3 to Elle King - Ex's u Oh's.mp3 ... -> it works from MMA to my Denon-AVR.

Greeting to where ever you are!

[rusty]

Thanks for the feedback. We're tracking this at:
http://www.ventismedia.com/mantis/view.php?id=13169

btw to reconfirm, does MMW render problematic tracks correctly to the denon device?

Thanks.

-Rusty