UnitiServe Problem w/ Recent CD's

It's because the metadata on newly released stuff is not in the AMG database. It's nothing to do with firmware.

That certainly answers the problem I am having and this must be an issue for many others as well.

What firmware are you on at the moment Audio 1 ?

Latest firmware for US/HDX etc released in Dec14 is 1.7b.

https://www.naimaudio.com/updates

This update also included MusicBrainz look up, so as I interstand it, the US looks up

AMG and if it doesn't find it then looks up MusicBrainz for a match.

Maybe this may solve the issue you are having?

Good luck!

You may have an issue with your internet connection? If you have no connection when you rip a CD the US will use it's own database to look for the info instead.

Being a new UnitiServe owner i've been ripping my CD collection over the past couple of weeks and after doing 500 or so i've had one that wouldn't rip at all (but would rip on my dealers NS-01) and a couple where it starts ripping songs and then stops and throws an error code

In one instance I cross checked it against the AMG database and found that there was an error in their metadata at that point.  I've had a few more that have done a similar thing but haven't cross checked the metadata yet.  

I had the thought of trying to rip these CD's with my internet disconnected to see if it makes a difference with the Serve not being able to interrogate the metadata and just ripping what is on the disc.  Will hopefully get round to trying it this weekend

The first time I ripped a disc without an internet connection, the UnitiServe's internal database decided to name it Start Transmission by Digital Blood, the next rip came back as Come Clean by Puddle of Mudd, with track titles like "Drift and Die", "Out of My Head", "Piss it All Away", and the noteworthy " She Hates Me". I chuckled at the sense of humour of Naim's programmers, sitting in the pub conjuring up names to fill a starter database... until a quick search revealed...

Egads !

Going back to the OP's problem, the issue of recognising a CD as being a CD is different from the issue of recognising what CD the CD is.  If the US chucks it out without ripping it, then it isn't recognising it as a CD.  That may be because it is damaged (unlikely if it is several unrelated CDs that show the problem) or because the CD in some way departs from the Red Book standard - for example because the disc has copy protection. It is nothing to do with whether or not there is an internet connection or whether the on line databases are correct or not. If the US fails to recognise a significant number of unrelated recent releases (by unrelated I mean different artists and different labels) then this sounds like a hardware issue and your US may want to go home to Salisbury for a visit.

if on the other hand the US rips the CD successfully but misidentifies what the CD is, then this is an issue about the databases which are checked by the US over the internet, or accessing same, or both.

i have had about 1% of CDs where for one reason or another the CD isn't recognised and also won't play on my Unitilite, but which plays fine on my Quad CDP99 and in my car. i ripped these with a PC and added them in them the downloads folder. I have had a similar number which are identified by my US as being something else entirely from what they are. This is a bit irritating but I too find fixing the issue immediately using the n-serve App on my iPad is the way to go. Quite a few, mainly older classical, recordings get the wrong cover art as picked by the US, often because there are multiple reissues and re-masterings of the same recording, but this is trivial to fix in n-serve as well.

i could imagine that if one had a real specialist interest, recognising what CD the CD was could be something to expect, but for people who buy mainline current or recent releases, i would think a frequent failure of the US to Identify the disc correctly might be something to have a chat on the phone with the excellent support guys at Naim about because its probably a network or configuration issue.

hope this helps

David