Naim app and Asset: issue with hypen sign

I use the hyphen on my UnitiServe, and with Asset and Minimserver, with the Naim App, and do not have issues.  I have a few albums with a hyphen in their name (Beatles anthologies, and a lot of live Grateful Dead concerts).  Are you using a standard EU or North American keyboard?  The traditional ascii hyphen or minus sign (ASCII 45) should not cause issues I am pretty sure.

Thanks for your answer Bart,

My keyboard is European (QWERTZ - Swiss French). I don’t think it could be at fault.

May I ask if you use spaces before and after the hyphen in your metadata tags?

I’m gonna post that in the Asset forum as well and see if something comes from there.

I have to say I don’t understand what’s happening and why I would be the only one to have that issue.

Any suggestion is very welcome

Hi Nicolas, 

I'm new to this world (almost about to finish ripping my CD collection).

I'm using DBpoweramp to rip my CDs and I notice that it tends to use commas rather than hyphens and the text after the comma does then show up within the naim app.

I had a play last night with using hyphens and the text after the hypen (I entered in dbpoweramp) did not come across into the naim app.

Harty

I've not used Asset in anger, but is there a setting which is meaning that hyphens are treated as a separator?

So

ARTIST = Wiener Philharmoniker - Nikolaus Harnoncourt

is being interpreted as

ARTIST (1) = Wiener Philharmoniker

ARTIST (2) = Nikolaus Harnoncourt

Feeling_zen, I'm sure it's hyphen signs and not em dashes. I only have FLAC files transcoded in WAV by asset

Eloise, I can't find a setting in Asset to change it's behaviour with hyphens. And no, in your example I only have ARTIST = Wiener Philarmoniker

So it seems some people liike Harty601 or myself have that issue and others like Bart don't: that's a bit weird.

But the most bizzare point still is that the problem only occurs when browsing the Asset server with the Naim app and not with another client.

Have you posted on the Asset help forum? They actually respond very quickly and you may search and find a similar issue.

Rather than chase our tail here, I found their free support extremely good.

I checked again, and album titles with a dash appear fine.  I've not tried to put a dash in an ARTIST field, but will happily do so later today when home just to see what Asset does with it in my Naim App.

I did search the Asset forum and found only one issue that was close to mine (similar but only when navigating by folders)

I did post there and was asked to send them one of my file. I did that and I'm now waiting for their answer.

Bart, may I ask if Asset is running on a Qnap NAS at your place? If it is the case I'd be very interested to have a look at your Asset configuration page. Do you think you could do a screen capture for me?

Nico, yes Asset is running on QNAP. Let me see if I can find and screenshot the config page for you.

I don't see anything on the config. page that looks remotely connected.  Anything particular you want to see?

Me neither Bart: I can't see what I could change in Asset to get rid of that issue.

I did a screen capture of my configuration if you'd prefer to check for differences with yours by yourself:

https://dl.dropboxusercontent....setConfiguration.png

I can also give you a link to one of my music file if you want to check it in your system.

I see you have a NDS, I have a NDX: could Asset and Naim app react differently because of that?

I'll wait for the answer from the guys at Asset before contacting Naim support.

Thanks again for your help

Nico - send me an email (mine is in my profile) with a link to a file  / files that give you problems and I'll try them on my server with Asset.

Done Bart, you should have my email.

I got an answer from Asset:

"We have reported to Naim, as everything looks correct from our side"

I'll write to Naim support about that. I'll just wait to see if the file I sent to Bart is showing right in his setting as it would mean that the issue is there with the NDX and not the NDS.

So Bart did try one of my file in his setting (thanks so much again for your time and help Bart).

He doesn’t have the issue in his setting. The difference I could spot is He’s using a NDS as I’m using a NDX.

I also discovered that I could get rid of the problem by enabling the UPnP compatibility mode in the Naim app settings…

… but at the price of not having the use of play queue and playlists (which is not very satisfactory).

I did write to Naim support and will let you know of the answer.

Cheers

FWIW I had the same issue. 

As a workaround, I simply use the tilde ~ instead of a dash - and it works perfectly

Thanks JSH,

I know I could go through all my files and change all the metadata tags that have dashes in a field but I still hope it could be corrected in a future app update.

I have to admit I'm not over enthusiastic about spending hours in retagging my music library

I had an answer from Phil telling me he was passing that to the software guys. Lets wait and see...

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

Did you determine the precise ASCII code your system is providing for the dash?  I know from experience that certain characters can be problematic on my UnitiServe; the standard ASCII dash is not one of them.  I believe that the standard dash is ascii code 045; it might be interesting to see if indeed that's the character your system is choking on.

I run Mac OS X 10.10 and use a QWERTZ keyboard (Swiss French).

I verified: the ASCII dash code is indeed 45.

I don't think the problem is there as it is only occuring with the Asset and Naim app combination (not when using MinimServer instead of Asset and not when using other clients instead of Naim app).

Did you change the entry, so that it was shorter before? Maybe you have to clear the upnp cache in the naim app?

Interesting . . . just "one of those things" I guess.