It's been a while, so I figured I'd update this thread:
1) The NAD M50.2 has gone through some software upgrades. Along the way it picked up DSD decoding ability!
The funny thing is, it doesn't work with the iOS app (on iPhone or ipad), and I assume it's not working on the Android app as well. However, on the PC, if you go to settings>playback, there is now a radio button for ENABLE DSD PLAYBACK. You click on this, then browse to your DSD folders, and the NAD converts your DSDs to FLACs and stores them on the NAD.
Good enough! I don't know when this suddenly appeared, it's certainly not documented in any of the update readmes, but it will do.
2) Due to a software update at HDTracks, the NAD doesn't automatically download your files any more. They are supposedly working on it, but I don't know when it will be fixed.
3) The fileshare issue still exists with windows 10. *If* you want to access your music files via window explorer on the NAD M50.2, you need to do the following:
run regedit
go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Paramaters
Look for the value AllowInsecureGuestAuth
change the value from 1 to 0.
Now you will be able to see the NAD M50.2 in your network devices, and you can access the fileshares.
I wouldn't leave this flag at 0 forever. Just do it to access the NAD M50.2 and once you're done (moving music files) reset it to 1.
You can also go to the command prompt (administrator mode) and type:
set -smbserverconfiguration -enablesmb2protocol $false
I assume after you're done, run the same command with $true instead of $false.
4) Finally, I don't know exactly what's going on, but the NAD is no longer wakeable via the app (if it's asleep). It used to be accessible at all times, but now whenever I want to access it, I have to turn the system on manually by touching the capacitative button to turn it on. I may have done this to myself when I tried to hardware the NAD to my network (took it off since it didn't work and I wasn't able to access the system at all because I had it on a different switch/subnet...totally my fault. I don't want to bridge the networks though.) I'm going to power cycle the system when I'm not using it and see if that fixes it.
1) The NAD M50.2 has gone through some software upgrades. Along the way it picked up DSD decoding ability!
The funny thing is, it doesn't work with the iOS app (on iPhone or ipad), and I assume it's not working on the Android app as well. However, on the PC, if you go to settings>playback, there is now a radio button for ENABLE DSD PLAYBACK. You click on this, then browse to your DSD folders, and the NAD converts your DSDs to FLACs and stores them on the NAD.
Good enough! I don't know when this suddenly appeared, it's certainly not documented in any of the update readmes, but it will do.
2) Due to a software update at HDTracks, the NAD doesn't automatically download your files any more. They are supposedly working on it, but I don't know when it will be fixed.
3) The fileshare issue still exists with windows 10. *If* you want to access your music files via window explorer on the NAD M50.2, you need to do the following:
run regedit
go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Paramaters
Look for the value AllowInsecureGuestAuth
change the value from 1 to 0.
Now you will be able to see the NAD M50.2 in your network devices, and you can access the fileshares.
I wouldn't leave this flag at 0 forever. Just do it to access the NAD M50.2 and once you're done (moving music files) reset it to 1.
You can also go to the command prompt (administrator mode) and type:
set -smbserverconfiguration -enablesmb2protocol $false
I assume after you're done, run the same command with $true instead of $false.
4) Finally, I don't know exactly what's going on, but the NAD is no longer wakeable via the app (if it's asleep). It used to be accessible at all times, but now whenever I want to access it, I have to turn the system on manually by touching the capacitative button to turn it on. I may have done this to myself when I tried to hardware the NAD to my network (took it off since it didn't work and I wasn't able to access the system at all because I had it on a different switch/subnet...totally my fault. I don't want to bridge the networks though.) I'm going to power cycle the system when I'm not using it and see if that fixes it.
