NDS Stops playing

David Hendon posted:

Jondhall posted:

Dustysox posted:

Jondhall posted:

Really sorry to hear of your woes. Especially since I have been suffering the exact same thing. I replaced my switch (netgear gs105) which sits between my mac mini server (Asset and minim software) and my qute 2.

It all started with radio 4 dropping out then coming back up. Heard lots people moaning about this so left well alone.

Then streaming started to just stop. No input initializing, music just stops. 

Completely rebuilt my server with win 10, assett and minim. Still does it.

Just ripped all my cables out and replaced. Even removed a wifi switch for a lamp at the side of the hifi.

Listening with bated breath. What a time for things to go wrong. I dont mind the time I just NEED my music.

Hope it all works out for you.

 

 

Good morning Jondhall, do you have any further developments?

Well, Gutted. No change at all. Tried the USB as suggested to OP and that stops too. So its the Qute :-(

It's worth trying a factory reset of your Qute before you send it off to Salisbury because that does sometimes fix odd behaviour. You do it with the remote, via the spanner/wrench key.

best

David

Hi David,

Sorry i missed this comment. I have tried numerous times a factory reset to no avail. Thank you for your advice, you never know eh!!!

Powering down the NDS cleared the Fault 36 error. Not sure why/how etc. I have spoken with my dealer to get the NDS off to Naim and also to get my 500 DR upgrade done at there same time...makes sense!! Just waiting for a "window". 

Really gutted as this means no music in the distant future added to the time I've had no music since the fault started.....GUTTED! It's surprising how much I really enjoy listening to music, more than I realised and how much i miss it. It really is one of my pleasures and really is therapeutic, relaxing and takes me on a real emotional journey sometimes.  

O well, maybe Easter.....!!! Until then..the Silence is deafening!!!!

Dusty have your problems always been around getting a Fault 36 error?  Back a year or two ago Fault 36 was a (too) common issue with the NDS, but one of the updates from Naim cured it - quite permanently in my case.  It sounded to me like you were having issues well beyond Fault 36.  And if you've done updates to version 4.x (4.4 is current) then I'm guessing it's a hardware issue with your NDS

In my case, powering down the NDS and letting it SIT would clear the Fault 36.  Again that is thankfully ancient history for me, and it was all fixed with software.

It's been some time since your NDS went off line. And it hasn't gone back to base yet. Bummer! Doing the 500 DR seems like the most sensible way forward in the long term. I hope you get a quick slot.

Bart posted:

Dusty have your problems always been around getting a Fault 36 error?  Back a year or two ago Fault 36 was a (too) common issue with the NDS, but one of the updates from Naim cured it - quite permanently in my case.  It sounded to me like you were having issues well beyond Fault 36.  And if you've done updates to version 4.x (4.4 is current) then I'm guessing it's a hardware issue with your NDS

In my case, powering down the NDS and letting it SIT would clear the Fault 36.  Again that is thankfully ancient history for me, and it was all fixed with software.

Hi Bart,

Happy New Year!

Sorry, I meant to type Fault 35 and not Fault 36. The NDS is running correct latest firmware. Thank you for your though.

Harry posted:

It's been some time since your NDS went off line. And it hasn't gone back to base yet. Bummer! Doing the 500 DR seems like the most sensible way forward in the long term. I hope you get a quick slot.

Hi Harry,

Happy New Year mate.

Yes, it has been a while since NDS went "sick"! Bad timing for me as it happened just prior to Christmas, and not a lot was going to happen until now. Hence I'm a bit peeved with it all. No quick fix. I know that when all has been sorted I will be over the moon again!!!!

Best wishes with it and a Happy New Year to you too.

Q2 looks promising.

I still have the fault 36 appearing 4/5 times on average after I power cycle my NDX + XP5. No FW update has cured it (I run the latest beta). When it happens it takes an undetermined number of power cycles to overcome it. Reading an older thread here I found during last week that it helps (when Fault 36 appears) to change input to anything but UPNP (can be done via the app, the remote is frozen) - next power cycle seems to do the job

DrPo posted:

I still have the fault 36 appearing 4/5 times on average after I power cycle my NDX + XP5. No FW update has cured it (I run the latest beta). When it happens it takes an undetermined number of power cycles to overcome it. Reading an older thread here I found during last week that it helps (when Fault 36 appears) to change input to anything but UPNP (can be done via the app, the remote is frozen) - next power cycle seems to do the job

Send a note to Phil Harris just to be sure that the DSP update (I think it was the DSP) software that fixes this is actually in whatever firmware you're running!  Worth checking, as that's an ANNOYING bug!

And HAPPY NEW YEAR Dusty

Hi, on the assumption you can't see Asset on your iPad/iPhone, have you tried manually calling up an album/track under uPnP on the NDS and play that.  You may then somehow (I'm not a techie but it worked a few times for me when I couldn't see Asset on iPad - luckily I have not come across this for a while now) "force" Asset to be seen on your tablet?

Good evening,

I/we may be on the path to understanding what might be causing me the problem.....Amazon Echo Dot!!

I was reading earlier Echo thread and was surprised to learn of other folk with a similar problem to me. I have three of the Dots and they are all now unplugged from the mains.The one in the lounge was connected to one of the inputs on my 552.

Lord only knows why this is happening. I did a full factory reset after unplugging the Dots and so far the Naim app is far more responsive and the music as yet has not cut out, not once.

I will speak with Naim in the morning to bring this to there attention and see if they can shed some light on the whys etc.

Suffice to say, it's great to be listening to music again! I will leave the NDS on loop over night to see if it has continued to play the music or stopped. 

What is curious is that we one of the Dots in the kitchen which is connected via bluetooth to my Muso Qb and have not had this problem. Also , with the Muso in the dining albeit running wireless, no problems there either. The Naim app connects to them instantly with no problem of music cutting out. It does seem to be a problem with the Dot & NDS. The Echo Dot does seem to affect the NDS ability to play music from UPnP/Spotify/USB.

Simon-in-Suffolk....any thoughts? Really strange.

Interesting. 

Interesting Dusty!  But given what others have said about the problems caused by Amazon Echo / Alexa devices, that could be your ENTIRE problem!

(I had a problem a couple of years ago where a screwy Apple Time Capsule was causing tons of drop-outs on my NDS and Qute2.  The buffers would empty out . . . In my case, it was a problem with the Apple device, as a factory reset of it cured it.  But it goes to show that other devices on your home network CAN interfere.) 

Most odd - let's hope the NDS continues to play uninterrupted.

Bart posted:

DrPo posted:

I still have the fault 36 appearing 4/5 times on average after I power cycle my NDX + XP5. No FW update has cured it (I run the latest beta). When it happens it takes an undetermined number of power cycles to overcome it. Reading an older thread here I found during last week that it helps (when Fault 36 appears) to change input to anything but UPNP (can be done via the app, the remote is frozen) - next power cycle seems to do the job

Send a note to Phil Harris just to be sure that the DSP update (I think it was the DSP) software that fixes this is actually in whatever firmware you're running!  Worth checking, as that's an ANNOYING bug!

The erroneous Fault 36 report was fixed - if you are getting ANY fault code that persists after a power cycle then it's a legitimate fault and needs attention.

Phil

Thanks Phil. "Vimion" (RC) had sent me a DSP Bootloader script some time ago which i had not managed to execute, I did so over the weekend (had to rename the .ldr file and edit the .bat script accordingly) and it worked. I will now monitor how the NDX responds after power cycling and if the problem persists i will report it here and to my dealer.

Bart posted:

Interesting Dusty!  But given what others have said about the problems caused by Amazon Echo / Alexa devices, that could be your ENTIRE problem!

(I had a problem a couple of years ago where a screwy Apple Time Capsule was causing tons of drop-outs on my NDS and Qute2.  The buffers would empty out . . . In my case, it was a problem with the Apple device, as a factory reset of it cured it.  But it goes to show that other devices on your home network CAN interfere.) 

Adam Zielinski posted:

Most odd - let's hope the NDS continues to play uninterrupted.

 

Hi all,

Just to confirm that beyond any doubt that it is the Echo Dot causing the problem. In the past two evenings i have switched off the Dot and had no problems with the NDS cutting out. In fact it has run on loop through the night with out any interruptions. YIPPEE!!!!!! When i switch on the Dot the NDS cuts out.

I spoke with Steven @ Naim yesterday morning (what a fine chap he is) and brought it to his attention. Hopefully this issue can be resolved. 

If anyone has any ideas/fixes I would be most interested...I'm all ears... you should see the size of them!!!!!

I am just glad to have music back...i can now focus on DR/service upgrade of my 500 amp now!!!

It has been a frustrating journey,and with all your help we have "nailed" what the problem is. I hope that if the any people have a similar problem a quick search ( i know this will please Adam!!!) will shed some light rather than days/weeks of " agro"!! 

Thank you al.

It might even be a good idea as a "sticky" at the top of the forum until things have been resolved.

DrPo posted:

Thanks Phil. "Vimion" (RC) had sent me a DSP Bootloader script some time ago which i had not managed to execute, I did so over the weekend (had to rename the .ldr file and edit the .bat script accordingly) and it worked. I will now monitor how the NDX responds after power cycling and if the problem persists i will report it here and to my dealer.

Unfortunately I still have the same "Fault 36" problem upon power cycling. I will contact my local dealer 

Ello all!

What i'm interested to know is-

Is this an Amazon Echo problem or Naim? I ask (i may have answered my own question!!) because the Muso and Muso Qb are unaffected by this, as is my Logitech Transporter which sits on the same Fraim as NDS connected to the same switch and looking at the same place where my music is stored.

Is there anything i can do within router/NDS settings to resolve this problem?

Is the firmware the Beta testers are using unaffected by Echo Dot, and if they reverse to firmware 4.4.00 that the problem manifests itself?

At the moment until some fix is available, I have been leaving the Echo Dot powered during the day for the family to use, and then power the Dot off of an evening when i want to listen to uninterrupted music would i be causing my NDS any technical problems which could result in damage which means the NDS has to go to Salisbury for repair?

Being that the NDS seems to be "sharing" network "stuff" would this impact audio quality?

Help....anyone!!!!

Dustysox posted:

Ello all!

What i'm interested to know is-

Is this an Amazon Echo problem or Naim? I ask (i may have answered my own question!!) because the Muso and Muso Qb are unaffected by this, as is my Logitech Transporter which sits on the same Fraim as NDS connected to the same switch and looking at the same place where my music is stored.

Is there anything i can do within router/NDS settings to resolve this problem?

Is the firmware the Beta testers are using unaffected by Echo Dot, and if they reverse to firmware 4.4.00 that the problem manifests itself?

At the moment until some fix is available, I have been leaving the Echo Dot powered during the day for the family to use, and then power the Dot off of an evening when i want to listen to uninterrupted music would i be causing my NDS any technical problems which could result in damage which means the NDS has to go to Salisbury for repair?

Being that the NDS seems to be "sharing" network "stuff" would this impact audio quality?

Help....anyone!!!!

 

The issue has been passed up to our software guys with some network traffic grabs from a forum members network - the likelihood is it's similar to what happened with Netflix whereby they were sending a malformed "Stop and listen" broadcast message that they then subsequently fixed however that has to be identified and confirmed.

Oddly it's not affecting everyone with Echo or Echo Dot units as we have a number of users who aren't seeing the same issues.

Phil

Dusty I can only imagine that your NDS is "safe" -- the issue that is effecting it seems very unlikely to actually damage it!  Just frustration . . . but I'm glad you didn't send it off for repair, get it back, and of course then suffer this same issue!

While beta testers cannot comment on what we're testing . . . or aren't testing . . . if I were you I would not worry that you are missing out on something that's a fix for you.  Trust Phil's comment that Naim are working on it and apparently don't have a solution yet (and that maybe it's the Echo's problem and not Naim's).

I think that your solution is perfectly appropriate -- turn off the Echos when you want to use your NDS.  And if Amazon push a firmware update for the Echos, grab it. Who knows maybe they'll fix it, even by accident.

Phil Harris posted:

Dustysox posted:

Ello all!

What i'm interested to know is-

Is this an Amazon Echo problem or Naim? I ask (i may have answered my own question!!) because the Muso and Muso Qb are unaffected by this, as is my Logitech Transporter which sits on the same Fraim as NDS connected to the same switch and looking at the same place where my music is stored.

Is there anything i can do within router/NDS settings to resolve this problem?

Is the firmware the Beta testers are using unaffected by Echo Dot, and if they reverse to firmware 4.4.00 that the problem manifests itself?

At the moment until some fix is available, I have been leaving the Echo Dot powered during the day for the family to use, and then power the Dot off of an evening when i want to listen to uninterrupted music would i be causing my NDS any technical problems which could result in damage which means the NDS has to go to Salisbury for repair?

Being that the NDS seems to be "sharing" network "stuff" would this impact audio quality?

Help....anyone!!!!

 

The issue has been passed up to our software guys with some network traffic grabs from a forum members network - the likelihood is it's similar to what happened with Netflix whereby they were sending a malformed "Stop and listen" broadcast message that they then subsequently fixed however that has to be identified and confirmed.

Oddly it's not affecting everyone with Echo or Echo Dot units as we have a number of users who aren't seeing the same issues.

Phil

Hi Phil,

Great to hear. I guess thats the problem fault finding when not all people wth Echo/Echo Dots are affected. If i can be of any help.......!

I wish you and the software guys a speedy solution.

Out of interest is Naim like the Wonka Factory and are the software guys Oompa Loompas!!!!!!!!!!!!!!!!!!!!! Just kidding!

I/we really appreciate the work and effort you guys go to ensure our music enjoyment of which you all do a brilliant job, thank you

.Bart posted:

Dusty I can only imagine that your NDS is "safe" -- the issue that is effecting it seems very unlikely to actually damage it!  Just frustration . . . but I'm glad you didn't send it off for repair, get it back, and of course then suffer this same issue!

While beta testers cannot comment on what we're testing . . . or aren't testing . . . if I were you I would not worry that you are missing out on something that's a fix for you.  Trust Phil's comment that Naim are working on it and apparently don't have a solution yet (and that maybe it's the Echo's problem and not Naim's).

I think that your solution is perfectly appropriate -- turn off the Echos when you want to use your NDS.  And if Amazon push a firmware update for the Echos, grab it. Who knows maybe they'll fix it, even by accident.

Spot on Bart. 

Is Beta Club a bit like Fight Club!!!!!!!

I have a work around which means i get to enjoy music again. My system was really singing last night, thoroughly enjoying the high quality it provides. Can't wait for my 500 DR upgrade over the next couple of months or so.

I do hope Naim/Amazon get it sorted and that this thread will serve to help others who suffer the same problem

No issues here with using Amazon Echo with my NDX at all... and Amazon Echo not causing any issues with my other UPnP devices with discovery messages (and I have a fair amount)  - so I doubt it is 'malformed'. I am using a later firmware on my NDX. i suspects its more an issue with the earlier streamer firmware reacting correctly from a UPnP discovery message that is not audio related.

Simon-in-Suffolk posted:

No issues here with using Amazon Echo with my NDX at all... and Amazon Echo not causing any issues with my other UPnP devices with discovery messages (and I have a fair amount)  - so I doubt it is 'malformed'. I am using a later firmware on my NDX. i suspects its more an issue with the earlier streamer firmware reacting correctly from a UPnP discovery message that is not audio related.

 

Hi Simon,

It is an odd one as none of my other UPnP devices are affected similar to your findings. I wonder if the firmware you are running albeit beta, is immune to this problem. I do hope so, and if so i hope for a firmware update REAL SOON!!

I hope so too... almost certain this is nothing to with Amazon at all - nothing to sort out there... Echo really works rather - very impressed with it.. and works very well with my home automation.

As I said on the Echo thread I have a similar problem with my SU but, fortunately, this only occurs once every week or so. The Mu-so and Mu-so qb are unaffected. I suspect, but am not sure, that the start of the problems occurred after the arrival of the Echo, they certainly have not always been there.