Beethoven's Piano Sonata Op. 14/1 still misrepresented as String Quartet Hess 34

[Hans_Valeton]

Continuing the discussion from [Beethoven’s Piano Sonata No. 9 Op. 14/1 misrepresented as the string quartet version in quite a number of albums]
(Beethoven's Piano Sonata No. 9 Op. 14/1 misrepresented as the string quartet version in quite a number of albums):

After five years (5 years!!!) nothing has been done about this issue? Why?

In the meantime my collection (only local files, no Qubuz or other subscriptions) has only grown.
And now, on the Beethoven Composer page, under compositions, I can now no longer find the original piano sonata composition, only the string quratet version:

Of the 56 recordings in the above list, only a few are of the actual string quartet version.

I’m getting a bit impatient! When is this ever going to be resolved???

[tripleCrotchet (Tony)]

It would be nice to get these composition miss-identifications fixed at source. Many others unfortunately. You can usually fix these manually, but I get why you don’t want to do that 56 times.

[Hans_Valeton]

@tripleCrotchet
Thanks for your reaction, Tony. It set me thinking.
I think the reason why not many people care about this misattribution is because it only occurs when I let my own file tags prevail over those supplied by Roon/TiVo.

Let’s take the 2022 Daniel Barenboim recording of Beethoven’s Piano Sonatas Nos. 7-12 as an example.

When i temporarily set the metadata preferences on album level ‘Multi-part composition grouping’ to ‘Prefer Roon’ and, for good measure, ‘Track’s title’ to ‘Prefer Roon’, then the 9th piano sonata is correctly shown:

But for every album that I’ve painstakingly tagged and groomed in Roon, I have always set the aforementioned metadata preferences (again, on album level) to ‘Prefer file’. And then the album is shown as follows:

Apart from from the obvious misattribution, this looks much better from my perspective. I hate the Roman numbers in the numbering of the movements, and I really don’t like Roon’s inconsistencies in composition / movement naming.
In my own file tags I have made sure that for every instance of a composition the WORK tag is filled with the exact same composition title.
In this case: Piano Sonata No. 9 in E major, Op. 14/1, which is, by the way, the canonical name of the composition according to TiVo/AllMusic.
Roon has a way of showing all sorts of variations on the canonical composition name in the album page, and only when you navigate to the composition page, the canonical one is consistently shown, although for Beethoven sonatas these inconsistencies are far less frequent than for lesser known composers.

To resume:
When Roon is allowed to show the composition/movements it gets from the TiVo database, it has no trouble showing the correct one, both in the album page as when navigating to the composition page.
But when I put the (mostly) exact same composition name in the WORK file tag, Roon suddenly couples the Piano Sonata to its String Quartet version.
This is so weird!

[tripleCrotchet (Tony)]

@Hans_Valeton

When i temporarily set the metadata preferences on album level ‘Multi-part composition grouping’ to ‘Prefer Roon’ and, for good measure, ‘Track’s title’ to ‘Prefer Roon’,

Interesting. I didn’t realise that has an effect. Mostly I just manually set the WORK/PART tags and that’s usually enough to correct miss-attributions. Every now and then it doesn’t work so I’ll try that trick next time.

I rather suspect the reason there is so little traction to fix long-standing composition miss-attributions like this is that they mostly go unnoticed in libraries.