New firmware update

Sorry to ask but is the Krystal a dust magnet and how on earth are we to clean? Never had such issues with my older AT cartridge.

Hi AC. I find the Krystal picks up dust on the taped underside which is a tad bothersome visually, but doesnā€™t affect the sound. The stylus picks up no more than my previous 10x5. A quick dab on the Vinyl Passion sticky pot quickly clears it away though. Just read your post on the Sondek thread and it definitely shouldnā€™t be sounding anything other than wonderful after those upgrades. Something is faulty or the Krystal doesnā€™t like how itā€™s being loaded/matched into the Nova maybe?

1 Like

Thanks KJC

I also noticed dust sticking to the ā€˜microporeā€™ like tape, mostly on the right of the cartridge as I look at it.

On older cartridges I had used AT liquid cleaners but have only used Linn green paper on this (why is none supplied with the cartridge or any instructions?).

The LP12 feeds an originally purchased recently serviced Linto which connects to my NAC 282 (as does the Nova as a temporary streaming source).

Sounds like a call to your dealer to sort out I guess AC. If my experience is typical, then your new TT really ought to be sounding wonderful.

1 Like

Thanks, Iā€™ve either been caught out in the hype, new presentation isnā€™t for me or somethingā€™s amiss with LP12 or generally.

Iā€™d be pleased if Naim Audio would make v3.4 available to everybody to ā€˜downgradeā€˜ if they wish until a fix to v3.5 is developed.

3 Likes

Iā€™d say until they actually ā€œfinishā€ v3.5 :roll_eyes:

I think my Star rebooted the other day, but as you say, I wasnā€™t listening to music at the time. I just suddenly heard the relay clicks you hear when you first power it on after a power cycle. I didnā€™t go over to check, so not sure it was indeed a reboot.

Or promptly release a v3.5.1 instead of having us wait 5 months for v3.6.0

1 Like

Iā€™d be pleased If v3.4 were made available (and v3.5 withdrawn) first thing Monday morning.

1 Like

Not sure it would be the best action to makeā€¦
But a serious discussion with their software team is mandatory.

" I suspect that all NDxxx users are experiencing random reboots ( in fact Iā€™m pretty sure of thatā€¦ )"

Nope.

The only weird thing Iā€™ve got now is the app display malfunction where it randomly doubles up on albums in my Qobuz list accessed via the ā€œFavouritesā€ symbol.

ND5 XS 2.

Clive, are you in touch with Naim tech support?

Iā€™ve had no problems with 3.5 and do not want to downgrade to 3.4. I would be certainly annoyed if it was withdrawn. Sound quality and functionality are superb here. There must be other gremlins at play.

2 Likes

I wouldnā€™t be that definitive about that. A reboot takes a couple of minutes and without a screen itā€™s hard to tell.

Taking a look at the DHCP server logs should give you an accurate answer.

+1

No problem with my ND555. No reboot.

I must admit that I powered it down while installing my new 552. But it was after the installation of the new firmware which in itself improved somewhat the sound clarity.

I didnā€™t do the factory reset.

1 Like

Thatā€™s what I thought too, until I checked my DHCP logs (and, of course, experienced a reboot while listening to some music).

Considering we have the same hardware and the same software, it is unlikely we donā€™t share the same problem.

But, of course, Iā€™d be glad to hear someone is not having problems with the v3.5.

1 Like

Weā€™ve had one member on here complaining about pops and crackles, distortion coming from their speakers, and was absolutely convinced it was the latest FW update causing it. It turns out, in the end, his new speakers were at fault. There needs to be some sort of perspective put into place here before bashing the update.

1 Like

Indeed. But random reboots are a problem, even if silent :wink:

1 Like

I have logged the uncommanded reboot as an issue and have received a ā€˜Ticket Numberā€™. I think Iā€™d rather live with a fortnightly screen freeze than the random interruption that v3.5 introduces. Of course, the screen freeze might not have been fully resolved with v3.5, but Iā€™d rather not wait to find out.