Post Reply 
Update 263 - unexpected behaviour re StreamSize
09-12-2025, 11:37 (This post was last modified: 09-12-2025 11:42 by simoncn.)
Post: #13
RE: Update 263 - unexpected behaviour re StreamSize
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.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Update 263 - unexpected behaviour re StreamSize - simoncn - 09-12-2025 11:37

Forum Jump:


User(s) browsing this thread: 1 Guest(s)