+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Update 263 - unexpected behaviour re StreamSize (/showthread.php?tid=7685)
Pages: 1 2
Update 263 - unexpected behaviour re StreamSize - FakePlasticDunk - 07-12-2025 14:06
I just applied Update 263 and got an error when restarting Minimserver about an invalid StreamSize in stream.options. Minimwatch greyed out and was unresponsive, Minimserver didn't seem to be running, so I restarted Minimwatch, and this time it allowed me to have a look at what I had StreamSize set to.
I'm transcoding to L16 and admittedly had the value set rather high, at 100GB - I think for recording a very long programme a while back. I experimented a bit and it seems it won't accept a value higher than 4GB now.
So this is fine, all working ok now, I was just a bit thrown by the error, as we'd previously discussed being able to set StreamSize higher for L16. Is this a deliberate change?
RE: Update 263 - unexpected behaviour re StreamSize - FakePlasticDunk - 07-12-2025 14:38
PS Just remembered that I'd realised that recording wouldn't go via the transcoding process anyway, and so it was pointless setting the StreamSize that high, but obviously forgot to change it back, or decided it didn't matter and left it as was.
RE: Update 263 - unexpected behaviour re StreamSize - simoncn - 07-12-2025 16:20
Thanks for letting me know about this. The incorrect limitation of the streamSize value to 4GB or less is a bug that was introduced inadvertently in MinimStreamer 2.1.
I understand that this isn't affecting what you are doing but it could be a problem for other users. It will be fixed in the next MinimStreamer update.
RE: Update 263 - unexpected behaviour re StreamSize - FakePlasticDunk - 07-12-2025 16:28
Thanks Simon, good to know.
RE: Update 263 - unexpected behaviour re StreamSize - FakePlasticDunk - 08-12-2025 16:34
Further to this, I seem to be experiencing more strange behaviour - since the update to 263 and presumably to Minimstreamer 2.1, I've lost the ability to stream a number of internet radio stations provided by a public service broadcaster who shall not be named, except for the speech stations, which work fine. I've checked the urls I'm using and they work fine in VLC.
Debug log file attached
The key moment seems to be
"Chain: error running chain
java.lang.NullPointerException"
which doesn't sound like anything good, does it.
RE: Update 263 - unexpected behaviour re StreamSize - simoncn - 08-12-2025 21:50
Thanks for reporting this problem and providing the log output. This problem as well as the problem with streamSize should be fixed in MinimStreamer 2.1.2, just released.
RE: Update 263 - unexpected behaviour re StreamSize - FakePlasticDunk - 08-12-2025 22:30
Great, that seems to have done the trick - thanks for the quick response Simon!
It still seems weird that I could stream the public service speech radio stations and even other music stations like Paradise, just not the public service music stations, whereas it seemed to affect all streams for other users.
RE: Update 263 - unexpected behaviour re StreamSize - simoncn - 08-12-2025 22:46
In your case, the problem was triggered by this combination:
1) The network stream entry in your .m3u file didn't specify the stream type (aac)
2) You specified aac:L16 in stream.transcode
RE: Update 263 - unexpected behaviour re StreamSize - FakePlasticDunk - 08-12-2025 22:54
That's odd, because I was under the impression that my .m3u entries for those streams did specify the stream type as aac, unless I've written them incorrectly. They all follow the format
#EXTINF:-1,[Rn;aac,48000] Radio n
Have I erred?
RE: Update 263 - unexpected behaviour re StreamSize - simoncn - 08-12-2025 23:15
Your stream definitions are correct and you shouldn't change them. I have verified that the NullPointerException error also occurs with your stream definitions and MinimStreamer 2.1.1.