I like to live dangerously
And as David H helpfully points out, it’s not all that dangerous.
My NDS came with v4.6 firmware. Only yesterday I was debating whether to install v4.7. So I guess I’ll wait a bit…
I like to live dangerously
And as David H helpfully points out, it’s not all that dangerous.
My NDS came with v4.6 firmware. Only yesterday I was debating whether to install v4.7. So I guess I’ll wait a bit…
@easeback1 you have convinced me to give wireless a go when this new update arrives. Good luck with the NDS should be a brilliant source. I think if you want to use Tidal, you may need 4.7 so it works properly.
Enjoy.
The wired-only advice likely dates from a decade or so ago when wi-fi networks were less stable.
Thanks, the NDS is proving to be a fantastic purchase. Running Qobuz via Audirvana / Mac Mini.
I can confirm David’s point that doing the update over WiFi is generally fine, over the years I must have done 20 or so updates without the Ethernet cable and never had one go wrong.
Also any reason you’re not using a local NTP source and using time.netweaver.uk instead ?
Or even pool.ntp.org.
Just did a packet capture on my mu-so v1 and noticed it.
And while you’re at it please also fix this long running bug
Reported several times,never got a straight answer.
Couldn’t care less about the security issue but if above bug could be fixed that would be great.
Amen to fixing the bug that complicates playing DSD tracks larger than 1 GB on first-gen streamers (NDS, NDX)! While this doesn’t manifest itself for much outside of the long movements of late 19th-century symphonies, it is a little disappointing that a company that sweats the details like Naim hasn’t been able to fix this bug.
I just checked the internal settings of a Muso Qb Gen1 & also wirssharked it and its using 0.pool.ntp.org as its NTP server of choice. This can be overiden if the DHCP server supplies an NTP server of choice to use.
See wireshark screenshot of choice of a Muso Qb gen1 starting up and doing the DNS lookup.
Best wishes
Steve Harris
Software Director
Naim Audio Ltd.
@Stevesky Thanks for that, Ah time.netweaver.uk must have been part of the pool.ntp.org.
16:21:55.694377 IP (tos 0x0, ttl 128, id 417, offset 0, flags [none], proto UDP (17), length 76)
mu-so.1236 > fluffykins.positive-internet.com.ntp: NTPv4, length 48
Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 4 (16s), precision -14
Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 305.522632087 (2036/02/07 06:33:21)
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 305.522632087 (2036/02/07 06:33:21)
16:21:55.702615 IP (tos 0x0, ttl 56, id 49808, offset 0, flags [none], proto UDP (17), length 76)
fluffykins.positive-internet.com.ntp > mu-so.1236: NTPv4, length 48
Server, Leap indicator: (0), Stratum 3 (secondary reference), poll 4 (16s), precision -22
Root Delay: 0.034774, Root dispersion: 0.025894, Reference-ID: ntp1.exa-networks.co.uk
Reference Timestamp: 3839412009.515010766 (2021/08/31 16:20:09)
Originator Timestamp: 305.522632087 (2036/02/07 06:33:21)
Receive Timestamp: 3839412115.695731596 (2021/08/31 16:21:55)
Transmit Timestamp: 3839412115.695782682 (2021/08/31 16:21:55)
Originator - Receive Timestamp: -455555485.826900491
Originator - Transmit Timestamp: -455555485.826849404
A packet capture of DNS has also confirmed.
16:32:37.384813 IP (tos 0x0, ttl 128, id 187, offset 0, flags [none], proto UDP (17), length 60)
mu-so.1234 > pfsense-user.domain: 13330+ A? 0.pool.ntp.org. (32)
16:32:38.228313 IP (tos 0x0, ttl 64, id 50773, offset 0, flags [none], proto UDP (17), length 124)
pfsense-user.domain > mu-so.1234: 13330 4/0/0 0.pool.ntp.org. A 185.208.170.29, 0.pool.ntp.org. A 129.250.35.251, 0.pool.ntp.org. A 109.74.206.120, 0.pool.ntp.org. A 178.62.16.103 (96)
16:32:39.236365 IP (tos 0x0, ttl 128, id 224, offset 0, flags [none], proto UDP (17), length 60)
mu-so.1236 > pfsense-user.domain: 13586+ A? 1.pool.ntp.org. (32)
16:32:39.327181 IP (tos 0x0, ttl 64, id 18942, offset 0, flags [none], proto UDP (17), length 124)
pfsense-user.domain > mu-so.1236: 13586 4/0/0 1.pool.ntp.org. A 193.47.147.20, 1.pool.ntp.org. A 85.199.214.101, 1.pool.ntp.org. A 185.83.169.27, 1.pool.ntp.org. A 139.143.5.30 (96)
Hi @SneakyPete, @JSchmidt
RE: DSD - Try the new code out when it comes out - you might be pleasantly surprised.
Best
Steve Harris
Software Director
Naim Audio Ltd.
Now you’ve made me curious!
Will certainly do. Thx in advance!
I will be keeping a keen eye out for notices about the updates… !
Thank you for clarifying @Stevesky
I ran into the same issue with my ORBI and Muso. Good to hear that a solution is on the way.
Not long to wait - the Mu-so first-gen rollout starts from later today (Firmware 2.0.0), followed later in week by further legacy product updates.
@Bluelines The update for your Qb has been released, so should pop up in the Naim App sometime soon. Full details in Richard’s post here:
Just completed 1 of 3 Qb updates all straightforward. On to number 2 and 3. Awaiting 272 update release next.
Watch this space on 272 - hoping for later this week…
and NDX??
I have both to do!
It’s for all the green screen Unitis, streaming preamps and streamers.
Yes, it’s for UnitiQute/Qute 2; UnitiLite; Uniti/Uniti 2; SuperUniti; NAC-N 172; NAC-N 272; ND5 XS; NDX; NDS.
Full guide to updating will be supplied when the software is released later this week.
FYI, Naim retailers worldwide have had a full briefing on the updates.