@soueric @whatu1tme2b Ok, it’s marked in the browser. But what does happen when you do that with 3.12? Access no more or is it only marked as not secure?
On my NDX 2, with or without XPS-DR, I found that 3.11 had some…what I would call “mystery sibilance”.
Yes some songs/genres were permanently harmed even moving up from 3.10, but other more friendly songs could be going really well and then BOOM, one snare hit or cymbal crash or plucked string absolutely blows your hair back. Knock wood, this has not happened yet, on any of the same songs. Perhaps we are back in 3.8’s general vicinity of it not putting a foot wrong.
I’m back in full music exploration mode. Stayed up WAY too late last night listening to music. Just couldn’t stop. One…more…song. That, for me, has not occurred since 3.8.
Sure, one question though, are you having equipment suited for this update? And if so, have you done the upgrade?
yes and yes
No, I don’t think so. I’m told it should effect just about anything, regardless of brand. Certainly I’ve had other kit here that changed markedly in sound after firmware changes. One bit of kit had users online rating the sound by firmware and you could choose what suited you best - albeit you may gain or lose features and bugs by doing so. The differences were not that subtle either. I seem to recall liking one best that unfortunately rendered the machine more tricky to use. Sounded good though!
I might need to revert to a previous firmware, with this new version I’m not getting anything done. All I do is listen to track after track. It’s addictive. Thank you Naim but it’s not good for productivity!
And you do not hear any change in the sound stage or performance of your system?
The webclient is really gone. You will see an error:
The requested url ‘http://x.x.x.x/webclient/’ was not found.
Welcome to da Hotel California, i.e. no ![]()
I’m told that the weblclient was considered a possible vulnerability by the 3rd party compliance testing house so had to be removed
Whilst in some circumstances there are obvious reasons why a web client may add vulnerabilities, I do think the common sense check of what does that really mean often goes missing on home appliances and ‘compliance’ checking. The same thing is used to justify removing SMBv1 support for example. However, in reality, most people using such devices to make music available to components that just work is really low risk. If hackers want to copy music files I’m sure there are easier ways to find them. Perhaps a toggle with a use at your own risk warning is the better option. Feels like the winners are the compliance companies who are never happy!
There’s likely near-equal concern for the device not being highjacked to work in a botnet like capacity. Big danger of that these days, even with small SoC designs like used in these devices.
Well if it updated without me knowing I’m not sure I’d have noticed tbh!
Yes, I can imagine. An embedded web-server can be used by attackers that have gained access to your local network. But the web-server is actually still there, because the diagnostics page is also served by it and that still works. So, only the end-point for the webclient is gone. Maybe it is also about limiting access to configuration options that are not available in the app. That could easily result in undesired behavior that people might complain about. Now you can only use configuration options available in the app, which drastically reduces the number of permutations that would have to be tested by Naim.
I decided some time ago to not use the webclient anymore for tweaking/configuration. The only thing I miss now is the ‘now playing’ page that I used to copy album art from.
And, of course, as in the automotive sector, introduces the possibility of pay-to-play features at a later date……… ![]()
![]()
![]()
Although in that sector few owners elect to activate the chargeable features; eg BMW indicators and main beam dip….. ![]()
![]()
![]()
![]()
ATB, J
I didn’t say every other manufacturer.
Given other manufacturers weren’t affected by the StreamUnlimited firmware update suggests it is so.
I’ve been using a Primare NP5 streaming bridge for 3 years. Can’t say I noticed any change in sound after a firmware update and there have probably been 3 or 4 in that time. In fact there was a firmware update on 27th April, it’s automatic over the internet, only knew about it because I noticed the status lamps turned red which indicated an update was in progress. I expect other forum members who use NP5 haven’t even realised there has been an update.
Anyway, it’s got to good news that owners of Naim streamers can now also enjoy a more enjoyable steaming experience. ![]()
Thanks for claryfing it. It’s quite a loss in my opinion, it was very handy.
@Richard.Dane is there any possibility to get something similar (or an alternative) back? And I don’t mean that for fiddling. It’s very useful and straightforward if you use a computer more than a tablet.
Still no changelog?
So, updated my Nova.
Not done any listening yet, but sitting in the same room as the Nova this afternoon for an hour or so it kept making clicking noises like it was turning on or off (which it wasn’t).
Unplugged unit from mains and reconnected and it continued. Not regularly but at odd time intervals. As no one else has mentioned this I am guessing it’s just me!
Will check app is up to date on all devices (all Apple) and try another unplug from mains and monitor over the weekend.
Finally a proper listen, dare I say its more old Naim more PRaT, I like it, thought the HF siblance is not good.