Handling of Apostrophes in Roon's metadata

Support
1

There are two Unicode characters for apostrophe (U+0027 and U+2019) and I find Roon uses both in its metadata. The end result is this:

Joe's Garage (U+0027)
Joe’s Garage (U+2019)

Which causes performers, composers, track titles etc. to mismatch and Roon then fails to assign associated metadata and group performances of track by the same composer. Please implement a search/replace filter to standardise existing and newly ingested metadata (presumably to U+0027).

1 Like
2

Try being called O’Neill :grin:

VB comments have lot to answer form

4

Hi @evand,

I’m going to get this over to the team for further investigation and tracking. I was hoping you might be able to provide an example (with screenshots in Roon) of this so the team can better understand the issue.

Just to be clear — This is data coming from Roon’s metadata sources and not file tags, correct?

Thanks!

5

Correct, there are instances of (U+2019) in Roon’s metadata sources. I know there are none in mine because I’ve ingested all tags from all files into a table and run a search which comes up empty.

I’ll have to keep an eye out in Roon - I’ve not kept track when encountering them.

Track artists:
https://pastebin.com/iRAT3wCF

Composer:
https://pastebin.com/JMDQT7QX

Albums:
https://pastebin.com/is8NLQeU

Albumartist:
https://pastebin.com/qe1uabP6

7

Thanks @evand — I’ll get this over to the team for further investigation.

8

@dylan, these were examples only to illustrate. There must be 1000’s of instances in Roon’s metadata cloud.

9

Hi @evand,

I looked into the data we have for some of these examples, and I’m not seeing multiple instances of the album with different characters that are causing an issue. So I can better present this to the team, can you share some screenshots in Roon of an example where the different characters are preventing items from being matched?

Thanks!

10

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.