Update 263 - unexpected behaviour re StreamSize

[FakePlasticDunk]

Possibly strange question, but with my stream definitions as above, and my transcode options as

*:L16,aac:L16

should my local stream URLs be of the format

http://192.168.1.9:9790/minimstreamer/*/Rn/$!transcode.L16

or is that last transcode part redundant? I am not selecting these from a playlist, they're in presets on the NP30.

[FakePlasticDunk]

I'm pretty sure that last transcode part is redundant - I think I know what I did, and what the speech stations and Paradise stations thus had in common when everything else stopped working:

I recently had reason to reset the presets for the two speech stations. Having forgotten the format - the presets are write-only, annoyingly - I flipped through my notes and found the template for the Paradise stations, which all have that /$!transcode.L16 on the end, and erroneously used that. It worked fine, so I didn't realise my mistake. I'm guessing that the /$!transcode.L16 somehow bypassed whatever was causing the problem with everything else. Does that sound plausible?

[simoncn]

The /$!transcode.L16 suffix on a stream URL tells MinimStreamer (in advance) to transcode the stream to L16 and means that MinimServer has informed the control point and renderer that it is an L16 stream. It is added to the URL created by MinimServer because the stream type in the .m3u file is aac and you have aac:L16 in stream.transcode. This was working correctly with MinimStreamer 2.1.1.

If you remove the /$!transcode.L16 suffix, MinimStreamer and the control point and renderer don't know the stream type in advance. MinimStreamer checks the stream type when it receives the stream from the network stream server and finds that it is aac. Because stream.transcode contains aac:L16, MinimStreamer makes an "on the fly" decision to transcode the stream to L16 and send the stream to the renderer as L16. This was not working with MinimStreamer 2.1.1 and produced a NullPointerException.

Now that the NullPointerException problem has been fixed in MinimStreamer 2.1.2, you can use either of the above approaches.

[FakePlasticDunk]

Thanks Simon, that's clear. It explains the discrepancies in behaviour between my various streams, and between mine and others', before the fix was applied.