Naim app and Asset: issue with hypen sign

Posted by: nicopra on 31 August 2015

I recently bought a new Qnap NAS since my old one couldn’t run Asset.

I have a strange issue with the Naim app and Asset.

I use the hyphen sign a lot when editing the metadata of my music files (example: “Wiener Philharmoniker - Nikolaus Harnoncourt” as artist or “Jazz - Vocal” as genre).

When I browse Asset with the Naim app, it only diisplays the first part of those tags.

For example “The London Symphony Orchestra - Sir Colin Davis” displays as “The London Symphony Orchestra”

or

“Classical - Baroque” and “Classical - Medieval” are displayed as two different folders when browsing by genre but both with the name “Classical”.

That makes it impossible for me to browse my collection properly.

It only happens when browsing Asset with the Naim app.

It doesn’t happen if I browse Asset with other clients (I checkked with MediaConnect on my tablet and PlugPlayer on my Mac)

It doesn’t happen when I browse MinimServer with the Naim app.

Anyone having the same problem? Is it a known issue? Is it a Naim or Asset issue? Am I condemned to retag most of my files if I want to use Asset with the Naim app?

Sorry for my bad english, I hope I was clear enough.
Cheers
Nicolas

Posted on: 03 October 2015 by JSH
Glad to be of some help. It depends on how many files you have but Bulk Rename Utility ( or something similar) might allow you to search and identify all the hyphens and replace them with tildes without spending for ever
 
 
Originally Posted by nicopra:

You were right JSH: not a word from Naim since two weeks.

 

Let's hope the new 4.4 firmware version will have that issue fixed!

 

And you were right again: I checked the several softwares I use to edit metadata and discovered that Jaikoz is able to batch replace a character in the metadata fields (Metadatics and dBpoeramp can't).

 

Though I didn't find the courage to start that. I'm waiting for the updated firmware and app with my finger crossed

 

Posted on: 06 October 2015 by nicopra

I just installed today's app update and cleared the UPnP cache: no change, the bug is still there.

 

I hadn't many hope as I got a message from Phil yesterday telling me the issue had been verified and was worked on.

 

Let's hope the next update will solve that (and bring us Qobuz streaming in the same time - what a christmas gift it would be for me !)