New firmware update

Not quite.

£ 27’000 streamer + random reboots = not acceptable.

3 Likes

Maybe it is different then. The noise I get is much less pleasant.

Yeah I was starting to get that idea as well.

For those of you who are not experiencing anymore the multiple reboots, do you have any issue with Qobuz songs taking longer to load and art work taking longer to show on the screen ?

Same here on SQ.

1 Like

Updating firmware can be a risky process. I guess that if I had spent £27K on a streamer, an experience that I am never likely to have, I would take the unit back to the supplying dealer and ask him to do the firmware and app update at the same time. If the update process failed, the dealer and I could then have a discussion about the streamer that he would loan to me while he and the factory were resolving this unacceptable problem!

The solution appears obvious … A more rigorous testing of updates by the factory before they are released

Oh yes!
Clearly, someone didn’t do its job.

The update process didn’t fail. Not at all. It went smoothly.

The fail is the software, or at least part of it… :roll_eyes:

PS : but… one must give to Caesar what is Caesar’s the ND555 sounds sublime!!! :notes: :musical_note: :notes:

Mine has not gone wrong as of yet.

As I replied to you before - this is not true. It would be more true if you extend your equation:

same hardware + same software + same features used = same problem.

Then I’d tend to agree. It is also the case that it should not be happening whatever the features used are.

But I have checked the logs and it has not gone wrong and I play a lot of music and it is all working fine with far better SQ with this updated version.

It may be mine will also go wrong a bit later - then I’ll report it has - I’ve no agenda here.

DB.

3 Likes

You’re right!

I use the ND555 with a Roon server. Everything else is deactivated on the ND555.

What is rather curious is that the ND555 did reboot twice (at least) while doing nothing (or at least nothing I could notice) :open_mouth:

It’s been stable for the last couple of days.

@BertBird had the same issue while streaming from Qobuz and locally.

I hope Naim did acknowledge the problem and is working on it. What bothers me is that Naim didn’t clearly admit that there actually is a problem.

2 Likes

With these sorts of ‘random’ faults you look at the development and test environments and could assume that the Developers and Testers did not notice this happen - what did they use to test, what features tested and for how long before the equipment was re-booted by the person deliberately (no long-time on soak-test)?

If only the Naim App was used and the fault only happens (just hypothetically) after a long period of time when certain features are exercised, then it may not have shown-up in test.

You can be sure all the logic-pathways and control-cycles within the code logic and how it is loaded into target equipment are being examined by Naim - they will want to identify what and how it is all happening and get the fix done. That can take some time.

If mine eventually re-boots, after a few weeks now, then annoying but for those that are having it happen every few hours in mid-music then that is needing the roll-back support Naim do seem to offer from support.

DB.

I received the below reply from Naim Support on Monday having returned the issues I was personally experiencing with the 3.5 update.

Ticket Received - Firmware 3.5 issues

Please be aware - we are experiencing unusually high numbers of incoming contacts and - as a result.- our response times have been delayed. We sincerely apologise for the inconvenience and delay and thank you for your patience

Makes me think they may have received one or two similar emails. To date I’ve received no further replies.

0.0

Received the exact same message.

1 Like

Perhaps it is more widespread? I don’t think we will ever know the actual numbers. I am sure Naim are working hard on it but as @Darkebear pointed out, depending on the nature of the issue it may take some time to resolve

Richard
My dealer tells me that Naim are not currently shipping any NDxxxx streamers with either the old or new firmware. They are waiting until the new FW is fixed properly, and will then ship. If it was as simple as you suggest, the would Naim not simply follow their own advice with the new FW and ship?
My new toy is delayed!

As previously stated my unity star experienced some quiet spells due to the 3.5 update, silence for 3 to 6 seconds and then an unexpected restart. I turned mine off for 15 hrs, I was just out, switched off the Wi-Fi for a minute and logged out of tidal on the Naim app. Been streaming from Tiday today so far without issues. Appreciate this is not the same as an NDXxx…

0.0
:crossed_fingers:

If this is correct, and hope it is, Naim took a wise decision.

What would also be nice is them to acknowledge the problem and reply to our emails saying they are aware of the the problem and are working to solve it.

Unfortunately I’m still waiting for an answer…

1 Like

I too received the same message. I’ve just called my Naim Audio retailer to ask if he’s aware of action being taken. I await a return call.

I got an email with that wording back on the 6th August well before the firmware dropped, I think it’s been their standard holding message for a while. I’m not saying people don’t deserve a response to their reports explaining what is happening, just sharing the information that the “unusually high numbers of incoming contacts” isn’t specific to this firmware drop.

3 Likes

My dealer told me the scarcity was down to demand and waiting for parts. More likely i reckon. All their demo gear is almost gone. I’ve had most of it! :rofl:

1 Like

It’s just as much of an issue for the owner of a £750 Qb2.

Stuff happens. Things go wrong. It’s not the end of the world. It’s irritating of course, and Naim will resolve it.

2 Likes