MinimServer and Simaudio Moon

[simoncn]

I have made some progress with this. The string 'Wed Nov 27 16:24:03' isn't a malformed request from the renderer, but a dateTime prefix that you have specified in the .logPrefix property.

I'm still not sure why the renderer is producing the "Read timed out" exception, or why this shows up in the log after the "ServerResourceBase: close" message. I think this is probably caused by some internal error condition in the renderer that has caused it to close the HTTP connection. A Wireshark trace for this would be very helpful.

[simoncn]

(28-11-2013 16:59)Andre Gosselin Wrote:  Thanks, files have been sent.

Thanks! These files look OK to me, and they are playing OK as well.

I don't think I'll be able to make further progress on this until I have seen the Wireshark trace for the failing case.

[Andre Gosselin]

(29-11-2013 00:01)simoncn Wrote:  

(28-11-2013 16:59)Andre Gosselin Wrote:  Thanks, files have been sent.

Thanks! These files look OK to me, and they are playing OK as well.

I don't think I'll be able to make further progress on this until I have seen the Wireshark trace for the failing case.

Simon,
Thanks for your reply, and sorry to have taken so long to answer you.

I tried today to rerip the album to see it this could throw some light on my problem. I ripped it in WAV format, no metadata. Everyting streamed OK on the same setup as previously described. I then added metadata one by one, until I set the "AlbumArtist" to "Chopin, Frédéric" (diacritics 'é' are important). The problem reappeared. I experimented with a few combinations on the "é" character:
AlbumArtist = "Chopin, Fredéric" OK
AlbumArtist = "Chopin, Fréderic" OK
AlbumArtist = "Chopin, Frederic" OK
AlbumArtist = "Chopin, Frédéric" FAILURE

It seems that the specific setting "Chopin, Frédéric" with 2 "é" in quick succession is creating the problem. I could verify that all albums in my music library where AlbumArtist is set to this evil string suffer from the same problem.

I never noticed the problem before, maybe because I came somewhat lately to MinimServer and used MediaMonKey before to serve my music. With this server, the problem does not occur, as mentioned before.

I pursued my experiments a bit further, changing components of my setup, one by one. I switched to another music server and reinstalled AssetUPnP which I once tried. The "Moon Mind+AssetUPnP+BubbleUPnP" combination shows the same problem. I switched to another control point, and combinations "Moon Mind+MinimServer+UPnPlay(Android)" and "Moon Mind+MinimServer+MediaHouse (Android)" worked OK.

Finally, combinations "Moon Mind+AssetUPnP+UPnPlay" and "Moon Mind+AssetUPnP+MediaHouse" also worked fine.

This seems to suggest that BubbleUPnP is at the heart of most of the problems, except in the case "Moon Mind+MediaMonkey+BubbleUPnP" which works OK and happened to be my comparison point up to now (so I suspected MinimServer to be the culprit).

Since IMHO the issue seems to lie with the encoding/decoding of diacritics in the XML data stream, do you know from your experience if the way this is done in MinimServer could create some issues for some control points if they are not carefull enough ? Could this be Java specific ?

I am not sure how to exactly and usefully report this problem to the good people (bubbleguum in this case). Is it still necessary to experiment with Wireshark traces ?

Thanks for your help and the time you took so far to answer me.

[simoncn]

(29-11-2013 04:01)Andre Gosselin Wrote:  It seems that the specific setting "Chopin, Frédéric" with 2 "é" in quick succession is creating the problem. I could verify that all albums in my music library where AlbumArtist is set to this evil string suffer from the same problem.

This is excellent progress!

Quote:I never noticed the problem before, maybe because I came somewhat lately to MinimServer and used MediaMonKey before to serve my music. With this server, the problem does not occur, as mentioned before.

It's possible that MediaMonkey doesn't include album artist information in the XML data that it sends to the control point. If so, this would explain the difference. Similarly, it's possible that BubbleUPnP may be sending more information to the renderer than the other control points you have tried.

I've tried playing these files with BubbleUPnP and my Linn DS. This works OK, so it seems that the problem is likely to be related to the specific combination of BubbleUPnP and the MOON MiND.

Quote:Since IMHO the issue seems to lie with the encoding/decoding of diacritics in the XML data stream, do you know from your experience if the way this is done in MinimServer could create some issues for some control points if they are not carefull enough ? Could this be Java specific ?

I don't think this is Java-related. Some control points and renderers have bugs in how they handle UTF-8 accented characters. The specifications are clear on how these should be encoded. It seems likely that either the MOON Mind or BubbleUPnP has a problem in this area.

Quote:I am not sure how to exactly and usefully report this problem to the good people (bubbleguum in this case). Is it still necessary to experiment with Wireshark traces ?

Thanks for your help and the time you took so far to answer me.

I think you can report the problem to bubbleguuum by sending him the information in this post. He will let you know if he needs to see a trace of what data is being exchanged between BubbleUPnP and the MOON MiND. There is no longer any need for you to produce the WireShark traces that I requested for MinimServer.

[bubbleguuum]

André: send me a BubbleUPnP log file playing the offending track.

I don't think it is an XML encoding issue. If it was, it wouldn't make sense for Fréderic (single é) to be successful.

I think it is possibly related to the size of the metadata XML passed to SetAVTransportURI, which is media server and control point specific (depends on how much metadata the media server returns and how much of this metdata the control point sends to the renderer).
I suspect some renderers to fail if passed metadata higher than a certain size.
Also some renderers will fail with stream URLs whose length is higher than a certain size. And minimserver's URL are not particularly short.