Asset issue?

Posted by: Mark Arnold on 10 December 2015

Hi all, ive ripped some of my albums onto my PCs hard drive (about 90 cds in total) so far and using Asset all working fine except on compilation albums its not showing the artist in the display of my NDX? Ive also noticed that occasionly i get the wrong song title with the one thats playing from the same artist? Any ideas?

Cheers

Mark

Posted on: 10 December 2015 by Huge

You need to sort out your metadata using an editor like DBPoweramp.

Posted on: 10 December 2015 by feeling_zen

Yeah this sounds like the type of problem you get when ripping compilations as WAV and applying metadata according to folder structure.

For sure you can fix this in dbpoweramp. But I think you can also prevent it happening in the first place.

Can you describe your current ripping and tagging process to us? That is better than second guessing where it is getting mixed up.

Posted on: 10 December 2015 by Bert Schurink

I think ripping as such always leads to some tagging issues which you can't totally control with the adaptations you can make in the ripper. So I always have the workflow. Ripping and trying to already clean as much as possible at the begginning. Put the album into MP3 tag and QA again are the tags correct is the artwork showing up correctly. Then I move the files to the NAS and make the real test by listening at least to the first song. Any sounds issues, sometimes the first song us distorted, do I have the artwork showing up, was the tagging and grouping correct.

 

very often I realize that I am myself the source of the problem especially when I am ripping tons of cd's

Posted on: 11 December 2015 by Mark Arnold

I ripped cd's via DBpoweeramp to Flac then transcode to WAV to the NDX from my computer

 

Posted on: 11 December 2015 by feeling_zen

That actually seems like it should be problem free to me. If you right click the files to view the metadata in dbpoweramp is the labelling correct? And if so, does rescanning the entire Asset linked library (not just for updates) change things?

Posted on: 11 December 2015 by Nick B

Having experienced the same issue in my setup using an NDS and Asset 4.6.1. on a QNAP NAS I believe this is an issue with Asset causing the problem in the Naim app. If you're sure your metadata is correct, try using the Kinsky app instead of the Naim app and the track artists should appear ok for your compilations (which makes it *look* like the problem is with the Naim app, but as I understand it the problem is related to the data Asset is sending to the Naim app - I may be wrong on this).

From the Asset forum, I believe this is a recognized bug which has not yet been fixed, but will be. Hope this helps.

Posted on: 11 December 2015 by Mark Arnold

Ok will have a look later at this thanks for all your help, hopefully rebooting asset will sort it

Posted on: 11 December 2015 by mrspoon

If you have an album artist and artist value Asset sends as:

<upnp:artist role="AlbumArtist">AlbumArtistValue</upnp:artist><upnp:artist role="Performer">ArtistValue</upnp:artist>
 
This is correct, however the Naim app is choosing the AlbumArtist value to show next to each track listing in an album listing, instead of the artist (performer). Ideally the album artist value should be shown at the top, and the artist value next to each track.
 
If you remove the album artist value from the tags (it is not needed anyhow for compilations, no need to have as 'Various Artists'), then just the artist value is sent.
Posted on: 11 December 2015 by Harry

Select an album. Clean all the tags out - everything. Put your own in. Does that fix it?

Posted on: 11 December 2015 by Nick B

Just tried removing the album artist from the tags for one compilation as a test, then rescanned for changes in Asset and restarted Asset (don't know if any/all of these steps is required) and track artist is now displayed under the track title - result !

Thanks for the tip Mr.Spoon !

I'm sure I've tried removing the album artist before so I'm curious to know whether I missed an element in the remove album artist-rescan-restart process or whether it's this in conjunction with the upgrade to Asset 4.6 or 4.6.1 that has resolved the issue.