MinimStreamer connection to Cambridge StreamMagic problems.

[simoncn]

The BubbleUPnP control point is telling the selected renderer to play a stream from a URL. From that point, the control point is out of the picture and the renderer is talking directly to the URL server (either a BBC server or MinimStreamer). The BubbleUPnP renderer is reading the stream without using byte-range requests, so everything is fine. The Stream Magic renderer is using byte-range requests to read the stream and this is incompatible with playing a radio stream.

As you say, the Radio function of Cambridge Connect and/or the Stream Magic must be doing something special to prevent this problem from occurring. Only Cambridge Audio would know exactly what this "something special" is. My expectation is that setting a custom URL for one of the radio presets would trigger this "something special" mode but you have discovered that this doesn't work.

There is another possiblility for the "something special". A BBC URL doesn't point directly to the audio stream but instead points to a .pls playlist file that points to the MP3 or AAC stream. It might be this level of indirection via a .pls file that is triggering the "something special". A MinimStreamer custom URL points directly to the transcoded AAC stream, so there is no indirection and this might cause the "something special" mode not to be activated. I am speculating here and the reason for the difference could be something else.