Trouble with Prokofiev

I have observed trouble again with misidentification of works that have similar Opus numbers orID’s

This one seems similar to the problem I have reported 2018 which is still not resolved IMO

Prokofiev has compiled three suites for his Ballet “Rome & Julia”. I have a couple of compete recordings and a couple of Suite recordings.

As per AllMusic there are the following work titles

  • Romeo and Juliet, ballet in 4 acts, Op. 64
  • Romeo and Juliet, Suite No. 1 for orchestra, Op. 64 bis
  • Romeo and Juliet, Suite No. 2 for orchestra, Op. 64 ter
  • Romeo and Juliet, Suite No. 3 for orchestra, Op. 101

I have tagged my files accordingly, but Roon is not able to distinguish them properly.

Examples:


My File Tags:

AllMusic

Roon lists it as three separate work instances but with the same work title, which neither comes from my files tags nor should it probably come from TiVo’s metadata.

The metadata reference is set to “prefer file”. If I switch to “prefer Roon” I get the following:

This are the file name tags only and not grouping happens whatsoever.

Switching back to “prefer file” yields the following:

This is not consistent with what I had before switching from “prefer file” to “prefer Roon” and is not consistent with my file tags at all.

This is just a single example. The attribution of work titles to me look like a total hit or miss.

@support could you please look into this? I think it’s a more general problem.

it‘s been a week without any reaction on this. I might as well just stop reporting anything and just quietly keep getting annoyed by these kind of issues, since nobody else seems to be experiencing them or might be bothered by them…

I just feel you…
I am in your same situation…bugged with all these troubles.

1 Like

Hi @Klaus_Kammerer1

Apologies for the delay! Our team’s queue is longer than typical at the moment, but we’re working to get back to everyone as quickly as we can.

I just wanted to reach out and let you know that our team has taken a look at your report and we put a ticket in for this issue. We appreciate the feedback!

2 Likes