MusicBrainz lookup issue with latest Uniti Core software 1.5 (7957)

Posted by: Sourav on 18 August 2017

MusicBrainz lookup used to work absolutely fine after the software update happened in month of April.
However, after I installed the latest software update (Aug 14th) it has has stopped working. Even the force Lookup 'Lookup Metadata' in Edit Metadata option does not bring the meta data from MusicBrainz.

Sent an email to uniti-support and Phil in this regard.
 
Regards,

Sourav

Posted on: 18 August 2017 by David Hendon
Sourav posted:
MusicBrainz lookup used to work absolutely fine after the software update happened in month of April.
However, after I installed the latest software update (Aug 14th) it has has stopped working. Even the force Lookup 'Lookup Metadata' in Edit Metadata option does not bring the meta data from MusicBrainz.

Sent an email to uniti-support and Phil in this regard.
 
Regards,

Sourav

It's still working OK with my Core which is also on firmware version 1.5 . I forced a lookup just now and the MusicBrainz lookup of a CD I chose at random took about 15 secs to return the result. Maybe it was down when you tried?

best

David

Posted on: 18 August 2017 by Sourav

Its working for existing albums in MusicBrainz.

But not when I add a new album in MusicBrainz. It used to work for new albums absolutely fine (used to show up in Core within few minutes) after the software upgrade in April.

Regards,

Sourav

Posted on: 18 August 2017 by David Hendon

Ok I will give that a try....

best

David

Posted on: 18 August 2017 by David Hendon

So I ripped a new CD which I was sure Musicbrainz would have (a Joni Mitchell album from way back) and Rovi found it. So I asked it to find MusicBrainz metadata and it took 10 secs or so to do so. Seems OK to me.

I suggest you try restarting your Core and the app too.

best

David

Posted on: 19 August 2017 by Sourav

Hi David,

I tried totally rebooting core by completely disconnecting the power cable. No luck.

This is something very similar to what it used to happen when I first time bought core in Feb. This problem got fixed after the software release in Apr.

Try inserting meta data in Mysicbrainz for a CD which does not already have meta data there. And then rip the CD using core. U should be able to replicate the problem.

However thanks a lot to u for trying to reproduce the problem.

Regards,

sourav

Posted on: 19 August 2017 by David Hendon

I'm not sure I understand what you are doing.

The way I use the Core is put the CD you want to rip into the slot on the Core. Let it rip and the CD will be ejected. Within a minute or so you can see the CD in the app. Click on it and then click on the 3 dots on the top right of the app screen. Select "Metadata editing". You can see the metadata and which metadata source it is using. You can select the Musicbrainz tab and if that metadata is missing, force a lookup by tapping on the link. After a few seconds it will either populate the Musicbrainz tab or tell you that it couldn't find that CD on Musicbrainz.  You can pick and choose and edit every field you can see there, so take the title from Rovi, the track names from Musicbrainz and edit some to say what you want for example. It's very flexible. And it checks metadata in the order Rovi, Musicbrainz, FreeDB. Once it's got a result it doesn't check anymore unless you force it to using the metadata editor.

If you rip the CD again (which isn't necessary unless you have missing tracks or errors or whatever), it just over-writes what is already there so it will lose the Musicbrainz setting you made on the copy already in the Core.

You might want to call Naim support to see what they say, but the above is based on my own experience of using the metadata editor a lot.

best

David

Posted on: 19 August 2017 by Sourav

Hi David,

Ur observations are sbsolutely in line with what I have experienced too.

However most of my CDs do not have meta data in MusicBrainz. So what I do is I go to MysicBrainz and add meta data for them. And then they used to appear in Core within few minutes.

After the software upgrade on Aug 14th if I add meta data for a CD (which did not have meta data in MusicBrainz) and then rip the CD,  the meta data does not appear in Core.

Regards,

Sourav

Posted on: 19 August 2017 by David Hendon

The reason most of your CDs don't have data in the Musicbrainz tab is because normally the Core finds it in Rovi.  Why do you want to add the Musicbrainz lookups?

You don't need to rip the CD a second time anyway. If you want to use the Musicbrainz metadata, you force a lookup, select what you want and press save. Then the Core will use whatever you told it to for that album.

If you rip a CD again after you have edited the metadata on the first rip, the Core will overwrite the old copy and you are back where you started.

I think it is working properly and I don't understand why you are reripping CDs that weren't using Musicbrainz metadata? You shouldn't rip the CD again.

best

David

Posted on: 19 August 2017 by Sourav

Well I am not re-ripping the CD. It's the first time repping itself causing the problem.

Regards,

Sourav

Posted on: 19 August 2017 by David Hendon
Sourav posted:

 

After the software upgrade on Aug 14th if I add meta data for a CD (which did not have meta data in MusicBrainz) and then rip the CD,  the meta data does not appear in Core.

 

This is the bit I think you have misunderstood. You should edit the metadata to add Musicbrainz after you rip the CD, not before.

best

David

Posted on: 19 August 2017 by Gazza

This may be similar to the King Crimson double cd, where a Rovi identified cd 1 and 2 as the same. Music brains forced look up would not save? Never had a reply from Naim!

Posted on: 19 August 2017 by Sourav

So u mean -

I first rip the cd. Then after finding that it does not have meta data I should go and add the metadata to MusicBrainz and lookup meta data using Core again ?

Regards,

Sourav

Posted on: 19 August 2017 by David Hendon
Sourav posted:

So u mean -

I first rip the cd. Then after finding that it does not have meta data I should go and add the metadata to MusicBrainz and lookup meta data using Core again ?

Regards,

Sourav

 

Yes that is what I am saying.

Ok so first rip the CD. Wait until it appears in the Naim app. Select that album in the app. Look for the three dots ... on the screen that shows the track listing. Click on that and there is a drop down menu. Click on metadata editing. You now have a new screen that allows you to see the metadata and where it comes from. You can select the tab Musicbrainz and if it's blank then click on the link that says "lookup metadata". After a few seconds it will either add the Musicbrainz metadata or tell you that it can't find any on Musicbrainz. You can choose what metadata you want to use and then click "Save" to get back to the track listing screen. All of these edits will stay in the Core and be used from now on. Obviously you can go in and edit again as many times as you want.

You mustn't edit metadata for CDs ripped in the Core any other way. For example if you use a metadata editing programme on a PC to edit a rip on the Core then firstly the Core will likely ignore those edits and you may break the indexing and find the Core doesn't show that or other albums at all. It is ok to edit metadata on downloads and rips in the downloads folder of the Core. In fact you have to do that because the app won't edit those even if you try. 

Bedt

David

Posted on: 19 August 2017 by David Hendon

You only add metadata to CD rips in the Core from inside the Naim app, never from any other metadata editing software.

best

David

Posted on: 19 August 2017 by David Hendon
Gazza posted:

This may be similar to the King Crimson double cd, where a Rovi identified cd 1 and 2 as the same. Music brains forced look up would not save? Never had a reply from Naim!

I think he's editing the metadata on Core rips with external software, so not the same problem you had.

Best

David

Posted on: 19 August 2017 by Gazza

OK did not pick up on that, thanks

Posted on: 19 August 2017 by Sourav
David Hendon posted:
Gazza posted:

This may be similar to the King Crimson double cd, where a Rovi identified cd 1 and 2 as the same. Music brains forced look up would not save? Never had a reply from Naim!

I think he's editing the metadata on Core rips with external software, so not the same problem you had.

Best

David

No I'm not.I'm not changing metadata file created by Uniti Core by using some other software.

I'm adding/editing the metadata by going directly to MusicBrainz application (https://musicbrainz.org/ and using MusicBrains PiCard application). This directly adds data to MusicBrainz database. Naim Core is supposed to pick up the data from that database.

I add/edit the data directly there because the other software/products I use (like Roon, PS Audio Memory Player, etc) also pick up metadata from MusicBrainz database. So I add it in one single place and every software picks up the data.

And this was working absolutely fine for Uniti Core till last week before the latest software upgrade of Uniti Core.

Regards.

Sourav

Posted on: 19 August 2017 by David Hendon

OK I see! I didn't understand that at all. 

I wonder how long it takes Musicbrainz to copy edits you have made across to the online database which Naim is querying. I assume that it won't be instant but will happen eventually, in which case you can update the Musicbrainz lookup in the Naim app (by pressing the "lookup metadata" link). It should bring down the latest data - in fact it tells you the time and date of the lookup. You might need to wait until the next day or something.

Possibly Naim is querying a different Musicbrainz server in the latest firmware, and the speed of proposing user updates across the Musicbrainz estate may not be uniform, but you need to talk to Naim support, I suggest on the phone, as this is quite hard to explain, as we have both found out! You can also report it using the in-app feedback which will get read by Naim. Good luck anyway.

best

David

Posted on: 07 September 2017 by Peter Lambert

I use MusicBrainz, and CDs added from Picard are added immediately to the database, and I think they can be retrieved immediately as well. But it maybe that Naim are using their own copy of the database for stability, and only update it once a day or once a week, would be interesting to know.