Threaded Mode | Linear Mode

simoncn · 20-01-2020, 21:28

Thanks for this feedback. It is my goal to make the user interface more friendly than it is at present but some aspects of this are likely to take some time to implement fully.

Martin H · (This post was last modified: 26-01-2020 15:15 by Martin H.)

Simon - due to real world distractions I have been a stranger to the site of late and had missed this altogether. I understand the rationale pf the 'news' which I hope will work well for you. I and am sure 'we' all appreciate what you have provided for so long based on donations alone. I would like to clarify a couple things.

1 - In practice I use 1 copy of Minimserver actively to serve music from my Melco but as I have added QNAP servers to the house I have installed the minimserver software onto each server for consistency of build really - a habit more than anything - and so it's on a further 4 devices (total of 5). Three of them are always 'stopped' and one is running just in case the Melco was to fail. Again this is just a habit really and I can obviously cope with 3 device license if and when it becomes relevant. But can I check is it 3 devices active (not stopped) or 3 devices installed. As I understand it - this isn't available on the QNAPs yet anyway and so this is perhaps a question for the future really. From what I have read the QNAP versions will continue to work at least until Minimserver 2 is made available - and supported?

2 - Maybe more current is the Melco I have is the original N1A. I can't see that in the minimserver 2 device list and I also just checked that its software version is the latest for that product but at 3.91. so...
i) - is this on your roadmap as a target device for the new software
ii) and if not, will the original version continue to be supported for those devices or is this just a matter of hoping it continues to work.

note - I will go and hunt around the Melco site but perhaps they have binned the N1a as a product which would be disappointing but obviously a different issue. (edit - they have discontinued it)

note - I have read through the thread but couldn't see the answers to these - apologies if I missed them.

simoncn · (This post was last modified: 26-01-2020 17:12 by simoncn.)

The device limit is for devices with MinimServer 2 installed and activated, not for devices that are currently running. If you are not using a device, you can deactivate the license on that device to free up a slot for another device.

Melco are working on a firmware update for the original N1A that will enable MinimServer 2 to be installed. When this is available, I will post an announcement here.

You can continue to use the existing MinimServer 0.8 on an N1A but there will be no more feature enhancements and probably no more bug fixes.

Martin H · 26-01-2020, 18:24

(26-01-2020 17:07)simoncn Wrote: The device limit is for devices with MinimServer 2 installed and activated, not for devices that are currently running. If you are not using a device, you can deactivate the license on that device to free up a slot for another device.

Melco are working on a firmware update for the original N1A that will enable MinimServer 2 to be installed. When this is available, I will post an announcement here.

You can continue to use the existing MinimServer 0.8 on an N1A but there will be no more feature enhancements and probably no more bug fixes.

Simon,

Makes sense and that matches my 'current running server pattern of Melco and hot backup'. I simply won't install it on the other devices. As it stands it won't install on any of my devices but I look forward to signing up as soon as I have a device that it works on. I assume the QNAPs will be somewhere further down your roadmap.

When we have a little less chaos (here at the house) I will check back and see if I am due to make a further donation for the version 1 - that I have been using. I suspect I am. Again many thanks.

simoncn · (This post was last modified: 30-01-2020 09:58 by simoncn.)

The Melco firmware update that enables MinimServer 2 to be installed on a Melco N1 is now available as version 3.92B from the Melco downloads page (USB installer only). For information about how to update a Melco N1 to MinimServer 2 using this firmware, see this page. For more information about installing and runnng MinimServer 2 on Melco devices, see this page.

beckphotonik · 30-01-2020, 18:52

(30-01-2020 09:57)simoncn Wrote: The Melco firmware update that enables MinimServer 2 to be installed on a Melco N1 is now available as version 3.92B from the Melco downloads page (USB installer only). For information about how to update a Melco N1 to MinimServer 2 using this firmware, see this page. For more information about installing and runnng MinimServer 2 on Melco devices, see this page.

Just performed this update. When I activated the trial licence I got an error message in red about absolute paths to my music library being invalid. The system seems to be working fine though. NB I am using Melco v3.92rc that Alan sent me NOT 3.92B if this makes a difference.

simoncn · 30-01-2020, 18:59

Where did you see this message and what exactly did it say?

beckphotonik · 30-01-2020, 19:29

(30-01-2020 18:59)simoncn Wrote: Where did you see this message and what exactly did it say?

Error setting property ContentDir: Not an absolute path: {/mnt/disk1/share/Music}

I now have the error in MinimWatch2 as I have just done a rescan so what should be an absolute path?

beckphotonik · (This post was last modified: 30-01-2020 20:00 by beckphotonik.)

(30-01-2020 19:29)beckphotonik Wrote:
(30-01-2020 18:59)simoncn Wrote: Where did you see this message and what exactly did it say?
Error setting property ContentDir: Not an absolute path: {/mnt/disk1/share/Music}

I now have the error in MinimWatch2 as I have just done a rescan so what should be an absolute path?

Minimwatch2 properties page seems to think the path is ok but the minim watch icon is red and pops up a error dialogue with the path message.

Minimserver.log and minimserver-out.log both show the message

simoncn · 30-01-2020, 20:37

The problem is the {} around the path. You can edit the contentDir field in MinimWatch to remove these.

It seems you have changed the contentDir setting from the default. The default is /mnt/disk1/share and also includes two expansion drives /mnt/expansion1 and /mnt/expansion2. How did you make this change? This information should enable me to work out where the {} came from.