Using this album as an example:
Here we have an album located in Qobuz grand selection:
I previously added this album to “my albums”, here:
Why is there no feedback shown for this album in Qobuz Grand selection, to confirm the album has already been added to “My Albums” and hearted? + symbol is still showing.
Can anyone please test this and confirm capability. Thanks
I presume because it hasn’t been released yet. Release date is the 20th.
Tidal have basic info but qobuz still to arrive I would imagine.
Nice assumption @ged_hickman1 but no bikkies today. Just noticed @grizaudio has put up more examples. This has occurred so many times in the last few weeks/months. Another example is latest Belle & Sebastian. Released on 13th. I added on 14th. Still showing under Qobuz discovery as not added.
Just another issue to add on top of huge gaps in playback/loading songs/gapless etc etc. perhaps it’s just Roon and Qobuz not just using the same means of communication at the moment.
Only time will tell because there was absolutely no improvement after latest update and I gave up earlier today. Shut everything down, played some vinyl, played some music without any gaps on Audirvāna and then thought I’ll give it another whirl.
And already out to 5 seconds between tracks after 30 mins.
I think you have taken a single instance and expanded it to the world. Nice try but your gripes are showing.
Qobuz Press awards:
My Albums:
Is this just me? or is this occurring for others?
I have logged out and into services via Roon settings, doesn’t help.
Core has been rebooted.
Well that is entirely possible to come to your conclusion of my response and I’m happy to accept your reading of same.
I’m also happy to just point out that this is just another in a long line of current issues in the wild. And I’ll leave it at that. Cheers.
I would assume some level of feedback would be appropriate and expected.
If an album has already be added from Qobuz/grand selection etc the option to add should be removed logically.
It would be great if a few members could test this and reported here.
It’s always been like that if you look via the Qobuz section. Roon gave some reasons for it somewhere but I can’t be bothered to find it. But I think that section is purely looking at Qobuz via the api and not Roons version of their database and it doesn’t have a clue what you have in Roon, going any other means is all via Roons version of Qobuz database which holds all the metadata of it being in your library etc.
It’s the same for Tidal it’s just how it’s been designed or a limitation of the API in this scenario. It’s disconnecting but it’s always been like this.
