New firmware update

Oh. Didn’t see that :grimacing:

The weird thing is that the streamer un/replugging recommendation after updating has now been removed from the sticky.

It’s simply not required. The streamers do the whole process automatically. All one has to do is hit the update icon. Leave well alone while doing it’s thing. After the process has finished, simply carry on from where one had left off before the update. Job done.

2 Likes

It’s most likely me being thick, but I never did understand the unplugging thing, given that the streamer is powered by external power supplies, or did they really mean to go as far as disconnecting the Burndies?

Not likely, Guv. :-1:

No, I believe they meant switch off and unplug the streamer’s power supply, leave 10 mins and plug back in.

What I don’t understand is why it (unplugging/replugging) was needed in the first place. More perplexing is that this was initially recommended after updating but that recommendation has now been withdrawn.

Weird!

Well I certainly needed to do it (though I only left off for 2-3 minutes) as it was completely broken without doing so!

Not in my case

To my understanding, some people had problems with their systems in the state they were in after update.
Sometimes, some „system state“ is „funny“ (shouldn’t be, but happens). And with 3.5 there seems to have been an issue, that the update process was not complete in all cases. (As much as I read here.)

Then it’s the typical IT cycle during trouble shooting (to get things working again, you work differently when trying to find the root cause): sleep/wake, shutdown/power-up (e.g. with deep sleep), hard-reset (e.g. remove power) - all this could clean some transient „funny state“. If state persists, hope, that clearing all stored settings removes it. (Factory reset.)
If problem persists still, it’s an inherent fault in the software (I.e.: you need an update), a HW fault (e.g. single units being defective, maybe subtly), or something strange in the environment (e.g. funny power supply, strange devices on the network, …).
Most of the latter cases are hard to identify and need „per case support“.

So, if you want to play safe and don’t like going through several steps: perform e.g. the power-cycle or factory reset after update. Otherwise wait for issues to appear, and if they do, choose your own steps in the „escalating reset procedures“.

While ideally nothing like this is needed (for most users, if support gets many individual cases, they may send out a note to „everyone“ about optional or recommended steps, to a) help people help themselves and b) potentially offload an overloaded helpdesk.

All kind of standard procedures, as I know them from IT (support) world.

I never had such a transient issue with my unit(s), hence I never did anything special after update.
(However, I often deep-sleep my system, hence it gets „rebooted“ often anyway.)

They mean disconnect the mains from the power supply, internal or external. It’s just to avoid people putting it into a sleep mode with the front panel button and taking it out of sleep, thinking that is a full restart.

Best

David

You really don’t need ten minutes off. It need to be long enough for the capacitors to discharge. For a streamer I reckon one minute is already belt and braces.

Best

David

2 Likes

If you’re waiting for those bean can sized caps in a 555 psu to discharge, you could be waiting a while!

Just updated as well. Hope this let’s the issues be a story from the past.

2 Likes

Listened about 2 hours today to 3.5.1 on ND555. SQ is great, 24/192 material that “buffered” before now doesn’t. Too early to tell about screen freezes.

I doubt it. The ND555 will still draw significant current as they discharge. It’s not like the capacitors feeding a power amp where the quiescent current is low.

Best

David

Plus only the caps feeding any power into memory circuits should matter for this. I doubt that caps used to power the amplifier section would matter as that current would just fry the memory circuitry anyways.

Well, looks my confidence may have been misplaced - my ND5 XS2 has just done a random reboot on 3.5.1 (and I had unplugged and left for 10+ minutes). Just the one so far, so perhaps a glitch - anyone else had any issues?

My Nova on 3.5.1 randomly rebooted earlier today. Pulled the plug for 10 minutes and now fine. Fingers crossed it now behaves.

Unplugged again

Sorry @Meni, ending a long Friday and I don’t understand - are you suggesting that I should try unplugging again?
Or that unplugging again works for you?
Or (perhaps less likely) that I should try listening to some acoustic versions <;)?

My Nova had been fine but it became very laggy and glitchy yesterday. Not done a factory reset before but I thought a fresh start and app delete and reinstall plus factory reset might be a good thing to do. Been fine since then but we’ll have to see.