MinimServer and Simaudio Moon

[simoncn]

(28-11-2013 00:54)Andre Gosselin Wrote:  Simon,
Many thanks for having taken time to research this issue. Can I ask a few more questions ?
I mentionned in my opening post that creating an OpenHome renderer for the Simaudio Moon renderer through BubbleUPnP server makes the problem disappear. Also, I did not mention that serving the album through the MediaMonkey server (without any transcoding or DSP effects) also works. Do you have any idea of what those 2 softwares do in that case ? Could it be that they implement a bit more "tolerance" when facing illegal or malformed requests, and could'nt such an approach benefit MinimServer and increase its appeal as the best music server ?

I think it's unlikely that another server could handle this error any better than MinimServer is doing. From looking at the log again, it seems that the output stream from MinimServer to the renderer was interrupted by a SocketException at the same time that the malformed request was sent (lines 1129 and 1131). No server would be able to recover from this output stream error.

Given that the problem doesn't occur with the BubbleUPnP OpenHome renderer or MediaMonkey, there is probably some difference in how the OpenHome renderer and MediaMonkey set up the streaming connection to the renderer, and this difference is somehow avoiding the renderer problem. To understand this difference, I would need to see full Wireshark traces for both the working and the failing scenarios.

For the failing case, you would need to run Wireshark on the Windows machine that is hosting MinimServer. For the working case, you would need to run the OpenHome renderer or MediaMonkey on a Windows machine, and run Wireshark on this Windows machine.

In both cases, you would need to start the WireShark trace before the renderer sends the Browse request for the failing track that will be played. For the working case, you can stop the Wireshark trace as soon as the music starts to play. For the failing case, you need to leave the Wireshark trace running until the renderer sends the malformed request, which is about 25 seconds after the request to play the track.

These WireShark traces will be too large to attach to a forum post, so you'll need to upload them to my FTP server.

Quote:I remember the ugly time when we had to face DRM protected music. When peering at the album cover, I see "ADRM" below the London
logo (see attachment). I tried to research the meaning of the ADRM mention, and I am unable to tell wether it has anything to do with DRM. Do you have any idea about that, and could this format (if indeed it is one) be at the heart of my problem ?

Thanks again

Your post doesn't contain an attachment. When adding an attachment, you need to select the attachment file and then click the "Add Attachment" button on the right. If you don't click the button, nothing will be attached.

Please can you also upload one of the failing files to my FTP server. I will look at the file to see if there is anything unusual about it.