4.6 update and upgrade sound quality ?

It’s most likely to be due to using a USB cable that is for charging mobile phones only rather than data transfer. The first time I did this I rooted around in the kitchen drawer for a mini usb cable; I had about 15 from previous mobile phones we’d had down the years. None of them worked as they were all charging only cables.

I went to Maplin and bought a data capable cable and it then worked fine.

Hope it gets sorted..

S3 posted:

It’s most likely to be due to using a USB cable that is for charging mobile phones only rather than data transfer. The first time I did this I rooted around in the kitchen drawer for a mini usb cable; I had about 15 from previous mobile phones we’d had down the years. None of them worked as they were all charging only cables.

I went to Maplin and bought a data capable cable and it then worked fine.

Hope it gets sorted..

This is definitely correct and I had the same experience of the first cable not working. But you have to get the driver installed before connecting any cable to the USB.

best

David

It has nothing to do with the cable, both are for data usage & working. Somehow the driver cannot be installed properly, Win 10 in this case. Not even if I installed it without the cable & booted the PC first... Why an earth USB & update can be this difficult?

OK I got it, it tooked 3 years to make this update & it is teasing me a BIT !!!

First there was no COM port available.

So I went off looking for drivers.

Tried all sorts until I found some that would install.

Them I got COM4 but no hook up with the streamer.

Went off and searched for more drivers, cables, etc.....

I've been over this so many times that my credit controller wants to raise an invoice to send to Naim!

Meanwhile, back on my clunky old laptop, which was earmarked for recycling in the near future, the drivers work perfectly and the updates run without a hitch.  And no, I don't have the original driver installer on this machine. Bugger!

If my old laptop had failed or been passed on, my flash new one would be nothing more than a sophisticated paperweight for this task and I would have pulled all of my (remaining) hair out.

I'm not IT stupid.  And I can RTFM. This isn't right. I think the user base needs more support from Naim HQ.

Could be a sales loser.

The so called upgrade has made my NDS sound worse. Yes a bit more detail but it also sounds brighter/harsher than before. The overall balance sound wrong too with bass emphasis and the sound stage is odd. The left/right speaker balance is too pronounced whereas before the speakers seem to disappear when listening.

I'll do a factory reset and give it another couple of days but at the moment I'm more inclined to sacrifice the extra detail and bass for the smoother and more balanced sound of the previous version. Is it possible to go back?

It is indeed possible to go back with the legacy streamers. But it would be worth trying the factory reset because most people reporting here are finding the firmware upgrade on an NDS to be good.

best

David

For those using Windows 10...

To work reliably on Win10 you now do need V6.7.5 of the driver (not the older V6.7).

wasn't sure about upgrading my NDS as it was sounding might fine anyhow - "if it ain't broke etc..." -- but curiosity got the better of me and in any case its probably a good idea to be always up to date firmware-wise

upgrade was very straight forward, just finished.

there is definitely a difference in SQ -- will need to assess a little more carefully when I have more time over this weekend and when the new firmware has "run-in" 

enjoy...

ken

Huge posted:

For those using Windows 10...

To work reliably on Win10 you now do need V6.7.5 of the driver (not the older V6.7).

Problem is how to ID if its v6.7 & v6.7.5.      The latest Naim .pdf has only one link to SiLabs & it installs whats on that link.  The link just shows as http://www.silabs.com/Support%...210x_VCP_Windows.zip & it downloads whatever tis on that link.   

The downloaded zip & then the installed driver has no such ID,  it shows as "CP210xVCPInstaller_x64"  & in properties there is no ref to anything like v6.7.

Do you have any how to find v6.7 info ????

ken c posted:

... when the new firmware has "run-in" 

enjoy...

ken

Love it!  

Mike-B posted:

Huge posted:

For those using Windows 10...

To work reliably on Win10 you now do need V6.7.5 of the driver (not the older V6.7).

Problem is how to ID if its v6.7 & v6.7.5.      The latest Naim .pdf has only one link to SiLabs & it installs whats on that link.  The link just shows as http://www.silabs.com/Support%...210x_VCP_Windows.zip & it downloads whatever tis on that link.   

The downloaded zip & then the installed driver has no such ID,  it shows as "CP210xVCPInstaller_x64"  & in properties there is no ref to anything like v6.7.

Do you have any how to find v6.7 info ????

Go into the zip file and look for a file called "v6-7-5-driver-release-notes.txt".

The important line is:
MCUSW-110    | Windows 10 certified against RS2 (Creators Update).

I have waited to post my views on SQ of the updated firmware to ensure that first impressions were sustained. I am now certain that there is an improvement through my NDS. I recognise improved clarity and definition in particular.

Just done my NDS and I must agree with GERRYMCG

OK I see that,  buts its hardly a user friendly way to ID a rev number.     The Naim .pdf link issues v6.7   (not v6.7.5)

I been in contact with Steve Harris & he tells me the teams are on to it.   

Being an old computer pro, I usually work out what any driver is, and then go to the original source to find and get the most appropriate version for my hardware and OS.

I do realise that most people either won't be that fastidious, or maybe don't have the experience to do this quite so easily as can I.

SJBABBEY,

Much obliged you sharing that link for driver installation. I just couldn't get it to work otherwise ????.

The change in sound hasn't quite got me dancing yet on the NDX. Seems to have increased the mid to high frequency for me.

I'll leave it for a few days then perhaps push the speakers back a bit and put the naca5 back on in place of TQ black ll.

Ray.

I have followed this and ready to update my UQ2, downloaded everything got cable ready etc, but reluctant to do so.

My Muso QB has been updating for 2 hours and progress has not moved. Naim app is asking not to turn off on my phone app and need to go out (i wish I'd used my tablet). If i go out my phone will not be on the same network, will it affect the update......help! 

What is actually happening with your Qb? What are the lights doing?

best

David

Huge posted:

Mike-B posted:

Huge posted:

For those using Windows 10...

To work reliably on Win10 you now do need V6.7.5 of the driver (not the older V6.7).

Problem is how to ID if its v6.7 & v6.7.5.      The latest Naim .pdf has only one link to SiLabs & it installs whats on that link.  The link just shows as http://www.silabs.com/Support%...210x_VCP_Windows.zip & it downloads whatever tis on that link.   

The downloaded zip & then the installed driver has no such ID,  it shows as "CP210xVCPInstaller_x64"  & in properties there is no ref to anything like v6.7.

Do you have any how to find v6.7 info ????

Go into the zip file and look for a file called "v6-7-5-driver-release-notes.txt".

The important line is:
MCUSW-110    | Windows 10 certified against RS2 (Creators Update).

Eat the dust & thanks for a tip but the same file, it does not work... this starts to be debugging with >10k streamer, well >25k with power supplies -> strange...

MCUSW-110    | Windows 10 certified against RS2 (Creators Update). 

Does my neighbour have an older laptop?

Hi David,

Nothing, the radio is lit, station 1 lit and the play/pause lit.

WBR

Guy

It’s very likely finished. Try changing radio channels. The app is not very good at saying what is going on. 

Hi HH,

It wont change channels, however the radio started playing. I can switch to input, but again, the input selected remains on one.

WBR

Guy

Additional, the network light is not blue.

Harry posted:

First there was no COM port available.

So I went off looking for drivers.

Tried all sorts until I found some that would install.

Them I got COM4 but no hook up with the streamer.

Went off and searched for more drivers, cables, etc.....

I've been over this so many times that my credit controller wants to raise an invoice to send to Naim!

Meanwhile, back on my clunky old laptop, which was earmarked for recycling in the near future, the drivers work perfectly and the updates run without a hitch.  And no, I don't have the original driver installer on this machine. Bugger!

If my old laptop had failed or been passed on, my flash new one would be nothing more than a sophisticated paperweight for this task and I would have pulled all of my (remaining) hair out.

I'm not IT stupid.  And I can RTFM. This isn't right. I think the user base needs more support from Naim HQ.

Could be a sales loser.

Buy new ND555? Based on this I do not. HQ make simple things easy & please do something? 

Thanks for the feedback.

I restarted the update (which is always a risk) and all seems well. The app never even downloaded the update and therefore didn't start the cycle, which it seems to be doing now, with rotating volume segments and white network light and sound.

Phew, didn't fancy a £650 bricked paper weight.

I guess this is due the stability of the (android) app.

WBR

Guy

Gandalf_fi posted:

Eat the dust & thanks for a tip but the same file, it does not work... this starts to be debugging with >10k streamer, well >25k with power supplies -> strange...

MCUSW-110    | Windows 10 certified against RS2 (Creators Update). 

Does my neighbour have an older laptop?

May I see if I can help?

First, go to Control Panel\All Control Panel Items\Programs and Features
Have a look for "Windows Driver Package - Silicon Laboratories Inc. (silabser) Ports (9/27/2017 6.7.5.1893)
If you don't have that, the right driver isn't installed

Next connect a data cable to the NDS.

Then go to Device Manager and look for "Ports (COM & LPT)
Expand that and look for the "Silicon Labs..." entry (there should only be one)
Look at the properties
Is that COM4?
If not note what COM port it is on.
If there's more than one COM port shown, what are the others listed as?