Synology DSM-5.1

Posted by: Mike-B on 09 November 2014

Synology have a new DSM with upgrades called DSM-5.1-5004

It has some nice features & includes a user selectable option to have updates installed automatically

To see whats included go to the Control Panel "Update & Restore"  & touch the "Whats New" tab

Posted on: 11 November 2014 by Mike-B

Have you checked or unchecked the  "downsample to preserve DSM" box ??? on the transcode enable page.   I can't verify as I have no .flac files,  I only use .wav so never transcode.

Posted on: 12 November 2014 by Bananahead

Hi Mike

 

The downsample=false means that it is un-checked.

 

Nigel

Posted on: 12 November 2014 by Mike-B

OK understood

Next question is what does the N streamer analysis indicate on the app & display.  Graeme McA's post says the Naim app shows 96kHz 4608kb/s. with on-the-fly transcoding

When I was playing with transcoding (not sure what DSM rev it was) I got the downsampled 3072kbs number with 96kHz .  I would be more believing of the Naim analysis display number as its math logical

Posted on: 12 November 2014 by Graeme MacArthur
Originally Posted by Mike-B:

OK understood

Next question is what does the N streamer analysis indicate on the app & display.  Graeme McA's post says the Naim app shows 96kHz 4608kb/s. with on-the-fly transcoding

Sorry if I wasn't clear. My straight HD files play at 96kHz 4608kb/s: nothing to do with transcoding. I stopped transcoding from FLAC to WAV because of the between-track glitch I was getting on gapless albums.

Posted on: 12 November 2014 by Foxman50

I believe, although this may have been fixed, that Media Server will convert 24bit to 16bit if you have set it to transcode from flac to wav.

 

As i said this may have been fixed but this was still the case a few months back.

 

Graeme

Posted on: 12 November 2014 by Bananahead
Originally Posted by Mike-B:

OK understood

Next question is what does the N streamer analysis indicate on the app & display.  Graeme McA's post says the Naim app shows 96kHz 4608kb/s. with on-the-fly transcoding

When I was playing with transcoding (not sure what DSM rev it was) I got the downsampled 3072kbs number with 96kHz .  I would be more believing of the Naim analysis display number as its math logical

I don't have the Naim app because they stupidly only support Apple and Android.

Posted on: 12 November 2014 by Mike-B

Foxman,  DSM-5.1 has a downsample enable or not check box

 

Bananahead,  what does your streamer display show

Posted on: 12 November 2014 by Foxman50
Originally Posted by Bananahead:

I don't like that Minimserver needs to be told to re-scan when new music is added because I always forget to force it.

If you forget to do this, as i have on many occasions, you can simply do this from a web page on your tablet/phone device.

 

It opens up a web page and you can simply hit rescan.

 

there are so many features that are not documented very well, but if you ask questions over on the minimserver forum you generally get a quick response, and to be honest when ive asked if something can be done and the response is it already does.

 

Graeme

Posted on: 12 November 2014 by Foxman50
Originally Posted by Mike-B:

Foxman,  DSM-5.1 has a downsample enable or not check box

 

Bananahead,  what does your streamer display show

Cheers Mike, thats good to know.

Posted on: 12 November 2014 by Bananahead
Originally Posted by Mike-B:

Foxman,  DSM-5.1 has a downsample enable or not check box

 

Bananahead,  what does your streamer display show

It shows that it is getting WAV at either 44.1 or 96 but doesn't show a bit depth or rate.

 

Maybe with the next firmware

Posted on: 12 November 2014 by Bananahead
Originally Posted by Foxman50:
Originally Posted by Bananahead:

I don't like that Minimserver needs to be told to re-scan when new music is added because I always forget to force it.

If you forget to do this, as i have on many occasions, you can simply do this from a web page on your tablet/phone device.

 

It opens up a web page and you can simply hit rescan.

 

there are so many features that are not documented very well, but if you ask questions over on the minimserver forum you generally get a quick response, and to be honest when ive asked if something can be done and the response is it already does.

 

Graeme

Yes I know but it is still inconvenient. Especially if it's not me wanting to play music.

Posted on: 12 November 2014 by alan33
Originally Posted by Bananahead:

I don't like that Minimserver needs to be told to re-scan when new music is added because I always forget to force it.

This hasn't been my experience. On my DS213+ the auto-update works fine, whenever any files are added to the music library. This is the advertised behaviour, so worth re-checking that you must force a re-scan. Also, there is a re-scan (comparison against existing cache) done on re-start, and you can force that to be a complete re-scan (ignoring existing cache and building a new one) at launch If you wish. Once set, these are persistent options and little or no manual intervention is (supposed to be) needed. 

 

The only times lhat I've manually re-scanned lately have been to see if my tag edits are working (eg changing to a simplified "genre" scheme that works better for me by eliminating "electric blues" and keeping only "blues", or updating album release dates to year-only in order to take advantage of the "by date" branch on the search tree...). To be honest, I'm not sure if a tag edit would trigger a re-scan, since I manually trigger one from MinimWatch as soon as I've done the edits in order to see the changes made so far reflected in nStream. 

 

Regards, alan 

 

Posted on: 12 November 2014 by Foxman50
Originally Posted by alan33:
Originally Posted by Bananahead:

I don't like that Minimserver needs to be told to re-scan when new music is added because I always forget to force it.

This hasn't been my experience. On my DS213+ the auto-update works fine, whenever any files are added to the music library. This is the advertised behaviour, so worth re-checking that you must force a re-scan. Also, there is a re-scan (comparison against existing cache) done on re-start, and you can force that to be a complete re-scan (ignoring existing cache and building a new one) at launch If you wish. Once set, these are persistent options and little or no manual intervention is (supposed to be) needed. 

 

The only times lhat I've manually re-scanned lately have been to see if my tag edits are working (eg changing to a simplified "genre" scheme that works better for me by eliminating "electric blues" and keeping only "blues", or updating album release dates to year-only in order to take advantage of the "by date" branch on the search tree...). To be honest, I'm not sure if a tag edit would trigger a re-scan, since I manually trigger one from MinimWatch as soon as I've done the edits in order to see the changes made so far reflected in nStream. 

 

Regards, alan 

 

Alan

 

How have you set it to auto scan, ive not seen an option for this. I have to say i actually think the manual scan is a good idea as if you open the log at the same time it throws up any tagging errors you may have made.

 

Graeme

Posted on: 12 November 2014 by Adrian F.
Originally Posted by Bananahead:l

I don't have the Naim app because they stupidly only support Apple and Android.

http://www.idc.com/prodserv/sm...-os-market-share.jsp

 

That means, in Q2 2014 Naim supports 96,4% of all global smartphones!

"stupidly only" - who?

Posted on: 12 November 2014 by Hmack

Adrian F originally posted:

 

"That means, in Q2 2014 Naim supports 96,4% of all global smartphones!

"stupidly only" - who? "

 

Only accurate if you restrict the discussion to the use of smartphones.

 

I use the Naim app on an iPOD Air when playing my ND5 XS. However, my favoured way of controlling my Klimax Renew streamer is with Kinsky installed on my Windows Laptop or PC. I also have Kinsky on the iPOD, but much prefer the Windows version.

 

Now that must mean a fairly large potential market out there.

Posted on: 12 November 2014 by Bananahead
Originally Posted by Adrian F.:
Originally Posted by Bananahead:l

I don't have the Naim app because they stupidly only support Apple and Android.

http://www.idc.com/prodserv/sm...-os-market-share.jsp

 

That means, in Q2 2014 Naim supports 96,4% of all global smartphones!

"stupidly only" - who?

Stupid you gets my vote.

 

Nobody sane would want to use a smartphone to control their hi-fi.

Posted on: 12 November 2014 by Graeme MacArthur

 

Nobody sane would want to use a smartphone to control their hi-fi.

That's me headed for the nuthouse then.

Posted on: 12 November 2014 by Mr Happy

Think I need to join you too Graeme 

Posted on: 12 November 2014 by Redmires
Originally Posted by Bananahead:
Originally Posted by Mike-B:

OK understood

Next question is what does the N streamer analysis indicate on the app & display.  Graeme McA's post says the Naim app shows 96kHz 4608kb/s. with on-the-fly transcoding

When I was playing with transcoding (not sure what DSM rev it was) I got the downsampled 3072kbs number with 96kHz .  I would be more believing of the Naim analysis display number as its math logical

I don't have the Naim app because they stupidly only support Apple and Android.

 

Assuming you have a Windows laptop/desktop you could always run an Android Emulator and install the Naim App on it. I use BlueStacks, which works perfectly but others are available.

 

Posted on: 12 November 2014 by alan33
Originally Posted by Foxman50:
How have you set it to auto scan, ive not seen an option for this. I have to say i actually think the manual scan is a good idea as if you open the log at the same time it throws up any tagging errors you may have made.


Hi Graeme -

I believe autoscan is the default behaviour, no option required; that is what the docs imply and that is my experience. That said, I don't really understand why it isn't being done for some MinimServer users. Not very helpful, I'm afraid! As a wild guess, we could compare user privileges for our respective minim accounts... I think the easiest way to trigger a scan on write in linux is to run a script using inotify...but that may not happen if the minim account does not have execute privileges.  Just a wag, I repeat - I didn't develop any of this stuff!!!

Regards alan

Posted on: 12 November 2014 by Foxman50
Originally Posted by alan33:
Originally Posted by Foxman50:
How have you set it to auto scan, ive not seen an option for this. I have to say i actually think the manual scan is a good idea as if you open the log at the same time it throws up any tagging errors you may have made.


Hi Graeme -

I believe autoscan is the default behaviour, no option required; that is what the docs imply and that is my experience. That said, I don't really understand why it isn't being done for some MinimServer users. Not very helpful, I'm afraid! As a wild guess, we could compare user privileges for our respective minim accounts... I think the easiest way to trigger a scan on write in linux is to run a script using inotify...but that may not happen if the minim account does not have execute privileges.  Just a wag, I repeat - I didn't develop any of this stuff!!!

Regards alan

Cheers Alan

 

I have to say it definitely doesn't auto scan for me. But as i said above its no big shakes to do it manually. Just thought if there was a tick box somewhere i could try it out, but I'm not familiar enough with linux to go messing around in there. 

 

Graeme

Posted on: 12 November 2014 by Bananahead

It only scans at start-up or if you initiate it manually.

 

I just updated a playlist ( saved on the NAS and managed with Mediamonkey ). When I look with Media Server the update is there but when I look with Minimserver it's missing. When I do a rescan it's there.

Posted on: 13 November 2014 by alan33
Originally Posted by Foxman50:
Originally Posted by alan33:
Originally Posted by Foxman50:
How have you set it to auto scan, ive not seen an option for this. I have to say i actually think the manual scan is a good idea as if you open the log at the same time it throws up any tagging errors you may have made.


Hi Graeme -

I believe autoscan is the default behaviour, no option required; that is what the docs imply and that is my experience. That said, I don't really understand why it isn't being done for some MinimServer users. Not very helpful, I'm afraid! As a wild guess, we could compare user privileges for our respective minim accounts... I think the easiest way to trigger a scan on write in linux is to run a script using inotify...but that may not happen if the minim account does not have execute privileges.  Just a wag, I repeat - I didn't develop any of this stuff!!!

Regards alan

Cheers Alan

 

I have to say it definitely doesn't auto scan for me. But as i said above its no big shakes to do it manually. Just thought if there was a tick box somewhere i could try it out, but I'm not familiar enough with linux to go messing around in there. 

 

Graeme

hi Graeme, bananahead, and others -

 

Wow, what a load of misinformation I have spouted!!! I need to spend more time at home relaxing!

 

Contrary to my other post, i do not have automatic scanning on MinimServer. Both Synology MediaStation and Twonky automatically scan when files are added; MinimWatch has the manual re-scan command. No idea how I got so confused - apologies!

 

Regards alan 

 

ps - on the minim forum there is a command line option to run a script when launching MinimWatch and an example of how to periodically scan your library  also, the developer Simon is considering how to add automatic scanning in a future release...but I repeat that I was confused when I said it worked for me. Wow. Sorry. .... 

 

pps - in my defence, thinking I had this feature but not able to rip and add an album to test, I went to the user manual and checked the documentation. Along with the scan-on-startup information, and the rescan command in MinimWatch, it says MinimWatch automatically updates the cache when any audio files are added, deleted, or changed. I mistook this to mean automatic at any time, rather than automatic at each re-start of the server. 

 

 

Posted on: 13 November 2014 by alan33
Originally Posted by alan33:
I think the easiest way to trigger a scan on write in linux is to run a script using inotify...

Well it turns out that the Internet is full of clever and energetic people (although, sadly, I do not seem to be one of them!)

A MinimServer forum member named winxi has already exploited exactly this Unix feature to create an auto scan service:

"The MinimServer Auto Restart package is an unofficial extension for MinimServer Synology users. It uses inotify-tools to watch the MinimServer content directoy(ies) for changes like moving, deleting or modifying files and it will restart MinimServer in case of such an event. The package should work with all Synology DS models supported by MinimServer."

He provides instructions for installation and a serious amount of support for those wishing to try it out (I have not installed it). For those with Synology NAS devices using x86 processors, note that there seems to be an issue with inotify in the latest DSM build, so do read through the discussion thread before diving in.

Again, my apologies for giving incorrect information earlier in this thread!

Regards alan

Posted on: 13 November 2014 by Foxman50

Thanks Alan for the update. I think i have seen the information you referred to above, but thought a bit above my ability, so left well alone.

 

Graeme