Core metadata problems

Posted by: Icedragon05 on 12 August 2018

Came across this problem when ripping CD today... Initial rip it shows as Unknown Album Unknown artist with some random index numbers. Refreshed metadata via all providers in the app, no help. Edited metadata originally Artist and Cover which appeared fine... then added tracks (15) saved and all looked ok, however when I went back to it later all change.

Currently in artist view it is in an unknown artist folder (correct cover) but no tracks with a few others that are in downloads folder and are labelled unknown

In album view it has now reverted to Artist correctly labelled album unknown cover correct all track edits have gone.

It did at one point appear in a artist folder next to others (same band)... which all ripped correctly with all correct metadata.

I have restarted the app(s) (mobile and tablet) and restarted and powered off the core without change.

anyone have any ideas how to "force" the metadata to save?

Posted on: 12 August 2018 by garyi

Are you certain your core has access to to the internet, it almost seems its unable to resolve DNS. If you have set a fixed IP, set it back to DHCP and try the rip again.

 

Posted on: 13 August 2018 by Icedragon05

It has access, it correctly ripped and saved cd's by the same band directly either side of this one.... I attempted rips with this album several times when it was showing no metadata, without change, and future manual labeling appears the problem. I tried this cd in my pc with media monkey which immediately correctly identified the metadata.

Posted on: 13 August 2018 by David Hendon

It's quite common for the Core metadata lookup to not find details on a CD. This is random so far as I can see and mostly if it doesn't find the metadata at the first go, it won't subsequently either, for all that it is supposed to keep looking. The metadatabases that Naim use seem just not to be very good, which isn't Naim's fault but does detract from the package.

But I haven't ever seen the problems with making metadata edits stick that you describe. Occasionally I have found the app does fail to leave Custom selected, so I have to go into edit again and reselect it, but that's all that I have noticed. It would be worth reporting your issue in the feedback option in the app because Naim are working on a service update for Core and this is something they could perhaps look at before they release the update.

best

David

Posted on: 13 August 2018 by Icedragon05

Yeah will do, it's only the misbehaving album so far and I might try a WAV download of the album and see if I can get that to stick.... haven't had much luck with that so far in downloads, even if picture in folder in the correct format it doesn't seem to find it and lists them as various.

When u say " fail to leave Custom selected" is that in the editing metadata section?

Posted on: 13 August 2018 by blythe

Depending on the way your core is set up, (I don't have one, so I might be barking up the wrong tree) it may be running some back-ground tasks which means any meta data changes cannot be made until its finished those back-ground tasks.

This is certainly the case with my HDX, where I have to wait some time before I can edit track/Artist data.

Posted on: 13 August 2018 by David Hendon
Icedragon05 posted:

Yeah will do, it's only the misbehaving album so far and I might try a WAV download of the album and see if I can get that to stick.... haven't had much luck with that so far in downloads, even if picture in folder in the correct format it doesn't seem to find it and lists them as various.

When u say " fail to leave Custom selected" is that in the editing metadata section?

If you go into edit metadata and it's an unknown album, unknown artist, then when you edit the entry you do so against the custom tab, which is the fourth option after Rovi, MusicBrainz and FreedB. If you work up a Custom alternative then once or twice I've had it  revert to Rovi or whatever and I've had to go back and tell it what I wanted to do again. I don't think this was just operator error by me, but it might have been (and it might have been with a beta too - I can't remember now.)

The Core doesn't have the shortcoming of having to wait to do edits that Blythe mentions. You can crack on with edits as soon as the rip has saved into the Core (a few seconds normally) and while it's ripping the next CD and playing a previous rip simultaneously too. 

Best

David