I can’t comment as to the top resolution limit of these as at the time I don’t recall what was the highest resolution files I had at the time. (Simple nested folders genre\artist\album\track files, with album names carrying essential info to differentiate, and track names usually simply as ripped or downloaded, just with added leading track number if spotted as missing at the time.) That meant it didn’t matter how complete or consistent metadata might be, or even if chunks or all were missing - in particular with classical that was a real boon.
MINIMSERVER FEATURES SOFTWARE
The absolute beauty of both LMS and Serviio with the ND5XS, though I don’t know if down to the server software or the player, was that I could browse and search perfectly using the file structure I had set up in the store. It also did what it said on the tin, serving music files to the ND5XS without a hitch, and likewise was a doddle to set up.
MINIMSERVER FEATURES FREE
When I abandoned the NSA325 NAS due to it being very noisy (acoustically), replacing it with a Mac Mini functioning as a NAS, I used Serviio, which was a free app. It did what it said on the tin, serving music files to the ND5XS without a hitch, and was a doddle to set up. Twonky, which came free with the cheap NAS (NSA325): it worked, however I didn’t like it, though I don’t remember any specifics as to what I didn’t like as it was some time ago, though I think it was more the awkwardness of setting up than performance.
I no longer use UPnP as I don’t stream my music across a network, but when I did, feeding an ND5XS, I used three UPnP servers in turn: I have yet to see a good control point for desktop use. Until that is done, we use mainly the Lumin control point on mobile and tablet. We have an Open Home control point in the making right now and have started looking into the possibilities of supporting multiroom. On top of this, we put BubbleUPnP to support shared playlists and multiple control points. VTuner and TuneIn are fine for browsing new radio stations but much too tedious for daily listening. The accumulated price is simply too high for that one feature, however brilliantly it may work.Įven if it is cumbersome to configure, the MinimServer is very flexible when it comes to metadata structure, which allows us to have radio stations inline with albums and podcasts, and present it on the control point in an intuitive manner. However, since we only use the streaming part and none of the augmented metadata features, we have chosen to phase it out in favour of Open Home. Roon is very, very smooth and handles diverse renderers very well. However, having not just Naim renderers, we needed something which would allow us to play multiroom and thus purchased Roon. Then when we bought the Naims, we purchased AssetUPnP to replace LMS. We kept the Transport for dedicated listening until we finally had to throw in the towel. Unfortunately, the control points slowly deteriorated, accounting for our diversion into Sonos.
LMS/SB was a perfect match for us, with a Transporter as the centrepiece. The past 6 months we have been using MinimServer with BubbleUPnP (for Open Home). My question now is if this could be fixed by the Limetech team or if there is any reason of how Limetech was defining the loopback adapter.We started with Squeezebox almost 15 years ago and went from there to Sonos (and regretted that profoundly) and went back and then via AssetUPnP onto Roon. As a workaround, I have used the command ip addr del 127.0.0.1/32 dev lo" The second of these bind attempts fails. The 127.0.0.1/8 combination is a superset of 127.0.0.1/32 and I can't see any reason why both would be needed. The ohNet UPnP stack (used by MinimServer) can't handle this because it treats 127.0.0.1/32 and 127.0.0.1/8 as if they were separate adapters and tries to bind both of these "adapters" to different sockets listening on address 127.0.0.1 port 9791. Here is an extract from the output of 'ip addr':ġ: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 The root cause is the following as identified by Simon who is the Minimserver developer: "unRAID is defining the loopback adapter with two different netmask values. MinimServer: ohNet port 9791 is already in use However Minimserver was not starting and came up with this message in the log file:
MINIMSERVER FEATURES DOWNLOAD
1) Create a folder to be used for building the Docker imageĢ) Download the file MinimServer-0.8.4. and save it in this folderģ) Download the file Dockerfile.bin save it in this folder and rename it to DockerfileĤ) In a terminal window, change directory to this folder and run the following commands:ĭocker run -p:1900:1900/udp -p:9790:9790 -p:9791:9791 -net=host minimserver:0.8.4.7
0 kommentar(er)
