New firmware update

Just sent mine too

1 Like

Yes - that mildly irritating issue that only you and I seemed to notice has vanished it seems! :slightly_smiling_face:
Operation here with ND555 and Melco are fine and best I recall them ever being.

SQ was an acclimatization to all the extra top-end detail that can tend to come out brash on some recordings and no problem on others. Very minor system tweaks (slight de-stressing some cables) which made very little difference before now clear the problem and the dynamic range suddenly leaps-up as if I turned-up the volume.

There does appear to be greater resolution capability in this version of Firmware. If as Naim claim this is all due to careful attention to how noise is being generated by how the Firmware is specifically loaded - and that the actual bits to the DAC are not changed at all since the last Release - then hopefully the various faults people are finding can be solved and the SQ not made worse in any later release.

DB.

3 Likes

@Richard.Dane the email bounced back. I probably misspelled your email address. Is it Richard.Dane@naimaudio.com ?

Thomas, no, as Iā€™m not at the factory I donā€™t have a Naim email address any more, just my own personal email.

1 Like

WHAT THE HELL JUST HAPPENED?

The chromecast control image on all visual apps (Youtube etc) now defaults to the ND5XS2. I canā€™t cast anything to my TV anymore.

Iā€™ve actually started shouting at the app.

WHAT. THE. ACTUAL. F***!!!

Not happy. Running out of patience.

Today, when I started playing an album (FLAC) from my local NAS, only a black screen was seen, but album art came on when I realized it and simply paused the playback. With previous black screens I had to switch to standby and on again. NDX2, v3.5.

I had that issue with 3.4 but just leaving the Uniti Star on and playing, the screen eventually woke up and came back (sometimes after a few hours).

So far the screen on 3.5 worked flawlessly with all sources (CD, Tidal, Roon) used on a daily basis since the update.

Thanks to Henry at the support desk.

The sudden override grab of Chromecast functionality was put in place, it would seem, by independent ā€œinitiativeā€. Also, it is now impossible to disable the native chromevast via the app settings.

It would seem that the change was made without it being agreed or notified within NAIM! Certainly not known about at the support desk. I mean, seriously guys?

This is getting beyond farcical.

Anyway. Got the TV chromecast dongle back by routing the optic cable via the nDAC and sound too.

I have to physically switch the nDAC from ā€œ1 prevā€ to ā€œ2 nextā€, which kind of adds another bit of fiddling about to get what I want but at least Iā€™ve stopped shouting at my phone. :roll_eyes::poop::angry:

With my NDX2 sometimes only a few tracks were played from an album and then playback stopped. This happened really seldom with all fw versions prior to 3.5.

This is getting awkward.

Apparently there are some users complaining about having issues with the 3.5 firmware that donā€™t email to support.

Folks, if we want things to be taken care off we need to report them to support, not only complaining about them.

But, before emailing

  • make sure you followed the update instructions
  • make sure you rebooted all your system, including switch(es), internet provider router, etc. Everything!
  • Make sure your problem is not related to something else (wifi, other devices, etcā€¦)
  • Connect your streamer preferably using an Ethernet cable, rather than wifi
2 Likes

None of that would have done any good.

So, thanks but, you knowā€¦

I have now.

HI @MikeD

REF: Chromecast - Naim have no way to stomp on other Chromecast devices on the network - each one is unique. What I believe you are experiencing is that the discovery mechanism of Chromecast devices (which uses Apple Bonjour) has ended up with a poisoned name cache, so the list of Chromecast devices are messed up. It is feasible that as the device was upgraded and the device gets restarted nā€™th times it confused other devices on the network.

Proposal:

  • Power cycle the Wifi router
  • Power cycle the Chromecast dongle - hence it will reregister its presence and I suspect will change IP address.
  • Power cycle your streamer. Mainly so Wifi router and product are 100% in sync.

For Chromecast this is all code direct from Google which is strictly certified. Naim are a partner incorporating their technology and itā€™s all closed components that Google have supplied.

If this doesnā€™t do the trick, please contact our helpdesk. If need be they can elevate issues to the relevant person to handle.

Best regards

Steve Harris
Software Director
Naim Audio Ltd.

3 Likes

Hello Steve. Please see my post aboveā€¦

Re: support and solution.

Hi all,
The answer might very well be buried in this thread and I promise I have looked.
Since the firmware update, which I quite like from an SQ perspective, I canā€™t get Tidal to work. It asks me to login and when I do it says ā€œsubscription requiredā€ I joined Tidal at least a year ago and have been making a monthly payment ever since.
Any suggestions? Iā€™ve rebooted, powered down router, etc. I have not gone the whole hog and completed a factory reset as Iā€™m a little nervous to do so.
Cheers

After Richard requested I did email support. However support should also have anyhow enough complaints about the stability of the firmware through this thread, that should give them some clues to resolve itā€¦

1 Like

So I seem to finally found a personal niggle with 3.5.

Iā€™m using my Uniti Star a lot for television sound via HDMI eARC. The source is an Apple TV and it is downmixing to stereo.

Since 3.5 I have noticed that every so often, when plugging in headphones there is a one second ZZZZZT sound. It only seems to happen after long HDMI ARC listening. If I then remove the headphones and plug them in again no zzzt sound. If I restart the HDMI source, no zzzt sound. So itā€™s very hard to triage.

Anyone else noticed something like this?

P.S. I also sent this to Naim support via mail.

Please see my post earlier today;

1 Like

Not quite the same as you describe, but similar. I have the HDMI input configured to come on automatically.

When I turned the TV on, my Star came on and sound switched to it. Then, after a short bit it had turned itself off again. When I then turned it back on I heard the loud static / ZZZZZT before sound switched to it again. Itā€™s kept working since.

This is the second time Iā€™m aware it happened.

I want to time after how long it turns itself off before reporting to support. Auto standby is 20 min, but Iā€™m fairly sure (not 100%) it was less.

@Richard.Dane Surely if R&D doesnā€™t have adequate or appropriate data to inform analysis and resolution, why doesnā€™t it set out precisely the information it needs so that all users who have experienced a random reboot can report the details through a common reporting format?

A fault whereby the firmware randomly interrupts music replay is such a fundamental failure that I would hope it would be the top issue on @charlie.hendersonā€™s agenda. It needs to be resolved as a matter of utmost urgency. I would certainly be willing to fill out and submit a form describing the set up and circumstances at the time of the reboot if it would help. I am sure others would be willing to do likewise.