Transcoding combinations UPnP and Internet Radio

[Pastim]

(13-03-2015 18:57)simoncn Wrote:  

(13-03-2015 18:41)Pastim Wrote:  Ah Ha! At last. Somewhere down the line, having said I was missing something fundamental, I have never noticed that this was the case. You may well have said so, or implied so, but I've not taken it in. You did say 'will not be transcoded' against my examples of this, but I did not realise the full import of what you said (I foolishly assumed that you meant it was somehow picking up the - part without the ^). So I have always assumed it was not completely ignored, and so have gone round and round in ever decreasing circles failing to find a workable solution that I can understand and make work.

If there are others who might fall into the same confusion it might help to have a brief mention in the user guide.

I won't ask why this is the way it works, I'm just happy to now know.

Thanks again.

I'm pleased this conversation has reached a successful conclusion.

The user guide covers UPnP only. The instructions for internet radio are on the MinimRadio page and I have chosen not to complicate this page by discussing transcoding there.

The "*" case was introduced because some UPnP control points and renderers need to know the stream type in advance before they open the stream. Using the "*" case enables MinimStreamer to give the control point the transcoded stream type in advance even though MinimStreamer doesn't know the actual stream type in advance. This situation doesn't arise for internet radio, so the "*" case doesn't apply there.

Ok. I won't ask why it doesn't arise for an Internet radio device. I'd rather hoped for a 'This option is only applicable to UPnP devices' against the "*" option, but I will make my own notes instead, because I will not remember this in 1 months time and don't want to fall into the trap (of my own making) again.

The End.