Post Reply 
Changes to WAV transcoding in MinimStreamer 2.1
05-12-2025, 11:56
Post: #1
Changes to WAV transcoding in MinimStreamer 2.1
MinimStreamer 2.1 has been released. It has new support for WAV transcoding for network streams and local files to handle large streams that exceed the size limit of 4GB imposed by the WAV specification (or 2GB for some renderers).

This support is provided by a new wavLimit option in the stream.options property. For details of how this option works, see this section of the MinimStreamer user guide.

Please post any questions about this here.
Find all posts by this user
Quote this message in a reply
05-12-2025, 15:09
Post: #2
RE: Changes to WAV transcoding in MinimStreamer 2.1
I have my server on a Synology DS218+ and I'm finding that I'm required to specify wavLimit for it to work, otherwise nothing plays and I get exceptions in the Log. Is that supposed to be the case? The webpage says 4GB is the default, which I thought would mean you don't need to specify it.

My settings:
stream.options: convOut=-af volume=replaygain=album
stream.transcode: mp3:wav, flac:wav;

If I add wavLimit=4GB to stream.options it all works fine.
Find all posts by this user
Quote this message in a reply
05-12-2025, 17:08 (This post was last modified: 05-12-2025 17:13 by RSJ.)
Post: #3
RE: Changes to WAV transcoding in MinimStreamer 2.1
Following today's update, MinimServer is no longer working. While it is running (on a QNAP NAS), the playlist runs through without any tracks playing.

Update: It seems that the following stream.transcode instruction no longer works - flac:wav24;192
Find all posts by this user
Quote this message in a reply
05-12-2025, 18:23
Post: #4
RE: Changes to WAV transcoding in MinimStreamer 2.1
This problem should be fixed now in MinimStreamer 2.1.1, just released. My apologies for the inconvenience this has caused.
Find all posts by this user
Quote this message in a reply
05-12-2025, 20:26
Post: #5
RE: Changes to WAV transcoding in MinimStreamer 2.1
Just tested it and it's working great! Thank you for the quick response.
Find all posts by this user
Quote this message in a reply
06-12-2025, 00:43
Post: #6
RE: Changes to WAV transcoding in MinimStreamer 2.1
The user guide says, "The stream ID can be any identifier of your choice or it can be specified as an asterisk (*)."

I installed Minimstreamer version 2.1.1. I set
stream.transcode: *:wav;
but when I played a .flac file, it remained .flac according to BubbleUpNP, rendering to a HEOS device. I had to set
stream.transcode: flac:wav,aac:wav,mp3:wav,*:wav;
in order to get all those files and streams to be transcoded.

Do I misunderstand what an asterisk does?
Find all posts by this user
Quote this message in a reply
06-12-2025, 13:06
Post: #7
RE: Changes to WAV transcoding in MinimStreamer 2.1
(05-12-2025 18:23)simoncn Wrote:  This problem should be fixed now in MinimStreamer 2.1.1, just released. My apologies for the inconvenience this has caused.

All good, now. Thank you.
Find all posts by this user
Quote this message in a reply
06-12-2025, 21:04
Post: #8
RE: Changes to WAV transcoding in MinimStreamer 2.1
(06-12-2025 00:43)Charles7 Wrote:  The user guide says, "The stream ID can be any identifier of your choice or it can be specified as an asterisk (*)."

I installed Minimstreamer version 2.1.1. I set
stream.transcode: *:wav;
but when I played a .flac file, it remained .flac according to BubbleUpNP, rendering to a HEOS device. I had to set
stream.transcode: flac:wav,aac:wav,mp3:wav,*:wav;
in order to get all those files and streams to be transcoded.

Do I misunderstand what an asterisk does?

The stream ID is not part of the stream.transcode property. It appears in a .m3u playlist that contains network streams that need to be routed through MinimStreamer for transcoding or other processing (see this section).

An asterisk in the stream.transcode property is used to specify transcoding settings for network streams of unspecified type (see this section). It does not affect transcoding of local files.
Find all posts by this user
Quote this message in a reply
06-12-2025, 21:18
Post: #9
RE: Changes to WAV transcoding in MinimStreamer 2.1
(06-12-2025 21:04)simoncn Wrote:  ...
An asterisk in the stream.transcode property is used to specify transcoding settings for network streams of unspecified type ... It does not affect transcoding of local files.

I found that *:wav; does not cause transcoding of local files nor of network streams. The streams are of specified type, such as .mp3 or .aac.

Anyway, it is clear that an asterisk here is not a general wildcard as it is in other contexts like directory commands in Windows and Linux.
Find all posts by this user
Quote this message in a reply
06-12-2025, 23:41
Post: #10
RE: Changes to WAV transcoding in MinimStreamer 2.1
*:wav transcodes network streams of unknown type, not all network streams. A network stream is of known type if the type is specified in the .m3u file. For example, the stream

#EXTINF:-1,[Linn] Linn Radio Classical
http://radio.linnrecords.com/cast/tunein.php/linnclassical/playlist.pls

has unknown type and would be transcoded by *:wav. If instead this stream were specified as

#EXTINF:-1,[Linn;mp3] Linn Radio Classical
http://radio.linnrecords.com/cast/tunein.php/linnclassical/playlist.pls

the stream would have the known type mp3 and would not be transcoded by *:wav.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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