Transcoding combinations UPnP and Internet Radio

[Pastim]

(13-03-2015 17:29)simoncn Wrote:  

(13-03-2015 14:25)Pastim Wrote:  Simon, I believe you are suggesting *:wav24/L16, aac:wav24/L16/-^ will provide a general solution to aac transcoding whether aac is explicit or not. Can you explain how that works for UPnP of different capabilities plus Internet Radios?

For an internet radio:

When MinimStreamer opens the stream and detects its type is aac, it sends the stream to the internet radio as an untranscoded aac stream because of the caret position in the aac:wav24/L16/-^ setting.

For a UPnP control point and renderer playing an aac stream whose type is specified as aac in the m3u file:

The control point gets three streams of types wav24, L16 and aac. It selects one (starting with wav24) based on the capabilities of the selected renderer.

For a UPnP control point and renderer playing an aac stream whose type is not specified in the m3u file:

The control point gets two streams of types wav24 and L16. It selects one (starting with wav24) based on the capabilities of the selected renderer.

Thanks.

You quote 3 cases, where I had thought there were 4. From previous answers my understanding was that if a '*' case is provided and aac is not explicit, the aac case is ignored, even for Internet Radio, in the same way as for UPnP. Was that incorrect? From your answer it seems that is a significant difference in processing rules that I have missed somewhere down the line.

If the aac case had not been supplied I understand Internet Radio would then have used the '*' case (where ^ is invalid) so would pick the first choice.