Disc No 2 is mislabelled - seven of the eight tracks are being identified as Symphony No 3 Eroica - which only applies to the first four tracks. Only the last track is being identified as Symphony No 2
My Beethoven 1-9 box (John Elliot Gardiner) set was completely messed up. Only two of the 9 showed up even. had to modify the meta data to get them to show, then had to fix all the mislabeled/identified albums and tracks. Classical seem to give ROON fits with all the different ways the tracks have been labeled and identified over the years.
I ran into the same problem with a boxed set of Shostakovich symphonies. Each CD had a slightly different title or title syntax.
I just renamed/combined the directories and/or renamed the files on disc to read the way I wanted.
Not really Roon’s fault. Really the fault of the ripper and the database it’s looking at.
@support, this issue was raised 3 years ago. As far as I can see it was never addressed. It is certainly fixable using WORK/PART tags in local libraries. However, with streamed content it is not.The Zinman Beethoven Symphonies 3 & 4 were re-packaged many times. I have added the complete 9 symphonies from Qobuz but it seems to be a problem with any Zinman Beethoven Symphonies 3 & 4 release.
Here you can see that on Disk 2, tracks 1-7 are assigned Beethoven Symphony 3, and only track 8 assigned Beethoven Symphony 4. It should be tracks 1-4 = Beethoven Symphony 3 and tracks 5-8 = Beethoven Symphony 4. It is not possible to fix these sorts of streamed metadata errors manually within roon. Is there something that can be done upstream with the metadata suppliers?
@Tony_Casey This one obviously fell through the radar a long time ago. Apologies for that. We’ve sent an request to the relevant metadata provider to get this fixed.
Manual settings sorts it , they seem to have Symphony 3 & 4 merged in some way.
The original track names have no Delimiters between work & part eg “-” or “:”
While we’re on old ones , the Symphony 3 metadata issue is still there
Now go to the composition
There is no split between Local and Tidal (in my case) , the other Symphonies are fine just Symphony 3
this is Symphony No. 2
Hej Mike. What exactly are you doing? Doesn’t work for me. Are we talking about the same thing?
This is streamed content (Qobuz). Not a local library.
-
In my case it is not only that there are no delimiters (“:” or “-”) there is no PART information coming through from Qobuz either.
-
Because it is streamed content, then in any case there are no WORK/PART tags that can be edited, so it cannot be fixed that way.
-
The only possibility, which I find very frequently with composition hierarchies that I have added from Qobuz is to edit the track itself. So here for example I attempt to add the missing PART.
Sometimes I find this will work, and roon will identify and display the composition hierarchy correctly. Sometimes this doesn’t work and I don’t know what the pattern is. It doesn’t matter what you do. No matter what combination of composition edits, delimiters etc. It simply will not work. So I am curious how you got it to work. Maybe it was a local manual edit? That always works.
I’d just like to get this working. But it does open up another can of worms. If the editing features of streamed and local content were the same (for example supporting WORK/PART tags for streamed content), then users (like myself I guess) who are embracing streaming more and more would be much more self sufficient. I cannot see that it is practical to fix the meta data supplier libraries one support request at a time.
This is a Local set I had already added Composition so I used MusiCHI Tagger (Text Processing) to split off the Movement then Told Roon to prefer file.
Obviously with a streamed version you’re stuck with it
Unfortunately yes. For a while I was baffled why roon chose to provide different editing functionality for local and streamed libraries. But then I realised that I got it wrong. Roon is providing the same editing functionality to both local and streamed libraries. That is, in many uses cases, as here, none to both. The only difference of course is that with local content roon is allowing the use of a 3rd party tagger but of course that work around doesn’t work with streamed content.
1 Like
No need to wait that long 
. This is actually now fixed in our database, though it could take up to a week to get pulled into your library via the normal metadata update process.
Thanks Joel. Appreciated. I’ve got a few other annoying ones but I can’t remember. I’ll post when they come up again.
Everything working. Just checked. Much appreciated.
2 Likes
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.