These represent two distinctly-formatted Qobuz album objects from two separate distributor releases - one at 44.1kHz/24-bit (left), and the other at 44.1kHz/16-bit (right).
Did exactly that and decided to open the issue because Roon was kind stuck spinning trying to add the second album it was just spinning for a long time. After it stopped, the second album was not added. Will retry just for yucks
[EDIT: retried - adding second album resulted again in Roon just spinning - has been for the last 1/2 hour or more without adding the album. You say it’s a duplicate release in qobuz, I don’t see that in the qobuz site - maybe Roon is no interpreting what it’s getting back from the API properly? ]
Err - how can I (or anyone ) be confused about that? THAT IS EXACTLY THE ISSUE.
Roon’s discography is showing two albums. QOBUZ ONLY SHOWS ONE - from what I could find. Adding one album works, adding the second one fails, causing Roon to spin indefinitely (as of this post’s time). That is probably because the second entry is probably a phantom release, as AGAIN, I cannot find it in qobuz.
Not sure who is at fault here, maybe both Roon and Qobuz, but well, two wrongs don’t make a right - if Roon can fix it on its side, it should.
There really is only one version displayed in the Qobuz app, the 24-bit one. Roon shows two from Qobuz, the 24-bit and the 16-bit one.
Nothing is lost and something gained. Clearly, Qobuz provides both to Roon. The fact that Qobuz doesn’t display the 16-bit can just a as much be a Qobuz issue. Or maybe they shouldn’t be offering the 16-bit to Roon.
If I click on Adam Fischer, I get both resolutions. So, it’s considered two different albums, not two versions of the same album. This is not uncommon.
Same for me. That’s not an exactly rare equivalence error, as you noted, I have a few like these in the library, where two albums appear separately although they are clearly versions of one album. (And that’s not the duplication issue, where the same album entity is displayed twice, but two distinct entities. The cases I have can curiously not be grouped either, although both are in the library)
Still, the 16-bit version doesn’t appear in Qobuz at all
Well, it has the same cover and is apparently the same recording in different resolutions - only the 24-bit has a recording date, but they both have the same release date. I’d say this makes it versions.
Anyway, I just added them both to the library, and this made them auto-group in My Albums
I wasn’t the one complaining, and it is not the end of the world, but there’s clearly something not right. I removed them from the library, and the Qobuz 16bit fell out of the group again. The Tidal 16 and 24 bit versions and the Qobuz 24 bit are in one group, just the Qobuz 16 bit isn’t.
That’s what tripped me out, that the album is listed only once in qobuz, hence my decision to report. Also the fact that Roon never stopped spinning after adding the second album. Upon checking, even though it looks like it was never added due to the eternal spinning, I see the grouping.
And what do you know? they both play.
Thinking the release is in a weird state in qobuz that does not get exposed in the main site, but it does in the API or with how Roon uses it.
Thanks for your patience. We’re investigating how Roon is handling this particular object and will respond shortly.
The spinning condition occurs when you attempt to add a streaming album to your library that already exists in the library - it’s a consequence of deep architectural distinctions between streaming and library objects in Roon. The fact that you’re encountering this symptom means Roon is, at some level, treating these separate Qobuz albums as one version.
Appreciate the response and thanks for looking into it - it ca be jarring to see two entries appear for seemingly exactly the same recording - we are not talking different masters/releases/etc - so, there is a sense that something is not right. I reported it because while this is not really a big deal for one recording,if it is or can become widespread, it will be annoying
It looks like Qobuz may have started de-duplicating albums in their app, which could explain why both versions aren’t appearing there. This isn’t something we’ve noticed specifically in the past.
In Roon, these two Qobuz releases are recognized as separate albums—likely due to a duplicate entry in TiVo’s database. One version has more complete metadata than the other, but this is based on the information provided by our metadata sources. Unfortunately, this isn’t something Roon can change directly at this time.
If you see other examples of this, always feel free to share it our way and we can get in touch with TiVo directly. Thanks again!